Error symbol grub disk native sectors not found

Code: Select all

sudo debconf-communicate grub-pc <<< "set grub-pc/install_devices /dev/nvme3n1"
0 value set

Code: Select all

sudo dpkg-reconfigure grub-pc
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..

Code: Select all

nvme3n1                                                                                   
├─nvme3n1p1  ext4   1.0   boot        69862ce0-63ef-406c-87f1-70edc6acc306  268.4M    38% /boot
├─nvme3n1p2  crypto 2                 d1e96fb4-c875-4b4a-8fce-668b9e451d48                
│ └─root.fsm                                                                  668G    23% /
└─nvme3n1p3  crypto 2                 9578a9af-e797-4398-8fec-683469866189                
  └─swap     swap   1     swapMX      bb99a4fc-bc4a-47bd-af73-652d9fb89ff2                [SWAP]

Code: Select all

sudo grub-install --target=i386-pc  --recheck /dev/nvme3n1

Code: Select all

grub-pc/mixed_legacy_and_grub2: true
* grub-pc/install_devices: /dev/nvme3n1
  grub-pc/install_devices_disks_changed:
  grub2/force_efi_extra_removable: false
* grub2/linux_cmdline_default: quiet splash
  grub2/kfreebsd_cmdline_default: quiet
  grub-pc/disk_description:
* grub-pc/install_devices_failed: true
  grub2/kfreebsd_cmdline:
  grub-pc/kopt_extracted: false
  grub2/update_nvram: true
  grub-pc/hidden_timeout: false
  grub-pc/install_devices_failed_upgrade: true
  grub-pc/partition_description:
* grub2/linux_cmdline:
  grub-pc/install_devices_empty: false
  grub-pc/chainload_from_menu.lst: true
  grub-pc/timeout: 5
  grub-pc/postrm_purge_boot_grub: false

Code: Select all

AME         FSTYPE      FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINT
nvme3n1                                                                                   
├─nvme3n1p1  ext4        1.0   boot   69862ce0-63ef-406c-87f1-70edc6acc306  268.4M    38% /boot
├─nvme3n1p2  crypto_LUKS 2            d1e96fb4-c875-4b4a-8fce-668b9e451d48                
│ └─root.fsm                                                                668.6G    23% /
└─nvme3n1p3  crypto_LUKS 2            9578a9af-e797-4398-8fec-683469866189                
  └─swap     swap        1     swapMX bb99a4fc-bc4a-47bd-af73-652d9fb89ff2                [SWAP]

Code: Select all

nstalling for i386-pc platform.
Installation finished. No error reported.

Code: Select all

Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-5.14.0-4mx-amd64
Found initrd image: /boot/initrd.img-5.14.0-4mx-amd64
Found memtest86+ image: /memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sdi1.  Check your device.map.
done

Code: Select all

sudo grub-install --target=i386-pc  --modules=normal --recheck /dev/nvme3n1

Latest upgrade broke Grub.

error:symbol ‘grub_disk-native-sectors-not-found’

grub rescue>

I know the steps are on the web,  Not sure about doing this.

It is a BIOS install.   I’m posting from a live usb devuan.

I mounted boot partition to  remove grub-efi-amd64 and reinstall grub-pc and get this

Setting up grub-pc (2.04-20) ...
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
dpkg: error processing package grub-pc (--configure):
 installed grub-pc package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)

nex step ?

Last edited by prizm02 (2022-09-11 10:27:57)

You need to chroot into the system with the API filesystems mounted for that to work.

Either use Rescue Mode to obtain a shell in the installed system or run these commands from the live environment:

apt update
apt install arch-install-scripts
mount /dev/sdXY /mnt
mount /dev/sdXZ /mnt/boot
arch-chroot /mnt

Replace X, Y & Z with the drive letter and partition numbers for the root (/) and /boot partitions, respectively.

From a shell in the installed system run these commands to fix things:

dpkg-reconfigure grub-pc
grub-mkconfig -o /boot/grub/grub.cfg

