Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Erreur au démarrage en dual boot

noje

Tente encore ça depuis le live USB:

sudo fsck.ext4 -v /dev/sda6

Réponds Yes et All a toute les proposition reboot pour voir.

Arnaud01500

Resultat


/dev/sda6: ***** FILE SYSTEM WAS MODIFIED *****

      209819 inodes used (11.18%, out of 1875968)
          96 non-contiguous files (0.0%)
         264 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 182446/34
     2423979 blocks used (32.32%, out of 7500032)
           0 bad blocks
           1 large file

      154610 regular files
       25252 directories
           9 character device files
           0 block device files
           0 fifos
          94 links
       29939 symbolic links (27322 fast symbolic links)
           0 sockets
------------
      209904 files

Arnaud01500

Après le redémarrage, j"arrive bien sur la page de connexion Linux donc il y a eu de l'amélioration.
Par contre je peux pas rentrer quand je met mon mot de passe, ça mouline un peu quand je met le mot de passe et je reviens sur l'écran de connexion.

noje

Passe en tty (ctrl+alt+F3 ou F2) rentre ton nom d’utilisateur et mot de passe manuellement.
Pour voir si ça passe ainsi.

Arnaud01500

J'ai redémarré mais de nouveau ce message d'erreur https://ibb.co/0m5n0CV
J'ai réessayé puis retour à la configuration initiale.

noje

Depuis une live usb installe gnome-disks (si il n’est pas présent par défaut, après ça dépend encore de la version d’Ubuntu).
Lance-le, puis sélectionne ton disque SSD si présent, clique sur les 3 barres en haut à droit puis « Données smart et auto-test » ou CTRL+S.

Regarde ce que ça te dit, après je sèche pense que tu as un gros soucis soit au niveau du disque (puisqu’il ne se répare pas ou alors au niveau du système).

Arnaud01500

J'obtiens ce résultat https://ibb.co/yWhSPS0
Est ce que tu me conseilles de changer le SSD ?

geole

Arnaud01500 a écritJe n'ai pas fais smartmontools car apparemment déconseillé sur les SSD.

Bonjour
Il ne faut pas le tester! Il faut demander son état c'est le chapitre 3 et pas le chapitre 2

Arnaud01500

J'ai fais la commande

sudo apt install nvme-cli

Après un redémarrage je suis toujours bloqué au démarrage.

Arnaud01500

Résultat de la commande

sudo apt install nvme-cli
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package nvme-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'nvme-cli' has no installation candidate

geole

Assez surprenant
Peux-tu donner ce retour

lsb_release -a && cat /etc/os-release

Arnaud01500

Le retour

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

geole

Je ne comprends pas. Si tu réessayais?

Arnaud01500

J'ai reessayé mais je suis toujours bloqué sur initramfs au démarrage de Ubuntu.

geole

Désolé
A croire qu'il y a un problème avec ton ssd

NOTA, je suis en train de réaliser que si tu dis avoir un nvme, le disque ne devrait pas s'appeler sda mais nvme

Avec le support d'installation
1) installation des logiciels

sudo add-apt-repository -y ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-info

sudo apt-get install --no-install-recommends smartmontools

2) Exécuter un boot-info et donner l'URL qui va être généré

sudo boot-info

3) Poster le retour de cette commande

sudo smartctl -s on -a /dev/sda

4) Installer de nouveau l'application, en espérant que cela aille mieux

sudo apt install nvme-cli

5) poster ces retours en mettant le bon nom

sudo nvme nvme-error-log /dev/sda
sudo nvme nvme-smart-log /dev/sda

6) réparer la partition comme tu l'as déjà fait.

sudo fsck  -y  /dev/sda6

7) et un second passage dont tu donneras le retour

sudo fsck -y   /dev/sda6

Puis reboot pour voir

Arnaud01500

Bonjour
URL généré par boot-info
https://paste.ubuntu.com/p/csX5dGTbM3/

