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 15/02/2019, à 22:07

Caryn

[Résolu] Disque dur invisible depuis branchement sur PS4

Bonjour à tous,

Mon fils a eu la brillante idée de brancher mon disque dur externe sur la PS4 pour regarder un film. Évidemment, il ne se souvient plus de ce qu'il a fait, ce qui était affiché... Il a sans doute juste cliquer sur "oui" à chaque fois qu'on lui posait une question. En tout cas, depuis, mon disque dur n'apparaît plus dans l'explorateur Windows, ni dans Nautilus sur Ubuntu.
Je suis en Ubuntu 16.04. C'est un ami qui me l'a installé, et je trouve ça franchement génial... tant que je n'ai pas à trop rentrer dans le terminal, parce que là je n'y connais rien !
Pourriez-vous m'aider à vérifier si mes données sont toujours sur mon disque, et trouver le moyen de m'en rendre l'accès ?

En fouillant sur le forum, j'ai déjà fait quelques manip, que voici :

kadieux@portable:~$ sudo fdisk -l
[sudo] Mot de passe de kadieux : 
Disque /dev/sda : 238,5 GiB, 256060514304 octets, 500118192 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 15C929D5-469A-45F8-A81D-FFF42843554A

Périphérique  Début       Fin  Secteurs Taille Type
/dev/sda1       2048   1050623   1048576   512M Système EFI
/dev/sda2    1050624   1550335    499712   244M Système de fichiers Linux
/dev/sda3    1550336 500117503 498567168 237,8G Système de fichiers Linux


Disque /dev/mapper/sda3_crypt : 237,8 GiB, 255264292864 octets, 498563072 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets


Disque /dev/mapper/ubuntu--vg-root : 229,9 GiB, 246797041664 octets, 482025472 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets


Disque /dev/mapper/ubuntu--vg-swap_1 : 7,9 GiB, 8464105472 octets, 16531456 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets


