Skip to main content
Topic: updated to unbootable (Read 1145 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

updated to unbootable

My rather old KDE system has been working fine as I updated it from time to time since first installed. The last update of grub made it unbootable. There was a wanring suggesting 2 commands but by then it was too late. I executed one of them without any visible error the other one failed.  Mounted for inspection

# ls /0/sa04/boot
amd-ucode.img  initramfs-linux-fallback.img  intel-ucode.img  vmlinuz-linux
grub           initramfs-linux.img           memtest86+

I installed grub via my designated go-do-grub system (Suse) but boot fails. If I break into the grub shell with "C" and

- set boot=(hd0,4)
- linux /boot/vmlinuz-linux root=/dev/sda4
- initrd /boot/initramfs-linux.img
- boot

the boot process begins but then dies out w. an eventually black screen.  

sda4  /   UUID is 25568ecc-3f4c-410d-8cfb-bb45afc10051
sda3 swap UUID is 02e6d9de-f403-4710-a401-e0c87c2b5f89
sdb1 data  UUID is 95cb7a9a-d7f2-4fb8-bf49-56828acf931c

/etc/fstab
UUID=25568ecc-3f4c-410d-8cfb-bb45afc10051   /      ext4   defaults,noatime    0 1
tmpfs                                       /tmp   tmpfs  defaults,noatime,mode=1777 0 0
UUID=02e6d9de-f403-4710-a401-e0c87c2b5f89   swap   swap   defaults,nofail      0  0
UUID=95cb7a9a-d7f2-4fb8-bf49-56828acf931c  /0/adat  ext4  defaults,nofail  0  2

I see nothing of note near end of dmesg,  /dev/sda4 seems to re-mounting for some reason

I don't think I'm up to trying a chroot, what can I do do recover

If I download a new KDE image is there a fix'er option on it?

TIA




------------------------------------------------------------

[    3.762868] EXT4-fs (sda4): mounted filesystem 25568ecc-3f4c-410d-8cfb-bb45afc10051 ro with ordered data mode. Quota mode: none.
[    4.744086] random: crng init done
[    5.369207] ATK0110 ATK0110:00: EC enabled
[    5.371076] sky2: driver version 1.30
[    5.371682] sky2 0000:05:00.0: Yukon-2 Optima chip revision 1
[    5.374248] sky2 0000:05:00.0 eth0: addr f4:6d:04:28:43:55
[    5.374271] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\_SB.PCI0.SBRG.ASOC.SMRG) (20230628/utaddress-204)
[    5.374278] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    5.385382] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    5.386570] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[    5.388400] input: PC Speaker as /devices/platform/pcspkr/input/input8
[    5.389934] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[    5.390787] acpi_cpufreq: overriding BIOS provided _PSD data
[    5.444690] mousedev: PS/2 mouse device common for all mice
[    5.480351] cryptd: max_cpu_qlen set to 1000
[    5.588992] i2c_dev: i2c /dev entries driver
[    5.589013] AVX version of gcm_enc/dec engaged.
[    5.589059] AES CTR mode by8 optimization enabled
[    5.591476] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    5.592256] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    5.592566] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    5.611096] snd_hda_intel 0000:08:00.1: Disabling MSI
[    5.611111] snd_hda_intel 0000:08:00.1: Handle vga_switcheroo audio client
[    5.742825] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:08:00.1/sound/card2/input9
[    5.742901] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:08:00.1/sound/card2/input10
[    5.742969] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:08:00.1/sound/card2/input11
[    5.743041] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:02.0/0000:08:00.1/sound/card2/input12
[    5.751175] snd_hda_codec_via hdaudioC1D0: autoconfig for VT2020: line_outs=4 (0x24/0x25/0x26/0x27/0x0) type:line
[    5.751182] snd_hda_codec_via hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    5.751185] snd_hda_codec_via hdaudioC1D0:    hp_outs=1 (0x28/0x0/0x0/0x0/0x0)
[    5.751188] snd_hda_codec_via hdaudioC1D0:    mono: mono_out=0x0
[    5.751190] snd_hda_codec_via hdaudioC1D0:    dig-out=0x2d/0x2e
[    5.751192] snd_hda_codec_via hdaudioC1D0:    inputs:
[    5.751194] snd_hda_codec_via hdaudioC1D0:      Front Mic=0x29
[    5.751196] snd_hda_codec_via hdaudioC1D0:      Rear Mic=0x2b
[    5.751198] snd_hda_codec_via hdaudioC1D0:      Line=0x2a
[    6.150099] input: HDA ATI SB Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input13
[    6.150178] input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input14
[    6.150252] input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card1/input15
[    6.150357] input: HDA ATI SB Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card1/input16
[    6.151966] nouveau 0000:08:00.0: vgaarb: deactivate vga console
[    6.153082] Console: switching to colour dummy device 80x25
[    6.153136] nouveau 0000:08:00.0: NVIDIA GK107 (0e7010a2)
[    6.165463] input: HDA ATI SB Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card1/input17
[    6.167302] input: HDA ATI SB Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card1/input18
[    6.167712] input: HDA ATI SB Line Out Side as /devices/pci0000:00/0000:00:14.2/sound/card1/input19
[    6.168048] input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input20
[    6.273029] nouveau 0000:08:00.0: bios: version 80.07.42.00.08
[    6.275328] nouveau 0000:08:00.0: fb: 2048 MiB DDR3
[    6.312344] kvm_amd: TSC scaling supported
[    6.312348] kvm_amd: Nested Virtualization enabled
[    6.312350] kvm_amd: Nested Paging enabled
[    6.312355] kvm_amd: LBR virtualization supported
[    6.314074] usb 2-2: reset high-speed USB device number 2 using ehci-pci
[    6.328728] MCE: In-kernel MCE decoding enabled.
[    6.468384] mt76x0u 2-2:1.0: ASIC revision: 76100002 MAC revision: 76502000
[    6.529231] EXT4-fs (sda4): re-mounted 25568ecc-3f4c-410d-8cfb-bb45afc10051 r/w. Quota mode: none.
[    6.549631] EXT4-fs (sda4): re-mounted 25568ecc-3f4c-410d-8cfb-bb45afc10051 r/w. Quota mode: none.
[    6.712510] Adding 6291452k swap on /dev/sda3.  Priority:-2 extents:1 across:6291452k SS
[    6.790716] mt76x0u 2-2:1.0: EEPROM ver:01 fae:00
[    6.837119] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    6.837901] usbcore: registered new interface driver mt76x0u
[    6.989825] EXT4-fs (sdb1): mounted filesystem 95cb7a9a-d7f2-4fb8-bf49-56828acf931c r/w with ordered data mode. Quota mode: none.
-----------------------------------------------------------------


 


