Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 03/06/2020, à 18:55

beekeeper

"minimal bash-like line" au démarrage

Bonjour à tou.te.s,

Un problème assez fréquent semble-t-il...
Donc, sur le portable d'un ami, ce message au démarrage de grub.

J'ai créé un boot info en live. L'adresse est ici: http://paste.ubuntu.com/p/8yWShvcQBs/
Merci beaucoup pour votre aide...

Hors ligne

#2 Le 03/06/2020, à 19:03

lucmars

Re : "minimal bash-like line" au démarrage

Le boot-info.e.s.z.y.x

boot-info-4ppa124                                              [20200603_1745]

============================== Boot Info Summary ===============================

 => No boot loader is installed in the MBR of /dev/sda.
 => Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (,msdos1)/boot/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp fat part_msdos 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/fbx64.efi /efi/Boot/shimx64.efi 
                       /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi 
                       /efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg

sda2: __________________________________________________________________________

    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:        /boot/grub/grub.cfg

sda3: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.05 20140113
    Boot sector info:  Syslinux looks at sector 6329536 of /dev/sdb1 for its 
                       second stage. SYSLINUX is installed in the 
                       /boot/syslinux directory. No errors found in the Boot 
                       Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/menu.lst /boot/grub/grub.cfg 
                       /boot/syslinux/syslinux.cfg /efi/BOOT/grubx64.efi 
                       /boot/grub/i386-pc/core.img /boot/syslinux/ldlinux.sys


================================ 0 OS detected =================================


============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Ubuntu 18.04.4 LTS, bionic, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled.

efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* ubuntu	HD(1,GPT,0c4eef51-9ec6-44db-aec0-3c88a10b9135,0x800,0x1a9000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: VerbatimSTORE N GO 5.00, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,MBR,0x50660fda,0x1f80,0x1cd8080)..BO

bed45d1c9554cea09924d3814cb7c446   sda1/Boot/fbx64.efi
6e94c3d33194c89bd327bfaa5871e294   sda1/Boot/shimx64.efi
64a633007e3d5a9a5943e417442548d6   sda1/ubuntu/grubx64.efi
4487628005555bfd4a4c0a47211e0700   sda1/ubuntu/mmx64.efi
f7a57b08bc7c1c85417ae4cea582d1d4   sda1/ubuntu/shimx64.efi
f7a57b08bc7c1c85417ae4cea582d1d4   sda1/Boot/BOOTX64.efi
1bd54ad95660feab365d15299242ff9f   sdb1/BOOT/grubx64.efi
7095619324a9fb786422d7427c056405   sdb1/BOOT/BOOTx64.efi


============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sda	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, no-os,	2048 sectors * 512 bytes
sdb	: notGPT,	no-BIOSboot,	has---ESP, 	liveusb,	not-mmc, no-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
sdb1	: 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,	farbios

Partitions info (2/3): _________________________________________________________

sda1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot
sda2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot
sdb1	: 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,	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-kernel,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	std-grub.d,	sda
sdb1	: not-sepboot,	no-kernel,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	std-grub.d,	sdb
sda3	: maybesepboot,	no-boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	std-grub.d,	sda

fdisk -l (filtered): ___________________________________________________________

Disk identifier: 0x6e037a9d
        Boot Start     End Sectors  Size Id Type
loop0p1 *        0 4153407 4153408    2G  0 Empty
loop0p2      12012   16939    4928  2.4M ef EFI (FAT-12/16/32)
Disk sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 5F9CA664-B9D9-457A-8FE4-28772DE28B6E
         Start        End    Sectors   Size Type
sda1      2048    1742847    1740800   850M EFI System
sda2   1742848   12228607   10485760     5G Microsoft reserved
sda3  12228608 1953523711 1941295104 925.7G Linux filesystem
Disk sdb: 14.4 GiB, 15489564672 bytes, 30253056 sectors
Disk identifier: 0x50660fda
      Boot Start      End  Sectors  Size Id Type
sdb1  *     8064 30253055 30244992 14.4G  c W95 FAT32 (LBA)

parted -lm (filtered): _________________________________________________________

