#1 Le 18/08/2021, à 20:57
- alouette
Problème (a priori) matériel pour lancement ubuntu
Bonjour,
Lors du démarrage d'un ordinateur, j'obtiens :
minimal bash-like line editing is supported. for the first word, tab lists possible command completions. anywhere else tab lists possible device or file completionsJ ai fait cette manipulation :
ubuntu@ubuntu:~$ sudo add-apt-repository -y ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-info && boot-infoet obtenu :
boot-info-4ppa130 [20210806_2040]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/sda.
=> Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi
/efi/ubuntu/fwupx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi
sda2: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 10
Boot files: /Windows/System32/winload.exe
sda4: __________________________________________________________________________
File system: BIOS Boot partition
Boot sector type: -
Boot sector info:
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda7: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 20.04.1 LTS
Boot files: /etc/fstab /etc/default/grub
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.04
Boot sector info: Syslinux looks at sector 16400 of /dev/sdb1 for its
second stage. The integrity check of Syslinux failed.
No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot/grub/grub.cfg /syslinux.cfg
/efi/BOOT/grubx64.efi /efi/BOOT/mmx64.efi /ldlinux.sys
================================ 2 OS detected =================================
OS#1: Ubuntu 20.04.1 LTS on sda7
OS#2: Windows 10 on sda3
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Ubuntu 20.04.1 LTS, focal, x86_64)
===================================== UEFI =====================================
BIOS is EFI-compatible, but it is not setup in EFI-mode for this live-session.
EFI in dmesg.
[ 0.027798] ACPI: UEFI 0x00000000B7F88000 000042 (v01 LENOVO CB-01 00000002 PTEC 00000002)
[ 0.027936] ACPI: UEFI 0x00000000B7F6E000 000152 (v01 LENOVO CB-01 00000001 PTEC 00000002)
This session has been detected as 'live' because df -Th / contains overlay
f7a57b08bc7c1c85417ae4cea582d1d4 sda1/Boot/bootx64.efi
bed45d1c9554cea09924d3814cb7c446 sda1/Boot/fbx64.efi
256fe27540b54b71cf38110338247688 sda1/ubuntu/fwupx64.efi
0460d855b6d422c080c1de02010c3ffd sda1/ubuntu/grubx64.efi
4487628005555bfd4a4c0a47211e0700 sda1/ubuntu/mmx64.efi
f7a57b08bc7c1c85417ae4cea582d1d4 sda1/ubuntu/shimx64.efi
9aeccc28d2f36520a9a75c418cb30db6 sda1/Microsoft/Boot/bootmgfw.efi
bfba095bab3eb0e778b6914caad7362b sda1/Microsoft/Boot/bootmgr.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sda : is-GPT, hasBIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda3 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda5 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda6 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda7 : is-os, 32, apt-get, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
Partitions info (2/3): _________________________________________________________
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot
sda5 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda6 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda7 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda1 : not-sepboot, no-kernel, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda3 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda5 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda6 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda7 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 119.25 GiB, 128035676160 bytes, 250069680 sectors
Disk identifier: E3BA229E-6606-433B-9422-0CA1417709B4
Start End Sectors Size Type
sda1 2048 534527 532480 260M EFI System
sda2 534528 567295 32768 16M Microsoft reserved
sda3 567296 147379178 146811883 70G Microsoft basic data
sda4 147380224 147382271 2048 1M BIOS boot
sda5 248020992 250068991 2048000 1000M Windows recovery environment
sda6 147382272 148432895 1050624 513M Microsoft basic data
sda7 148432896 248020991 99588096 47.5G Linux filesystem
Partition table entries are not in disk order.
Disk sdb: 3.74 GiB, 3999268864 bytes, 7811072 sectors
Disk identifier: 0x000c2abf
Boot Start End Sectors Size Id Type
sdb1 * 2048 7811071 7809024 3.7G c W95 FAT32 (LBA)
parted -lm (filtered): _________________________________________________________
sda:128GB:scsi:512:512:gpt:ATA SAMSUNG MZNLN128:;
1:1049kB:274MB:273MB:fat32:EFI system partition:boot, esp;
2:274MB:290MB:16.8MB::Microsoft reserved partition:msftres;
3:290MB:75.5GB:75.2GB:ntfs:Basic data partition:msftdata;
4:75.5GB:75.5GB:1049kB:::bios_grub;
6:75.5GB:76.0GB:538MB:fat32::msftdata;
7:76.0GB:127GB:51.0GB:ext4::;
5:127GB:128GB:1049MB:ntfs:Basic data partition:diag;
sdb:3999MB:scsi:512:512:msdos: USB DISK 2.0:;
1:1049kB:3999MB:3998MB:fat32::boot, lba;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 1AAF-6D8C 9a94d287-29ad-4f72-82b8-b980b6637dd7 SYSTEM_DRV EFI system partition
├─sda2 33999672-277b-4b40-8d94-8d02856972c9 Microsoft reserved partition
├─sda3 ntfs 226EB29B6EB266E7 b39aef51-c760-432f-b015-9f604994f423 Windows Basic data partition
├─sda4 3b4c4f0d-8935-442d-a13b-5c0acab5ae53
├─sda5 ntfs 6C903FA1903F7126 e1a2c88b-818a-4063-afa8-6a602e47ba20 Basic data partition
├─sda6 vfat F3E6-54DC f409b570-cff1-475f-a89b-6eac5cd6880c
└─sda7 ext4 a0e09b53-ce72-4aae-8538-c8e8472fde99 7fd6a7a6-5504-4884-ae0f-e9e815e02257
sdb
└─sdb1 vfat 5499-16DC 000c2abf-01 UBUNTU 20_0
df (filtered): _________________________________________________________________
Avail Use% Mounted on
sda1 221M 14% /mnt/boot-sav/sda1
sda3 15.9G 77% /mnt/boot-sav/sda3
sda5 489.7M 51% /mnt/boot-sav/sda5
sda6 512M 0% /mnt/boot-sav/sda6
sda7 39.3G 10% /mnt/boot-sav/sda7
sdb1 1.1G 70% /cdrom
Mount options: __________________________________________________________________
sda1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda3 ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda5 ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda6 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda7 rw,relatime
sdb1 ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid 80dc881c-0f5f-4e86-863e-9a7e7640d28c root hd0,gpt5
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
========================== sda7/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda7 during installation
UUID=a0e09b53-ce72-4aae-8538-c8e8472fde99 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda6 during installation
UUID=F3E6-54DC /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
======================= sda7/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
===================== sda7: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 17123 juil. 31 2020 10_linux
-rwxr-xr-x 1 root root 42128 juil. 31 2020 10_linux_zfs
-rwxr-xr-x 1 root root 12894 juil. 31 2020 20_linux_xen
-rwxr-xr-x 1 root root 12059 juil. 31 2020 30_os-prober
-rwxr-xr-x 1 root root 1424 juil. 31 2020 30_uefi-firmware
-rwxr-xr-x 1 root root 214 juil. 31 2020 40_custom
-rwxr-xr-x 1 root root 216 juil. 31 2020 41_custom
====================== sdb1/boot/grub/grub.cfg (filtered) ======================
Ubuntu
Ubuntu (safe graphics)
OEM install (for manufacturers)
Boot from next volume
UEFI Firmware Settings
========================= sdb1/syslinux.cfg (filtered) =========================
DEFAULT loadconfig
LABEL loadconfig
CONFIG /isolinux/isolinux.cfg
APPEND /isolinux/
==================== sdb1: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1
================== sdb1: Location of files loaded by Syslinux ==================
GiB - GB File Fragment(s)
?? = ?? syslinux.cfg 1
?? = ?? ldlinux.sys 1
=============================== StdErr Messages ================================
File descriptor 63 (pipe:[182561]) leaked on lvs invocation. Parent PID 9324: /bin/bash
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi of
sda7,
using the following options: sda1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file
Blockers in case of suggested repair: __________________________________________
The current session is in BIOS-compatibility mode. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode.
Confirmation request before suggested repair: __________________________________
Your Linux on sda7 is 32-bit, so it may be incompatible with your 64-bit UEFI firmware. You may want to install a 64-bit Linux instead.
Are you sure you want to continue anyway?
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the Ubuntu 20.04.1 LTS entry (sda1/efi/****/grub****.efi (**** will be updated in the final message) 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\****\grub****.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.J'avais fait une sauvegarde du système complet ainsi qu'une autre de chacunes des partitions distinctes, tout restauré mais même résultat. J'ai installé Ubuntu sur une clé et essayé de le réinstaller sur l'ordi, même résultat. De même avec une clé windows.
J'ai comme l'impression que l'un des composants est mort. Comment savoir lequel ?
Merci d avance
Hors ligne
#2 Le 19/08/2021, à 19:10
- geole
Re : Problème (a priori) matériel pour lancement ubuntu
Bonjour
extrait du boot-info
Your Linux on sda7 is 32-bit, so it may be incompatible with your 64-bit UEFI firmware. You may want to install a 64-bit Linux instead.
Are you sure you want to continue anyway?Où as-tu téléchargé la version en question?
sda7: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 20.04.1 LTS
Boot files: /etc/fstab /etc/default/grubLes grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 23/08/2021, à 02:13
- alouette
Re : Problème (a priori) matériel pour lancement ubuntu
Au moment où j'ai fait le boot info, j'utilisais une version ubuntu téléchargée sur le site ubuntu il y a un peu plus d'un an. C'était la version 18, j'ai reçu une proposition de mise à niveau il y a quelques mois, cela fonctionnait très bien
Hors ligne
#4 Le 23/08/2021, à 13:26
- geole
Re : Problème (a priori) matériel pour lancement ubuntu
Bonjour
Je ne comprends pas tout
Peut-être que tu avais une installation en 32 bits qui a été mise à niveau en 20.04 et qui suite à une mise à jour n'est plus compatible
Mais cet ordinateur est certainement EFI et tu as booté en LEGACY
De plus, la partition EFI devait être en N° 5 sur 80dc881c-0f5f-4e86-863e-9a7e7640d28c
===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid 80dc881c-0f5f-4e86-863e-9a7e7640d28c root hd0,gpt5or cette partition n'existe plus et la partition N°5 est une partition NTFS et pas EXT4
sda5 248020992 250068991 2048000 1000M Windows recovery environmentDe plus la structure de boot de SDA7 n'existe plus
sda7/boot/grub/grub.cfgsda7 : is-os, 32, apt-get, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbiosJe ne sais pas trop ce que cela va donner
1) Boote en EFI avec ton support d'installation
2) Vérifie que tu as bien booté en EFI
[ -d /sys/firmware/efi ] && echo "Session EFI" || echo "Session non-EFI"3) Vérifies que le processeur est compatible 64 bits afin de savoir si une version 64 bits est installable
sudo dmidecode -t44) Installe boot-repair https://doc.ubuntu-fr.org/boot-repair
sudo add-apt-repository -y ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-repair ; boot-repair5) et fais la réparation recommandée en cliquant au bon endroit. Elle a prévu de faire cette chose
the default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi of
sda7,
using the following options: sda1/boot/efi,
Dernière modification par geole (Le 23/08/2021, à 13:38)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#5 Le 24/08/2021, à 11:54
- alouette
Re : Problème (a priori) matériel pour lancement ubuntu
Merci, je vais tester ça dans le week-end
Hors ligne