No Boot After Bullseye Upgrade - Error: disk lvmid/mz0ckd
2 Attachment(s)
No Boot after updating from 19.4 to 21.3 using the information here:
Upgrading from MX-19 to MX-21 without reinstalling https://mxlinux.org/wiki/system/upgr...-reinstalling/ After the upgrade completed and after reboot it seemed successful but after another reboot I receive error at "disk lvmid/mz0ckd.... and it wont boot. I can boot to my cdrom MX Live (cant seem to boot to USB on this AMD Athlon 64) I can boot to the mx live 21.3 dvd and using the boot tools get to the hardrive install and it runs fine. Ive tried boot repair etc. but nothing seems to help and the only way to get to the hard drive install is through the live DVD. I have this computer dual booting to Mint or MX for several years and has worked without issue until this MX upgrade. Please let me know what additional info is needed. Thanks for any help. Fairway |
Hi, what does the bios tell you about boot drives, seems like it's opting for the Floppy Disk (fd0).
see how you go. |
2 Attachment(s)
Quote:
Its an old PC and it has two old hardrives. Though Ive tinkered with linux for ~10 years Im not that savy with it but I can cut and paste commands and do some elementary things. I can get the 21.3 install running if I boot to the MX Live menu then toggle through the boot loader select options and eventually get to a grub menu and there I can select MX Linux or Mint and both run fine. The other thing with the 21.3 is it runs fine except there is no Network Manager and I have to run sudo /sbin/NetworkManager to get connection. |
Hi, it's been a while since I saw that Pheonix BIOS screen. :-)
Can you pick a different drive in boot-1? Next time you boot into your OS you might try to reinstall grub (the boot loader). Once you are in the booted desktop open a terminal screen with root permissions. s"u" or "su -" or even "sudo" if you have it setup. open /etc/default/grub as root with a text file editor, like nano (in the teminal) Code:
nano /etc/default/grub this is why it broke... this used to be automatic, but for privacy concerns you have to do it yourself! Code:
# discover other os's Now we can re-run update-grub Code:
update-grub I'm hoping this may help you get the windows boot back on your other machine as well. See how you go. |
I have reinstalled grub 5 ways from sundown to no avail.
when i run Code:
nano /etc/default/grub I did reinstall from live without issue but the boot issue is still there. |
...then add the line and save it.
before you run update-grub, make sure os-prober package is installed. |
2 Attachment(s)
Quote:
I can boot to the mx live disk, go to Switch to Grub Bootloader, Boot Recue Options, Grub Bootloader where it finds (hd0.1) root mx19 and (hdo.5) no label. At this point I can select (hd0.1) root mx19 and it comes to a MX Libretto option and I can select that and successfully boot into MX or - I can select (hd0.5) no label and it comes to Linux Mint and I can select that and successfully boot into Mint Thanks for your help. (Maybe its time I retire this old AMD Athlon 64 machine!) |
Ah, I see there was already a rule there for os prober, there is a duplicate GRUB_DISABLE_OS_PROBER.
Comment (#) the last line Code:
# discover other os's |
2 Attachment(s)
Quote:
I did notice possibly a typo in the "nano /etc/default/grub" see red below (fi instead of if?) is that an error? #run dpkg-reconfigure grub-pc to allow toggle of os-prober GRUB_DISABLE_OS_PROBER=false GRUB_DISABLE_OS_PROBER=false if [ -e /etc/default/grub.mx-defaults ]; then . /etc/default/grub.mx-defaults fi GRUB_DISABLE_OS_PROBER=false GRUB_THEME="/boot/grub/themes/mx_linux/theme.txt" # discover other os's # GRUB_DISABLE_OS_PROBER=true On another note I am able to boot to the live disk, scroll and select boot from hard disk and from there can select either MX23 or Mint and both run normal (see photos). Edit: changing the "fi" to "if" doesnt make any difference - (still getting same boot error). |
2 Attachment(s)
Well - I still have the boot error and I think the MX upgrade installed the boot info to the wrong drive/partition. (I have two old drives and I think in looking at this its installed on SDB1 so im going to try reinstaalling Grub on SDB1 for kickes.
I just thought I'd post this Quick Sys Info in case anything jumps out to a passerby perusing my troubles. Enjoy! " Code:
System: Here is what i just ran: MX64@mx:~ $ sudo grub-install --root-directory=/mnt /dev/sdb sh: 46: /etc/default/grub: Syntax error: end of file unexpected (expecting "then") Installing for i386-pc platform. Installation finished. No error reported. MX64@mx:~ $ Rebooting now! Edit: Well the only thing that changed is that it doesnt boot to Grub Rescue anymore it boots to Grub but im limited with skills at that point (see photo). Edit: Edit: ran the MX Boot Repair heres the result Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/50_linuxmint.cfg' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.2.0-33-generic Found initrd image: /boot/initrd.img-6.2.0-33-generic Found linux image: /boot/vmlinuz-6.2.0-32-generic Found initrd image: /boot/initrd.img-6.2.0-32-generic Found linux image: /boot/vmlinuz-5.19.0-41-generic Found initrd image: /boot/initrd.img-5.19.0-41-generic Found linux image: /boot/vmlinuz-6.2.0-33-generic Found initrd image: /boot/initrd.img-6.2.0-33-generic Found linux image: /boot/vmlinuz-6.2.0-32-generic Found initrd image: /boot/initrd.img-6.2.0-32-generic Found linux image: /boot/vmlinuz-5.19.0-41-generic Found initrd image: /boot/initrd.img-5.19.0-41-generic grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map. Found MX 23 Libretto (23) on /dev/sda1 done Rebooting again!! EDIT EDIT EDIT:( Same - boots to grub Here is another photo showing the partition info. |
All times are GMT -5. The time now is 03:19 AM. |