I presume you’re running testing/unstable? You really should mention the version in the OP.

EDIT: and please replace the thread title with something useful (eg, «GRUB update lands at ‘grub rescue>’ prompt»). This is actually a common problem at the moment:

https://archlinux.org/news/grub-bootloa … ibilities/

If you had bothered to search before posting you would probably have found the solution more quickly.

Last edited by Head_on_a_Stick (2022-09-11 09:06:55)

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.

Hold on, I missed this:

Why was grub-efi-amd64 installed?

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.

The amd64 live isos have grub-efi-amd64 installed and the grub-pc deb package available inside the iso for bios boots. If the iso is booted in uefi mode, it installs grub-efi. If the iso is booted in bios mode, the installer will install grub-pc. If you boot in bios mode and chroot the installed system, you need to install the grub-pc package before running grub-install. It’s in the root of the filesystem. So run dpkg -i /grub-pc*.deb before running grub-install.

If the iso is booted in bios mode and the disk has gpt partition table, the installer will warn you that you need a special partition for grub, at least 1mb with no filesystem and with flag bios_grub (in gparted) or ef03 (in gdisk).

Edit: Just after hitting Submit, I saw that the first message says this happened after an upgrade. Now I’m not sure if my answer if relevant.

Install is Chimaera stable,  the update  stopped at a screen that asked where and how to install the new grub. I  selected sda1.  I thought the motherboard settings were wrong.

Is Recovery mode the same as Rescue mode .

Last edited by prizm02 (2022-09-11 10:40:13)

No.

I provided the link for a reason. Please read it.

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.

The following string will be used as Linux parameters for the default   │
  │ menu entry but not for the recovery mode.                               │
  │                                                                         │
  │ Linux default command line:                                             │
  │                                       

grub-mkconfig -o /boot/grub/grub.cfg_

following fsmithread

dpkg: error processing package grub-pc (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.9.4-2) ...
Errors were encountered while processing:
 grub-pc

The live usb has Failsafe but no Rescue Boot Option.

Last edited by prizm02 (2022-09-11 11:55:01)

Just for clarification, is this a general problem with the latest upgrade of grub?

I’ve just been updating my legacy-bios Chimaera installation (using synaptic).
There are lots of upgrades available today, including one to grub-pc, from 2.04-20 to 2:06-3~deb11u1.
I’ve installed all the other upgrades.
Is this safe to install the grub upgrade or will it just give me a grub rescue> prompt and a headache?

Last edited by Marjorie (2022-09-11 11:38:29)

Chimaera: Just tried the update on my laptop: Yes, the grub update will cause headaches. Acer Aspire 5 A515-44, efi only, encrypted LVM with unencrypted root. The installation worked on second try (had to enable rw for the efivarfs), creates a new debian entry in the efi, on reboot the grub rescue shell comes up with «symbol grub_disk_native_sectors not found».

When I use F12 to select my original entry devuan4 the laptop boots. Then I removed the debian, and now I am getting the error also on my devuan4.

Then use arch-chroot from the live environment, as I suggested in my first post.

Are you even reading replies?

Yes. Details on the Arch News item to which I linked. It’s been all over the Arch forums recently.

Debian’s 11.5 point release has an upgraded GRUB version, which is highly unusual. I’m not sure if that also has the problem.

I don’t use GRUB myself…

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.

Got my laptop fixed again. Booted the installer stick into rescue mode, chrooted into the encrypted system. To get that working I needed to load some Realtek firmware for wired network access. Took me a while to figure out that the stick I first used wasn’t FAT formatted. The installer didn’t like that. 

# grub-install --bootloader-id=devuan4 --no-uefi-secure-boot
# update-grub

That fixed it for me.

Edith

Note to the public: in general probably a simple

# grub-install 
# update-grub

will do the job.

Last edited by rolfie (2022-09-11 17:21:59)

I got fed up and reinstalled.

Thanks for all replies.