You are not logged in.
Pages: 1
I have a probably very noobish question. I've been using Arch for about 2 years now, and yesterday I've upgraded the system as I always do. But then today when I turned it on, it wouldn't boot with this message:
:: running early hook [udev]
Starting version 240
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-partuuid/657da3f0-5a76-49ef-9c3d-08fa79316e61 ...
ERROR: device 'PARTUUID=657da3f0-5a76-49ef-9c3d-08fa79316e61' on real root mount: /new_root: can't find PARTUUID=657da3f0-5a76-49ef-9c3d-08fa79316e61.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#This shell was unresponsive (actually I think no usb devices were working and so also the keyboard).
Searching around, that seems a quite frequent error for first time users installing their system, but not much so after a successfully completed upgrade. After checking that my disks were ok, and that no uuid changed in the process (yes, I know it's foolish, but I thought it could somehow change), I eventually found a suggestion to boot a live cd, chroot into my install, upgrade the system (which only upgraded a few user packages and I don't think had anything to do with the fix) and run 'mkinitcpio -p linux'. It actually worked, and my system is back online, but I'm seeking some information:
What the heck made the root partition "hidden" to the systemd bootloader? Can a somehow corrupted ramdisk do that?
Should I be worried about the disk health?
Thank you in advance for your help.
Offline
Pages: 1