![]() ![]() Sector size (logical/physical): 512 bytes / 512 bytes Check your fdisk -l output is as follows: Disk /dev/sda: 29.82 GiB, 32017047552 bytes, 62533296 sectors Grub-install: error: cannot find a GRUB drive for /dev/mapper/ventoy1. Results in an error about one of the individual partitions ( /dev/mapper/ventoy1), and previous errors in the output of sudo apt-get upgrade reference /dev/mapper/ventoy2 (which is /boot) with the same error. (hd3) /dev/disk/by-id/ata-Samsung_SSD_860_QVO_4TB_S4CXNF0M423112DĬhanging the contents to (hd0) /dev/mapper/ventoy ![]() I did sudo grub-mkdevicemap, which gave me a /boot/grub/device.map with physical disks as follows: (hd0) /dev/disk/by-id/ata-TS32GSSD420K_D964580002 Attempting to enter /dev/mapper/ventoy as the device results in the same prompt, so I finished the upgrade without reinstalling GRUB and am now trying to fix it. dev/sda2 is Ventoy's EFI partition, rather than the one inside the VDI. (Enter the items or ranges you want to select, separated by Please check again to make sure that GRUB isġ. Installed GRUB core image stays in sync with GRUB modules and Is no longer present, or whose unique identifier has changedįor some reason. When it comes to reinstalling GRUB, I get the following message: The GRUB boot loader was previously installed to a disk that I have an Ubuntu Server 22.04 install running from a VDI image booted using Ventoy which I'm trying to apt-get upgrade. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |