You are not logged in.

Pages: 1

#1 2018-12-19 21:13:23

goldfish777
Member
Registered: 2012-11-04
Posts: 32

[SOLVED] Missing kernel modules after nivida and linux update

I was performing routine updates and it resulted in an unbootable system.

Here's what happened...

I ran the following command:

sudo pacman -Syu

Here are the logs for that particular update:

[2018-12-19 15:07] [PACKAGEKIT] synchronizing package lists
[2018-12-19 15:07] [PACMAN] Running 'pacman -Syu'
[2018-12-19 15:07] [PACMAN] synchronizing package lists
[2018-12-19 15:07] [PACMAN] starting full system upgrade
[2018-12-19 15:08] [ALPM] transaction started
[2018-12-19 15:08] [ALPM] upgraded amd-ucode (20181026.1cb4e51-1 -> 20181216.211de16-1)
[2018-12-19 15:08] [ALPM] upgraded archlinux-keyring (20181128-1 -> 20181218-1)
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 5357F3B111688D88C1D88119FCF2CB179205AC90...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 5559BC1A32B8F76B3FCCD9555FA5E5544F010D48...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 5A2257D19FF7E1E0E415968CE62F853100F0D0F0...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Updating trust database...
[2018-12-19 15:08] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2019-03-29
[2018-12-19 15:08] [ALPM] upgraded libmagick (7.0.8.16-1 -> 7.0.8.18-1)
[2018-12-19 15:08] [ALPM] upgraded imagemagick (7.0.8.16-1 -> 7.0.8.18-1)
[2018-12-19 15:08] [ALPM] upgraded dbus (1.12.10-2 -> 1.12.12-1)
[2018-12-19 15:08] [ALPM] upgraded cups-filters (1.21.5-2 -> 1.21.6-1)
[2018-12-19 15:08] [ALPM] upgraded gwenhywfar (4.20.0-2 -> 4.20.1-1)
[2018-12-19 15:08] [ALPM] upgraded nvidia-utils (415.23-1 -> 415.25-1)
[2018-12-19 15:08] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2018-12-19 15:08] [ALPM] upgraded polkit (0.115+3+g8638ec5-1 -> 0.115+24+g5230646-1)
[2018-12-19 15:08] [ALPM] upgraded kdevelop (5.3.1-1 -> 5.3.1-2)
[2018-12-19 15:08] [ALPM] upgraded kmail (18.12.0-1 -> 18.12.0-2)
[2018-12-19 15:08] [ALPM] upgraded libgsf (1.14.44-1 -> 1.14.45-1)
[2018-12-19 15:08] [ALPM] upgraded libxnvctrl (415.23-1 -> 415.25-1)
[2018-12-19 15:08] [ALPM] upgraded linux-firmware (20181026.1cb4e51-1 -> 20181216.211de16-1)
[2018-12-19 15:08] [ALPM] upgraded linux (4.19.8.arch1-1 -> 4.19.9.arch1-1)
[2018-12-19 15:08] [ALPM] upgraded nvidia (415.23-1 -> 415.25-1)
[2018-12-19 15:08] [ALPM] upgraded nvidia-settings (415.23-1 -> 415.25-1)
[2018-12-19 15:08] [ALPM] transaction completed
[2018-12-19 15:08] [ALPM] running '60-linux.hook'...
[2018-12-19 15:08] [ALPM] running '90-linux.hook'...
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Starting build: 4.19.9-arch1-1-ARCH
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Starting build: 4.19.9-arch1-1-ARCH
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-19 15:08] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-12-19 15:08] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-19 15:08] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-12-19 15:08] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-12-19 15:08] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-12-19 15:08] [ALPM] running 'systemd-sysusers.hook'...
[2018-12-19 15:08] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-12-19 15:08] [ALPM] running 'systemd-update.hook'...
[2018-12-19 15:08] [ALPM] running 'update-desktop-database.hook'...
[2018-12-19 15:08] [ALPM] running 'update-mime-database.hook'...

After the upgrade, I rebooted and was presented with an error about missing modules which resulted in my system being unable to mount /boot.

I then booted into an arch live USB and chrooted into my arch install. After poking around a bit, I noticed the initramfs (/boot/initramfs-linux.img) that was generated had the modules from 4.19.8-arch1-1-ARCH despite having just installed 4.19.9-arch1-1-ARCH.

I ran the following command:

lsinitcpio /boot/initramfs-linux.img