sda:1000GB:scsi:512:4096:gpt:ATA TOSHIBA MQ04ABF1:;
1:1049kB:892MB:891MB:fat32:EFI system partition:boot, esp;
2:892MB:6261MB:5369MB:fat32:Basic data partition:msftres;
3:6261MB:1000GB:994GB:::;
sdb:15.5GB:scsi:512:512:msdos:Verbatim STORE N GO:;
1:4129kB:15.5GB:15.5GB:fat32::boot, lba;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda                                                                                                                
├─sda1 vfat     F64B-7325                            0c4eef51-9ec6-44db-aec0-3c88a10b9135 ESP                      EFI system partition
├─sda2 vfat     228A-A60E                            e0d6e699-f13a-4418-8ec0-77d91a444830 OS                       Basic data partition
└─sda3                                               0a485755-896a-447f-a213-8b6497156341                          
sdb                                                                                                                
└─sdb1 vfat     50B9-9A96                            50660fda-01                          STORE                    

df (filtered): _________________________________________________________________

       Avail Use% Mounted on
sda1   819.1M   3% /mnt/boot-sav/sda1
sda2     2.4G  52% /mnt/boot-sav/sda2
sdb1     1.5G  89% /isodevice

Mount options: __________________________________________________________________

sda1   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda2   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sdb1   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================

search.fs_uuid 3423293f-448e-40be-b3d7-763d40ded600 root hd0,gpt3 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

====================== sda2/boot/grub/grub.cfg (filtered) ======================

Install Complete, remove media and reboot.
Dell Recovery
Dell Recovery (safe graphics mode)

==================== sda2: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1

====================== sdb1/boot/grub/menu.lst (filtered) ======================

