[byers@f14 ~]$ uname -r 2.6.35.13-92.fc14.i686.PAE
[Background: Re: backup copy of F14 boots, but can't login. endless recycle of login screen: fixed by 'touch /.autorelabel, reboot'. Still was unable to make id:3:initdefault: take effect. Ctrl-Alt-F2 does get me to text login screen. Also can get to runlevel 3 by appending '3' to kernel line]
Since then, I noticed I was getting a newly updated /.autofsck every time I rebooted.
Thinking this was indicating I needed to run fsck, I did touch /forcefcsk, rebooted, and the system did the fsck, no errors, needed no response from me.
Still getting a newly updated /.autofsck on every reboot. Still no effect id:3:initdefault in inittab.
Any advice re /.autofsck? Does its continual reappearance indicate a problem?
thanks Jack
On 3 July 2011 22:29, jackson byers byersjab@gmail.com wrote:
Any advice re /.autofsck? Does its continual reappearance indicate a problem?
http://www.redhat.com/archives/rhl-list/2004-November/msg02920.html
###########################################################
The /.autofsck file is created by the system automatically at boot time by the /etc/rc.sysinit script by simply touching the file. It has no content. The logic behind it is, that if the host went down not properly (i.e. power loss) the /etc/rc.sysinit script will find this .autofsck file at next boot time and the system can act with a default scenario or like configured within the file /etc/sysconfig/autofsck. If the hosts shuts down or reboots properly, then the .autofsck file will be erased by the /etc/init.d/halt script and no automatic filesystem check will happen next boot. I think this answers the 3 questions by Ralf. The file is generated by /etc/rc.sysinit, used by the system to know about no proper shutdowns and you should leave the file as it is. There is not any need to delete it. Btw. the /.autofsck file mechanism is used in all Fedora releases since FC1.
############################################################
-
Jackson Byers -
Sam Sharpe