Forum Linux.débutant Disque innacessible

Posté par  . Licence CC By‑SA.
Étiquettes :
0
19
juin
2016

Bonjour à tous,

Suite au post "http://linuxfr.org/forums/linux-debutant/posts/probleme-avec-grub", j'ai pu utiliser le Grub de ma Debian et celui de ma Kali sans soucis.

Malheureusement, après 3 reboots normaux, je n'ai plus accès à mon M-SATA Debian.

  • Le M-SATA apparaît bien dans le BIOS.
  • Si je boot dessus, je ne vois même pas apparaître Grub.
  • Si je boot sur le second disque, je vois apparaître le Grub du second disque, mais l'entrée qui permet de booter sur mon premier disque me donne:
...
/dev/sdb5: read failed after 0 of 4096 at 8192: Input/output error
Volume group "NOTJIL-vg" not found
Skipping volume groupe NOTJIL-vg
Uneable to find LVM volume NOTJIL-vg/root
Gave up waiting for root device. common problems:
...
ALERT! /dev/mapper/NOTJIL--vg-root does not exists. Dropping to a shell
modprobe: module ehci-orion not found in module.dep

Busybox...
..
(initramfs)_

J'ai donc abandonné et booté sur la Kali ou comme un imbécile, j'ai pensé que Grub était peut-être cassé.

J'ai donc ré appliqué la procédure du lien précédant, qui a retiré l'entrée Grub vers la Debian et je n'ai plus accès au prompt (initramfs)_

j'ai essayé de monter les partitions LVM du M-SATA pour faire un chroot comme expliqué dans le lien précédant:

root@NOTKALI:~# vgscan
  Reading all physical volumes.  This may take a while...
root@NOTKALI:~# vgchange -a y
root@NOTKALI:~# lvmdiskscan
  /dev/sda1 [     114,37 GiB] 
  /dev/sda5 [       4,87 GiB] 
  /dev/sdb1 [     243,00 MiB] 
  /dev/sdb5: read failed after 0 of 4096 at 8192: Erreur d'entrée/sortie
  /dev/sdb5 [     119,00 GiB] LVM physical volume
  0 disks
  3 partitions
  0 LVM physical volume whole disks
  1 LVM physical volume
root@NOTKALI:~# lvdisplay 
root@NOTKALI:~#

Je pense raisonnablement pouvoir dire que je suis dans la m****.

Avez vous une idée pour m'en sortir?

