Why is my root filesystem always scanned at boot?
Posted
by
luri
on Ask Ubuntu
See other posts from Ask Ubuntu
or by luri
Published on 2011-02-14T11:35:30Z
Indexed on
2011/02/16
23:35 UTC
Read the original article
Hit count: 324
I always have a pause at boot saying my filesystems are being checked (with a "press C to cancel" note, too). Actually (seeing boot.log
) I think it's the /
fs, which is located at /dev/sdb5
Several questions altoghether, here (hope this does not break any rule):
- Is this normal?
- Can I (or even should I) prevent this anyhow?
- According to boot.log (below) the fs does not seem to be 'clean', or, at least, it's in an state or condition that makes fsck always can it for errors for a while (just a few seconds). How can I fix it?
Edit: This is my boot.log:
fsck desde util-linux-ng 2.17.2
udevd[515]: can not read '/etc/udev/rules.d/z80_user.rules'
/dev/sdb5: 249045/32841728 ficheros (0.3% no contiguos), 20488485/131338752 bloques
init: ureadahead-other main process (1111) terminated with status 4
init: ureadahead-other main process (1116) terminated with status 4
Password: * Starting AppArmor profiles [160G Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
[154G[ OK ]
* Setting sensors limits [160G
[154G[ OK ]
And this is dumpe2fs results for the filesystem being checked (well, the relevant part of the log):
Filesystem volume name: <none>
Last mounted on: /
Filesystem UUID: 42509bf9-f3e6-460a-8947-ec0f5c1fbcc8
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 32841728
Block count: 131338752
Reserved block count: 6566937
Free blocks: 110850356
Free inodes: 32592701
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 992
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Fri Dec 10 19:44:15 2010
Last mount time: Mon Feb 14 17:00:02 2011
Last write time: Mon Feb 14 16:59:45 2011
Mount count: 1
Maximum mount count: 33
Last checked: Mon Feb 14 16:59:45 2011
Check interval: 15552000 (6 months)
Next check after: Sat Aug 13 17:59:45 2011
Lifetime writes: 331 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 28049496
Default directory hash: half_md4
Directory Hash Seed: d3d24459-514b-4413-b840-e970b766095b
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Tamaño de fichero de transacciones: 128M
Journal length: 32768
Journal sequence: 0x0005e0c4
Journal start: 1
This is the relevant (at least I think this is the fs being checked) line in fstab:
#Entry for /dev/sdb5 :
UUID=42509bf9-f3e6-460a-8947-ec0f5c1fbcc8 / ext4 errors=remount-ro 0 1
© Ask Ubuntu or respective owner