Who, has loved us more?

Re: updated to unbootable

Reply #1
Reinstalling seemed the the only possible cure so  ...dome.
 
But on boot I get

"ModemManager (2205): <info>[base-manager] couldn't check support for device 'sys/devices/pci0000:00/0000"00.2/usb2: not supported by any plugin"

Asus Crosshair-IV Formula, 16gb, only two usb devs plugged-in at the time: durgod keyboard and usb mouse.
Who, has loved us more?

Re: updated to unbootable

Reply #2
I don't think I'm up to trying a chroot, what can I do do recover
The rescue is trivial nowadays and the process is described on our wiki. It boils down to this:
Code: [Select]
# mount /dev/YOUR-ROOT-PARTITION /mnt
# artix-chroot /mnt
# mkinitcpio -P
# grub-install --recheck /dev/sda                                                   # for BIOS systems
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub   # for UEFI systems
# grub-mkconfig -o /boot/grub/grub.cfg
# exit
Reboot and profit.

Re: updated to unbootable

Reply #3
Try a rEFInd iso

Re: updated to unbootable

Reply #4
I don't think I'm up to trying a chroot, what can I do do recover
The rescue is trivial nowadays and the process is described on our wiki. It boils down to this:
Code: [Select]
# mount /dev/YOUR-ROOT-PARTITION /mnt
# artix-chroot /mnt
# mkinitcpio -P
# grub-install --recheck /dev/sda                                                   # for BIOS systems
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub   # for UEFI systems
# grub-mkconfig -o /boot/grub/grub.cfg
# exit
Reboot and profit.

