| View previous topic :: View next topic |
| Author |
Message |
gasparov
Tux's lil' helper
Joined: 13 Apr 2006
Posts: 105
|
 Posted: Sun Aug 03, 2014 3:30 pm Post subject: [Solved]All fstab partitions get fsck every single boot |
 |
|
Hi,
I have this problem with systemd. All partitions of fstab are checked every single boot, furthermore the screen gets black and I have to wait without knowing what is going on; I can only see the hdd led on. This is not a big problem for system partitions but it is for bigger partitions. Here's an example
| Code: | cat /etc/fstab|grep home
LABEL=SSDHome /home ext4 noatime,discard,user_xattr 0 2
|
Here is tune2fs -l before rebooting
| Code: | tune2fs 1.42.10 (18-May-2014)
Filesystem volume name: SSDHome
Last mounted on: /home
Filesystem UUID: 24bb40ce-3747-4b82-8e4d-484072b11f49
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: 1901952
Block count: 7661654
Reserved block count: 383082
Free blocks: 6220408
Free inodes: 1786136
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 561
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8128
Inode blocks per group: 508
RAID stride: 32612
Flex block group size: 16
Filesystem created: Fri Jul 6 20:44:57 2012
Last mount time: Sun Aug 3 14:51:16 2014
Last write time: Sun Aug 3 14:51:16 2014
Mount count: 1
Maximum mount count: 34
Last checked: Sun Aug 3 14:51:15 2014
Check interval: 15552000 (6 months)
Next check after: Fri Jan 30 13:51:15 2015
Lifetime writes: 1324 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: 910963
Default directory hash: half_md4
Directory Hash Seed: 3b18be77-3f24-4c86-9afe-6eeaa9f48921
Journal backup: inode blocks
|
Here is after
| Code: | tune2fs 1.42.10 (18-May-2014)
Filesystem volume name: SSDHome
Last mounted on: /home
Filesystem UUID: 24bb40ce-3747-4b82-8e4d-484072b11f49
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: 1901952
Block count: 7661654
Reserved block count: 383082
Free blocks: 6219153
Free inodes: 1786004
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 561
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8128
Inode blocks per group: 508
RAID stride: 32612
Flex block group size: 16
Filesystem created: Fri Jul 6 20:44:57 2012
Last mount time: Sun Aug 3 15:21:20 2014
Last write time: Sun Aug 3 15:21:20 2014
Mount count: 1
Maximum mount count: 34
Last checked: Sun Aug 3 15:21:19 2014
Check interval: 15552000 (6 months)
Next check after: Fri Jan 30 14:21:19 2015
Lifetime writes: 1324 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: 390945
Default directory hash: half_md4
Directory Hash Seed: 3b18be77-3f24-4c86-9afe-6eeaa9f48921
Journal backup: inode blocks
|
Anybody understand this behaviour?
Last edited by gasparov on Sun Aug 03, 2014 6:12 pm; edited 1 time in total |
|
| Back to top |
|
 |
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Sun Aug 03, 2014 3:47 pm Post subject: |
|
|
Hi,
are you sure the partitions are fsck every boot? Do you see a message telling it?
The black screen can come from missing firmwares who are not in the kernel image and the initramfs. The kernel video driver have to wait until the root partition is accessible to load the requiered firmwares to be able to manage the video card for a screen display.
_________________
Paul |
|
| Back to top |
|
|
gasparov
Tux's lil' helper
Joined: 13 Apr 2006
Posts: 105
|
| Posted: Sun Aug 03, 2014 5:48 pm Post subject: |
|
|
Hi, thanks
I'm not 100% sure but changing fstab to stop fsck from
| Code: | | LABEL=Storage /media/Storage ext4 defaults,user_xattr 0 3 |
to (no fsck)
| Code: | | LABEL=Storage /media/Storage ext4 defaults,user_xattr 0 0 |
makes everything faster (aka from 7 minutes to 25 seconds for booting).
I can see the screen during booting, it gets black after a while, just before lightdm starts. When the system does the fsck it's completely black and it comes back when the hdd led stops.During shut down, all black. |
|
| Back to top |
|
|
gasparov
Tux's lil' helper
Joined: 13 Apr 2006
Posts: 105
|
| Posted: Sun Aug 03, 2014 6:12 pm Post subject: |
|
|
Everything regarding the fsck seems to be automagically fixed, I upgraded the kernel to the last stable release, I was running 3.10.
Also I figured out that i had a problem with ntp and I had this message in the logs:Superblock last write time is in the future.
One of these two fixed the problem (I think the latter).Anyway thanks Logicien. |
|
| Back to top |
|
|
|
Other Things Gentoo