Here are the relevant bits from the output that caught my attention:

...
usr/lib/modules/4.19.8-arch1-1-ARCH
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.devname
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.builtin.bin
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.symbols.bin
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.softdep
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.alias.bin
usr/lib/modules/4.19.8-arch1-1-ARCH/modules.dep.bin
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/virtio_blk.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/ahci.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/sr_mod.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/mmc_block.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/firewire-sbp2.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/jbd2.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/hid-generic.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/virtio_ring.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/fscrypto.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/usb-storage.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/xhci-hcd.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/sd_mod.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/hid.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/cdrom.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/uas.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/scsi_mod.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/firewire-core.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/libahci.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/xhci-pci.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/crc32c-intel.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/crc-itu-t.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/libata.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/mbcache.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/mmc_core.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/crc32c_generic.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/ext4.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/crc16.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/usbhid.ko
usr/lib/modules/4.19.8-arch1-1-ARCH/kernel/virtio.ko
...

Before fully fixing the problem, I ran the following command:

mkinitcpio -p linux

which resulted in the following output:

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: '/lib/modules/4.19.8-arch1-1-ARCH' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: '/lib/modules/4.19.8-arch1-1-ARCH' is not a valid kernel module directory

At that point I decided to reinstall the linux package.

I ran the following:

pacman -S linux

here are the pacman logs for that:

[2018-12-19 15:35] [PACMAN] Running 'pacman -S linux'
[2018-12-19 15:35] [ALPM] transaction started
[2018-12-19 15:35] [ALPM] reinstalled linux (4.19.9.arch1-1)
[2018-12-19 15:35] [ALPM] transaction completed
[2018-12-19 15:35] [ALPM] running '60-linux.hook'...
[2018-12-19 15:36] [ALPM] running '90-linux.hook'...
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Starting build: 4.19.9-arch1-1-ARCH
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Starting build: 4.19.9-arch1-1-ARCH
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-12-19 15:36] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-12-19 15:36] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-12-19 15:36] [ALPM] running 'systemd-update.hook'...
[2018-12-19 15:37] [PACKAGEKIT] synchronizing package lists
[2018-12-19 15:42] [PACKAGEKIT] synchronizing package lists
[2018-12-19 15:42] [PACKAGEKIT] synchronizing package lists

At that point I rebooted and everything seems to be fine now. I'm not sure what happened. Any insight into this issue would be much appreciated. Thanks!

Last edited by goldfish777 (2018-12-19 21:25:24)

Offline

#2 2018-12-19 21:18:15

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Missing kernel modules after nivida and linux update

Your /boot wasn't mounted for the initial upgrade: it is common enough. What's in your /etc/fstab?

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2018-12-19 21:24:46

goldfish777
Member
Registered: 2012-11-04
Posts: 32

Re: [SOLVED] Missing kernel modules after nivida and linux update

You sir, are a genius! That's exactly it. I recently upgraded my desktop and copied my system over from the old SATA SSD to my new NVME SSD and I apparently forgot to update /etc/fstab. It is referencing my old SSD.

For reference here is my /etc/fstab:

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3
UUID=a5f16703-ebd0-4079-bd9d-5d05e8a2838d       /               ext4            rw,relatime     0 1

# /dev/sda1
UUID=E12E-4DFE          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/sda2
UUID=184f01ba-6260-4b94-8245-3cb2f3fe110c       none            swap            defaults,pri=-2 0 0

I will be sure to update that so this doesn't happen going forward. Thanks!

Offline

#4 2018-12-19 21:36:40

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Missing kernel modules after nivida and linux update

goldfish777 wrote:

You sir, are a genius!

Mostly I am referred to as "the evil triangle thingy"... tongue

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2018-12-19 21:43:53

goldfish777
Member
Registered: 2012-11-04
Posts: 32

Re: [SOLVED] Missing kernel modules after nivida and linux update

I'm a little confused as to how my system was booting properly to begin with. So grub has the correct UUID pointing to my new SSD's root partition but /etc/fstab was pointing to my old drive. My UEFI is configured to boot off of the new drive. I just looked at the root partition on my old drive and it has not been modified since the hardware upgrade. Why was my old /boot being mounted but not my old root?

Offline

#6 2018-12-19 21:56:36

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Missing kernel modules after nivida and linux update

systemd will handle the initial mounting, but then unmount /boot after the machine is up. That's why it is a relatively common issue here.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

Pages: 1

Board footer

Powered by FluxBB