LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > antiX / MX Linux
User Name
Password
antiX / MX Linux This forum is for the discussion of antiX and MX Linux.

Notices


Reply
  Search this Thread
Old 10-11-2023, 12:29 PM   #1
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Rep: Reputation: Disabled
No Boot After Bullseye Upgrade - Error: disk lvmid/mz0ckd


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
Attached Thumbnails
Click image for larger version

Name:	error.jpg
Views:	13
Size:	258.6 KB
ID:	41828  
Attached Files
File Type: txt inxi.txt (6.1 KB, 21 views)

Last edited by Fairway; 10-11-2023 at 12:48 PM.
 
Old 10-11-2023, 04:57 PM   #2
GlennsPref
Senior Member
 
Registered: Apr 2004
Location: Brisbane, Australia
Distribution: Devuan
Posts: 3,657
Blog Entries: 33

Rep: Reputation: 283Reputation: 283Reputation: 283
Hi, what does the bios tell you about boot drives, seems like it's opting for the Floppy Disk (fd0).

see how you go.
 
Old 10-11-2023, 06:51 PM   #3
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by GlennsPref View Post
Hi, what does the bios tell you about boot drives, seems like it's opting for the Floppy Disk (fd0).
see how you go.
Here is a couple of photos of the BIOS settings. Could upgrading from 19.4 to 21.3 have an effect on BIOS?
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.
Attached Thumbnails
Click image for larger version

Name:	boot settings.jpg
Views:	10
Size:	262.4 KB
ID:	41830   Click image for larger version

Name:	boot priority.jpg
Views:	9
Size:	255.2 KB
ID:	41831  
 
Old 10-12-2023, 05:43 PM   #4
GlennsPref
Senior Member
 
Registered: Apr 2004
Location: Brisbane, Australia
Distribution: Devuan
Posts: 3,657
Blog Entries: 33

Rep: Reputation: 283Reputation: 283Reputation: 283
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
change this line from true to false,
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
GRUB_DISABLE_OS_PROBER=false
save the changes in file and quit the editor. (CTRL+o, ctrl+x)

Now we can re-run update-grub
Code:
update-grub
if asked, select your first hdd, root partition.

I'm hoping this may help you get the windows boot back on your other machine as well.

See how you go.

Last edited by GlennsPref; 10-12-2023 at 05:53 PM. Reason: osprober is at default set to off.
 
Old 10-12-2023, 08:49 PM   #5
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Original Poster
Rep: Reputation: Disabled
I have reinstalled grub 5 ways from sundown to no avail.
when i run
Code:
nano /etc/default/grub
I dont see what your referring to as there is no true or false line to change.
I did reinstall from live without issue but the boot issue is still there.

Last edited by Fairway; 10-12-2023 at 08:50 PM.
 
Old 10-12-2023, 09:26 PM   #6
GlennsPref
Senior Member
 
Registered: Apr 2004
Location: Brisbane, Australia
Distribution: Devuan
Posts: 3,657
Blog Entries: 33

Rep: Reputation: 283Reputation: 283Reputation: 283
...then add the line and save it.

before you run update-grub, make sure os-prober package is installed.
 
Old 10-13-2023, 08:59 AM   #7
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by GlennsPref View Post
...then add the line and save it.
before you run update-grub, make sure os-prober package is installed.
Ok - I (think) I ran "nano /etc/default/grub" and added the line. I dont know how to upload that data so i attached a photo of it and uploaded the terminal commands you suggested. Unfortunately it is still booting to "grub rescue".
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!)
Attached Thumbnails
Click image for larger version

Name:	terminal pic.jpg
Views:	9
Size:	260.9 KB
ID:	41838  
Attached Files
File Type: txt update grub.txt (695 Bytes, 7 views)
 
Old 10-13-2023, 07:51 PM   #8
GlennsPref
Senior Member
 
Registered: Apr 2004
Location: Brisbane, Australia
Distribution: Devuan
Posts: 3,657
Blog Entries: 33

Rep: Reputation: 283Reputation: 283Reputation: 283
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
GRUB_DISABLE_OS_PROBER=true
 