Retour de smartctl

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-42-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 860 EVO M.2 500GB
Serial Number:    S414NB0M124876P
LU WWN Device Id: 5 002538 e40c7635b
Firmware Version: RVT22B6Q
User Capacity:    500107862016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Dec 22 05:25:46 2020 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  85) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       3733
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       1231
177 Wear_Leveling_Count     0x0013   098   098   000    Pre-fail  Always       -       17
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   076   054   000    Old_age   Always       -       24
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       68
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       10895693262

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3728         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Installation de nvme-cli sans erreur cette fois.

Je bloque a cette étape pour voir les erreurs.

sudo nvme nvme-error-log /dev/sda6
ERROR: Invalid sub-command 'nvme-error-log'
nvme-1.9
usage: nvme <command> [<device>] [<args>]

The '<device>' may be either an NVMe character device (ex: /dev/nvme0) or an
nvme block device (ex: /dev/nvme0n1).

The following are all implemented sub-commands:
  list                  List all NVMe devices and namespaces on machine
  list-subsys           List nvme subsystems
  id-ctrl               Send NVMe Identify Controller
  id-ns                 Send NVMe Identify Namespace, display structure
  id-ns-granularity     Send NVMe Identify Namespace Granularity List, display structure
  list-ns               Send NVMe Identify List, display structure
  list-ctrl             Send NVMe Identify Controller List, display structure
  list-secondary        List Secondary Controllers associated with a Primary Controller
  ns-descs              Send NVMe Namespace Descriptor List, display structure
  id-nvmset             Send NVMe Identify NVM Set List, display structure
  id-uuid               Send NVMe Identify UUID List, display structure
  create-ns             Creates a namespace with the provided parameters
  delete-ns             Deletes a namespace from the controller
  attach-ns             Attaches a namespace to requested controller(s)
  detach-ns             Detaches a namespace from requested controller(s)
  get-ns-id             Retrieve the namespace ID of opened block device
  get-log               Generic NVMe get log, returns log in raw format
  telemetry-log         Retrieve FW Telemetry log write to file
  fw-log                Retrieve FW Log, show it
  changed-ns-list-log   Retrieve Changed Namespace List, show it
  smart-log             Retrieve SMART Log, show it
  ana-log               Retrieve ANA Log, show it
  error-log             Retrieve Error Log, show it
  effects-log           Retrieve Command Effects Log, show it
  endurance-log         Retrieve Endurance Group Log, show it
  get-feature           Get feature and show the resulting value
  device-self-test      Perform the necessary tests to observe the performance
  self-test-log         Retrieve the SELF-TEST Log, show it
  set-feature           Set a feature and show the resulting value
  set-property          Set a property and show the resulting value
  get-property          Get a property and show the resulting value
  format                Format namespace with new block format
  fw-commit             Verify and commit firmware to a specific slot (fw-activate in old version < 1.2)
  fw-download           Download new firmware
  admin-passthru        Submit an arbitrary admin command, return results
  io-passthru           Submit an arbitrary IO command, return results
  security-send         Submit a Security Send command, return results
  security-recv         Submit a Security Receive command, return results
  get-lba-status        Submit a Get LBA Status command, return results
  resv-acquire          Submit a Reservation Acquire, return results
  resv-register         Submit a Reservation Register, return results
  resv-release          Submit a Reservation Release, return results
  resv-report           Submit a Reservation Report, return results
  dsm                   Submit a Data Set Management command, return results
  flush                 Submit a Flush command, return results
  compare               Submit a Compare command, return results
  read                  Submit a read command, return results
  write                 Submit a write command, return results
  write-zeroes          Submit a write zeroes command, return results
  write-uncor           Submit a write uncorrectable command, return results
  verify                Submit a verify command, return results
  sanitize              Submit a sanitize command
  sanitize-log          Retrieve sanitize log, show it
  reset                 Resets the controller
  subsystem-reset       Resets the subsystem
  ns-rescan             Rescans the NVME namespaces
  show-regs             Shows the controller registers or properties. Requires character device
  discover              Discover NVMeoF subsystems
  connect-all           Discover and Connect to NVMeoF subsystems
  connect               Connect to NVMeoF subsystem
  disconnect            Disconnect from NVMeoF subsystem
  disconnect-all        Disconnect from all connected NVMeoF subsystems
  gen-hostnqn           Generate NVMeoF host NQN
  dir-receive           Submit a Directive Receive command, return results
  dir-send              Submit a Directive Send command, return results
  virt-mgmt             Manage Flexible Resources between Primary and Secondary Controller 
  version               Shows the program version
  help                  Display this help