Merci.  When I first read 'trivial' I saw red but when I read artix-chroot I saw green. I had to find out and did :-)  This is a great little tool, thank you devs!  (BTW I think grub-install 'includes' grub-mkconfig...?)

Unfortunately the results are mixed:

On my T480  laptop everything went fine, new install from the 2023 KDE-Live dvd, full update, 1920x1080 resolution, just pointed it at a copy of my desktop /home/user directory and all is fine.

On my desktop (where the last update including a grub failure and warning had led to disaster) it's another story. I recopied that partition and did the suggested artix-chroot footwork which made it bootable but only to a black screen. Did another artix-chroot and updated it in the hopes of a fix but no cigar. Another partition got a new installation and a full update but it coughs up only a 1024-resolution, it's the only one available in the KDE hardware settings dialog. Somewhere I saw "because of Wayland" but I don't recall EVER having set wayland instead of X11.


--
"Nous n'héritons pas de la terre de nos parents, nous l'empruntons à nos enfants."  Antoine de Saint-Exupéry
 
Who, has loved us more?


Re: updated to unbootable

Reply #6
Try a rEFInd iso
My laptop is EFI  (or both), my desktop is only Legacy-BIOS. Not sure what that iso does.
My mistake.
rEFInd is a boot manager which auto discovers bootable EFI OS installations on a computer.
So handy to recover from broken grub situations without the need to chroot if you have it on a USB or CD. It can also replace grub.
But entirely useless with legacy BIOS :)

Re: updated to unbootable

Reply #7

The rescue is trivial nowadays and the process is described on our wiki. It boils down to this:
Code: [Select]
# mount /dev/YOUR-ROOT-PARTITION /mnt
# artix-chroot /mnt
# mkinitcpio -P
# grub-install --recheck /dev/sda                                                   # for BIOS systems
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub   # for UEFI systems
# grub-mkconfig -o /boot/grub/grub.cfg
# exit
Reboot and profit.

Merci.  When I first read 'trivial' I saw red but when I read artix-chroot I saw green. I had to find out and did :-)  This is a great little tool, thank you devs!  (BTW I think grub-install 'includes' grub-mkconfig...?)

Unfortunately the results are mixed:

On my T480  laptop everything went fine, new install from the 2023 KDE-Live dvd, full update, 1920x1080 resolution, just pointed it at a copy of my desktop /home/user directory and all is fine.

On my desktop (where the last update including a grub failure and warning had led to disaster) it's another story. I recopied that partition and did the suggested artix-chroot footwork which made it bootable but only to a black screen. Did another artix-chroot and updated it in the hopes of a fix but no cigar. Another partition got a new installation and a full update but it coughs up only a 1024-resolution, it's the only one available in the KDE hardware settings dialog. Somewhere I saw "because of Wayland" but I don't recall EVER having set wayland instead of X11.


I suspect that you are having a problem with the video card modules.  They recently on the kernel level changed, or so I heard at my local NYLXS group meeting.  NVIDIA has opened all their binaries now.

Anyway, the video modules and kernel have to MATCH verions.  Mount the partition in a rescue disk and just take a look.  It is possible, and I could be wrong, that at one point a non-standard module was installed for video, or maybe for CUDA?  and it was left behind by the upgrade.

Re: updated to unbootable

Reply #8

My laptop is EFI  (or both), my desktop is only Legacy-BIOS. Not sure what that iso does.
My mistake.
rEFInd is a boot manager which auto discovers bootable EFI OS installations on a computer.
So handy to recover from broken grub situations without the need to chroot if you have it on a USB or CD. It can also replace grub.itha; one cr one can never have enough boot-aids around :-)