# This is a sample menu.lst file. You should make some changes to it.
# The old install method of booting via the stage-files has been removed.
# Please install GRLDR boot strap code to MBR with the bootlace.com
# utility under DOS/Win9x or Linux.
timeout 30
default /default
#convert -resize 640x480 -colors 14 /media/multisystem/boot/splash/splash.png /media/multisystem/boot/splash/splash.xpm.gz
splashimage=/boot/splash/splash.xpm.gz
#color blue/green yellow/red white/magenta white/magenta
foreground=0033FF
background=FF3300
#http://diddy.boot-land.net/grub4dos/Grub4dos.htm
#http://www.boot-land.net/forums/index.php?showforum=66
#http://diddy.boot-land.net/grub4dos/files/syntax.htm
#Ne supprimez pas ce marqueur! / Do not remove this marker!
#MULTISYSTEM_START
#MULTISYSTEM_STOP
#Ne supprimez pas ce marqueur! / Do not remove this marker!
#http://diddy.boot-land.net/grub4dos/files/syntax.htm
title Chainloader into GRUB 2
find --set-root /boot/grub/boot.img
chainloader /boot/grub/boot.img
boot
#title Chainloader into Syslinux
#map (hd0) (hd0)
#map (hd0) (hd0)
#chainloader (hd0,0)+1
#rootnoverify (hd0,0)
##Autre solution pour chainer Syslinux
##faire une copie du mbr de la clé USB
##dd if=/dev/sd?1 of=/media/multisystem/syslinux.mbr bs=512 count=1
#title Chainloader into Syslinux
#find --set-root --ignore-floppies --ignore-cd /syslinux.mbr
#map (hd0) (hd0)
#map (hd0) (hd0)
#map --rehook
#find --set-root --ignore-floppies --ignore-cd /syslinux.mbr
#chainloader /syslinux.mbr
##Autre solution pour chainer Syslinux
#title Chainloader into Syslinux
#find --set-root /boot/syslinux/ldlinux.sys
#chainloader /boot/syslinux/ldlinux.sys
##Autre solution pour chainer Syslinux
#title Chainloader into Syslinux
#find --set-root --ignore-floppies --ignore-cd /boot/syslinux/redir.img
#kernel /boot/syslinux/memdisk
#initrd /boot/syslinux/redir.img
#http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/
title FreeDos
kernel /boot/syslinux/memdisk
initrd /boot/img/fdboot.img
title find and load NTLDR of Windows NT/2K/XP
fallback 1
find --set-root --ignore-floppies --ignore-cd /ntldr
map () (hd0)
map (hd0) ()
map --rehook
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
savedefault --wait=2
title find and load BOOTMGR of Windows VISTA/SEVEN
fallback 2
find --set-root --ignore-floppies --ignore-cd /bootmgr
map () (hd0)
map (hd0) ()
map --rehook
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
savedefault --wait=2
title find and load CMLDR, the Recovery Console of Windows NT/2K/XP
fallback 3
find --set-root --ignore-floppies --ignore-cd /cmldr
map () (hd0)
map (hd0) ()
map --rehook
find --set-root --ignore-floppies --ignore-cd /cmldr
chainloader /cmldr
#####################################################################
# write string "cmdcons" to memory 0000:7C03 in 2 steps:
#####################################################################
# step 1. Write 4 chars "cmdc" at 0000:7C03
write 0x7C03 0x63646D63
# step 2. Write 3 chars "ons" and an ending null at 0000:7C07
write 0x7C07 0x00736E6F
savedefault --wait=2
title find and load IO.SYS of Windows 9x/Me
fallback 4
find --set-root /io.sys
chainloader /io.sys
savedefault --wait=2
title find and boot 0PE.ISO
fallback 5
find --set-root /0PE/0PE.ISO
map /0PE/0PE.ISO (0xff) || map --mem /0PE/0PE.ISO (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2
title find and boot MicroPE.ISO
fallback 6
find --set-root /boot/MicroPE.ISO
map /boot/MicroPE.ISO (0xff) || map --mem /boot/MicroPE.ISO (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2
title find and boot ubcd.iso
fallback 8
find --set-root /ubcd.iso
map /ubcd.iso (0xff) || map --mem /ubcd.iso (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2
title commandline
commandline
title reboot
reboot
title halt
halt

====================== sdb1/boot/grub/grub.cfg (filtered) ======================

PrimTux
PrimTux xforcevesa
HandyLinux Live
HandyLinux Installation
Emmabuntüs V2 Debian Stretch amd64
Voyager-18.04-amd64.iso
xubuntu-18.04.1-desktop-amd64.iso
ubuntu-18.04.4-desktop-amd64.iso
______________Grub4Dos______________
Grub4Dos
______________Syslinux______________
Syslinux
Syslinux
Syslinux
______________UTIL______________
0-testfakebios
Windows 7 BIOS/MBR
Windows XP BIOS/MBR
grub.cfg auf sdb1
Chain other configfile
Return default menu
Chainer UUID de la partition
PLoP Boot Manager
Super Grub2 Disk
Super Grub Disk
Smart Boot Manager
BKO (boot.kernel.org)
vbeinfo
lspci
gfxpayload 640x480
gfxpayload 800x600
gfxpayload 1024x768
gfxpayload 1280x1024
Reboot

================== sdb1/boot/syslinux/syslinux.cfg (filtered) ==================

default /boot/syslinux/vesamenu.c32
prompt 0
timeout 40
ontimeout 0
MENU TITLE MultiSystem LiveUSB
MENU DEFAULT 0
MENU BACKGROUND /boot/splash/splash.png
#Ne supprimez pas ce marqueur! / Do not remove this marker!
#MULTISYSTEM_START
#MULTISYSTEM_MENU_DEBUT|19-01-2016-15:07:57-978891148|slitaz1|multisystem-slitaz|34Mio|
label 27405
MENU LABEL slitaz
KERNEL /slitaz1/boot/bzImage
append initrd=/slitaz1/boot/rootfs4.gz,/slitaz1/boot/rootfs3.gz,/slitaz1/boot/rootfs2.gz,/slitaz1/boot/rootfs1.gz rw root=/dev/null autologin
#MULTISYSTEM_MENU_FIN|19-01-2016-15:07:57-978891148|slitaz1|multisystem-slitaz|34Mio|
#MULTISYSTEM_STOP
#Ne supprimez pas ce marqueur! / Do not remove this marker!
label 0
MENU LABEL PLoP Boot Manager
KERNEL /boot/img/plpbt
label 1
MENU LABEL Grub2
kernel /boot/syslinux/chain.c32 file=/boot/grub/boot.img
label 2
MENU LABEL Grub4Dos
kernel /boot/grub.exe
LABEL 3
MENU LABEL Hardware Detection Tool
KERNEL /boot/syslinux/hdt.c32
#Exemple pour booter un iso avec version recente de memdisk
#label 4
#MENU LABEL boot iso
#KERNEL /boot/syslinux/memdisk
#APPEND iso raw initrd=/g4u.iso
#LABEL 5
#KERNEL /boot/syslinux/memdisk
#APPEND initrd=freebsd.img floppy
#LABEL 6
#MENU LABEL Chainer win
#KERNEL /boot/syslinux/chain.c32 ntldr=/ntldr
#LABEL 7
#MENU LABEL Chainer partition 2
#kernel /boot/syslinux/chain.c32
#append hd0 2

==================== sdb1: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/menu.lst                             1
            ?? = ??             boot/grub/grub.cfg                             1
            ?? = ??             boot/grub/i386-pc/core.img                     1

================== sdb1: Location of files loaded by Syslinux ==================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/syslinux/syslinux.cfg                     1
            ?? = ??             boot/syslinux/ldlinux.sys                      1
            ?? = ??             boot/syslinux/chain.c32                        1
            ?? = ??             boot/syslinux/hdt.c32                          1
            ?? = ??             boot/syslinux/ifplop.c32                       1
            ?? = ??             boot/syslinux/menu.c32                         1
            ?? = ??             boot/syslinux/reboot.c32                       1
            ?? = ??             boot/syslinux/vesamenu.c32                     1

=============== sdb1: Version of COM32(R) files used by Syslinux ===============

 boot/syslinux/chain.c32            :  COM32R module (v4.xx)
 boot/syslinux/hdt.c32              :  COM32R module (v4.xx)
 boot/syslinux/ifplop.c32           :  COM32R module (v4.xx)
 boot/syslinux/menu.c32             :  COM32R module (v4.xx)
 boot/syslinux/reboot.c32           :  COM32R module (v4.xx)
 boot/syslinux/vesamenu.c32         :  COM32R module (v4.xx)


=============================== StdErr Messages ================================

File descriptor 63 (pipe:[98294]) leaked on lvs invocation. Parent PID 16990: /bin/bash

Error code 12
mount -r /dev/sda3 /mnt/boot-sav/sda3

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

mount -r /dev/sda3 : Error code 12
Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

Dernière modification par lucmars (Le 03/06/2020, à 19:05)


Gaulois Matter !

Hors ligne

#3 Le 04/06/2020, à 08:55

malbo

Re : "minimal bash-like line" au démarrage

Bonjour,
Le Boot-info indique qu'il n'y a plus d'OS vivant dans cet ordi. Il y a bien des traces d'une installation de Ubuntu dans la partition sda1 mais c'est tout.

Hors ligne

#4 Le 04/06/2020, à 12:36

beekeeper

Re : "minimal bash-like line" au démarrage

malbo a écrit :

Bonjour,
Le Boot-info indique qu'il n'y a plus d'OS vivant dans cet ordi. Il y a bien des traces d'une installation de Ubuntu dans la partition sda1 mais c'est tout.

Ouh la la, ça veut dire quoi ça ? Mauvaise manip qui aurait tout supprimé ? Pas même de /home ? Donc toutes les données ont disparu ??
Faut réinstaller alors c'est bien ça ?...

à Lucmars: ça veut dire quoi e.s.z.y.x ?

Hors ligne

#5 Le 04/06/2020, à 12:48

malbo

Re : "minimal bash-like line" au démarrage

Il y a peut-être moyen de récupérer des données mais moi je ne m'implique pas là-dedans. Si ton ami veut absolument récupérer les données et qu'il peut payer pour ça, il peut demander un devis à un spécialiste  (voir Rémy SABATIER ici)

Dernière modification par malbo (Le 04/06/2020, à 12:49)

Hors ligne