Ubuntu-fr

plts

[Dual Boot] Grub qui ne démarre pas

Bonjour, j'ai essayé d'installer Ubuntu récemment et après une mise à jour de Windows, Grub ne démarrait plus

J'ai crée un espace de 50GO pour l'installation

L'installation s'est bien déroulé puis je suis retourné sur Windows 10 et j'ai effectué une mise à jour

A partir de ce moment là, je n'avais plus l'option pour démarrer sur Ubuntu ou Windows Manager
(Le fast boot était activé à ce moment là)

J'ai supprimé la partition de 50GO que j'avais crée et j'ai supprimé Ubuntu sur l'UEFI

J'ai réinstallé Ubuntu en désactivant le fast-boot puis j'ai utilisé boot-repair

Voici le diagnostic :
https://paste.ubuntu.com/p/g8B8xMy5Pm/

J'ai redémarré mon ordi puis j'ai eu de nouveau l'option pour aller sur Ubuntu ou Windows (Grub)
J'ai redémarré mon ordi une nouvelle fois pour m'assurer que ça marche puis l'option a de nouveau disparu

Si quelqu'un a une solution, je suis preneur, merci d'avance.

(ORDINATEUR PORTABLE ASUS FX571GT)

Dernière modification par plts (Le 14/02/2021, à 16:24)

malbo

Re : [Dual Boot] Grub qui ne démarre pas

