10.13 High Sierra macOs High Sierra fsroot tree is invalid

Je n'y comprends rien. D'après toute mon expérience > la commande est valide, pourtant.

Passe cette variante :
Bloc de code:
diskutil resizeVolume disk0s3 300g jhfs+ SOS 0b
 
Non malheureusement cela ne fonctionne pas plus.
Barre de progression jusque 40% puis plantage.

C'est à taper la tête sur un mur.

L'action est-elle possible par utilitaire disque ?
 
Tu dois pouvoir faire pareil dans l'«Utilitaire de Disque».

Sinon > il doit falloir re-démarrer en coup et rebooter par internet via ⌘⌥R. J'ai l'impression qu'il a un plantage.
 
Ok je vais alors tenter un redémarrage et relancer les commande dans l'ordre jusqu'à en avoir une qui passe.

Pour utilitaire disque, je vais attendre encore un peu. Pas super secure (une erreur et vite arrivé)
 
Toujours pas. J'en passerais surement pas l'interface graphique sinon sur un DDE.

Bloc de code:
-bash-3.2# diskutil resizeVolume disk0s3 220g jhfs+ SOS 0b
Resizing to 220000000000 bytes and adding 1 partition
Started partitioning on disk0s3 Crucial_SSD_HD
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk0s3
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Crucial_SSD_HD appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Shrinking file system
Error: -69787: The partition cannot be resized; try reducing the amount of change in the size of the partition
-bash-3.2#
-bash-3.2# diskutil resizeVolume disk0s3 250g jhfs+ SOS 0b
Resizing to 250000000000 bytes and adding 1 partition
Started partitioning on disk0s3 Crucial_SSD_HD
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk0s3
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Crucial_SSD_HD appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Shrinking file system
Error: -69787: The partition cannot be resized; try reducing the amount of change in the size of the partition
-bash-3.2#
-bash-3.2# diskutil resizeVolume disk0s3 300g jhfs+ SOS 0b
Resizing to 300000000000 bytes and adding 1 partition
Started partitioning on disk0s3 Crucial_SSD_HD
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk0s3
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Crucial_SSD_HD appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Shrinking file system
Error: -69787: The partition cannot be resized; try reducing the amount of change in the size of the partition
-bash-3.2#
 
Je ne comprends rien à ce blocage du re-partitionnement. J'ai déjà passé d'innombrables fois ce type de commande sans problème.

Tu n'as pas un DDE avec de l'espace libre > et les bons paramètres (table GUID > format jhfs+ de volume) ?
 
Pareil je ne comprends pas, et je confirme, j'ai pu voir ça sur le forum, tu en as passés beaucoup.

J'ai un DDE au format NTFS avec quelques giga (pas loin de 200g) sur lequel on pourrais créer une table GUID avec partition au format JHFS+
 
Si tu n'as pas de données sur le DDE > tu l'attaches au Mac > diskutil list > tu postes le tableau.
 
diskutil list
Bloc de code:
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         129.9 GB   disk0s2
   3:                  Apple_HFS Crucial_SSD_HD          369.8 GB   disk0s3

/dev/disk1 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.1 GB     disk1
   1:                  Apple_HFS OS X Base System        2.0 GB     disk1s1

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +129.9 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume Crucial_SSD_OS          60.9 GB    disk2s1
   2:                APFS Volume Preboot                 19.9 MB    disk2s2
   3:                APFS Volume Recovery                503.9 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +5.2 MB     disk3

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk4

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk8

/dev/disk9 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk9

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +12.6 MB    disk10

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk11

/dev/disk12 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk12

/dev/disk13 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk13

/dev/disk14 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk14

/dev/disk15 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk15

/dev/disk16 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk16

/dev/disk17 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk17

/dev/disk18 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk18

/dev/disk19 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk19

/dev/disk20 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk20

/dev/disk21 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *320.1 GB   disk21
   1:               Windows_NTFS HD-WESTERN              320.1 GB   disk21s1

df -H /Volumes/HD-WESTERN/
Bloc de code:
-bash-3.2# df -H /Volumes/HD-WESTERN/
Filesystem      Size   Used  Avail Capacity iused     ifree %iused  Mounted on
/dev/disk21s1   320G   118G   202G    37%    3946 197356336    0%   /Volumes/HD-WESTERN
-bash-3.2#
 
La je te répond NON.
  • Il n'est pas possible de splitter le disque (tout en préservant les données) et créer une table GUID avec partition au format JHFS+ ?
  • Si trop compliqué ou risqué, je vois/j'essaye pour obtenir (demain) un DDE, sur lequel est installé macOS Maverick avec 70g dispo. On créra une parttiton pour acceuillir High-Sierra. Possible ?
 
La table de partition désignée par FDisk_partition_scheme = MBR. Elle interdit le re-partitionnement en mode "live" (non destructeur = re-dimensionnement de volumes) > ce quel que soit le format de système de fichiers de la partition-cible.