Disque /dev/sdb : 931,5 GiB, 1000204883968 octets, 1953525164 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
kadieux@portable:~$ dmesg | tail -100
[81008.390260] usb-storage 3-2:1.0: USB Mass Storage device detected
[81008.390669] scsi host8: usb-storage 3-2:1.0
[81010.693252] scsi 8:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[81010.693763] sd 8:0:0:0: Attached scsi generic sg1 type 0
[81010.695502] sd 8:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[81010.695868] sd 8:0:0:0: [sdb] Write Protect is off
[81010.695873] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
[81010.696191] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[81010.713039] sd 8:0:0:0: [sdb] Attached SCSI disk
[81026.541137] usb 3-2: USB disconnect, device number 6
[81026.541692] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
[81026.541716] sd 8:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[81034.652989] usb 3-1: new SuperSpeed USB device number 7 using xhci_hcd
[81034.671328] usb 3-1: New USB device found, idVendor=0480, idProduct=a202
[81034.671331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[81034.671333] usb 3-1: Product: External USB 3.0
[81034.671334] usb 3-1: Manufacturer: TOSHIBA
[81034.671336] usb 3-1: SerialNumber: 20151207009554F
[81034.672083] usb-storage 3-1:1.0: USB Mass Storage device detected
[81034.672156] scsi host9: usb-storage 3-1:1.0
[81037.344531] scsi 9:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[81037.344920] sd 9:0:0:0: Attached scsi generic sg1 type 0
[81037.346427] sd 9:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[81037.346755] sd 9:0:0:0: [sdb] Write Protect is off
[81037.346760] sd 9:0:0:0: [sdb] Mode Sense: 23 00 00 00
[81037.348146] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[81037.366999] sd 9:0:0:0: [sdb] Attached SCSI disk
[81115.690985] thinkpad_acpi: EC reports that Thermal Table has changed
[81551.855963] usb 3-1: USB disconnect, device number 7
[81551.856787] sd 9:0:0:0: [sdb] Synchronizing SCSI cache
[81551.856839] sd 9:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[81555.890927] usb 3-1: new SuperSpeed USB device number 8 using xhci_hcd
[81555.909312] usb 3-1: New USB device found, idVendor=0480, idProduct=a202
[81555.909315] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[81555.909318] usb 3-1: Product: External USB 3.0
[81555.909320] usb 3-1: Manufacturer: TOSHIBA
[81555.909322] usb 3-1: SerialNumber: 20151207009554F
[81555.909968] usb-storage 3-1:1.0: USB Mass Storage device detected
[81555.910051] scsi host10: usb-storage 3-1:1.0
[81558.856052] scsi 10:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[81558.858777] sd 10:0:0:0: Attached scsi generic sg1 type 0
[81558.860182] sd 10:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[81558.861099] sd 10:0:0:0: [sdb] Write Protect is off
[81558.861105] sd 10:0:0:0: [sdb] Mode Sense: 23 00 00 00
[81558.862991] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[81558.879235] sd 10:0:0:0: [sdb] Attached SCSI disk
[82259.567883] usb 3-1: USB disconnect, device number 8
[82259.568649] sd 10:0:0:0: [sdb] Synchronizing SCSI cache
[82259.568686] sd 10:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[82265.795703] usb 3-1: new SuperSpeed USB device number 9 using xhci_hcd
[82265.813843] usb 3-1: New USB device found, idVendor=0480, idProduct=a202
[82265.813846] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[82265.813848] usb 3-1: Product: External USB 3.0
[82265.813850] usb 3-1: Manufacturer: TOSHIBA
[82265.813852] usb 3-1: SerialNumber: 20151207009554F
[82265.814562] usb-storage 3-1:1.0: USB Mass Storage device detected
[82265.819243] scsi host11: usb-storage 3-1:1.0
[82268.767513] scsi 11:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[82268.768020] sd 11:0:0:0: Attached scsi generic sg1 type 0
[82268.769761] sd 11:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[82268.770139] sd 11:0:0:0: [sdb] Write Protect is off
[82268.770144] sd 11:0:0:0: [sdb] Mode Sense: 23 00 00 00
[82268.770492] sd 11:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[82268.787598] sd 11:0:0:0: [sdb] Attached SCSI disk
[82690.084084] usb 3-1: USB disconnect, device number 9
[82690.084639] sd 11:0:0:0: [sdb] Synchronizing SCSI cache
[82690.084683] sd 11:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[82705.012025] usb 3-1: new SuperSpeed USB device number 10 using xhci_hcd
[82705.030140] usb 3-1: New USB device found, idVendor=0480, idProduct=a202
[82705.030143] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[82705.030146] usb 3-1: Product: External USB 3.0
[82705.030147] usb 3-1: Manufacturer: TOSHIBA
[82705.030149] usb 3-1: SerialNumber: 20151207009554F
[82705.030849] usb-storage 3-1:1.0: USB Mass Storage device detected
[82705.031260] scsi host12: usb-storage 3-1:1.0
[82708.077599] scsi 12:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[82708.078127] sd 12:0:0:0: Attached scsi generic sg1 type 0
[82708.079985] sd 12:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[82708.080308] sd 12:0:0:0: [sdb] Write Protect is off
[82708.080313] sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
[82708.082539] sd 12:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[82708.097600] sd 12:0:0:0: [sdb] Attached SCSI disk
[82742.884175] usb 3-1: USB disconnect, device number 10
[82742.886624] sd 12:0:0:0: [sdb] Synchronizing SCSI cache
[82742.886652] sd 12:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[82889.470170] usb 3-3: new SuperSpeed USB device number 11 using xhci_hcd
[82889.488857] usb 3-3: New USB device found, idVendor=0480, idProduct=a202
[82889.488860] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[82889.488863] usb 3-3: Product: External USB 3.0
[82889.488865] usb 3-3: Manufacturer: TOSHIBA
[82889.488867] usb 3-3: SerialNumber: 20151207009554F
[82889.489584] usb-storage 3-3:1.0: USB Mass Storage device detected
[82889.489789] scsi host13: usb-storage 3-3:1.0
[82892.417160] scsi 13:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
[82892.417478] sd 13:0:0:0: Attached scsi generic sg1 type 0
[82892.419058] sd 13:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
[82892.419381] sd 13:0:0:0: [sdb] Write Protect is off
[82892.419384] sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
[82892.419964] sd 13:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[82892.437175] sd 13:0:0:0: [sdb] Attached SCSI disk

Qu'en pensez-vous ?
Merci d'avance de votre aide.


Modération : merci d'utiliser les balises code (explications ici).

Dernière modification par Caryn (Le 16/02/2019, à 22:44)

Hors ligne

#2 Le 15/02/2019, à 22:19

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Bonsoir,

J'en pense que c'était une mauvaise idée.

On va installer testdisk et voir ce qu'il s'est passé:

sudo apt install testdisk

Hors ligne

#3 Le 15/02/2019, à 22:26

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Voilà ce que ça donne :

kadieux@portable:~$ sudo apt install testdisk
[sudo] Mot de passe de kadieux : 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
Progression : [ 83%] [#############################################.........] 
  libdjvulibre21:i386 libfftw3-double3:i386 libfuse2:i386
  libgdk-pixbuf2.0-0:i386 libgif7:i386 libgomp1:i386 libgraphite2-3:i386
  libharfbuzz0b:i386 libilmbase12:i386 libllvm5.0 libllvm5.0:i386
  liblqr-1-0:i386 libnpth0:i386 libopenexr22:i386
  libp11-kit-gnome-keyring:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386
  libpangoft2-1.0-0:i386 libpixman-1-0:i386 libqmi-glib1 libqpdf17
  libreadline6:i386 librsvg2-2:i386 librsvg2-common:i386 libxcb-render0:i386
  libxcb-shm0:i386 ocl-icd-libopencl1:i386 os-prober:i386 pinentry-curses:i386
  wine-gecko2.21:i386
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les NOUVEAUX paquets suivants seront installés :
  testdisk
0 mis à jour, 1 nouvellement installés, 0 à enlever et 53 non mis à jour.
Il est nécessaire de prendre 324 ko dans les archives.
Après cette opération, 1 241 ko d'espace disque supplémentaires seront utilisés.
Réception de:1 [url]http://fr.archive.ubuntu.com/ubuntu[/url] xenial/universe amd64 testdisk amd64 7.0-1 [324 kB]
324 ko réceptionnés en 0s (1 027 ko/s)
Sélection du paquet testdisk précédemment désélectionné.
(Lecture de la base de données... 416514 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../testdisk_7.0-1_amd64.deb ...
Dépaquetage de testdisk (7.0-1) ...
Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
Paramétrage de testdisk (7.0-1) ...

En revanche, les barres de progression semblent s'être arrêté à 83%.


Modération : merci d'utiliser les balises code (explications ici).

Dernière modification par cqfd93 (Le 15/02/2019, à 22:30)

Hors ligne

#4 Le 15/02/2019, à 22:42

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Actuellement, il n'y a plus aucune partition détectée par fdisk, on verra demain si on peut réparer avec testdisk

Hors ligne

#5 Le 15/02/2019, à 22:44

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

OK
A demain
Merci

Hors ligne

#6 Le 16/02/2019, à 18:06

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

On va commencer par vérifier l'état du disque:

sudo apt install smartmontools
sudo smartctl -s on -a /dev/sdb

Hors ligne

#7 Le 16/02/2019, à 19:38

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Bonjour
Voici le résultat :
kadieux@portable:~$ sudo apt install smartmontolls
[sudo] Mot de passe de kadieux :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
E: Impossible de trouver le paquet smartmontolls
kadieux@portable:~$ sudo smartctl -s on -a /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-141-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdb: Unknown USB bridge [0x0480:0xa202 (0x315)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Hors ligne

#8 Le 16/02/2019, à 20:33

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Peux tu lire le premier message de https://forum.ubuntu-fr.org/viewtopic.php?id=1614731 afin de poster correctement les retours?

Ensuite tu pourras donner

sudo smartctl -d sat -s on -a /dev/sdb

J'ai peur que ça marche pas vu https://www.smartmontools.org/wiki/Supp … SB-Devices
On avisera suivant le retour

Dernière modification par Nuliel (Le 16/02/2019, à 20:33)

Hors ligne

#9 Le 16/02/2019, à 20:41

moko138

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Merci de mettre tes retours de commande entre balises-code.
  - -

sudo smartctl -s on -d sat -a /dev/sdb

%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel :  À la découverte de dcraw

Hors ligne

#10 Le 16/02/2019, à 20:42

moko138

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Naziel :
Ctrl f        0x0480:0xa202


%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel :  À la découverte de dcraw

Hors ligne

#11 Le 16/02/2019, à 20:43

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

@moko138: oui, j'ai vu, si on a cette erreur on passera par la compilation de smart

Hors ligne

#12 Le 16/02/2019, à 20:59

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

kadieux@portable:~$ sudo smartctl -d sat -s on -a /dev/sdb
[sudo] Mot de passe de kadieux : 
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-141-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01UBD... (USB 3.0)
Device Model:     TOSHIBA MQ01UBD100
Serial Number:    Z572TNHET
LU WWN Device Id: 0 000000 000000000
Firmware Version: AX101U
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Feb 16 20:54:28 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

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

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					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: 	 ( 250) 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: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2603
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4371
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1121
 10 Spin_Retry_Count        0x0033   187   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2600
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       3
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       392
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       6823
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       25 (Min/Max 14/55)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   099   099   000    Old_age   Always       -       796
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       180
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
	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 18 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was in standby mode.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:57.582  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:56.973  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:56.971  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 00 00      00:49:56.970  IDENTIFY DEVICE
  ff ff ff ff ff ff ff 0c      00:49:56.969  [VENDOR SPECIFIC]

Error 17 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:52.553  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:48.785  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT

Error 16 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:48.785  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]

Error 15 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:34.789  SET FEATURES [Set transfer mode]

Error 14 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:34.789  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 00 00      00:49:34.788  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

kadieux@portable:~$ sudo smartctl -s on -d sat -a /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-141-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01UBD... (USB 3.0)
Device Model:     TOSHIBA MQ01UBD100
Serial Number:    Z572TNHET
LU WWN Device Id: 0 000000 000000000
Firmware Version: AX101U
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Feb 16 20:55:01 2019 CET
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 Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					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: 	 ( 250) 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: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2603
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4371
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1121
 10 Spin_Retry_Count        0x0033   187   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2600
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       3
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       392
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       6823
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       25 (Min/Max 14/55)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   099   099   000    Old_age   Always       -       796
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       180
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
	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 18 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was in standby mode.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:57.582  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:56.973  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:56.971  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 00 00      00:49:56.970  IDENTIFY DEVICE
  ff ff ff ff ff ff ff 0c      00:49:56.969  [VENDOR SPECIFIC]

Error 17 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:52.553  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:48.785  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT

Error 16 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:48.785  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]

Error 15 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:45.018  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:34.789  SET FEATURES [Set transfer mode]

Error 14 occurred at disk power-on lifetime: 238 hours (9 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 20 50 f7 4d 4b  Error: UNC 32 sectors at LBA = 0x0b4df750 = 189658960

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 f6 4d 40 00      00:49:41.246  READ DMA EXT
  25 03 80 f0 f6 4d 40 00      00:49:35.400  READ DMA EXT
  ef 03 45 00 00 00 00 00      00:49:34.791  SET FEATURES [Set transfer mode]
  ef 03 0c 00 00 00 00 00      00:49:34.789  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 00 00      00:49:34.788  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

Hors ligne

#13 Le 16/02/2019, à 21:23

moko138

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

[HS]
Naziel :
Je te propose cette variante, beaucoup plus lisible, de ls -l /dev/disk/by-id

ls -l /dev/disk/by-id | grep -Ev "part|sr|Reader" | tr -s " " | awk '{print $9,$11}' | sort -k2 | column -s" " -t

                      [/HS]
  - -
[HS 2]
Je n'ai pas compris ton message de 20h43.  Ah si ! OK !
                      [/HS 2]

Dernière modification par moko138 (Le 16/02/2019, à 21:25)


%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel :  À la découverte de dcraw

Hors ligne

#14 Le 16/02/2019, à 21:29

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

HS1: Effectivement, le retour est clairement plus lisible! Adopté!
------------------------------
Les dernières erreurs smart sont vieilles (datent de 1121 - 218 heures).

Tu peux lancer

sudo testdisk

copie colle à chaque fois la page testdisk qui apparaît, on va avancer comme cela.

Dernière modification par Nuliel (Le 16/02/2019, à 21:29)

Hors ligne

#15 Le 16/02/2019, à 21:55

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

kadieux@portable:~$ ls -l /dev/disk/by-id | grep -Ev "part|sr|Reader" | tr -s " " | awk '{print $9,$11}' | sort -k2 |column -s" " -t
dm-name-sda3_crypt                                                            ../../dm-0
dm-uuid-CRYPT-LUKS1-484fc7508bcc406daa1c86738697e1ff-sda3_crypt               ../../dm-0
lvm-pv-uuid-2FldCs-ZYDp-F8M4-h3mk-N2u3-xiO4-ys0Bpx                            ../../dm-0
dm-name-ubuntu--vg-root                                                       ../../dm-1
dm-uuid-LVM-OB2b0gkRLk7d67HimCeZEqs1HqC2fCXSsWsq0NW9OxSRzhJhckoIignT4x3h1GUA  ../../dm-1
dm-name-ubuntu--vg-swap_1                                                     ../../dm-2
dm-uuid-LVM-OB2b0gkRLk7d67HimCeZEqs1HqC2fCXSBEMHUuCN0q5dBVzGynfSjromsPzTaeG2  ../../dm-2
ata-TOSHIBA_THNSFJ256GCSU_X5ES10UXT8LW                                        ../../sda
wwn-0x500080d9104bee9a                                                        ../../sda
usb-TOSHIBA_External_USB_3.0_20151207009554F-0:0    

Hors ligne

#16 Le 16/02/2019, à 21:57

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org


TestDisk is free data recovery software designed to help recover lost
partitions and/or make non-booting disks bootable again when these symptoms
are caused by faulty software, certain types of viruses or human error.
It can also be used to repair some filesystem errors.

Information gathered during TestDisk use can be recorded for later
review. If you choose to create the text file, testdisk.log , it
will contain TestDisk options, technical information and various
outputs; including any folder/file names TestDisk was used to find and
list onscreen.

Use arrow keys to select, then press Enter key:
>[ Create ] Create a new log file
 [ Append ] Append information to log file
 [ No Log ] Don't record anything

Hors ligne

#17 Le 16/02/2019, à 22:01

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Tu peux faire create puis choisir le disque dur externe de 1 To (/dev/sdb normalement, vérifie la taille)

Dernière modification par Nuliel (Le 16/02/2019, à 22:02)

Hors ligne

#18 Le 16/02/2019, à 22:07

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org


Disk /dev/sdb - 1000 GB / 931 GiB - TOSHIBA External USB 3.0

Please select the partition table type, press Enter when done.
>[Intel  ] Intel/PC partition
 [EFI GPT] EFI GPT partition map (Mac i386, some x86_64...)
 [Humax  ] Humax partition table
 [Mac    ] Apple partition map
 [None   ] Non partitioned media
 [Sun    ] Sun Solaris partition
 [XBox   ] XBox partition
 [Return ] Return to disk selection




Note: Do NOT select 'None' for media with only a single partition. It's very
rare for a disk to be 'Non-partitioned'.

Dernière modification par Caryn (Le 16/02/2019, à 22:08)

Hors ligne

#19 Le 16/02/2019, à 22:10

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

C'est bon, tu peux prendre le premier choix Intel

Hors ligne

#20 Le 16/02/2019, à 22:12

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org


Disk /dev/sdb - 1000 GB / 931 GiB - TOSHIBA External USB 3.0
     CHS 121601 255 63 - sector size=512

>[ Analyse  ] Analyse current partition structure and search for lost partitions
 [ Advanced ] Filesystem Utils
 [ Geometry ] Change disk geometry
 [ Options  ] Modify options
 [ MBR Code ] Write TestDisk MBR code to first sector
 [ Delete   ] Delete all data in the partition table
 [ Quit     ] Return to disk selection

Hors ligne

#21 Le 16/02/2019, à 22:13

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Ok, tu peux faire analyse

Hors ligne

#22 Le 16/02/2019, à 22:14

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
Current partition structure:
     Partition                  Start        End    Size in sectors


Partition sector doesn't have the endmark 0xAA55











*=Primary bootable  P=Primary  L=Logical  E=Extended  D=Deleted
>[Quick Search]
                            Try to locate partition

Hors ligne

#23 Le 16/02/2019, à 22:15

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Donc le début a visiblement été effacé, en particulier le MBR.
Tu peux faire quick search

Hors ligne

#24 Le 16/02/2019, à 22:16

Caryn

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
     Partition               Start        End    Size in sectors
>* HPFS - NTFS              0  32 33 121601  25 24 1953519616











Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
*=Primary bootable  P=Primary  L=Logical  E=Extended  D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
     Enter: to continue
NTFS, blocksize=4096, 1000 GB / 931 GiB

Hors ligne

#25 Le 16/02/2019, à 22:22

Nuliel

Re : [Résolu] Disque dur invisible depuis branchement sur PS4

Voilà la partition recherchée, avec les flèches tu devrais pouvoir aller sur

>* HPFS - NTFS              0  32 33 121601  25 24 1953519616

et passer de l'étoile * à P avec la flèche gauche ou droite.
en bas devrait apparaitre Quit et Write. Tu choisis write.

Hors ligne