Bonjour,
Je colle le rapport dont tu as donné le lien ( https://paste.ubuntu.com/p/g8B8xMy5Pm/ ) dans le post #1 :

boot-repair-4ppa125                                              [20210214_1546]

============================= Boot Repair Summary ==============================



=================== blkid (filtered) before raid activation: ===================
/dev/nvme0n1p5: UUID="fc601483-826a-45db-9e7b-429c1f51430f" TYPE="ext4" PARTUUID="29677401-73f1-4e11-9fae-9da805d4578e"
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="4E1F-940B" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b33701f1-9522-4e98-8254-4b4cba46fdda"
/dev/nvme0n1p3: LABEL="OS" UUID="1EDC216ADC213E01" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="dfe153b9-d1c5-4144-af9d-de7e87c34c35"
/dev/nvme0n1p4: LABEL="RECOVERY" UUID="983E08883E08621C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5f5e83ae-1391-4da2-aca5-9599ee530471"
/dev/nvme1n1: TYPE="isw_raid_member"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="962615d2-590b-40f7-9bcb-535f4ad654c1"
mdadm --assemble --scan

mdadm --detail --scan
ARRAY /dev/md/imsm0 metadata=imsm UUID=dee493ef:b557fe82:f6a80aa8:bfa18d34
Error code 12
mount -r /dev/nvme0n1p3 /mnt/boot-sav/nvme0n1p3

mount -r /dev/nvme0n1p3 : Error code 12
Error code 12
mount -r /dev/nvme0n1p3 /mnt/boot-sav/nvme0n1p3

mount -r /dev/nvme0n1p3 : Error code 12
Error code 12
mount -r /dev/nvme0n1p3 /mnt/boot-sav/nvme0n1p3

mount -r /dev/nvme0n1p3 : Error code 12

This will install the [mdadm] packages. Do you want to continue?
mdadm: Container /dev/md/imsm0 has been assembled with 1 drive
mdadm: (IMSM): Unsupported attributes : 3000000
mdadm: Unsupported attributes in IMSM metadata.Arrays activation is blocked.
mdadm: Cannot activate member /md127/0 in /dev/md/imsm0.
mdadm: (IMSM): Unsupported attributes : 3000000
mdadm: Unsupported attributes in IMSM metadata.Arrays activation is blocked.
mdadm: Cannot activate member /md127/1 in /dev/md/imsm0.
mdadm: (IMSM): Unsupported attributes : 3000000
mdadm: Unsupported attributes in IMSM metadata.Arrays activation is blocked.
mdadm: Cannot activate member /md127/0 in /dev/md/imsm0.
mdadm: (IMSM): Unsupported attributes : 3000000
mdadm: Unsupported attributes in IMSM metadata.Arrays activation is blocked.
mdadm: Cannot activate member /md127/1 in /dev/md/imsm0.
Warning: Not all of the space available to /dev/nvme0n1 appears to be used, you can fix the GPT to use all of the space (an extra 4544 blocks) or continue with the current setting?
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Could not mount read-write, trying read-only
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
The backup GPT table is not on the end of the device. This problem will be corrected by write.
/usr/share/boot-sav/bs-cmd_terminal.sh: line 177: warning: command substitution: ignored null byte in input

Recommended repair: ____________________________________________________________

The default repair of the Boot-Repair utility will purge (in order to sign-grub) and reinstall the grub-efi-amd64-signed of
nvme0n1p5,
using the following options:        nvme0n1p1/boot/efi,
Additional repair will be performed: unhide-bootmenu-10s  use-standard-efi-file


/boot/efi added in nvme0n1p5/fstab
nvme0n1p5/boot/efi not empty
apt-get -y update
Purge the GRUB of nvme0n1p5
grub-efi-amd64-signed available

0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
DEBCHECK debOK, grub-efi-amd64-signed
DEBCHECK debOK
shim-signed available
Please type: sudo dpkg --configure -ansudo apt-get install -fynsudo apt-get install -y mdadmnsudo mdadm --assemble --scannsudo apt-get purge -y grub*-common shim-signed
shim-signed available
linux-headers-generic available
linux-signed-generic NOT available (apt-cache policy  problem)
Then type: sudo apt-get install -y grub-efi-amd64-signed os-prober shim-signed linux-headers-generic

Unhide GRUB boot menu in nvme0n1p5/etc/default/grub

======= Reinstall the grub-efi-amd64-signed os-prober shim-signed linux-headers-generic of nvme0n1p5 =======

grub-install --version
grub-install (GRUB) 2.04-1ubuntu26.8

efibootmgr -v from chroot before grub install
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000
Boot0000* Windows Boot Manager	HD(1,GPT,b33701f1-9522-4e98-8254-4b4cba46fdda,0x800,0x82000)/File(EFIMICROSOFTBOOTBOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0002* ubuntu	HD(1,GPT,b33701f1-9522-4e98-8254-4b4cba46fdda,0x800,0x82000)/File(EFIUBUNTUSHIMX64.EFI)

uname -r
5.8.0-43-generic

grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot
Installing for x86_64-efi platform.
Installation finished. No error reported.
df /dev/nvme0n1p1
mv /boot/efi/EFI/Boot/bootx64.efi /boot/efi/EFI/Boot/bkpbootx64.efi
cp /boot/efi/EFI/ubuntu/shimx64.efi /boot/efi/EFI/Boot/bootx64.efi
cp /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/Boot/

grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot
Installing for x86_64-efi platform.
Installation finished. No error reported.

efibootmgr -v from chroot after grub install
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000
Boot0000* Windows Boot Manager	HD(1,GPT,b33701f1-9522-4e98-8254-4b4cba46fdda,0x800,0x82000)/File(EFIMICROSOFTBOOTBOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0002* ubuntu	HD(1,GPT,b33701f1-9522-4e98-8254-4b4cba46fdda,0x800,0x82000)/File(EFIubuntushimx64.efi)

update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.8.0-43-generic
Found initrd image: /boot/initrd.img-5.8.0-43-generic
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Failed to read last sector (998304397): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/nvme0n1p3': Invalid argument
The device '/dev/nvme0n1p3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Unhide GRUB boot menu in nvme0n1p5/boot/grub/grub.cfg

Boot successfully repaired.

You can now reboot your computer.

Please do not forget to make your UEFI firmware boot on the The OS now in use - Ubuntu 20.04.2 LTS CurrentSession entry (nvme0n1p1/EFI/ubuntu/shimx64.efi file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.

If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi

============================ Boot Info After Repair ============================

On y voit la mention "isw_raid_member". Je pense que tu as un ordi équipé de Optane H10. Tu trouveras des infos dans cette discussion sur la façon de désactiver Optane H10 : https://forum.ubuntu-fr.org/viewtopic.php?id=2061777

EDIT : tu as noté dans ton post #1 que ton modèle est "ASUS FX571GT" mais c'est imprécis. Il y a deux modèles dont le nom commence par FX571GT et qui sont équipés de Optane H10 :
FX571GT-AL717T visible sur cette page du site LaptopSpirit : https://www.laptopspirit.fr/275534/asus … ptane.html
FX571GT-AL894T visible sur cette autre page du site LaptopSpirit : https://www.laptopspirit.fr/280337/asus … leger.html
Si ton modèle est un de ces deux-là, je te prie de pérciser lequel. Sinon, je te prie de donner le nom complet de ton modèle.

Dernière modification par malbo (Le 14/02/2021, à 16:52)

plts

Re : [Dual Boot] Grub qui ne démarre pas

C'est bien ce modèle : https://www.laptopspirit.fr/280337/asus … leger.html
(J'ai installé le programme pour retirer optane et mon ordi a affiché un message d'erreur "unmountable volume")

malbo

Re : [Dual Boot] Grub qui ne démarre pas

C'est bien ce modèle : https://www.laptopspirit.fr/280337/asus … leger.html

Donc il s'agit du modèle Asus FX571GT-AL894T
Pour que je puisse voir la situation, je te prie de faire un Boot-info depuis une session live de Ubuntu 20.04.2 et de donner l'URL de ce Boot-info dans ta réponse.