See 'nvme help <command>' for more information on a specific command

The following are all installed plugin extensions:
  intel           Intel vendor specific extensions
  lnvm            LightNVM specific extensions
  memblaze        Memblaze vendor specific extensions
  wdc             Western Digital vendor specific extensions
  huawei          Huawei vendor specific extensions
  netapp          NetApp vendor specific extensions
  toshiba         Toshiba NVME plugin
  micron          Micron vendor specific extensions
  seagate         Seagate vendor specific extensions
  virtium         Virtium vendor specific extensions
  shannon         Shannon vendor specific extensions

See 'nvme <plugin> help' for more information on a plugin

xubu1957

Bonjour,

Collage du Boot-repair, pour les spécialistes :

boot-info-4ppa125                                              [20201222_0522]

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

 => Windows 7/8/2012 is installed in the MBR of /dev/sda.
 => Windows 7/8/2012 is installed in the MBR of /dev/sdb.
 => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.

sda1: __________________________________________________________________________

    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:        

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:        /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi 
                       /efi/Boot/fbx64.efi /efi/Boot/grubx64.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

sda3: __________________________________________________________________________

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

sda4: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 8 or 10
    Boot files:        /Windows/System32/winload.exe

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:       ext4
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /mnt/BootInfo/sda6: cannot mount; probably corrupted filesystem on /dev/sda6.

sda7: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /mnt/BootInfo/sda7: cannot mount; probably corrupted filesystem on /dev/sda7.

sdb1: __________________________________________________________________________

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

sdb2: __________________________________________________________________________

    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:        

sdc1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 6.04
    Boot sector info:  Syslinux looks at sector 32832 of /dev/sdc1 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 sda6
OS#2:   Windows 8 or 10 on sda4

============================ 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, and is setup in EFI-mode for this live-session.
SecureBoot disabled.

efibootmgr -v
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0002,0000,0001,0003
Boot0000* Windows Boot Manager	HD(2,GPT,bbd354d5-bc6a-4bc6-8993-720d23feb889,0xfa000,0x31800)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.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.}...a................
Boot0001* Hard Drive	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.a.m.s.u.n.g. .S.S.D. .8.6.0. .E.V.O. .M...2. .5.0.0.G.B...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L.4.S.4.1.B.N.M.0.2.1.8.4.6.7. .P. . . . ........BO..NO..........S.T.2.0.0.0.D.M.0.0.6.-.2.D.M.1.6.4...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .4.Z.C.Z.B.K.X.V........BO
Boot0002* ubuntu	HD(2,GPT,bbd354d5-bc6a-4bc6-8993-720d23feb889,0xfa000,0x31800)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0003* USB KEY	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)..GO..NO........y.U.S.B. .D.i.s.k. .3...0. .0.0.0.9...................\.,.@.r.d.=.X..........A.......................6..Gd-.;.A..MQ..L.4.2.7.6.0.4.5.4.7.7.3.3.3.2.5.4........BO
Boot0004* UEFI: USB Disk 3.0 0009, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(22,0)/HD(1,MBR,0x5df8f2,0x800,0x3a01800)..BO

