I have a home server which is just spare computer parts running SnapRAID and mergerfs. I did a sudo apt-get dist-upgrade from 4.9.0.9-amd64 to 4.19.0.5-amd64 and now it won't boot properly. It just spits out the following a bunch of times:
Code: Select all
Multiple VGs found with the same name: skipping dmaphesto-vg
Use --select vg_uuid=<uuid> in place of the VG name.
Multiple VGs found with the same name: skipping dmaphesto-vg
Use --select vg_uuid=<uuid> in place of the VG name.
mdadm: No arrays found in config file or automatically
Multiple VGs found with the same name: skipping dmaphesto-vg
Use --select vg_uuid=<uuid> in place of the VG name.
mdadm: No arrays found in config file or automatically
...
Code: Select all
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/dmaphesto--vg-root does not exist. Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs) _
Code: Select all
BOOT_IMAGE=/vmlinuz-4.19.0.5-amd64 root=/dev/mapper/dmaphesto--vg-root ro quiet
Code: Select all
setparams 'Debian GNU/Linux, with Linux 4.19.0-5-amd64'
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then
search --no-floppy --fs-uuid --set=root e075c0a4-d8b3-447f-8b7c-f09492596297
else
search --no-floppy --fs-uuid --set=root e075c0a4-d8b3-447f-8b7c-f09492596297
fi
echo 'Loading Linux 4.19.0-5-amd64'
linux /vmlinuz-4.19.0.5-amd64 root=/dev/mapper/dmaphesto--vg-root ro quiet
echo 'Loading initial ramdisk'
initrd /initrd.img-4.19.0-5-amd64'
Code: Select all
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Multiple VGs found with the same name: skipping dmaphesto-vg
Use -- select vd_uuid=<uuid> in place of the VG name.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Multiple VGs found with the same name: skipping dmaphesto-vg
Use -- select vd_uuid=<uuid> in place of the VG name.
/dev/mapper/dmaphesto--vg-root: clean
I’ve tried googling and watching youtube videos for similar issues but no luck. Did grub-mkconfig and compared it to /boot/grub/grub.cfg as suggested in this post http://forums.debian.net/viewtopic.php?f=17&t=137923 but there’s no difference between the two like there was in that post. Still did a grub-update and fsck -fy on my disks but to no avail.
I'm fairly green when it comes to Linux so I don't really know how to continue. Any clue on how to solve this?
Thanks!