View previous topic :: View next topic |
Author |
Message |
Xanadu Guru
Joined: 10 Oct 2002 Posts: 335 Location: Hour West of Philly (USA)
|
Posted: Fri May 15, 2015 2:14 pm Post subject: Partition Won't Automount |
|
|
Hey!
Can someone please tell me why /usr/local won't mount at boot? I pretty much only reboot my machine when stable gentoo-sources is updated, so I can't really say when this started happening...
Active fstab:
Code: |
# egrep -v '^$|^\#' /etc/fstab
/dev/sda1 / ext4 rw,defaults,noatime,discard 1 1
/dev/sdb5 none swap sw 0 0
/dev/sdb6 /usr/local ext4 rw,defaults,noatime 1 1
proc /proc proc defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
|
Relevant portion of dmesg:
Code: |
# dmesg | grep -i sd[ab]
[ 0.000000] Kernel command line: BOOT_IMAGE=Linux-3.18.12 root=801 quiet oops=panic panic=14 fastboot resume=swap:/dev/sda8 net.ifnames=0 splash=silent,nofadein,theme:default console=tty1 video=simplefb 3
[ 0.803312] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
[ 0.803369] sd 2:0:0:0: [sda] Write Protect is off
[ 0.803371] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.803390] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.803796] sda: sda1
[ 0.804034] sd 2:0:0:0: [sda] Attached SCSI disk
[ 0.804505] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 0.814509] sd 3:0:0:0: [sdb] Write Protect is off
[ 0.814514] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 0.814551] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.876078] sdb: sdb1 < sdb5 sdb6 >
[ 0.876431] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 0.877898] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[ 0.878113] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
[ 0.880100] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 0.880102] EXT4-fs (sda1): write access will be enabled during recovery
[ 1.191339] EXT4-fs (sda1): recovery complete
[ 1.219466] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 8.394815] Adding 3156704k swap on /dev/sdb5. Priority:-1 extents:1 across:3156704k FS
[ 8.616547] EXT4-fs (sda1): re-mounted. Opts: discard
|
Code: |
# find /etc/runlevels -iname '*localmount*'
/etc/runlevels/boot/localmount
|
No errors. Nothing. init simply doesn't bring it up at boot. It manually mounts just fine without needing fsck.
As you see in dmesg, the physical drive it self is seen and initialized at boot just fine because the kernel mounts my swap on it. Is there something I'm just totally missing???
I hacked in a workaround in local.start for now
Code: | [ ! "$(mount | grep /usr/local)" ] && mount /usr/local |
which works, but I would REALLY likke to know why /usr/local won't mount normally.
Thank you!
M. _________________ I'm not a prophet or a stone-age man
I'm just a mortal with potential of a super man
-David Bowie |
|
Back to top |
|
|
russK l33t
Joined: 27 Jun 2006 Posts: 665
|
Posted: Fri May 15, 2015 2:37 pm Post subject: |
|
|
I noticed it is doing a recovery on your sda1 which is your root filesystem. I wonder if the automount is wanting to occur during that recovery and so it fails. Is your box shutting down cleanly?
Quote: | [ 0.880100] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 0.880102] EXT4-fs (sda1): write access will be enabled during recovery
[ 1.191339] EXT4-fs (sda1): recovery complete
|
|
|
Back to top |
|
|
Xanadu Guru
Joined: 10 Oct 2002 Posts: 335 Location: Hour West of Philly (USA)
|
Posted: Fri May 15, 2015 2:54 pm Post subject: |
|
|
russK wrote: | I noticed it is doing a recovery on your sda1 which is your root filesystem. I wonder if the automount is wanting to occur during that recovery and so it fails. Is your box shutting down cleanly?
Quote: | [ 0.880100] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 0.880102] EXT4-fs (sda1): write access will be enabled during recovery
[ 1.191339] EXT4-fs (sda1): recovery complete
|
|
/me slaps his forehead
Thank you for pointing that out...
There's been a few times I have to properly SysRq* my way to a reboot because of Fail2Ban locking up the shutdown process (this newer versions just... suck... I never had the older versions do this...).
I guess I can't sit here right this moment and say whether the dmesg snippet I posted was a SysRq reboot or not as I rebooted it a couple times last night for the kernel update and I have an nVidia card (Yes, I'm aware I can just modprobe, I like to reboot it to know 100% for sure the module will load) and I forget which dmesg I saved. I'll bounce it again when I get home.
Judging on what you've pointed out to me, that may have been a SysRq reboot (again, because of Fail2Ban... 0.9.* just sucks.... 0.8.* never did this).
M.
* Reboot Even If System Utterly Broken - I could never memorize Linus' thing about raising elephants... _________________ I'm not a prophet or a stone-age man
I'm just a mortal with potential of a super man
-David Bowie |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|