My hard disk had been crashing and failed completely recently, so I bought a DVD HD caddy and a reconditioned SSD card from eBay as I thought this would be an easy fix. (Turns out Lenovo don't put access to the DVD tray release screw on the back of the C20 all-in-one, so I had to spudge the back off anyway, a major pain. I could've just used an adapter to fit the SSD in the HD tray. Not quite as bad as cleaning the fan, which involves taking the motherboard out, but I digress.)
I installed Bookworm on the SSD, and in the process the old HD appeared as an installation option. I assumed that it was just the HD controller identifying itself to the installer and that it was still broken (the issue seems to be mechanical judging from the strange noises it makes when failing) and went ahead with a default install on the SSD.
On rebooting grub showed me the two Debian installs on the HD, but not the new install on the SSD. Not sure how I did it, but after booting into the HD installations to check them, and investigating BIOS settings, the SSD installation appeared, but with this warning:
Gave me the following output:
The system was trying to boot using GRUBX64.EFI from the HD which didn't work, but then using SHIMX64.EFI followed by GRUBX64.EFI on the SSD which did.
I tried removing the HD entry and changing the boot order, but nothing seemed to stick and I still got the secure boot violation message after a reboot. There doesn't seem to be any way in the "BIOS" settings to control boot order. (It's set to EFI boot only.)
This morning I'm getting the following, so maybe something has changed. (Wasn't paying attention during the boot - needed tea!- and can't even remember if the violation message appeared this time.
It's nice to see the old HD is still working for the moment, but I can still hear hear it making mechanical noises during boot. Ideally I would like to make it invisible during boot to avoid any physical activity in the HD mechanism which might cause it to die permanently, but still have the option to mount the partitions at some point to look for stuff I need to backup. Is this possible? Gnome Disks has a "make invisible to firmware" option. Would that work?
Is there an option in the Debian installer that would have allowed me to ignore the HD completely during the installation to avoid this situation?
I installed Bookworm on the SSD, and in the process the old HD appeared as an installation option. I assumed that it was just the HD controller identifying itself to the installer and that it was still broken (the issue seems to be mechanical judging from the strange noises it makes when failing) and went ahead with a default install on the SSD.
On rebooting grub showed me the two Debian installs on the HD, but not the new install on the SSD. Not sure how I did it, but after booting into the HD installations to check them, and investigating BIOS settings, the SSD installation appeared, but with this warning:
Bookworm on the SSD boots normally after clicking OK to this message.secure boot violation invalid signature detected
Code:
# efibootmgr -vCode:
root@lenovo-debian-xfce:~# efibootmgr -vBootCurrent: 0001Timeout: 2 secondsBootOrder: 000B,0001,000C,0009,000A,0004,0003Boot0001* debianHD(1,GPT,a3b74f5d-3eb9-41d0-a19c-a1c79e2110ef,0x800,0x100000)/File(\EFI\DEBIAN\SHIMX64.EFI)Boot0003* Generic Usb DeviceVenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)Boot0004* CD/DVD DeviceVenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)Boot0009* UEFI: IPV4 Realtek PCIe GBE Family ControllerPciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(1c3947ad7779,0)/IPv4(0.0.0.00.0.0.0,0,0)..BOBoot000A* UEFI: IPV6 Realtek PCIe GBE Family ControllerPciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(1c3947ad7779,0)/IPv6([::]:<->[::]:,0,0)..BOBoot000B* debianHD(1,GPT,bf9d9903-b7c6-4196-994d-afb6098e992b,0x800,0x100000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BOBoot000C* debianHD(1,GPT,a3b74f5d-3eb9-41d0-a19c-a1c79e2110ef,0x800,0x100000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BOI tried removing the HD entry and changing the boot order, but nothing seemed to stick and I still got the secure boot violation message after a reboot. There doesn't seem to be any way in the "BIOS" settings to control boot order. (It's set to EFI boot only.)
This morning I'm getting the following, so maybe something has changed. (Wasn't paying attention during the boot - needed tea!- and can't even remember if the violation message appeared this time.
Code:
root@lenovo-debian-xfce:~# efibootmgr -vBootCurrent: 0001Timeout: 2 secondsBootOrder: 0001,000C,0009,000A,0004,0003Boot0001* debianHD(1,GPT,a3b74f5d-3eb9-41d0-a19c-a1c79e2110ef,0x800,0x100000)/File(\EFI\DEBIAN\SHIMX64.EFI)Boot0003* Generic Usb DeviceVenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)Boot0004* CD/DVD DeviceVenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)Boot0009* UEFI: IPV4 Realtek PCIe GBE Family ControllerPciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(1c3947ad7779,0)/IPv4(0.0.0.00.0.0.0,0,0)..BOBoot000A* UEFI: IPV6 Realtek PCIe GBE Family ControllerPciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(1c3947ad7779,0)/IPv6([::]:<->[::]:,0,0)..BOBoot000C* debianHD(1,GPT,a3b74f5d-3eb9-41d0-a19c-a1c79e2110ef,0x800,0x100000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BOIs there an option in the Debian installer that would have allowed me to ignore the HD completely during the installation to avoid this situation?
Statistics: Posted by FreewheelinFrank — 2024-06-24 06:12 — Replies 3 — Views 25