Il vaut mieux que tu attendes demain d'avoir un DDE "malléable".
 
La table de partition désignée par FDisk_partition_scheme = MBR. Elle interdit le re-partitionnement en mode "live" (non destructeur = re-dimensionnement de volumes) > ce quel que soit le format de système de fichiers de la partition-cible.

Il vaut mieux que tu attendes demain d'avoir un DDE "malléable".


Ok.
Merci pour ton aide macomaniac.
Bonne soirée.
 
:coucou: macomania,

Tu es dispo, on peut reprendre ?

diskutil
Bloc de code:
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         129.9 GB   disk0s2
   3:                  Apple_HFS Crucial_SSD_HD          369.8 GB   disk0s3

/dev/disk1 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.1 GB     disk1
   1:                  Apple_HFS OS X Base System        2.0 GB     disk1s1

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +129.9 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume Crucial_SSD_OS          60.9 GB    disk2s1
   2:                APFS Volume Preboot                 19.9 MB    disk2s2
   3:                APFS Volume Recovery                503.9 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk3
   1:                        EFI EFI                     314.6 MB   disk3s1
   2:                  Apple_HFS WD_HD_OSX               129.5 GB   disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3
   4:                  Apple_HFS WD_HD_DATA              369.5 GB   disk3s4

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +5.2 MB     disk4

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk8

/dev/disk9 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk9

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk10

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +12.6 MB    disk11

/dev/disk12 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk12

/dev/disk13 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk13

/dev/disk14 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk14

/dev/disk15 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk15

/dev/disk16 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk16

/dev/disk17 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk17

/dev/disk18 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk18

/dev/disk19 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk19

/dev/disk20 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk20

/dev/disk21 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk21

Espace disques dispo :
Bloc de code:
-bash-3.2# df -H

Filesystem     Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s1   2.0G   1.3G   733M    64%   44898 4294922381    0%   /
devfs          214k   214k     0B   100%     724          0  100%   /dev
/dev/disk4     5.2M   508k   4.7M    10%      21 4294967258    0%   /private/var/log
/dev/disk5     524k   147k   377k    29%       6 4294967273    0%   /Volumes
/dev/disk6     524k   147k   377k    29%       7 4294967272    0%   /private/var/tmp
/dev/disk7     524k   160k   365k    31%      12 4294967267    0%   /private/var/run
/dev/disk8     2.1M   147k   1.9M     8%       3 4294967276    0%   /private/tmp
/dev/disk9     524k   143k   381k    28%       2 4294967277    0%   /System/Installation
/dev/disk10    524k   299k   225k    58%      20 4294967259    0%   /private/var/db
/dev/disk11     13M   2.7M   9.9M    22%      50 4294967229    0%   /private/var/folders
/dev/disk12    2.1M   205k   1.9M    10%      22 4294967257    0%   /private/var/root/Library
/dev/disk14    2.1M   143k   2.0M     7%       2 4294967277    0%   /private/var/root/Library/Containers
/dev/disk15    524k   176k   348k    34%      10 4294967269    0%   /Library/Preferences
/dev/disk16    524k   164k   360k    32%       6 4294967273    0%   /Library/Preferences/SystemConfiguration
/dev/disk17    1.0M   176k   872k    17%       5 4294967274    0%   /Library/Keychains
/dev/disk18    6.3M   176k   6.1M     3%       2 4294967277    0%   /private/var/tmp/RecoveryTemp
/dev/disk19    6.3M   860k   5.4M    14%       4 4294967275    0%   /private/var/tmp/OSISPredicateUpdateProductTemp
/dev/disk20    524k   143k   381k    28%       2 4294967277    0%   /private/var/tmp/InstallerCookies
/dev/disk21    2.1M   143k   2.0M     7%       2 4294967277    0%   /Library/Logs/DiagnosticReports
/dev/disk0s3   370G   199G   171G    54%   39469 4294927810    0%   /Volumes/Crucial_SSD_HD
/dev/disk3s2   129G    40G    90G    31%  620652 4294346627    0%   /Volumes/WD_HD_OSX
/dev/disk3s4   370G   369G   194M   100%   21134 4294946145    0%   /Volumes/WD_HD_DATA
-bash-3.2#
-bash-3.2# df -H /Volumes/WD_HD_OSX/
Filesystem     Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk3s2   129G    40G    90G    31%  620652 4294346627    0%   /Volumes/WD_HD_OSX
-bash-3.2#

DDE Avec macOS Maverick (je pense...) avec quelques giga dispo (pas loin de 90g) sur lequel on pourrais tenter un resize et créer une table GUID avec partition au format JHFS+ pour install de high Sierra. Tu en penses quoi ?
Dis moi, je suis prêt pour dérouler les actions...
 