Merci d'avance.

  • # Précisions

    Posté par  . Évalué à 1.

    Voici l'output de dmesg:

    root@NOTKALI:/home/user0# dmesg | egrep "(sdb)|(LITEON)"
    [    1.299987] ata5.00: ATA-8: LITEON IT SMS-128L9M, RM70206, max UDMA/133
    [    1.300947] scsi 4:0:0:0: Direct-Access     ATA      LITEON IT SMS-12 206  PQ: 0 ANSI: 5
    [    1.302750] sd 4:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB)
    [    1.302838] sd 4:0:0:0: [sdb] Write Protect is off
    [    1.302840] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [    1.302863] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [    1.303245]  sdb: sdb1 sdb2 < sdb5 >
    [    1.303503] sd 4:0:0:0: [sdb] Attached SCSI disk
    [    1.331986] sd 4:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [    1.331988] sd 4:0:0:0: [sdb] tag#4 Sense Key : Medium Error [current] [descriptor] 
    [    1.331990] sd 4:0:0:0: [sdb] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
    [    1.331992] sd 4:0:0:0: [sdb] tag#4 CDB: Read(10) 28 00 00 00 08 38 00 00 08 00
    [    1.331994] blk_update_request: I/O error, dev sdb, sector 2104
    [    6.682977] sd 4:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [    6.682982] sd 4:0:0:0: [sdb] tag#24 Sense Key : Medium Error [current] [descriptor] 
    [    6.682986] sd 4:0:0:0: [sdb] tag#24 Add. Sense: Unrecovered read error - auto reallocate failed
    [    6.682990] sd 4:0:0:0: [sdb] tag#24 CDB: Read(10) 28 00 00 00 08 38 00 00 08 00
    [    6.682992] blk_update_request: I/O error, dev sdb, sector 2104
    [    6.683072] Buffer I/O error on dev sdb1, logical block 7, async page read
    [    7.061067] sd 4:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [    7.061071] sd 4:0:0:0: [sdb] tag#22 Sense Key : Medium Error [current] [descriptor] 
    [    7.061074] sd 4:0:0:0: [sdb] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
    [    7.061077] sd 4:0:0:0: [sdb] tag#22 CDB: Read(10) 28 00 00 07 a8 10 00 00 08 00
    [    7.061080] blk_update_request: I/O error, dev sdb, sector 501776
  • # Précisions: Smartctl

    Posté par  . Évalué à 1.

    root@NOTKALI:/home/user0# smartctl -a /dev/sdb
    smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.0-kali1-amd64] (local build)
    Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Device Model:     LITEON IT SMS-128L9M
    Serial Number:    002504133515
    LU WWN Device Id: 5 002303 1003a7c53
    Add. Product Id:  RM702060
    Firmware Version: RM70206
    User Capacity:    128.035.676.160 bytes [128 GB]
    Sector Size:      512 bytes logical/physical
    Rotation Rate:    Solid State Device
    Device is:        Not in smartctl database [for details use: -P showall]
    ATA Version is:   ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 4a
    SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is:    Sun Jun 19 15:51:17 2016 CEST
    SMART support is: Available - device has SMART capability.
    SMART support is: 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:        (   10) seconds.
    Offline data collection
    capabilities:            (0x15) SMART execute Offline immediate.
                        No Auto Offline data collection support.
                        Abort Offline collection upon new
                        command.
                        No Offline surface scan supported.
                        Self-test supported.
                        No Conveyance Self-test supported.
                        No 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:    (   1) minutes.
    Extended self-test routine
    recommended polling time:    (  10) 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
      1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
      5 Reallocated_Sector_Ct   0x0003   100   100   000    Pre-fail  Always       -       0
      9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       1037
     12 Power_Cycle_Count       0x0003   100   100   000    Pre-fail  Always       -       367
    170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       24
    171 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       1
    172 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       0
    173 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       68
    174 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       31
    175 Program_Fail_Count_Chip 0x0003   100   100   000    Pre-fail  Always       -       1
    176 Erase_Fail_Count_Chip   0x0003   100   100   000    Pre-fail  Always       -       0
    177 Wear_Leveling_Count     0x0003   100   100   000    Pre-fail  Always       -       70462
    178 Used_Rsvd_Blk_Cnt_Chip  0x0003   100   100   000    Pre-fail  Always       -       2
    179 Used_Rsvd_Blk_Cnt_Tot   0x0003   100   100   000    Pre-fail  Always       -       24
    180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   000    Pre-fail  Always       -       656
    181 Program_Fail_Cnt_Total  0x0003   100   100   000    Pre-fail  Always       -       1
    182 Erase_Fail_Count_Total  0x0003   100   100   000    Pre-fail  Always       -       0
    183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
    184 End-to-End_Error        0x0033   088   088   000    Pre-fail  Always       -       12
    187 Reported_Uncorrect      0x0003   100   100   000    Pre-fail  Always       -       23
    188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
    192 Power-Off_Retract_Count 0x0003   100   100   000    Pre-fail  Always       -       31
    195 Hardware_ECC_Recovered  0x0003   100   100   000    Pre-fail  Always       -       0
    196 Reallocated_Event_Count 0x0003   100   100   000    Pre-fail  Always       -       24
    198 Offline_Uncorrectable   0x0003   100   100   000    Pre-fail  Always       -       3
    199 UDMA_CRC_Error_Count    0x0003   100   100   000    Pre-fail  Always       -       0
    232 Available_Reservd_Space 0x0003   097   097   010    Pre-fail  Always       -       0
    233 Media_Wearout_Indicator 0x0003   100   100   000    Pre-fail  Always       -       3170
    241 Total_LBAs_Written      0x0003   100   100   000    Pre-fail  Always       -       50725
    242 Total_LBAs_Read         0x0003   100   100   000    Pre-fail  Always       -       43371
    
    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%      1037         -
    
    Selective Self-tests/Logging not supported
    
    root@NOTKALI:/home/user0#
    • [^] # Re: Précisions: Smartctl

      Posté par  . Évalué à 1.

      Apparement, l'output de cette commande a changé:

      root@NOTKALI:/mnt/boot# smartctl -a /dev/sdb
      smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.0-kali1-amd64] (local build)
      Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
      
      === START OF INFORMATION SECTION ===
      Device Model:     LITEON IT SMS-128L9M
      Serial Number:    002504133515
      LU WWN Device Id: 5 002303 1003a7c53
      Add. Product Id:  RM702060
      Firmware Version: RM70206
      User Capacity:    128.035.676.160 bytes [128 GB]
      Sector Size:      512 bytes logical/physical
      Rotation Rate:    Solid State Device
      Device is:        Not in smartctl database [for details use: -P showall]
      ATA Version is:   ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 4a
      SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
      Local Time is:    Sun Jun 19 17:45:48 2016 CEST
      SMART support is: Available - device has SMART capability.
      SMART support is: 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:        (   10) seconds.
      Offline data collection
      capabilities:            (0x15) SMART execute Offline immediate.
                          No Auto Offline data collection support.
                          Abort Offline collection upon new
                          command.
                          No Offline surface scan supported.
                          Self-test supported.
                          No Conveyance Self-test supported.
                          No 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:    (   1) minutes.
      Extended self-test routine
      recommended polling time:    (  10) 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
        1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
        5 Reallocated_Sector_Ct   0x0003   100   100   000    Pre-fail  Always       -       0
        9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       1038
       12 Power_Cycle_Count       0x0003   100   100   000    Pre-fail  Always       -       367
      170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       24
      171 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       1
      172 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       0
      173 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       68
      174 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       31
      175 Program_Fail_Count_Chip 0x0003   100   100   000    Pre-fail  Always       -       1
      176 Erase_Fail_Count_Chip   0x0003   100   100   000    Pre-fail  Always       -       0
      177 Wear_Leveling_Count     0x0003   100   100   000    Pre-fail  Always       -       70462
      178 Used_Rsvd_Blk_Cnt_Chip  0x0003   100   100   000    Pre-fail  Always       -       2
      179 Used_Rsvd_Blk_Cnt_Tot   0x0003   100   100   000    Pre-fail  Always       -       24
      180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   000    Pre-fail  Always       -       656
      181 Program_Fail_Cnt_Total  0x0003   100   100   000    Pre-fail  Always       -       1
      182 Erase_Fail_Count_Total  0x0003   100   100   000    Pre-fail  Always       -       0
      183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
      184 End-to-End_Error        0x0033   088   088   000    Pre-fail  Always       -       12
      187 Reported_Uncorrect      0x0003   100   100   000    Pre-fail  Always       -       23
      188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
      192 Power-Off_Retract_Count 0x0003   100   100   000    Pre-fail  Always       -       31
      195 Hardware_ECC_Recovered  0x0003   100   100   000    Pre-fail  Always       -       0
      196 Reallocated_Event_Count 0x0003   100   100   000    Pre-fail  Always       -       24
      198 Offline_Uncorrectable   0x0003   100   100   000    Pre-fail  Always       -       3
      199 UDMA_CRC_Error_Count    0x0003   100   100   000    Pre-fail  Always       -       0
      232 Available_Reservd_Space 0x0003   097   097   010    Pre-fail  Always       -       0
      233 Media_Wearout_Indicator 0x0003   100   100   000    Pre-fail  Always       -       3170
      241 Total_LBAs_Written      0x0003   100   100   000    Pre-fail  Always       -       50725
      242 Total_LBAs_Read         0x0003   100   100   000    Pre-fail  Always       -       43371
      
      SMART Error Log Version: 1
      Warning: ATA error count 0 inconsistent with error log pointer 2
      
      ATA Error Count: 0
          CR = Command Register [HEX]
          FR = Features Register [HEX]
          SC = Sector Count Register [HEX]
          SN = Sector Number Register [HEX]
          CL = Cylinder Low Register [HEX]
          CH = Cylinder High Register [HEX]
          DH = Device/Head Register [HEX]
          DC = Device Command Register [HEX]
          ER = Error register [HEX]
          ST = Status register [HEX]
      Powered_Up_Time is measured from power on, and printed as
      DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
      SS=sec, and sss=millisec. It "wraps" after 49.710 days.
      
      Error 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
        When the command that caused the error occurred, the device was in an unknown state.
      
        After command completion occurred, registers were:
        ER ST SC SN CL CH DH
        -- -- -- -- -- -- --
        f9 30 03 00 00 00 00  Device Fault
      
        Commands leading to the command that caused the error were:
        CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
        -- -- -- -- -- -- -- --  ----------------  --------------------
        10 f9 03 00 08 00 00 b7  18d+15:23:34.696  RECALIBRATE [OBS-4]
        10 f9 03 00 08 00 00 b6  18d+15:23:34.696  RECALIBRATE [OBS-4]
        10 f9 03 00 08 00 00 b4  18d+15:23:34.696  RECALIBRATE [OBS-4]
        10 f9 03 00 08 00 00 b2  18d+15:23:34.696  RECALIBRATE [OBS-4]
        10 00 00 00 08 00 00 00  18d+15:23:34.696  RECALIBRATE [OBS-4]
      
      Error -1 occurred at disk power-on lifetime: 768 hours (32 days + 0 hours)
        When the command that caused the error occurred, the device was in an unknown state.
      
        After command completion occurred, registers were:
        ER ST SC SN CL CH DH
        -- -- -- -- -- -- --
        00 07 00 00 00 0f a8
      
        Commands leading to the command that caused the error were:
        CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
        -- -- -- -- -- -- -- --  ----------------  --------------------
        07 00 08 00 00 10 a8 03  48d+11:38:05.696  [RESERVED]
        07 00 08 00 00 10 a8 03  48d+11:35:54.624  [RESERVED]
        07 00 08 00 00 10 a8 03  48d+07:05:01.696  [RESERVED]
        07 00 08 00 00 10 a8 03  45d+07:05:06.816  [RESERVED]
        07 00 08 00 00 10 a8 00  45d+07:04:01.280  [RESERVED]
      
      Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
        When the command that caused the error occurred, the device was in an unknown state.
      
        After command completion occurred, registers were:
        ER ST SC SN CL CH DH
        -- -- -- -- -- -- --
        10 e9 a8 07 00 60 40
      
        Commands leading to the command that caused the error were:
        CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
        -- -- -- -- -- -- -- --  ----------------  --------------------
        e9 10 a8 07 00 60 3e 00      00:08:44.291  READ BUFFER DMA
        e9 10 a8 07 00 60 3c 00      00:08:44.291  READ BUFFER DMA
        e9 10 a8 07 00 60 3a 00      00:08:44.291  READ BUFFER DMA
        e9 10 a8 07 00 60 38 00      00:08:44.291  READ BUFFER DMA
        00 00 00 00 00 03 00 00      00:08:44.288  NOP [Abort queued commands]
      
      Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
        When the command that caused the error occurred, the device was in an unknown state.
      
        After command completion occurred, registers were:
        ER ST SC SN CL CH DH
        -- -- -- -- -- -- --
        07 00 00 60 36 e9 03
      
        Commands leading to the command that caused the error were:
        CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
        -- -- -- -- -- -- -- --  ----------------  --------------------
        00 07 00 60 24 6a 03 a8   3d+02:33:55.464  NOP [Reserved subcommand] [OBS-ACS-2]
        00 07 00 60 7f 62 03 a8   3d+02:33:55.464  NOP [Reserved subcommand] [OBS-ACS-2]
        00 00 00 60 2b 1c 03 08   3d+02:33:55.464  NOP [Abort queued commands]
        00 00 00 60 29 1c 03 08  11d+06:17:58.528  NOP [Abort queued commands]
        00 00 00 03 00 00 00 00  11d+15:37:12.960  NOP [Abort queued commands]
      
      Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
        When the command that caused the error occurred, the device was in an unknown state.
      
        After command completion occurred, registers were:
        ER ST SC SN CL CH DH
        -- -- -- -- -- -- --
        60 00 28 1c 03 00 00
      
        Commands leading to the command that caused the error were:
        CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
        -- -- -- -- -- -- -- --  ----------------  --------------------
        00 60 26 1c 03 00 00 00      00:08:58.624  NOP [Reserved subcommand] [OBS-ACS-2]
        00 60 11 1a 03 00 00 00      00:09:00.160  NOP [Reserved subcommand] [OBS-ACS-2]
        00 60 0f 1a 03 00 08 00      00:08:58.624  NOP [Reserved subcommand] [OBS-ACS-2]
        00 60 bb f9 03 00 08 00      00:08:58.624  NOP [Reserved subcommand] [OBS-ACS-2]
        00 03 00 00 00 00 08 00   1d+11:40:54.656  NOP [Reserved subcommand] [OBS-ACS-2]
      
      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%      1037         -
      
      Selective Self-tests/Logging not supported
      
      root@NOTKALI:/mnt/boot#
  • # lvm

    Posté par  . Évalué à 2. Dernière modification le 20 juin 2016 à 01:20.

    Une petite recherche son ton message d'erreur lvm me donne cela :

    http://www.linuxtechi.com/fixing-lvm-io-errors/

    Si cela ne suffit pas comme dit dans les commentaires : kpartx -d

    Bonne chance ;).

    • [^] # Re: lvm

      Posté par  . Évalué à 1.

      Ce qui m'inquiète, c'est que dans le post, le gars voit son VG et son LV.

      Moi je vois rien du tout…

      Et j'ai peur de ne pas réussir à monter cette partition.

      • [^] # Re: lvm

        Posté par  . Évalué à 2.

        Oui en effet ça craint…

        Tu as touché à quelque chose au niveau des disques / partitions depuis la réinstallation du grub ?

        • [^] # Re: lvm

          Posté par  . Évalué à 1.

          Sorry, j'étais à l'étranger pour le boulot.

          Non, je ne pense pas avoir touché à quoi que ce soit sur les disques.

          J'ai lancé un ddrescue de tous le M-SATA avant de partir et je vois que seul 30M serait corrompus.

          J'imagine que c'est la que se trouvait LVM.

          Maintenant, j'aimerais bien accéder à mes données…

          Un fdisk -l me montre bien mes partitions dans le fichier de travail (une copie de l'original).

          J'ai tenté un losetup --offset pour charger la partition dans /dev puis la monter, ce qui ne marche évidement pas puisque la partition est de type LVM.

          Donc j'ai tenté un vgcreate, lvcreate en renommant mon VG et mon LV d’après mes souvenirs (donc comme Debian les génère: NOM_MACHINE-vg).
          Je ne sais pas si les noms ont une importance.

          J'ai donc un LV, mais je n'arrive pas à le monter via mount.

          J'avoue que je ne maîtrise pas du tout les outils que je tente d'utiliser et que je les utilise donc probablement mal.

          Je suis ouvert à toute proposition…

Suivre le flux des commentaires

Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.