Old 10-14-2023, 06:27 AM   #9
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by GlennsPref View Post
Ah, I see there was already a rule there for os prober, there is a duplicate GRUB_DISABLE_OS_PROBER.
Comment (#) the last line statement.
Code:
# discover other os's
GRUB_DISABLE_OS_PROBER=true
No success by commenting (#) the last didnt help as still get the same error at boot.

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).
Attached Thumbnails
Click image for larger version

Name:	live boot select boot from hard disk.jpg
Views:	10
Size:	256.3 KB
ID:	41849   Click image for larger version

Name:	live boot select mx 23 or mint.jpg
Views:	4
Size:	256.1 KB
ID:	41850  

Last edited by Fairway; 10-14-2023 at 06:38 AM. Reason: clarification
 
Old 10-15-2023, 02:42 PM   #10
Fairway
Member
 
Registered: Nov 2019
Posts: 59

Original Poster
Rep: Reputation: Disabled
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:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=823296
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: M2N-SLI DELUXE v: 1.XX serial: <superuser required>
    BIOS: Phoenix v: ASUS M2N-SLI DELUXE Revision 1804 date: 09/16/2010
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech K520 serial: <filter> charge: 70% (should be ignored)
    rechargeable: yes status: discharging
CPU:
  Info: model: AMD Athlon 64 X2 6000+ bits: 64 type: MCP arch: K8 level: v1 built: 2004-06
    process: AMD 90nm family: 0xF (15) model-id: 0x43 (67) stepping: 3 microcode: N/A
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 256 KiB desc: d-2x64 KiB; i-2x64 KiB
    L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 3014 min/max: N/A cores: 1: 3014 2: 3014 bogomips: 12055
  Flags: ht lm nx pae sse sse2 sse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA G73 [GeForce 7600 GT] vendor: BFG Tech driver: nouveau v: kernel non-free:
    series: 304.xx status: legacy (EOL) last: release: 304.137 kernel: 4.13 xorg: 1.19 arch: Curie
    process: 90-130nm built: 2003-13 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-2
    empty: DVI-I-1,TV-1 bus-ID: 04:00.0 chip-ID: 10de:0391 class-ID: 0300 temp: 55.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nouveau
    unloaded: fbdev,modesetting,vesa alternate: nv dri: nouveau gpu: nouveau display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: DVI-I-2 model: Samsung S23C570 serial: <filter> built: 2013 res: 1920x1080 hz: 60
    dpi: 96 gamma: 1.2 size: 510x287mm (20.08x11.3") diag: 585mm (23") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 2.1 Mesa 22.3.6 renderer: NV4B direct-render: Yes
Audio:
  Device-1: NVIDIA MCP55 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:06.1 chip-ID: 10de:0371 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: NVIDIA MCP55 Ethernet vendor: ASUSTeK type: network bridge driver: forcedeth v: kernel
    port: ec00 bus-ID: 00:08.0 chip-ID: 10de:0373 class-ID: 0680
  IF: eth0 state: down mac: <filter>
  Device-2: NVIDIA MCP55 Ethernet vendor: ASUSTeK type: network bridge driver: forcedeth
    v: kernel port: eb00 bus-ID: 00:09.0 chip-ID: 10de:0373 class-ID: 0680
  IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-3: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee v: kernel
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: dc00 bus-ID: 02:00.0 chip-ID: 10ec:818b
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 778.42 GiB used: 22.38 GiB (2.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500630AS size: 465.76 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: M scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD3200AAJS-56B4A0 size: 298.09 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 3A01
    scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Lexar model: USB Flash Drive size: 14.57 GiB
    block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 229.36 GiB size: 224.7 GiB (97.97%) used: 22.38 GiB (10.0%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
    maj-min: 8:2
  ID-2: swap-2 type: file size: 10.75 GiB used: 0 KiB (0.0%) priority: -3 file: /swap/swap
Sensors:
  System Temperatures: cpu: 49.0 C mobo: 38.0 C gpu: nouveau temp: 55.0 C
  Fan Speeds (RPM): cpu: 1762 psu: 0 case-1: 0 case-2: 0 case-3: 0 case-4: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.40 vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2218 libs: 1140 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
    1: deb https://deb.opera.com/opera-stable/ stable non-free
Info:
  Processes: 233 Uptime: 7h 15m wakeups: 48 Memory: 7.75 GiB used: 2.95 GiB (38.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
"

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.
Attached Thumbnails
Click image for larger version

Name:	new grub error.jpg
Views:	10
Size:	253.4 KB
ID:	41857   Click image for larger version

Name:	drive partition.jpg
Views:	8
Size:	233.0 KB
ID:	41859  

Last edited by Fairway; 10-15-2023 at 06:13 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Upgrade Debian 10 Buster to Debian 11 Bullseye: A Step-by-Step Guide LXer Syndicated Linux News 0 08-24-2021 12:51 PM
LXer: How To Upgrade To Debian 11 Bullseye From Debian 10 Buster LXer Syndicated Linux News 0 08-15-2021 03:27 PM
LXer: How to Upgrade Debian 10 Buster to Debian 11 Bullseye LXer Syndicated Linux News 0 07-26-2021 07:21 AM
"systemd[1]: Failed to mount /run/systemd/cryptsetup/keydev-crypt5" <= boot error after Bullseye (Debian 11) debootstrap installation libCognition Debian 0 05-25-2021 01:48 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > antiX / MX Linux

All times are GMT -5. The time now is 06:10 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration