05-27-2025, 04:46 PM
As you have a UEFI system, processing grub-efi-amd64-signed makes some sense.
You are correct there are a lot of entries.
I got side tracked with the same error on a BIOS system which appeared to clear on subsequent updates/upgrades.
I've not been able to work why it happened on that system and I cannot reproduce it at the moment.
As neither system is a VM, it is hard to understand why we both had identical references to mounting a non-existent device with the same 'by-id' reference of
ata-VBOX_HARDDISK_VBad170837-5acc172c-part2
The page that Jerry suggested implies the need to replace the ata-VBOX_HARDDISK_* reference in some way, but I may be missing something there.
I'm sorry but at the moment, I have no safe suggestions to get updates working on your system. If (and only if) this is a new installation with nothing of value on it, you could try erasing and re-installing. That's what I'm going to try on my BIOS machine to see if I reproduce it again.
You are correct there are a lot of entries.
I got side tracked with the same error on a BIOS system which appeared to clear on subsequent updates/upgrades.
I've not been able to work why it happened on that system and I cannot reproduce it at the moment.
As neither system is a VM, it is hard to understand why we both had identical references to mounting a non-existent device with the same 'by-id' reference of
ata-VBOX_HARDDISK_VBad170837-5acc172c-part2
The page that Jerry suggested implies the need to replace the ata-VBOX_HARDDISK_* reference in some way, but I may be missing something there.
I'm sorry but at the moment, I have no safe suggestions to get updates working on your system. If (and only if) this is a new installation with nothing of value on it, you could try erasing and re-installing. That's what I'm going to try on my BIOS machine to see if I reproduce it again.
stevef
clueless
clueless