No mistake, my laptop is EFI or Legacy-Bios; one can never have enough boot-aids in the house :-)
https://imgur.com/M1WNQ6q.png  [gave up on gentoo]
Who, has loved us more?

Re: updated to unbootable

Reply #9
On my desktop (where the last update including a grub failure and warning had led to disaster) it's another story. I recopied that partition and did the suggested artix-chroot footwork which made it bootable but only to a black screen. Did another artix-chroot and updated it in the hopes of a fix but no cigar. Another partition got a new installation and a full update but it coughs up only a 1024-resolution, it's the only one available in the KDE hardware settings dialog. Somewhere I saw "because of Wayland" but I don't recall EVER having set wayland instead of X11.
You may need to try a different kernel (try linux-lts); also, I saw you're using nouveau, you'll probably have better luck if you use nvidia instead, if you have a new card. Don't change both at once, begin with nvidia.

Re: updated to unbootable

Reply #10
On my desktop (where the last update including a grub failure and warning had led to disaster) it's another story. I recopied that partition and did the suggested artix-chroot footwork which made it bootable but only to a black screen. Did another artix-chroot and updated it in the hopes of a fix but no cigar. Another partition got a new installation and a full update but it coughs up only a 1024-resolution, it's the only one available in the KDE hardware settings dialog. Somewhere I saw "because of Wayland" but I don't recall EVER having set wayland instead of X11.
You may need to try a different kernel (try linux-lts); also, I saw you're using nouveau, you'll probably have better luck if you use nvidia instead, if you have a new card. Don't change both at once, begin with nvidia.

Been having issues with POS nvidia card on 6 distros used ever since arrival of kernel 6.7 regardless of wheteher nvidia driver's installed or not.

Just pulled the GT640 card and rebooted with AMD card replacing it, problem gone across the board with zero additional interventions!





Who, has loved us more?



Re: updated to unbootable

Reply #13
On my desktop (where the last update including a grub failure and warning had led to disaster) it's another story. I recopied that partition and did the suggested artix-chroot footwork which made it bootable but only to a black screen. Did another artix-chroot and updated it in the hopes of a fix but no cigar. Another partition got a new installation and a full update but it coughs up only a 1024-resolution, it's the only one available in the KDE hardware settings dialog. Somewhere I saw "because of Wayland" but I don't recall EVER having set wayland instead of X11.
You may need to try a different kernel (try linux-lts); also, I saw you're using nouveau, you'll probably have better luck if you use nvidia instead, if you have a new card. Don't change both at once, begin with nvidia.

I though all the nvidea stuff is now being given a Free Software license and is built into the kernel?

Auch I am repeating myself. Not sure what kicked Nous off into the Linus poster.

 

Re: updated to unbootable

Reply #14
Although I finally salvaged the system, upgrading it to Plasma6 made the deskbars unusable as well as most app-launching icons.  So I did a fresh install using the 2023 kde image, I'm upgrading IT as I write this so I'll see how the Plasma6 bit works out.

BUT I came across an issue during isntall which did result in an unbootable system and THIS is what I tought I should address here, it may or may not have been a factor is previous installs that also ended up being unbootable.

Installation from the live KDE DVD ended up hanging at the point of "installing boot manager". With no other option I did a reset but don't really remenber at which stage got this

Code: [Select]
os-prober timed out 

Possible contributing factor is the presence of now 3 other OSes (down form 6 others).  Just thought I'd post it.

The following boot got me only a grub promt, fortunately. from which I booted Suse Tumbleweed manually and then had the grub boot code redeployed by Yast.

1
Maybe nothing should be written by grub until os-prober has completed successfully?

2
If timed-out or whatever then only the Artiux installation should be made bootable, better then nothing and that would still cater to a  "C" break into the grub prompt from the grub menu to boot another OS.






Who, has loved us more?