GRUB debian 11 -> error processing package grub-cloud-amd64 lors de la mise à jour
... / GRUB debian 11 -> error p...
< Previous question   -   Next question >
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Question

GRUB debian 11 -> error processing package grub-cloud-amd64 lors de la mise à jour
by
TTY
Contributor
Created on 2022-09-23 14:34:28 (edited on 2024-09-04 12:07:07) in Serveurs dédiés

Bonjour à tous,

La machine est une Debian 11 qui à 2 SSD RAID 1 (pas NVME)
Pas de UEFI.

`apt upgrade`
->
> The following packages will be upgraded:
> grub-common grub-efi-amd64-bin grub-efi-amd64-signed grub-pc-bin grub2-common
[...]
Setting up grub-common (2.06-3~deb11u2) ...
Setting up grub-efi-amd64-bin (2.06-3~deb11u2) ...
Setting up grub-efi-amd64-signed (1+2.06+3~deb11u2) ...
Setting up grub2-common (2.06-3~deb11u2) ...
Setting up grub-pc-bin (2.06-3~deb11u2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for grub-cloud-amd64 (0.0.5) ...
Installing for i386-pc platform.
mdadm: /dev/md does not appear to be an md device
grub-install: error: ioctl RAID_VERSION error: Inappropriate ioctl for device.
dpkg: error processing package grub-cloud-amd64 (--configure):
installed grub-cloud-amd64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
grub-cloud-amd64

`fdisk -l`
->
> Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors
> Disk model: SAMSUNG MZ7LM480
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xe7f3680b

> Device Boot Start End Sectors Size Id Type
> /dev/sdb1 2048 904142847 904140800 431.1G fd Linux raid autodetect
> /dev/sdb2 904142848 937697279 33554432 16G 83 Linux


> Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
> Disk model: SAMSUNG MZ7LM480
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x86c301e8

> Device Boot Start End Sectors Size Id Type
> /dev/sda1 2048 904142847 904140800 431.1G fd Linux raid autodetect
> /dev/sda2 904142848 937697279 33554432 16G 83 Linux
> /dev/sda3 937698992 937703087 4096 2M 83 Linux


> Disk /dev/md1: 431 GiB, 462785871872 bytes, 903878656 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes

`apt list --installed | grep -i grub`
->
> grub-cloud-amd64/stable,now 0.0.5 amd64 [installed]
> grub-common/stable-updates,now 2.06-3~deb11u2 amd64 [installed,automatic]
> grub-efi-amd64-bin/stable-updates,now 2.06-3~deb11u2 amd64 [installed,automatic]
> grub-efi-amd64-signed/stable-updates,now 1+2.06+3~deb11u2 amd64 [installed,automatic]
> grub-pc-bin/stable-updates,now 2.06-3~deb11u2 amd64 [installed,automatic]
> grub2-common/stable-updates,now 2.06-3~deb11u2 amd64 [installed,automatic]

Auriez vous des conseils à me donner ?
Upvotes (0)
1206 Views
3 Replies ( Latest reply on 2022-11-18 16:28:48 by
JPLor
)


/dev/md does not appear to be an md device


Le script post install lance ceci :
> grub-probe -t device /boot/ | sed -Ee 's/[0-9]+$//' -e 's/([0-9])p$/\1/'

ce qui donne /dev/md en réponse et ensuite il essaie de faire :
> grub-install --target=i386-pc /dev/md

mais je pense que le script ne marche pas car dans un le cas d'un raid1 software :
il faudrait que la mise à jour grub donne quelque chose comme :
> grub-install --target=i386-pc /dev/sda
> grub-install --target=i386-pc /dev/sdb
Helpful (0)

Merci @ChristopheGX,

`grub-install --target=i386-pc /dev/sda`
->
> Installing for i386-pc platform.
> Installation finished. No error reported.

`grub-install --target=i386-pc /dev/sdb`
->
>Installing for i386-pc platform.
>Installation finished. No error reported.

Du coup,
apt upgrade
->
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Setting up grub-cloud-amd64 (0.0.5) ...
> Scanning processes...
> Scanning candidates...
> Scanning processor microcode...
> Scanning linux images...

> Failed to check for processor microcode upgrades.

`update-grub`
->
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.10.0-18-amd64
> Found initrd image: /boot/initrd.img-5.10.0-18-amd64
> Found linux image: /boot/vmlinuz-5.10.0-17-amd64
> Found initrd image: /boot/initrd.img-5.10.0-17-amd64
> Found linux image: /boot/vmlinuz-5.10.0-13-amd64
> Found initrd image: /boot/initrd.img-5.10.0-13-amd64
> done

ça m'a l'air OK tout ça.
Je tente un reboot ce weekend tu penses ?
Helpful (0)
J

Bonjour
Comme j'ai le même problème je voulais savoir si la manip avait marché ?
Merci !
Helpful (0)

Oui impeccable !
Helpful (0)
J

Arghh....
Malheureusement :
`grub-install --target=i386-pc /dev/sda` :
> Installing for i386-pc platform.
> grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
> grub-install: error: embedding is not possible, but this is required for RAID and LVM install.

No luck...
Mais je m'aperçois que contrairement à l'OP je suis en UEFI.
Quelqu'un aurait une idée ?
Supprimer grub-cloud-amd64 (qui fait à la fois grub-pc et grub-efi) et mettre une version efi uniquement ? Mais ça été installé comme ça avec le repository OVH et ça marchait avant la mise à jour de grub (grub-cloud-amd64 lui-même n'a pas changé)...
Helpful (0)

Related questions

Join discussion