Cannot find is never a good sign. Grub and disk drivers need to recognize the same devices in the same order, lest there be trouble like here described. Are any storage devices here on PATA? Is there a PATA controller in the PC? Is there an internal multi-card reader connected to USB? These types of characteristics can cause conflicting enumeration among bootloader and drive systems, the likes of which to avoid are a large part of why device access years ago was switched to using UUIDs by default. Perhaps input/output from parted -l might be useful here even after seeing lsblk &/or blkid output. efibootmgr -v might be useful as well. You've told us nothing about the hardware involved other than storage....Generating grub configuration file .../usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check your device.map.run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1...
Giving any BIOS 4 potential devices from which boot might be viable is really not the easiest of jobs, nor more than one ESP partition.
Statistics: Posted by mrmazda — 2024-05-19 05:25 — Replies 8 — Views 266
