You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2008-02-05 21:41:18
- Faybarn
- Member
- Registered: 2008-02-05
- Posts: 3
Filesystem check every boot [Solved]
Every time i boot my computer arch performs a filesystem check, this then fails and arch has to reboot. After the reboot arch works fine, but this is causing my boot to take twice as long as it should. Any ideas on how to solve this?
I have installed arch to a 4gb HCSD card and are running it on the asus eee pc.
Last edited by Faybarn (2008-02-06 14:26:44)
Currently running Arch on an Asus Eee 701.
Offline
#2 2008-02-05 23:22:46
- colnago
- Member
- From: Victoria, BC
- Registered: 2004-03-25
- Posts: 438
Re: Filesystem check every boot [Solved]
Maybe post your fstab line.
Offline
#3 2008-02-05 23:37:16
- Thrillhouse
- Member
- From: Arlington, VA, USA
- Registered: 2007-05-29
- Posts: 175
Re: Filesystem check every boot [Solved]
Check the last number in the line in your entry for / in /etc/fstab. If it is 1, change it to 0.
A good reference for fstab:
http://www.tuxfiles.org/linuxhelp/fstab.html
For the strength of the pack is the wolf, and the strength of the wolf is the pack.
Offline
#4 2008-02-06 08:58:54
- Faybarn
- Member
- Registered: 2008-02-05
- Posts: 3
Re: Filesystem check every boot [Solved]
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
none /tmp tmpfs defaults 0 0
none /var/log tmpfs defaults 0 0
/dev/sdb1 / ext2 defaults,noatime 0 1
Currently running Arch on an Asus Eee 701.
Offline
#5 2008-02-06 14:24:56
- Faybarn
- Member
- Registered: 2008-02-05
- Posts: 3
Re: Filesystem check every boot [Solved]
Changing the 1 to a 0 has solved my problem for now, Thanks guys.
Currently running Arch on an Asus Eee 701.
Offline
#6 2008-02-06 23:56:40
- codemac
- Member
- From: Cliche Tech Place
- Registered: 2005-05-13
- Posts: 794
- Website
Re: Filesystem check every boot [Solved]
I actually had a very similar problem, but it was due to udev rules. I was automounting a drive as umask=000 before the rc got to checking the filesystems, thus failing because the filesystem was all ready mounted. By editing and correcting some udev rules I had written, it was no longer arbitrarily mounted, and this did not fail the filesystem check.
Just leaving that little tidbit here for public documentation. Remember that changing the 1 to a 0 only means you aren't fixing your problem, just avoiding it. Try running fsck on your own on the drive, see what it's actually complaining about.
edited for spelling
Last edited by codemac (2008-02-06 23:57:06)
Offline
Pages: 1