78415fb8fb9b909f8029858113f1335f   sda2/Boot/bkpbootx64.efi
78415fb8fb9b909f8029858113f1335f   sda2/Boot/bootx64.efi
2895d47544fd587b26c7e29be1295c27   sda2/Boot/fbx64.efi
d8b4b9ae3018b1f4612611be7f42507a   sda2/Boot/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84   sda2/Boot/mmx64.efi
8ed07d5ee4e5e1534bcf64037b7589ff   sda2/ubuntu/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84   sda2/ubuntu/mmx64.efi
78415fb8fb9b909f8029858113f1335f   sda2/ubuntu/shimx64.efi
3c080490d0eb8fdb738f298c3e44b3e0   sda2/Microsoft/Boot/bootmgfw.efi
da7c9088c9d0bff4ac469abdfc8f540e   sda2/Microsoft/Boot/bootmgr.efi


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

Disks info: ____________________________________________________________________

sda	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	2048 sectors * 512 bytes
sdb	: is-GPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, no-os,	34 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
sda4	: is-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios
sda5	: no-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios
sda6	: is-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios
sda7	: no-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios
sdb2	: no-os,	32, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	farbios

Partitions info (2/3): _________________________________________________________

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

fdisk -l (filtered): ___________________________________________________________

Disk sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: 0465A9F5-FB44-428C-AB52-02CC9F26EE0B
          Start       End   Sectors   Size Type
sda1       2048   1023999   1021952   499M Windows recovery environment
sda2    1024000   1226751    202752    99M EFI System
sda3    1226752   1259519     32768    16M Microsoft reserved
sda4    1259520 765953528 764694009 364.6G Microsoft basic data
sda5  975669248 976771071   1101824   538M Windows recovery environment
sda6  765954048 825954303  60000256  28.6G Linux filesystem
sda7  825954304 975669247 149714944  71.4G Linux filesystem
Partition table entries are not in disk order.
Disk sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 9256765B-D14C-4AC0-B7AE-74B1D0515A2D
      Start        End    Sectors  Size Type
sdb1     34      32767      32734   16M Microsoft reserved
sdb2  32768 3907026943 3906994176  1.8T Microsoft basic data
Disk sdc: 29 GiB, 31142707200 bytes, 60825600 sectors
Disk identifier: 0x005df8f2
      Boot Start      End  Sectors Size Id Type
sdc1  *     2048 60825599 60823552  29G  c W95 FAT32 (LBA)

parted -lm (filtered): _________________________________________________________

sda:500GB:scsi:512:512:gpt:ATA Samsung SSD 860:;
1:1049kB:524MB:523MB:ntfs:Basic data partition:hidden, diag;
2:524MB:628MB:104MB:fat32:EFI system partition:boot, esp;
3:628MB:645MB:16.8MB::Microsoft reserved partition:msftres;
4:645MB:392GB:392GB:ntfs:Basic data partition:msftdata;
6:392GB:423GB:30.7GB:ext4::;
7:423GB:500GB:76.7GB:ext4::;
5:500GB:500GB:564MB:ntfs::hidden, diag;
sdb:2000GB:scsi:512:4096:gpt:ATA ST2000DM006-2DM1:;
1:17.4kB:16.8MB:16.8MB::Microsoft reserved partition:msftres;
2:16.8MB:2000GB:2000GB:ntfs:Basic data partition:msftdata;
sdc:31.1GB:scsi:512:512:msdos:USB Disk 3.0:;
1:1049kB:31.1GB:31.1GB:fat32::boot, lba;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL        PARTLABEL
sda                                                                                                    
├─sda1 ntfs     00DC2C65DC2C5766                     b69da358-1cac-40b8-90b4-2d2e531c61a3 Récupération Basic data partition
├─sda2 vfat     702C-8759                            bbd354d5-bc6a-4bc6-8993-720d23feb889              EFI system partition
├─sda3                                               90b26dda-3742-4ec0-93e9-e85b262757d2              Microsoft reserved partition
├─sda4 ntfs     0C4A2D884A2D6F9E                     320cfb1a-c807-4bae-a984-0542f8f4fbbf              Basic data partition
├─sda5 ntfs     5EF477B9F477924F                     db9af8fb-2bc9-4e3b-a56d-e5798dd651d8              
├─sda6 ext4     9d7b012c-6caa-4976-8356-14d320788579 3f920c67-de55-41db-af63-af7740e787ca              
└─sda7 ext4     24dd27b3-8bfa-4e33-9df7-a656ed6b6e44 a5a4072d-b5da-4507-bdb5-8298b041c59b              
sdb                                                                                                    
├─sdb1                                               f36fc9aa-3f7b-4c84-a701-1c3016d3e6e3              Microsoft reserved partition
└─sdb2 ntfs     0E34DB4734DB3107                     de3e85c5-ab9e-4ea7-b815-a60be9d5adcf Arnaud       Basic data partition
sdc                                                                                                    
└─sdc1 vfat     6653-4D9B                            005df8f2-01                          UBUNTU 20_0  