Alors passe la commande :
Bloc de code:
diskutil resizeVolume disk3s2 49g jhfs+ SOS 0b

  • qui réduit le volume WD_HD_OSX à 49 Go et crée un volume SOS de 80 Go environ.

=> on va bien voir si elle passe...
 
J'ai déjà lancer le resize en partant d'une des commande vue ensemble hier.

J'ai réduit le volume WD_HD_OSX à 55 Go ce qui laisse environ 75 Go

La commande à correctement était exécuté, et l'install de High Sierra validé.
 
La commande à correctement était exécuté

Ah ! quand même...
361608_original.png


Tu vas bien voir une fois ta session ouverte > si tu peux remonter le volume Crucial_SSD_OS.
 
Impossible de remonter le disque, impossible de le réparer, et erreur de "space" sur les containers.

Bloc de code:
Last login: Tue Jan 23 21:25:11 on ttys000
MacBook-Pro-de-Jamil:~ sos$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         129.9 GB   disk0s2
   3:                  Apple_HFS Crucial_SSD_HD          369.8 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +129.9 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Crucial_SSD_OS          60.9 GB    disk1s1
   2:                APFS Volume Preboot                 19.9 MB    disk1s2
   3:                APFS Volume Recovery                503.9 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     314.6 MB   disk2s1
   2:                  Apple_HFS WD_HD_OSX               55.0 GB    disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
   4:                  Apple_HFS SOS                     73.8 GB    disk2s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk2s5
   6:                  Apple_HFS WD_HD_DATA              369.5 GB   disk2s6

MacBook-Pro-de-Jamil:~ sos$ diskutil mountDisk disk1
One or more volume(s) failed to mount
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyDisk disk1
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition
scheme, you might be able to repair it with "diskutil repairDisk disk1"
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s2
Volume Preboot on disk1s2 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s3
Volume Recovery on disk1s3 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s4
Volume VM on disk1s4 mounted
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mount disk1s1
Volume on disk1s1 failed to mount; it appears to be an APFS Volume which might be locked
Try "diskutil apfs unlockVolume"
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil apfs unlockVolume disk1s1
Passphrase:
Unlocking any cryptographic user on APFS Volume disk1s1
Error unlocking APFS Volume: The given APFS Volume is not encrypted (-69593)
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil mountDisk disk1
One or more volume(s) failed to mount
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyVolume disk1s1
Started file system verification on disk1s1 Crucial_SSD_OS
Verifying file system
Volume is already unmounted
Live mode required because other APFS Volumes in its Container are mounted
Using live mode
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
error: apfs_root: btn: invalid o_oid (0x79503)
fsroot tree is invalid
The volume /dev/rdisk1s1 could not be verified completely
File system check exit code is 0
Restoring the original state found as unmounted
Finished file system verification on disk1s1 Crucial_SSD_OS
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil verifyVolume disk1s2
Started file system verification on disk1s2 Preboot
Verifying file system
Volume was successfully unmounted
Live mode required because other APFS Volumes in its Container are mounted
Using live mode
Performing fsck_apfs -n -l -x /dev/rdisk1s2
Checking volume
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the object map
Checking the APFS volume superblock
Checking the object map
Checking the fsroot tree
Checking the snapshot metadata tree
Checking the extent ref tree
Checking the snapshots
Verifying allocated space
error: Underallocation Detected on Main device: (1018944+64) bitmap address (440656)
error: Underallocation Detected on Main device: (1019008+64) bitmap address (440656)
error: Underallocation Detected on Main device: (1019072+12) bitmap address (440656)
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 2 @ -1 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
warning: error (6) getting cib 5 bitmap 4 @ 4294967295 on device 0
Space Verification failed
The volume /dev/rdisk1s2 could not be verified completely
File system check exit code is 0
Restoring the original state found as mounted
Finished file system verification on disk1s2 Preboot
MacBook-Pro-de-Jamil:~ sos$
MacBook-Pro-de-Jamil:~ sos$ diskutil repairDisk disk1
Nonexistent, unknown, or damaged partition map scheme
If you are sure this disk contains a (damaged) APM, MBR, or GPT partition map,
you can hereby try to repair it enough to be recognized as a map; another
"diskutil repairDisk disk1" might then be necessary for further repairs
Proceed? (y/N) y
Error repairing map: MediaKit reports bad partition or no map found (-5324)
MacBook-Pro-de-Jamil:~ sos$
:banghead::banghead::banghead::mad::mad::mad:
Et maintenant Docteur, on fait quoi ?
 
On a fait tout ce qu'on pouvait et je pense qu'il n'y a plus rien à faire. Il y trop d'erreurs radicales dans le système de fichiers apfs générateur du volume > pour qu'il puisse être remonté.

Soit tu fais ton deuil des données du volume > soit tu tentes (mais c'est payant - dans les 100€) une récupération avec un logiciel de récupération de données.