Arch Linux

emacsomancer

Member

Registered: 2014-09-20

Posts: 211

3.18.5-1 kernel won't mount /home - fails to start

The previous kernel 3.18.4-1 and the current LTS kernel 3.14.30-1 both boot fine, but the just-updated 3.18.5-1 kernel complains about not being about to mount my /home directory and thus fails to start.

Here are messages from the journal which seem revelant:

Linux version 3.18.5-1-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jan 30 07:31:50 CET 2015
....
irq 19: nobody cared (try booting with the "irqpoll" option)
.....
handlers:
[<ffffffffa0042a50>] usb_hcd_irq [usbcore]
[<ffffffffa0042a50>] usb_hcd_irq [usbcore]
Disabling IRQ #19
......
sd 1:0:0:0: [sda] No Caching mode page found
sd 1:0:0:0: [sda] Assuming drive cache: write through
......
Failed to create mount unit file /run/systemd/generator/-.mount, as it already exists. Duplicate entry in /etc/fstab?
Failed to create mount unit file /run/systemd/generator/home.mount, as it already exists. Duplicate entry in /etc/fstab?
......
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 PST 2015
.......
Job dev-sda4.device/start timed out.
Timed out waiting for device dev-sda4.device.
Dependency failed for /home.
Dependency failed for Local File Systems.
Job local-fs.target/start failed with result 'dependency'.
Job home.mount/start failed with result 'dependency'.
Dependency failed for File System Check on /dev/sda4.
Job systemd-fsck@dev-sda4.service/start failed with result 'dependency'.
Job dev-sda4.device/start failed with result 'timeout'.
Failed at step EXEC spawning /bin/plymouth: No such file or directory
root : TTY=tty1 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/reboot

The "Failed to create mount unit" messages have been there for the past few kernels (at one update, systemd or some module seemed to have edited my /etc/fstab and commented out my / and /home mounts, and then failed to boot because it couldn't find the mounts; I uncommented my original UUID-mounting / and /home in /etc/fstab and since then I've got the "failed to create mount unit" message at boot).

The "irq 19" message is new.

Right now I'm running fine on the LTS kernel (perhaps it's better just to stick to LTS kernels anyway?), but I would like to know what to do to fix boot with the 3.18.5-1 kernel (perhaps by getting someone to care about irq 19?).

soldier1184

Member

From: California

Registered: 2015-01-27

Posts: 11

Re: 3.18.5-1 kernel won't mount /home - fails to start

look in your fstab folder for any current discrepancies an find the duplicate if applicable if not applicable re run mount an --force or -f option to force mount if that doesn't help then reinstall root ( ie start arch live boot mount root drive ( assuming home is 2nd HDD instead of relating to 1st ) an reinstall the linux OS an move on from there or search google