df (filtered): _________________________________________________________________

       Avail Use% Mounted on
sda1     489M   2% /mnt/boot-sav/sda1
sda2    59.3M  38% /mnt/boot-sav/sda2
sda4   320.3G  12% /mnt/boot-sav/sda4
sda5    47.9M  91% /mnt/boot-sav/sda5
sdb2     1.8T   0% /mnt/boot-sav/sdb2
sdc1    26.4G   9% /cdrom

Mount options: __________________________________________________________________

sda1   rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda2   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda4   rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda5   rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sdb2   rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sdc1   ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

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

search.fs_uuid 9d7b012c-6caa-4976-8356-14d320788579 root hd0,gpt6 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

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

Ubuntu
Ubuntu (safe graphics)
OEM install (for manufacturers)
Boot from next volume
UEFI Firmware Settings

========================= sdc1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /isolinux/isolinux.cfg
  APPEND /isolinux/

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

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

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

           GiB - GB             File                                 Fragment(s)
            ?? = ??             syslinux.cfg                                   1
            ?? = ??             ldlinux.sys                                    1


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

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

Error code 32
mount -r /dev/sda6 /mnt/boot-sav/sda6

mount -r /dev/sda6 : Error code 32
Error code 32
mount -r /dev/sda7 /mnt/boot-sav/sda7

mount -r /dev/sda7 : Error code 32
Error code 32
mount -r /dev/sda6 /mnt/boot-sav/sda6

mount -r /dev/sda6 : Error code 32
Error code 32
mount -r /dev/sda7 /mnt/boot-sav/sda7

mount -r /dev/sda7 : Error code 32
Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the MBR.
Additional repair would be performed:  win-legacy-basic-fix   restore-efi-backups

FrancisFDZ

Bonjour,
Quelque chose me chiffonne dans ce boot info :
D'une part

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

 => Windows 7/8/2012 is installed in the MBR of /dev/sda.
 => Windows 7/8/2012 is installed in the MBR of /dev/sdb.
 => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.

ce qui laisserait penser que nous sommes en mode "legacy" (MBR)
D'autre part

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:        /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi 
                       /efi/Boot/fbx64.efi /efi/Boot/grubx64.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

Ce qui me semble que le système boote en mode UEFI sud sd2

Est-ce normal docteur(s) ?

[Edit] La réponse est aussi dans ce même boot info

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

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

Mais ça ne me semble pas cohérent. [/Edit]
[Edit2] Oops ! C'est le boot sur la clé en live qui se fait en UEFI !? [/Edit2]

geole

Bonjour
Je me suis trompé: Ce n'est pas un nvme d'où le refus de réponse.
Il faut faire la suite car la partition est encore "nase" mais il y a aussi sda7
6) réparer la partition comme tu l'as déjà fait.

sudo fsck  -y  /dev/sda6

sudo fsck  -y  /dev/sda7

7) et un second passage dont tu donneras le retour

sudo fsck -y   /dev/sda6

sudo fsck  -y  /dev/sda7

FrancisFDZ

Suite à mon post #38 : est-il normal que le boot de ce PC soit en mode legacy et que le boot en live se fasse en UEFI ?

NB : mon matériel est relativement ancien et je boote toujours sur MBR avec un partitionnement "classique". Mes connaissances en UEFI sont très limitées.

« Page précédente Page suivante »