Pages : 1
#1 Le 09/09/2018, à 17:08
- toitoinebzh
Disque dur HS ?
Bonjour,
Voilà j'ai récupéré un disque dur 1To auquel j'essaye d'accéder sans succès.
Le disque dur apparait bien sur le bureau, je peux l'ouvrir mais rien n'est visbible à l'intérieur et impossible d'écrire dessus.
J'ai tenté de le formater avec gparted mais j'ai le message 'erreur d'entrée/sortie'.
Voilà le retour de quelques commandes
antoine@Frankenstein:~$ sudo lsblk -o size,name,fstype,label,mountpoint
SIZE NAME FSTYPE LABEL MOUNTPOINT
143,4M loop0 squashfs /snap/skype/48
87M loop1 squashfs /snap/core/5145
140M loop2 squashfs /snap/skype/45
141,3M loop3 squashfs /snap/skype/51
86,9M loop4 squashfs /snap/core/4917
87,9M loop5 squashfs /snap/core/5328
465,8G sda
46,6G ├─sda1 ext4 /
1,9G ├─sda2 swap [SWAP]
46,6G ├─sda3 ext4 /home
370,8G └─sda4 ext4 /document
931,5G sdb
931,5G └─sdb1
1024M sr0 antoine@Frankenstein:~$ sudo smartctl -s on -a /dev/sdb1
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: Elements 1078
Revision: 1056
Compliance: SPC-4
User Capacity: 1000170586112 bytes [1,00 TB]
Logical block size: 512 bytes
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Serial number: WX21EA3XF758
Device type: disk
Local Time is: Sun Sep 9 16:59:49 2018 CEST
NO MEDIUM present in device
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.antoine@Frankenstein:~$ dmesg | tail -30
[10827.178125] sd 6:0:0:0: [sdb] Attached SCSI disk
[10837.202716] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[10837.202725] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[10837.202731] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[10837.202738] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 08 00
[10837.202742] print_req_error: critical medium error, dev sdb, sector 6162672
[10840.975227] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[10840.975235] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[10840.975241] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[10840.975248] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 01 00
[10840.975252] print_req_error: critical medium error, dev sdb, sector 6162672
[10840.975263] Buffer I/O error on dev sdb1, logical block 6160624, async page read
[10844.683870] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[10844.683878] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[10844.683884] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[10844.683891] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f1 00 00 01 00
[10844.683896] print_req_error: critical medium error, dev sdb, sector 6162673
[10844.683907] Buffer I/O error on dev sdb1, logical block 6160625, async page read
[10848.371765] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[10848.371773] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[10848.371779] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[10848.371786] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f2 00 00 06 00
[10848.371791] print_req_error: critical medium error, dev sdb, sector 6162674
[10848.371802] Buffer I/O error on dev sdb1, logical block 6160626, async page read
[10848.371811] Buffer I/O error on dev sdb1, logical block 6160627, async page read
[10848.371817] Buffer I/O error on dev sdb1, logical block 6160628, async page read
[10848.371823] Buffer I/O error on dev sdb1, logical block 6160629, async page read
[10848.371828] Buffer I/O error on dev sdb1, logical block 6160630, async page read
[10848.371832] Buffer I/O error on dev sdb1, logical block 6160631, async page read
[10880.441404] usb 2-3: reset high-speed USB device number 7 using ehci-pciantoine@Frankenstein:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 003: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard)
Bus 007 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 007: ID 1058:1078 Western Digital Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root huble disque dur n'est pas toujours visible sous fdisk -l
Hors ligne
#2 Le 09/09/2018, à 17:32
- Babdu89
Re : Disque dur HS ?
Bonjour,
Pour faire avancer les choses pour les spécialistes des disques dur.
Stp, Veux tu bien refaire le smart contrôle sur le disque /dev/sdb et non sur la partition /dev/sdb1 . C'est ce qui va les intéresser.
Merci pour eux.
@+. Babdu89 .
J'ai découvert Ubuntu avec la 07.10.... Et alors?!... Depuis je regarde de temps en temps si Windows marche toujours....
Hors ligne
#3 Le 09/09/2018, à 17:41
- toitoinebzh
Re : Disque dur HS ?
et voilà
antoine@Frankenstein:~$ sudo smartctl -s on -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x1058:0x1078 (0x1056)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryHors ligne
#4 Le 09/09/2018, à 19:00
- Babdu89
Re : Disque dur HS ?
Bonsoir.
Ce n'est pas bon, voir ici comment faire
https://doc.ubuntu-fr.org/smartmontools
Je ne suis pas spécialiste en la question, mais si çà peut faire avancer les réponses qui te seront apportées.
Peut-être ceci d'après la doc;
sudo smartctl -s on -a /dev/sdb@+. Babdu89 .
Dernière modification par Babdu89 (Le 09/09/2018, à 19:02)
J'ai découvert Ubuntu avec la 07.10.... Et alors?!... Depuis je regarde de temps en temps si Windows marche toujours....
Hors ligne
#5 Le 09/09/2018, à 19:20
- toitoinebzh
Re : Disque dur HS ?
ta commande donne
antoine@Frankenstein:~$ sudo smartctl -s on -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x1058:0x1078 (0x1056)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryvoilà a quoi j'arrive avec la doc
antoine@Frankenstein:~$ sudo smartctl -s on -d scsi -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: Elements 1078
Revision: 1056
Compliance: SPC-4
User Capacity: 1000170586112 bytes [1,00 TB]
Logical block size: 512 bytes
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Serial number: WX21EA3XF758
Device type: disk
Local Time is: Sun Sep 9 19:13:29 2018 CEST
NO MEDIUM present in device
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.Hors ligne
#6 Le 09/09/2018, à 19:26
- xinu
Re : Disque dur HS ?
/dev/sdb: Unknown USB bridge [0x1058:0x1078 (0x1056)]
A la vue de ce message, tu peux tenter la commande suivante :
sudo smartctl -s on -d sat -a /dev/sdbAsus PM8H61-MX USB3 Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz DDR3 8Go
Ubuntu 16.04 LTS - ESM 64 bits. Bureau Unity. Ubuntu 20.04 LTS 64 bits . Gnome 3.36.8
Hors ligne
#7 Le 09/09/2018, à 19:31
- toitoinebzh
Re : Disque dur HS ?
salut
avec l'option "sat" ça ne fonctionne pas, avec "scsi" j'ai un retour
voilà les deux commandes
antoine@Frankenstein:~$ sudo smartctl -s on -d sat -a /dev/sdb
[sudo] Mot de passe de antoine :
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error no medium present
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.antoine@Frankenstein:~$ sudo smartctl -s on -d scsi -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: Elements 1078
Revision: 1056
Compliance: SPC-4
User Capacity: 1000170586112 bytes [1,00 TB]
Logical block size: 512 bytes
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Serial number: WX21EA3XF758
Device type: disk
Local Time is: Sun Sep 9 19:30:20 2018 CEST
NO MEDIUM present in device
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
antoine@Frankenstein:~$ Dernière modification par toitoinebzh (Le 09/09/2018, à 19:35)
Hors ligne
#8 Le 09/09/2018, à 19:41
- xinu
Re : Disque dur HS ?
Essayer ces commandes une à la fois, en remplaçant X par la lettre qui identifie ton disque (dans ton cas c'est la lettre b).
sudo smartctl -s on -d ata -a /dev/sdX
sudo smartctl -s on -d auto -T verypermissive -a /dev/sdX
sudo smartctl -s on -d test -T verypermissive -a /dev/sdXDernière modification par xinu (Le 09/09/2018, à 19:42)
Asus PM8H61-MX USB3 Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz DDR3 8Go
Ubuntu 16.04 LTS - ESM 64 bits. Bureau Unity. Ubuntu 20.04 LTS 64 bits . Gnome 3.36.8
Hors ligne
#9 Le 09/09/2018, à 19:44
- toitoinebzh
Re : Disque dur HS ?
et voilà les 3 commandes
antoine@Frankenstein:~$ sudo smartctl -s on -d ata -a /dev/sdb
[sudo] Mot de passe de antoine :
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: Invalid argument
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
antoine@Frankenstein:~$ sudo smartctl -s on -d auto -T verypermissive -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x1058:0x1078 (0x1056)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
antoine@Frankenstein:~$ sudo smartctl -s on -d test -T verypermissive -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x1058:0x1078 (0x1056)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
antoine@Frankenstein:~$ edit :
j'ai vu que tu as modifier ton message voilà la premiere commande corrigée
antoine@Frankenstein:~$ sudo smartctl -s on -d ata -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: Invalid argument
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.Dernière modification par toitoinebzh (Le 09/09/2018, à 19:47)
Hors ligne
#10 Le 09/09/2018, à 21:06
- xinu
Re : Disque dur HS ?
Je sèche 
Sinon, il reste la possibilité de sortir le disque de son boîtier et de le connecter directement au port SATA interne...
Mais en se basant sur le premier message et les erreurs de lecture rapportées par dmesg, il y a peu de chances que ce disque soit encore utilisable.
A+
Dernière modification par xinu (Le 10/09/2018, à 17:27)
Asus PM8H61-MX USB3 Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz DDR3 8Go
Ubuntu 16.04 LTS - ESM 64 bits. Bureau Unity. Ubuntu 20.04 LTS 64 bits . Gnome 3.36.8
Hors ligne
#11 Le 09/09/2018, à 21:33
- Babdu89
Re : Disque dur HS ?
Et avec les commandes données dans le chapitre ; 3.4 Cas des boîtiers et autres adaptateurs USB, de la doc?
https://doc.ubuntu-fr.org/smartmontools
Avec;
sudo smartctl -s on -a -d sat /dev/sdb@+. Babdu89 .
Dernière modification par Babdu89 (Le 09/09/2018, à 21:51)
J'ai découvert Ubuntu avec la 07.10.... Et alors?!... Depuis je regarde de temps en temps si Windows marche toujours....
Hors ligne
#12 Le 09/09/2018, à 22:32
- moko138
Re : Disque dur HS ?
"d sat" a déjà été montré à 19h31.
- -
Tu peux essayer
sudo smartctl -s on -d sat -T verypermissive -a /dev/sdbet
sudo smartctl -s on -d scsi -T verypermissive -a /dev/sdbMais surtout, montre
dmesg | grep -C50 "10827.178125" | head -51et, séparément :
dmesg | grep -Ei "I/O error|sdb|logical block|lba"Et comme l'a dit xinu, le disque est mal en point.
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#13 Le 10/09/2018, à 17:40
- toitoinebzh
Re : Disque dur HS ?
et voilà le tout
antoine@Frankenstein:~$ dmesg | tail -30
[ 670.258016] sd 6:0:0:0: [sdb] Spinning up disk...
[ 671.275998] .
[ 672.300077] .
[ 673.324120] .
[ 674.348169] .
[ 674.469548] ready
[ 674.469964] sd 6:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
[ 674.471217] sd 6:0:0:0: [sdb] Write Protect is off
[ 674.471224] sd 6:0:0:0: [sdb] Mode Sense: 53 00 10 08
[ 674.472484] sd 6:0:0:0: [sdb] No Caching mode page found
[ 674.472494] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 674.617352] sdb: sdb1
[ 674.621823] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 683.825603] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 683.825611] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 683.825617] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 683.825624] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 08 00
[ 683.825629] print_req_error: critical medium error, dev sdb, sector 6162672
[ 687.536619] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 687.536627] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 687.536633] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 687.536640] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 01 00
[ 687.536645] print_req_error: critical medium error, dev sdb, sector 6162672
[ 687.536657] Buffer I/O error on dev sdb1, logical block 6160624, async page read
[ 691.376110] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 691.376118] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 691.376124] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 691.376131] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f1 00 00 01 00
[ 691.376136] print_req_error: critical medium error, dev sdb, sector 6162673
[ 691.376147] Buffer I/O error on dev sdb1, logical block 6160625, async page readantoine@Frankenstein:~$ sudo smartctl -s on -d sat -T verypermissive -a /dev/sdb
[sudo] Mot de passe de antoine :
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error no medium present
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: [No Information Found]
Local Time is: Mon Sep 10 17:34:43 2018 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enable failed: scsi error no medium present
Read SMART Data failed: scsi error no medium present
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error no medium present
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
Read SMART Error Log failed: scsi error no medium present
Read SMART Self-test Log failed: scsi error no medium present
Selective Self-tests/Logging not supportedantoine@Frankenstein:~$ sudo smartctl -s on -d sat -T verypermissive -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error no medium present
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: [No Information Found]
Local Time is: Mon Sep 10 17:34:50 2018 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enable failed: scsi error no medium present
Read SMART Data failed: scsi error no medium present
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error no medium present
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
Read SMART Error Log failed: scsi error no medium present
Read SMART Self-test Log failed: scsi error no medium present
Selective Self-tests/Logging not supportedantoine@Frankenstein:~$ sudo smartctl -s on -d scsi -T verypermissive -a /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-33-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WD
Product: Elements 1078
Revision: 1056
Compliance: SPC-4
User Capacity: 1000170586112 bytes [1,00 TB]
Logical block size: 512 bytes
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Serial number: WX21EA3XF758
Device type: disk
Local Time is: Mon Sep 10 17:35:32 2018 CEST
NO MEDIUM present in device
SMART support is: Unavailable - device lacks SMART capability.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
unable to fetch IEC (SMART) mode page [unsupported field in scsi command]
=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Error Counter logging not supported
No self-tests have been loggedantoine@Frankenstein:~$ dmesg | grep -C50 "674.621823" | head -51
[ 25.979828] audit: type=1400 audit(1536592915.571:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=712 comm="apparmor_parser"
[ 25.979833] audit: type=1400 audit(1536592915.571:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=712 comm="apparmor_parser"
[ 25.979835] audit: type=1400 audit(1536592915.571:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=712 comm="apparmor_parser"
[ 25.980170] audit: type=1400 audit(1536592915.575:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=709 comm="apparmor_parser"
[ 25.980173] audit: type=1400 audit(1536592915.575:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=709 comm="apparmor_parser"
[ 25.980175] audit: type=1400 audit(1536592915.575:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=709 comm="apparmor_parser"
[ 25.980177] audit: type=1400 audit(1536592915.575:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=709 comm="apparmor_parser"
[ 25.980412] audit: type=1400 audit(1536592915.575:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=708 comm="apparmor_parser"
[ 25.980416] audit: type=1400 audit(1536592915.575:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=708 comm="apparmor_parser"
[ 25.980853] audit: type=1400 audit(1536592915.575:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=713 comm="apparmor_parser"
[ 28.025153] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 28.321430] r8169 0000:03:00.0 enp3s0: link down
[ 28.321433] r8169 0000:03:00.0 enp3s0: link down
[ 28.321516] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 29.767825] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
[ 29.768267] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
[ 29.951259] nvidia-modeset: Allocated GPU:0 (GPU-2128742c-14b4-59d9-cdd5-da3358930c02) @ PCI:0000:01:00.0
[ 30.604922] r8169 0000:03:00.0 enp3s0: link up
[ 30.604930] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 31.661405] vboxdrv: Found 4 processor cores
[ 31.680227] vboxdrv: TSC mode is Invariant, tentative frequency 3221476731 Hz
[ 31.680228] vboxdrv: Successfully loaded version 5.2.10_Ubuntu (interface 0x00290001)
[ 31.685908] VBoxNetFlt: Successfully started.
[ 31.690780] VBoxNetAdp: Successfully started.
[ 31.694469] VBoxPciLinuxInit
[ 31.697389] vboxpci: IOMMU not found (not registered)
[ 668.984017] usb 2-3: new high-speed USB device number 2 using ehci-pci
[ 669.142387] usb 2-3: New USB device found, idVendor=1058, idProduct=1078
[ 669.142394] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 669.142399] usb 2-3: Product: Elements 1078
[ 669.142402] usb 2-3: Manufacturer: Western Digital
[ 669.142406] usb 2-3: SerialNumber: 575832314541335846373538
[ 669.243172] usb-storage 2-3:1.0: USB Mass Storage device detected
[ 669.243467] scsi host6: usb-storage 2-3:1.0
[ 669.243742] usbcore: registered new interface driver usb-storage
[ 669.272918] usbcore: registered new interface driver uas
[ 670.253193] scsi 6:0:0:0: Direct-Access WD Elements 1078 1056 PQ: 0 ANSI: 6
[ 670.253967] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 670.258016] sd 6:0:0:0: [sdb] Spinning up disk...
[ 671.275998] .
[ 672.300077] .
[ 673.324120] .
[ 674.348169] .
[ 674.469548] ready
[ 674.469964] sd 6:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
[ 674.471217] sd 6:0:0:0: [sdb] Write Protect is off
[ 674.471224] sd 6:0:0:0: [sdb] Mode Sense: 53 00 10 08
[ 674.472484] sd 6:0:0:0: [sdb] No Caching mode page found
[ 674.472494] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 674.617352] sdb: sdb1
[ 674.621823] sd 6:0:0:0: [sdb] Attached SCSI diskantoine@Frankenstein:~$ dmesg | grep -Ei "I/O error|sdb|logical block|lba"
[ 3.042495] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 3.043872] sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 670.258016] sd 6:0:0:0: [sdb] Spinning up disk...
[ 674.469964] sd 6:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
[ 674.471217] sd 6:0:0:0: [sdb] Write Protect is off
[ 674.471224] sd 6:0:0:0: [sdb] Mode Sense: 53 00 10 08
[ 674.472484] sd 6:0:0:0: [sdb] No Caching mode page found
[ 674.472494] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 674.617352] sdb: sdb1
[ 674.621823] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 683.825603] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 683.825611] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 683.825617] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 683.825624] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 08 00
[ 683.825629] print_req_error: critical medium error, dev sdb, sector 6162672
[ 687.536619] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 687.536627] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 687.536633] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 687.536640] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f0 00 00 01 00
[ 687.536645] print_req_error: critical medium error, dev sdb, sector 6162672
[ 687.536657] Buffer I/O error on dev sdb1, logical block 6160624, async page read
[ 691.376110] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 691.376118] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 691.376124] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 691.376131] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f1 00 00 01 00
[ 691.376136] print_req_error: critical medium error, dev sdb, sector 6162673
[ 691.376147] Buffer I/O error on dev sdb1, logical block 6160625, async page read
[ 695.128872] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 695.128880] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[ 695.128885] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error
[ 695.128892] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 5e 08 f2 00 00 06 00
[ 695.128897] print_req_error: critical medium error, dev sdb, sector 6162674
[ 695.128908] Buffer I/O error on dev sdb1, logical block 6160626, async page read
[ 695.128917] Buffer I/O error on dev sdb1, logical block 6160627, async page read
[ 695.128923] Buffer I/O error on dev sdb1, logical block 6160628, async page read
[ 695.128928] Buffer I/O error on dev sdb1, logical block 6160629, async page read
[ 695.128933] Buffer I/O error on dev sdb1, logical block 6160630, async page read
[ 695.128938] Buffer I/O error on dev sdb1, logical block 6160631, async page read
[ 791.344286] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.344294] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.344301] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.344308] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e 3e 50 00 00 f0 00
[ 791.344312] print_req_error: I/O error, dev sdb, sector 6176336
[ 791.344324] Buffer I/O error on dev sdb1, logical block 6174288, lost async page write
[ 791.344334] Buffer I/O error on dev sdb1, logical block 6174289, lost async page write
[ 791.344340] Buffer I/O error on dev sdb1, logical block 6174290, lost async page write
[ 791.344345] Buffer I/O error on dev sdb1, logical block 6174291, lost async page write
[ 791.344350] Buffer I/O error on dev sdb1, logical block 6174292, lost async page write
[ 791.344356] Buffer I/O error on dev sdb1, logical block 6174293, lost async page write
[ 791.344361] Buffer I/O error on dev sdb1, logical block 6174294, lost async page write
[ 791.344366] Buffer I/O error on dev sdb1, logical block 6174295, lost async page write
[ 791.344378] Buffer I/O error on dev sdb1, logical block 6174296, lost async page write
[ 791.344383] Buffer I/O error on dev sdb1, logical block 6174297, lost async page write
[ 791.349901] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.349909] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.349915] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.349921] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e 3f 40 00 00 f0 00
[ 791.349925] print_req_error: I/O error, dev sdb, sector 6176576
[ 791.354766] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.354773] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.354779] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.354785] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e bd d8 00 00 f0 00
[ 791.354789] print_req_error: I/O error, dev sdb, sector 6208984
[ 791.360401] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.360409] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.360415] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.360421] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e be c8 00 00 f0 00
[ 791.360425] print_req_error: I/O error, dev sdb, sector 6209224
[ 791.366137] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.366144] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.366150] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.366156] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e bf b8 00 00 f0 00
[ 791.366160] print_req_error: I/O error, dev sdb, sector 6209464
[ 791.371888] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.371895] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.371901] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.371907] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e c0 a8 00 00 f0 00
[ 791.371911] print_req_error: I/O error, dev sdb, sector 6209704
[ 791.377510] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.377517] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.377524] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.377530] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e c1 98 00 00 f0 00
[ 791.377534] print_req_error: I/O error, dev sdb, sector 6209944
[ 791.383260] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.383267] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.383273] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.383279] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e c2 88 00 00 f0 00
[ 791.383283] print_req_error: I/O error, dev sdb, sector 6210184
[ 791.388884] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.388891] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.388897] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.388904] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e c3 78 00 00 f0 00
[ 791.388907] print_req_error: I/O error, dev sdb, sector 6210424
[ 791.394632] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 791.394640] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 791.394646] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 791.394652] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 5e c4 68 00 00 f0 00
[ 791.394656] print_req_error: I/O error, dev sdb, sector 6210664
antoine@Frankenstein:~$ Hors ligne
#14 Le 10/09/2018, à 18:55
- moko138
Re : Disque dur HS ?
Extrait de dmesg | grep -Ei "I/O error|sdb|logical block|lba"
en rangeant dans l'ordre numérique les secteurs qui présentent
soit une erreur d'entrée sortie ("I/O error")
soit une erreur crtique du support ("critical medium error") :
[ 687.536657] Buffer I/O error on dev sdb1, logical block 6160624, async page read
[ 691.376147] Buffer I/O error on dev sdb1, logical block 6160625, async page read
[ 695.128908] Buffer I/O error on dev sdb1, logical block 6160626, async page read
[ 695.128917] Buffer I/O error on dev sdb1, logical block 6160627, async page read
[ 695.128923] Buffer I/O error on dev sdb1, logical block 6160628, async page read
[ 695.128928] Buffer I/O error on dev sdb1, logical block 6160629, async page read
[ 695.128933] Buffer I/O error on dev sdb1, logical block 6160630, async page read
[ 695.128938] Buffer I/O error on dev sdb1, logical block 6160631, async page read
[ 683.825629] print_req_error: critical medium error, dev sdb, sector 6162672
[ 683.825629] print_req_error: critical medium error, dev sdb, sector 6162672
[ 687.536645] print_req_error: critical medium error, dev sdb, sector 6162672
[ 691.376136] print_req_error: critical medium error, dev sdb, sector 6162673
[ 687.536645] print_req_error: critical medium error, dev sdb, sector 6162672
[ 691.376136] print_req_error: critical medium error, dev sdb, sector 6162673
[ 695.128897] print_req_error: critical medium error, dev sdb, sector 6162674
[ 791.344324] Buffer I/O error on dev sdb1, logical block 6174288, lost async page write
[ 791.344334] Buffer I/O error on dev sdb1, logical block 6174289, lost async page write
[ 791.344340] Buffer I/O error on dev sdb1, logical block 6174290, lost async page write
[ 791.344345] Buffer I/O error on dev sdb1, logical block 6174291, lost async page write
[ 791.344350] Buffer I/O error on dev sdb1, logical block 6174292, lost async page write
[ 791.344356] Buffer I/O error on dev sdb1, logical block 6174293, lost async page write
[ 791.344361] Buffer I/O error on dev sdb1, logical block 6174294, lost async page write
[ 791.344366] Buffer I/O error on dev sdb1, logical block 6174295, lost async page write
[ 791.344378] Buffer I/O error on dev sdb1, logical block 6174296, lost async page write
[ 791.344383] Buffer I/O error on dev sdb1, logical block 6174297, lost async page write
[ 791.344312] print_req_error: I/O error, dev sdb, sector 6176336
[ 791.349925] print_req_error: I/O error, dev sdb, sector 6176576
[ 791.354789] print_req_error: I/O error, dev sdb, sector 6208984
[ 791.360425] print_req_error: I/O error, dev sdb, sector 6209224
[ 791.366160] print_req_error: I/O error, dev sdb, sector 6209464
[ 791.371911] print_req_error: I/O error, dev sdb, sector 6209704
[ 791.377534] print_req_error: I/O error, dev sdb, sector 6209944
[ 791.383283] print_req_error: I/O error, dev sdb, sector 6210184
[ 791.388907] print_req_error: I/O error, dev sdb, sector 6210424
[ 791.394656] print_req_error: I/O error, dev sdb, sector 6210664Les erreurs actuelles - mais ça va se propager - vont
du secteur 6.160.624 au secteur 6.210.664.
Si je comprends bien ton
j'ai récupéré un disque dur 1To
on t'a donné une ruine et tu n'as aucune donnée à récupérer dessus.
Est-ce exact ?
Si oui,
a) et si tu trouves des outils compatibles avec l'état de ton disque, tu peux t'amuser :
- à créer une nouvelle table des partitions
- puis à créer une partition commençant à 20.480 Mio (= 20 Gio). Aucune partition avant, puisque le mal va se propager.
b) ou bien tu as gagné un presse-papiers.
- -
Si non et que tu as des données à récupérer,
alors tu débranches immédiatement le disque, pour les raisons exposées là : Récupération de données - Importance de débrancher le disque,
puis tu ouvres un fil de récupération, en indiquant l'url ./viewtopic.php?id=2030481 du présent fil.
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#15 Le 10/09/2018, à 20:05
- toitoinebzh
Re : Disque dur HS ?
oui je l'ai récupérer sans savoir si ce dd fonctionnait
je cherche à le refaire marcher
j'ai déja tenter de créer une nouvelle table de partition avec gparted, j'ai le message 'erreur d'entrée/sortie'.
je pense que je vais devoir choisir la solution b 
Hors ligne
Pages : 1