#1 Le 17/10/2024, à 18:06
- jpl-bz
utiliser le dernier boot-repair en session live Ubuntu + cas réel
bonjour,
préalablement à une installation envisagée (Ubuntu, Debian ou autre dérivé Debian) je voudrais améliorer la situation rapportée par un Boot-Repair "ancien" * .
L'idée , si j'ai bien compris ce qui se dit dans [Réparateur de démarrage] Développement du logiciel Boot-Repair,
serait
- de booter avec la clé usb du système souhaité (Ubuntu 24 LTS, Debian 12, autre)
puis,
dans la session live,
- installer le dernier DEB boot-repair_4ppa2081_all.deb ( ........ trouvé sur ? ... )
- le lancer (pas de message "installé" , pas d'icône, pas trouvé dans / ou autre dossier, donc .......... quelle ligne de commande va le faire ? ...)
puis,
créer le boot-info, le copier ici ...
Seulement quand j'aurai eu vos avis sur les ? ci-dessus qui me bloquent.
(penser Indiquer ce sujet dans https://forum.ubuntu-fr.org/viewtopic.php?id=509791 )
cordialement
* le boot-info ancien est le suivant :
boot-info-4ppa125 [20241001_0751]
============================== Boot Info Summary ===============================
=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector
826165248 of the same hard drive for core.img. core.img is at this
location and looks for (,gpt9)/boot/grub. It also embeds following
components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_gpt biosdisk
---------------------------------------------------------------------------
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/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/memtest.efi
sda2: __________________________________________________________________________
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: /bootmgr /Boot/BCD
sda3: __________________________________________________________________________
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/Boot/mmx64.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 /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
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: Windows 10
Boot files: /bootmgr /Windows/System32/winload.exe
sda6: __________________________________________________________________________
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:
sda7: __________________________________________________________________________
File system: BIOS Boot partition
Boot sector type: Grub2's core.img
Boot sector info:
sda8: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 22.04.4 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
sdb: ___________________________________________________________________________
File system: iso9660
Boot sector type: Unknown
Boot sector info:
Operating System:
Boot files: /boot/grub/grub.cfg
================================ 2 OS detected =================================
OS#1: Ubuntu 22.04.4 LTS on sda9
OS#2: Windows 10 on sda5
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Boot-Repair-Disk 64bit 20200604, bionic, x86_64)
===================================== UEFI =====================================
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot enabled.
efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001,0002,0001,2002,2003
Boot0000* EFI USB Device (Generic Flash Disk) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0x2c534026,0x3c4,0x1340)RC
Boot0001* Windows Boot Manager HD(3,GPT,b754471d-a97d-413d-a5c9-a18d7df134e6,0x363800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0002* Ubuntu HD(3,GPT,b754471d-a97d-413d-a5c9-a18d7df134e6,0x363800,0x82000)/File(\EFI\ubuntu\grubx64.efi)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
ff6d345785671fbcea9561a3cbc47702 sda1/Boot/bootx64.efi
87b6d22295a16073d8d456fc574441a8 sda1/Microsoft/Boot/bootmgfw.efi
ff6d345785671fbcea9561a3cbc47702 sda2/Boot/bootx64.efi
87b6d22295a16073d8d456fc574441a8 sda2/Microsoft/Boot/bootmgfw.efi
728124f6ec8e22fbdbe7034812c81b95 sda3/Boot/bootx64.efi
c152ec201c37b6e97bbc2207e49d1271 sda3/Boot/fbx64.efi
fdafb5eece6caeccb788c946a28e6872 sda3/Boot/mmx64.efi
f62c28d9b477b6a1a7b1c991b2b6637d sda3/ubuntu/grubx64.efi
fdafb5eece6caeccb788c946a28e6872 sda3/ubuntu/mmx64.efi
728124f6ec8e22fbdbe7034812c81b95 sda3/ubuntu/shimx64.efi
65ad5b21d383bf7e929b760c0365e892 sda3/Microsoft/Boot/bootmgfw.efi
6ac6140f2977efdbfe2c6b6e8e832495 sda3/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
sda2 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda3 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda5 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda6 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda8 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda9 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ng, update-grub, farbios
Partitions info (2/3): _________________________________________________________
sda1 : maybeESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda2 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, bootmgr, is-winboot
sda3 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, bootmgr, is-winboot
sda5 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, notwinboot
sda6 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sda8 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda9 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda2 : not-sepboot, no-boot, 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
sda8 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda9 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Disk identifier: 6812C36A-3B98-4517-AA2C-1F72774B842D
Start End Sectors Size Type
sda1 2048 534527 532480 260M Sony boot partition
sda2 534528 3553279 3018752 1.5G Windows recovery environment
sda3 3553280 4085759 532480 260M EFI System
sda4 4085760 4347903 262144 128M Microsoft reserved
sda5 4347904 826163663 821815760 391.9G Microsoft basic data
sda6 1412999168 1465147391 52148224 24.9G Windows recovery environment
sda7 826165248 826167295 2048 1M BIOS boot
sda8 826167296 827217919 1050624 513M Microsoft basic data
sda9 827217920 1412999167 585781248 279.3G Linux filesystem
Partition table entries are not in disk order.
Disk sdb: 3.8 GiB, 4026531840 bytes, 7864320 sectors
Disk identifier: 0x2c534026
Boot Start End Sectors Size Id Type
sdb1 * 0 1802239 1802240 880M 0 Empty
sdb2 964 5891 4928 2.4M ef EFI (FAT-12/16/32)
Disk zram0: 953.5 MiB, 999800832 bytes, 244092 sectors
Disk zram1: 953.5 MiB, 999800832 bytes, 244092 sectors
parted -lm (filtered): _________________________________________________________
sda:750GB:scsi:512:4096:gpt:ATA TOSHIBA MQ01ABD0:;
1:1049kB:274MB:273MB:fat32:EFI system partition:hidden;
2:274MB:1819MB:1546MB:ntfs:Basic data partition:hidden, diag;
3:1819MB:2092MB:273MB:fat32:EFI system partition:boot, esp;
4:2092MB:2226MB:134MB::Microsoft reserved partition:msftres;
5:2226MB:423GB:421GB:ntfs::msftdata;
7:423GB:423GB:1049kB:::bios_grub;
8:423GB:424GB:538MB:fat32::msftdata;
9:424GB:723GB:300GB:ext4::;
6:723GB:750GB:26.7GB:ntfs:Basic data partition:hidden, diag;
sdb:4027MB:scsi:512:512:msdos:Generic Flash Disk:;
2:494kB:3017kB:2523kB:::esp;
zram1:1000MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1000MB:1000MB:linux-swap(v1)::;
zram0:1000MB:unknown:4096:4096:loop:Unknown:;
1:0.00B:1000MB:1000MB:linux-swap(v1)::;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 2E42-502E 75326f14-c728-4104-b6ed-3ac4075adca3 SONYSYS EFI system partition
├─sda2 ntfs 1402AF5D02AF429A f146b459-db15-4b31-9a77-e9ff2a7fcd99 Windows RE tools Basic data partition
├─sda3 vfat 32AF-0ADB b754471d-a97d-413d-a5c9-a18d7df134e6 EFI system partition
├─sda4 d3d69d49-2c68-46fe-83a9-32417039bcd9 Microsoft reserved partition
├─sda5 ntfs 12B4B062B4B04A4D 3ccf5949-6ca9-4e6b-b2bc-450709b8aa47 Basic data partition
├─sda6 ntfs 3402B64202B6093E 3a745fdf-49ac-477c-9a22-49323354db5d Recovery Basic data partition
├─sda7 9eae0c74-ec3a-429e-be9e-3f4f6977aeda
├─sda8 vfat 37BE-D875 8424ed41-8284-4d1e-a7d4-d9182ef385a1
└─sda9 ext4 93d985a0-cca9-4d60-b5f1-e6e936e89c21 9f8738dd-8710-4589-84bc-04f056c2ae4b
sdb iso9660 2020-06-13-00-42-55-00 Boot-Repair-Disk 64bit
├─sdb1 iso9660 2020-06-13-00-42-55-00 2c534026-01 Boot-Repair-Disk 64bit
└─sdb2 vfat D055-8513 2c534026-02 Boot-Repair-Disk 64bit
zram0
zram1
df (filtered): _________________________________________________________________
Avail Use% Mounted on
sda1 236M 8% /mnt/boot-sav/sda1
sda2 766.8M 48% /mnt/boot-sav/sda2
sda3 203.6M 19% /mnt/boot-sav/sda3
sda5 274.3G 30% /mnt/boot-sav/sda5
sda6 1.6G 94% /mnt/boot-sav/sda6
sda8 512M 0% /mnt/boot-sav/sda8
sda9 160.9G 37% /mnt/boot-sav/sda9
sdb 0 100% /cdrom
Mount options: __________________________________________________________________
sda1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda2 ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda3 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda5 ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda6 ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda8 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda9 rw,relatime
sdb ro,noatime,nojoliet,check=s,map=n,blocksize=2048
===================== sda3/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid 12c03c18-bf6b-4753-bcff-f5c7146924bd root hd0,gpt10
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
====================== sda9/boot/grub/grub.cfg (filtered) ======================
Ubuntu 93d985a0-cca9-4d60-b5f1-e6e936e89c21
Ubuntu, with Linux 6.8.0-45-generic 93d985a0-cca9-4d60-b5f1-e6e936e89c21
Ubuntu, with Linux 6.5.0-35-generic 93d985a0-cca9-4d60-b5f1-e6e936e89c21
Ubuntu, with Linux 5.15.0-122-generic 93d985a0-cca9-4d60-b5f1-e6e936e89c21
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###
========================== sda9/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda9 during installation
UUID=93d985a0-cca9-4d60-b5f1-e6e936e89c21 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda8 during installation
UUID=37BE-D875 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
======================= sda9/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=true
GRUB_INIT_TUNE="480 440 1"
==================== sda9: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
494.859428406 = 531.351265280 boot/grub/grub.cfg 1
438.585353851 = 470.927437824 boot/grub/i386-pc/core.img 1
489.190425873 = 525.264220160 boot/vmlinuz 2
402.729488373 = 432.427495424 boot/vmlinuz-5.15.0-122-generic 2
493.945884705 = 530.370355200 boot/vmlinuz-6.5.0-35-generic 1
489.190425873 = 525.264220160 boot/vmlinuz-6.8.0-45-generic 2
402.729488373 = 432.427495424 boot/vmlinuz.old 2
491.382514954 = 527.617957888 boot/initrd.img 1
474.940425873 = 509.963399168 boot/initrd.img-5.15.0-122-generic 8
491.674800873 = 527.931797504 boot/initrd.img-6.5.0-35-generic 4
491.382514954 = 527.617957888 boot/initrd.img-6.8.0-45-generic 1
474.940425873 = 509.963399168 boot/initrd.img.old 8
===================== sda9: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 18683 Apr 15 2022 10_linux
-rwxr-xr-x 1 root root 43031 Apr 15 2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18 2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Apr 15 2022 30_os-prober
-rwxr-xr-x 1 root root 1372 Apr 15 2022 30_uefi-firmware
-rwxr-xr-x 1 root root 700 Feb 21 2022 35_fwupd
-rwxr-xr-x 1 root root 214 Jan 13 2021 40_custom
-rwxr-xr-x 1 root root 215 Apr 15 2022 41_custom
=========================== sda9/etc/grub.d/35_fwupd ===========================
#! /bin/sh
# SPDX-License-Identifier: LGPL-2.1+
set -e
[ -d ${pkgdatadir:?} ]
# shellcheck source=/dev/null
. "$pkgdatadir/grub-mkconfig_lib"
if [ -f /var/lib/fwupd/uefi_capsule.conf ] &&
ls /sys/firmware/efi/efivars/fwupd-*-0abba7dc-e516-4167-bbf5-4d9d1c739416 1>/dev/null 2>&1; then
. /var/lib/fwupd/uefi_capsule.conf
if [ "${EFI_PATH}" != "" ] && [ "${ESP}" != "" ]; then
echo "Adding Linux Firmware Updater entry" >&2
cat << EOF
menuentry 'Linux Firmware Updater' \$menuentry_id_option 'fwupd' {
EOF
${grub_probe:?}
prepare_grub_to_access_device '`${grub_probe} --target=device \${ESP}` | sed -e "s/^/\t/"'
cat << EOF
chainloader ${EFI_PATH}
}
EOF
fi
fi
====================== sdb/boot/grub/grub.cfg (filtered) =======================
Boot-Repair-Disk session
Boot-Repair-Disk session (failsafe)
==================== sdb: Location of files loaded by Grub =====================
GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1
======================== Unknown MBRs/Boot Sectors/etc =========================
Unknown GPT Partiton Type
329701f46e06124e8273346c5641494f
Unknown BootLoader on sdb
00000000 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 |3...............|
00000010 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 |................|
00000020 33 ed fa 8e d5 bc 00 7c fb fc 66 31 db 66 31 c9 |3......|..f1.f1.|
00000030 66 53 66 51 06 57 8e dd 8e c5 52 be 00 7c bf 00 |fSfQ.W....R..|..|
00000040 06 b9 00 01 f3 a5 ea 4b 06 00 00 52 b4 41 bb aa |.......K...R.A..|
00000050 55 31 c9 30 f6 f9 cd 13 72 16 81 fb 55 aa 75 10 |U1.0....r...U.u.|
00000060 83 e1 01 74 0b 66 c7 06 f3 06 b4 42 eb 15 eb 02 |...t.f.....B....|
00000070 31 c9 5a 51 b4 08 cd 13 5b 0f b6 c6 40 50 83 e1 |1.ZQ....[...@P..|
00000080 3f 51 f7 e1 53 52 50 bb 00 7c b9 04 00 66 a1 b0 |?Q..SRP..|...f..|
00000090 07 e8 44 00 0f 82 80 00 66 40 80 c7 02 e2 f2 66 |..D.....f@.....f|
000000a0 81 3e 40 7c fb c0 78 70 75 09 fa bc ec 7b ea 44 |.>@|..xpu....{.D|
000000b0 7c 00 00 e8 83 00 69 73 6f 6c 69 6e 75 78 2e 62 ||.....isolinux.b|
000000c0 69 6e 20 6d 69 73 73 69 6e 67 20 6f 72 20 63 6f |in missing or co|
000000d0 72 72 75 70 74 2e 0d 0a 66 60 66 31 d2 66 03 06 |rrupt...f`f1.f..|
000000e0 f8 7b 66 13 16 fc 7b 66 52 66 50 06 53 6a 01 6a |.{f...{fRfP.Sj.j|
000000f0 10 89 e6 66 f7 36 e8 7b c0 e4 06 88 e1 88 c5 92 |...f.6.{........|
00000100 f6 36 ee 7b 88 c6 08 e1 41 b8 01 02 8a 16 f2 7b |.6.{....A......{|
00000110 cd 13 8d 64 10 66 61 c3 e8 1e 00 4f 70 65 72 61 |...d.fa....Opera|
00000120 74 69 6e 67 20 73 79 73 74 65 6d 20 6c 6f 61 64 |ting system load|
00000130 20 65 72 72 6f 72 2e 0d 0a 5e ac b4 0e 8a 3e 62 | error...^....>b|
00000140 04 b3 07 cd 10 3c 0a 75 f1 cd 18 f4 eb fd 00 00 |.....<.u........|
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 04 17 00 00 00 00 00 00 26 40 53 2c 00 00 80 00 |........&@S,....|
000001c0 01 00 00 3f e0 6f 00 00 00 00 00 80 1b 00 00 fe |...?.o..........|
000001d0 ff ff ef fe ff ff c4 03 00 00 40 13 00 00 00 00 |..........@.....|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=============================== StdErr Messages ================================
File descriptor 63 (pipe:[55601]) leaked on lvs invocation. Parent PID 19262: /bin/bash
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
sda9,
using the following options: sda3/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file
Confirmation request before suggested repair: __________________________________
Warning: continuing without internet would leave your system unbootable. Please connect internet.
The boot of your PC is in Secure mode. You may want to retry after changing it to non-Secure mode.
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 22.04.4 LTS entry (sda3/efi/****/shim****.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\****\shim****.efi (**** will be updated in the final message)Dernière modification par jpl-bz (Le 18/10/2024, à 10:44)
Hors ligne
#2 Le 18/10/2024, à 10:42
- jpl-bz
Re : utiliser le dernier boot-repair en session live Ubuntu + cas réel
Une part envisagée du traitement préalable, pour simplifier (Grub, etc) et gagner de la place, après sauvegarde des données en exemplaire unique, consisterait à ne laisser du windows que le minimum.
A-t-il besoin des sda1 à sda8 en totalité (2 niveaux de mise à jour windows selon mentions sda1 à sda6 ? recovery utile ou pas à ce jour ?) ?
Je vois les éléments de place à gagner dans le rapport boot-info :
(Je ne suis pas l'auteur des mises à jour Windows.)
fdisk -l (filtered): ___________________________________________________________
Disk sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Disk identifier: 6812C36A-3B98-4517-AA2C-1F72774B842D
Start End Sectors Size Type
sda1 2048 534527 532480 260M Sony boot partition
sda2 534528 3553279 3018752 1.5G Windows recovery environment
sda3 3553280 4085759 532480 260M EFI System
sda4 4085760 4347903 262144 128M Microsoft reserved
sda5 4347904 826163663 821815760 391.9G Microsoft basic data
sda6 1412999168 1465147391 52148224 24.9G Windows recovery environment
sda7 826165248 826167295 2048 1M BIOS boot
sda8 826167296 827217919 1050624 513M Microsoft basic data
sda9 827217920 1412999167 585781248 279.3G Linux filesystem
Partition table entries are not in disk order.Windows 8 est évoqué dans sda1 à sda6
Windows 10 dans
================================ 2 OS detected =================================
OS#1: Ubuntu 22.04.4 LTS on sda9
OS#2: Windows 10 on sda5Vos rapports boot-info de machines plus simples UEFI/Ubuntu/Windows vous indiquent combien de disques nécessaires ?
cordialement
Hors ligne
#3 Le 18/10/2024, à 11:02
- geole
Re : utiliser le dernier boot-repair en session live Ubuntu + cas réel
Bonjour.
extrait du boot-info.
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot enabled.Donc la partition de boot legacy est inutile.
( initialement tu as du probablement faire une installation en legacy qui n'a pas détecté windows),
sda7: __________________________________________________________________________
File system: BIOS Boot partition
Boot sector type: Grub2's core.img
Boot sector info: Normalement, tu peux te passer de la partition de remise à l'état usine.
Si tu la lances, tu vas détruire ubuntu.
sda6 1412999168 1465147391 52148224 24.9G Windows recovery environmentSDA1 est livré par le constructeur de l'ordinateur.
sda1 2048 534527 532480 260M Sony boot partition
Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/memtest.efiA priori, il ne contient pas grand chose. De plus, c'est aussi dans SDA3. Mais vu sa position, récupérer son espace disque est compliqué. Il faudrait déplacer les partitions.
Je ne comprends pas ton boot EFI. Tu n'as pas de partition 10!
===================== sda3/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid 12c03c18-bf6b-4753-bcff-f5c7146924bd root hd0,gpt10 Fais donc la réparation recommandée.
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of sda9, using the following options: sda3/boot/efi,Dernière modification par geole (Le 18/10/2024, à 11:23)
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
#4 Le 18/10/2024, à 20:58
- jpl-bz
Re : utiliser le dernier boot-repair en session live Ubuntu + cas réel
... parmi les questions il y a la façon d'installer actualiser le boot-repair pendant une session live ubuntu (autre?) . On peut s'inspirer de
sudo add-apt-repository -y ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-repair ; boot-repairsuggéré dans https://forum.ubuntu-fr.org/viewtopic.p … #p22502723 ? ... ou pas ?
Hors ligne
#5 Le 18/10/2024, à 21:09
- geole
Re : utiliser le dernier boot-repair en session live Ubuntu + cas réel
On peut aussi lire la documentation ubuntu.
https://doc.ubuntu-fr.org/boot-repair a écrit :
Installer Boot-Repair depuis une session live (DVD ou liveUSB) de Ubuntu
Si vous disposez d’un liveDVD (ou d'une liveUSB) de Ubuntu, et que votre PC en panne a une connexion internet, vous pouvez installer Boot-Repair temporairement:Démarrer l’ordinateur sur le live CD (ou la liveUSB) Ubuntu;
Choisir Essayer Ubuntu;
Si ce n'est pas déjà fait, connecter internet et vérifier qu'il fonctionne.
ping -c5 google.com
Puis installer le logiciel en faisant un copier/coller de la commande suivante dans un terminal :
sudo add-apt-repository -y ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-repair ; boot-repair
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
#6 Le 28/10/2024, à 11:05
- jpl-bz
Re : utiliser le dernier boot-repair en session live Ubuntu + cas réel
ok, merci c'est bien ça ... à suivre test réel plus tard.
Dernière modification par jpl-bz (Le 28/10/2024, à 11:06)
Hors ligne