#1 Le 18/02/2024, à 23:39
- dalron
Disque dur Seagate impossible d'acces... Zut...
Et voilà... un disque externe plein de données personnelles auquel je ne peux plus accéder sous Ubuntu ou Windows... Seagate Expansion Desktop Drive 3To
J'ai lu divers tutos mais je suis largué... Si quelqu'un peut m'aider ce serait hyper cool... Merci d'avance
Ubuntu le détecte, le nomme "3.0 TB Volume"
Si je veux l'ouvrir le DD clignote mais sans s'arrêter ni afficher le contenu.
Si je double clique dessus il m'affiche : "Erreur - An operation is already pending"
Ou bien "Error mounting /dev/sdb1 at /media/romain/74C087F8C087BF3C1: Unknown error when mounting /dev/sdb1"
J'essaie lsblk -af et cela me renvoie :
romain@romain-compaq15notebookpc:~$ lsblk -af
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /snap/cups/1024
loop1
squash 4.0 0 100% /snap/bare/5
loop2
squash 4.0 0 100% /snap/core20/2105
loop3
squash 4.0 0 100% /snap/core22/1033
loop4
squash 4.0 0 100% /snap/core18/2812
loop5
squash 4.0 0 100% /snap/firefox/2987
loop6
squash 4.0 0 100% /snap/chromium/2757
loop7
squash 4.0 0 100% /snap/chromium/2749
loop8
squash 4.0 0 100% /snap/core22/1122
loop9
squash 4.0 0 100% /snap/core20/2182
loop10
squash 4.0 0 100% /snap/firefox/3779
loop11
squash 4.0 0 100% /snap/gnome-3-38-2004/143
loop12
squash 4.0 0 100% /snap/gnome-42-2204/141
loop13
squash 4.0 0 100% /snap/gtk-common-themes/1535
loop14
squash 4.0 0 100% /snap/kde-frameworks-5-core18/35
loop15
squash 4.0 0 100% /snap/qnotero/197
loop16
squash 4.0 0 100% /snap/qt515-core20/29
loop17
squash 4.0 0 100% /snap/signal-desktop/620
loop18
squash 4.0 0 100% /snap/signal-desktop/622
loop19
squash 4.0 0 100% /snap/snapd/19457
loop20
squash 4.0 0 100% /snap/snapd/20671
loop21
squash 4.0 0 100% /snap/whatsie/148
loop22
squash 4.0 0 100% /snap/zotero-snap/65
loop23
sda
├─sda1
│ ntfs WINRE F676F3C376F38323
├─sda2
│ vfat FAT32 72E2-DFCA 98,6M 61% /boot/efi
├─sda3
│
├─sda4
│ ntfs Windows
│ C86C014D6C013828 16,6G 88% /media/romain/Windows
├─sda5
│ ntfs ROMAIN2
│ EA46E4EB46E4BA09 94,1M 99% /media/romain/ROMAIN2
├─sda6
│ ntfs D06813146812F944
├─sda7
│ ntfs ROMAIN
│ 0DDC09680DDC0968 1,4G 99% /media/romain/ROMAIN
├─sda8
│ ext4 1.0 76dce384-cc31-4683-b510-f962317847a0 28,7G 47% /var/snap/firefox/common/host-hunspell
│ /
├─sda9
│ swap 1 619e18c2-e57c-4bfa-a997-0a2cf8008b4d
└─sda10
ntfs RECOVERY
9058F0D458F0B9D4
sdb
└─sdb1
ntfs 74C087F8C087BF3C
J'essaie sudo dmesg | grep sdb
romain@romain-compaq15notebookpc:~$ sudo dmesg | grep sdb
[sudo] Mot de passe de romain :
[ 7516.983202] sd 2:0:0:0: [sdb] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
[ 7516.985027] sd 2:0:0:0: [sdb] Write Protect is off
[ 7516.985053] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 7516.986163] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 7520.655227] sdb: sdb1
[ 7520.655968] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 7586.557204] ntfs3: sdb1: It is recommened to use chkdsk.
[ 7786.032047] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7786.032087] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=192s
[ 7786.032103] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7786.032116] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 7786.032132] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 5d 00 00 1e 00
[ 7786.032141] I/O error, dev sdb, sector 5956328 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 7976.630055] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7976.630096] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=190s
[ 7976.630112] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7976.630126] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 7976.630142] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 7b 00 00 1e 00
[ 7976.630152] I/O error, dev sdb, sector 5956568 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
OU BIEN (si je le branche sans chercher à fouiner dedans)
romain@romain-compaq15notebookpc:~$ sudo dmesg | grep sdb
[sudo] Mot de passe de romain :
[ 7516.983202] sd 2:0:0:0: [sdb] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
[ 7516.985027] sd 2:0:0:0: [sdb] Write Protect is off
[ 7516.985053] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 7516.986163] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 7520.655227] sdb: sdb1
[ 7520.655968] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 7586.557204] ntfs3: sdb1: It is recommened to use chkdsk.
[ 7786.032047] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7786.032087] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=192s
[ 7786.032103] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7786.032116] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 7786.032132] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 5d 00 00 1e 00
[ 7786.032141] I/O error, dev sdb, sector 5956328 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 7976.630055] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7976.630096] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=190s
[ 7976.630112] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7976.630126] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 7976.630142] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 7b 00 00 1e 00
[ 7976.630152] I/O error, dev sdb, sector 5956568 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.715912] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=166s
[ 8142.715944] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 99 00 00 10 00
[ 8142.715956] I/O error, dev sdb, sector 5956808 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 2
[ 8142.728628] device offline error, dev sdb, sector 5956936 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728802] device offline error, dev sdb, sector 5957176 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728835] device offline error, dev sdb, sector 5957416 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728930] device offline error, dev sdb, sector 5957656 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728960] device offline error, dev sdb, sector 5957896 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729051] device offline error, dev sdb, sector 5958136 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729080] device offline error, dev sdb, sector 5958376 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729199] device offline error, dev sdb, sector 5958616 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729220] device offline error, dev sdb, sector 5958856 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 2
[ 8142.792717] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[ 8142.792831] sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 8162.860231] sd 2:0:0:0: [sdb] 732566645 4096-byte logical blocks: (3.00 TB/2.73 TiB)
[ 8162.861571] sd 2:0:0:0: [sdb] Write Protect is off
[ 8162.861593] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 8162.862586] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8162.870097] sdb: sdb1
[ 8162.870758] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 8164.721684] ntfs3: sdb1: It is recommened to use chkdsk.
[ 8165.051316] ntfs3: sdb1: volume is dirty and "force" flag is not set!
Hors ligne
#2 Le 19/02/2024, à 00:11
- geole
Re : Disque dur Seagate impossible d'acces... Zut...
Bonsoir.
Zut, il va certainement falloir que tu en achète un autre.
Tu as dis que windows ne pouvait rien faire.
J'ai vu le probleme dans la trace.
7520.655227] sdb: sdb1
[ 7520.655968] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 7586.557204] ntfs3: sdb1: It is recommened to use chkdsk.
[ 7786.032047] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7786.032087] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=192s
[ 7786.032103] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7786.032116] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Logical unit is in process of becoming ready
[ 7786.032132] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b 5c 5d 00 00 1e 00
[ 7786.032141] I/O error, dev sdb, sector 5956328 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 7976.630055] sd 2:0:0:0: [sdb] tag#0 timing out command, waited 180s
[ 7976.630096] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=190s
[ 7976.630112] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
[ 7976.6301
Il y a un secteur impossible à lire. Cela a duré trois minutes.
I/O error, dev sdb, sector 5956328 timing out command, waited 180s
Dans un premier temps.
Tu vas donner l'état smartctl du disque.
Installation du logiciel https://doc.ubuntu-fr.org/smartmontools
Puis chapitre trois.
Pour la suite, on va tenter d'accèder autrement à ce secteur.Sauf s'il y en a plein dans cet état.
et on tentera de dupliquer le disque car je crains des dégats.
[ 8142.715956] I/O error, dev sdb, sector 5956808 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 2
[ 8142.728628] device offline error, dev sdb, sector 5956936 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728802] device offline error, dev sdb, sector 5957176 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728835] device offline error, dev sdb, sector 5957416 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728930] device offline error, dev sdb, sector 5957656 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.728960] device offline error, dev sdb, sector 5957896 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729051] device offline error, dev sdb, sector 5958136 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729080] device offline error, dev sdb, sector 5958376 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729199] device offline error, dev sdb, sector 5958616 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 2
[ 8142.729220] device offline error, dev sdb, sector 5958856 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 2
[ 8142.792717
Ces secteurs ont probablement aussi un problème
Donne aussi ces retours.
sudo fdisk -l /dev/sdb
ls -ls /dev/disk/by-id
qui pourraient servir à fabriquer la future partition si tu achètes un disque de plus grande taille
Suivant ce que smartcl dira on envisagera de dupluquer ou pas avant de demander à windows de faire un chkdsk de la partition.
Car c'est un peu surprenant que windows n'aient pas proposé de le faire.
Question: As-tu un double des données de ce disque?
Dernière modification par geole (Le 19/02/2024, à 00:40)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 19/02/2024, à 08:23
- dalron
Re : Disque dur Seagate impossible d'acces... Zut...
Merci d'abord pour ton aide
Beaucoup de données n'étaient pas dupliquées donc j'aimerais bien y arriver...
Voici déjà pour Smart...
romain@romain-compaq15notebookpc:~$ sudo smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/sdb -d sat # /dev/sdb [SAT], ATA device
romain@romain-compaq15notebookpc:~$ sudo smartctl -s on -a -d sat /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.5.0-18-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1CH166
Serial Number: W1F1B0G5
LU WWN Device Id: 5 000c50 0538e8888
Firmware Version: CC43
User Capacity: 3000592982016 bytes [3,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Feb 19 08:22:17 2024 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 overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
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: ( 575) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 334) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 093 093 006 Pre-fail Always - 139468449
3 Spin_Up_Time 0x0003 094 091 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 863
5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 3616
7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 8593261526
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 477
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 383
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 259
188 Command_Timeout 0x0032 100 097 000 Old_age Always - 8 8 14
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 079 039 045 Old_age Always In_the_past 21 (0 43 21 17 0)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 260
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 3041
194 Temperature_Celsius 0x0022 021 061 000 Old_age Always - 21 (0 9 0 0 0)
197 Current_Pending_Sector 0x0012 087 017 000 Old_age Always - 2144
198 Offline_Uncorrectable 0x0010 087 017 000 Old_age Offline - 2144
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 207h+44m+13.559s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 14788950528
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1694294667
SMART Error Log Version: 1
ATA Error Count: 195 (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 195 occurred at disk power-on lifetime: 477 hours (19 days + 21 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 00 48 c5 59 00 Error: UNC at LBA = 0x0059c548 = 5883208
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 00 08 48 c5 59 40 00 00:00:33.428 READ DMA EXT
25 00 08 48 a5 59 40 00 00:00:33.371 READ DMA EXT
25 00 08 48 95 59 40 00 00:00:30.353 READ DMA EXT
25 00 08 48 8d 59 40 00 00:00:30.236 READ DMA EXT
25 00 08 48 89 59 40 00 00:00:27.368 READ DMA EXT
Error 194 occurred at disk power-on lifetime: 477 hours (19 days + 21 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 00 48 95 59 00 Error: UNC at LBA = 0x00599548 = 5870920
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 00 08 48 95 59 40 00 00:00:30.353 READ DMA EXT
25 00 08 48 8d 59 40 00 00:00:30.236 READ DMA EXT
25 00 08 48 89 59 40 00 00:00:27.368 READ DMA EXT
25 00 08 48 87 59 40 00 00:00:24.259 READ DMA EXT
25 00 08 48 86 59 40 00 00:00:21.239 READ DMA EXT
Error 193 occurred at disk power-on lifetime: 477 hours (19 days + 21 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 00 48 89 59 00 Error: UNC at LBA = 0x00598948 = 5867848
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 00 08 48 89 59 40 00 00:00:27.368 READ DMA EXT
25 00 08 48 87 59 40 00 00:00:24.259 READ DMA EXT
25 00 08 48 86 59 40 00 00:00:21.239 READ DMA EXT
25 00 08 c8 85 59 40 00 00:00:21.237 READ DMA EXT
25 00 08 88 85 59 40 00 00:00:21.211 READ DMA EXT
Error 192 occurred at disk power-on lifetime: 477 hours (19 days + 21 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 00 48 87 59 00 Error: UNC at LBA = 0x00598748 = 5867336
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 00 08 48 87 59 40 00 00:00:24.259 READ DMA EXT
25 00 08 48 86 59 40 00 00:00:21.239 READ DMA EXT
25 00 08 c8 85 59 40 00 00:00:21.237 READ DMA EXT
25 00 08 88 85 59 40 00 00:00:21.211 READ DMA EXT
25 00 08 68 85 59 40 00 00:00:21.161 READ DMA EXT
Error 191 occurred at disk power-on lifetime: 477 hours (19 days + 21 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 00 48 86 59 00 Error: UNC at LBA = 0x00598648 = 5867080
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 00 08 48 86 59 40 00 00:00:21.239 READ DMA EXT
25 00 08 c8 85 59 40 00 00:00:21.237 READ DMA EXT
25 00 08 88 85 59 40 00 00:00:21.211 READ DMA EXT
25 00 08 68 85 59 40 00 00:00:21.161 READ DMA EXT
25 00 08 58 85 59 40 00 00:00:21.120 READ DMA EXT
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
#4 Le 19/02/2024, à 10:03
- geole
Re : Disque dur Seagate impossible d'acces... Zut...
Bonjour
J'espère que tu pourras te faire rembourser le disque puisqu'il semble jeune.
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 477
Il y a trop se secteurs impossibles à lire
197 Current_Pending_Sector 0x0012 087 017 000 Old_age Always - 2144
Et il en a rencontré un certain nombre de mauvais qualité qu'il a du remplacer au fil de l'eau.
5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 3616
De plus, sa mécanique de recherche n'est pas terrible (environ 50% de ce qu'on peut espérer.).
7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always
.
Cela fait presque deux erreurs par heure.
Error 192 occurred at disk power-on lifetime: 477 hours (19 days + 21 hours)
Donc achat d'un nouveau disque d'au moins 3 TO et un peu de lecture pour patienter.
Lorsque tu auras le nouveau disque, tu reprends contact en donnant ce retour après avoir branché les deux disques et formaté le nouveau disque en NTFS.
ls -ls /dev/disk/by-id
et
sudo fdisk -l
La première commande proposée sera de ce style
sudo ddrescue -f -N -n -b4096 -K524288 /dev/sdb1 /dev/sdc1 $HOME/suivi
sudo ddrescue -f -c1 -b4096 /dev/sdb1 /dev/sdc1 $HOME/suivi
Comme ce sont des disques externes, on mettra les noms des partitions afin d'éviter de faire la copie inverse par accident.
( Je serais très peu disponible dans peu de temps mais il y a d'autres intervenants)
Dernière modification par geole (Le 19/02/2024, à 10:19)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#5 Le 12/03/2024, à 21:49
- dalron
Re : Disque dur Seagate impossible d'acces... Zut...
Bon le disque dur n'est pas endommagé. Je me suis reconnecté avec Windows et il fonctionnait. Puis retour sur Ubuntu il fonctionnait... Deux jours plus tard, même problème avec un autre disque dur externe.... bizarre... et ce soir idem avec un disque interne pour aller sur la partition de sauvegarde de mes données... comme si Ubuntu perdait mes disques en cours de route...
Ce soir j'essaie : sudo ntfsfix /dev/sda7
Mounting volume... $MFTMirr does not match $MFT (record 3).
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda7 was processed successfully.
Ma partition interne est re-accessible ! et idem avec mes disques externes... Haleluya (ou un truc du genre !)
Mais je vais pas recommencer tous les jours hein... Lubuntu il va me fatiguer sinon... Une idée ? Merci beaucoup par avance
Hors ligne
#6 Le 12/03/2024, à 21:58
- geole
Re : Disque dur Seagate impossible d'acces... Zut...
Bonsoir.
Refais des rapports smartctl des disques à problèmes.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#7 Le 13/03/2024, à 09:43
- iznobe
Re : Disque dur Seagate impossible d'acces... Zut...
Bonjour ,
Bon le disque dur n'est pas endommagé.
n ' importe quoi , vu le rapport smartctl , bien sur qu ' il est endommagé !
accessible et endommagé , ce n' est pas l' inverse l' un de l ' autre et c ' est pas parceque le disque est accessible qu ' il n' est pas endommagé .
le rapport smartctl , sera le meme sous windobz et sur ubuntu , montrant les meme secteurs defectueux et exactement le meme etat du disque ( tout abimé ) .
Dans 6 mois ( si tu as de la chance ) ton disque sera complétement mort .
Cela n ' a aucun rapport avec le fait d' utiliser ubuntu .
C ' est plutot le fait que ubuntu est plus regardant sur l 'etat du disque que windobz .
et les disques avec les partitions NTFS , ca se repare avec windobz ! il vaut mieux eviter d ' utilser ntfsfix quand c ' est possible .
meme ubuntu te le dis lui-meme :
[ 7586.557204] ntfs3: sdb1: It is recommened to use chkdsk.
chkdsk est un programme windobz prevu pour reparer le systeme de fichier NTFS qui est proprieté de windobz .
Cela implique que linux ( et donc ubuntu ) , ne sait pas comment faire pour une reparation parfaite .
Ces problemes de disque externe sont surtout dûs au fait de comment on utilise les HDD et surtout comment on les deconnecte en general .
Un disque dur , ca s ' use , petit à petitsauf que dans ton cas il est deja hyper usé pour un nombre d' heure d ' utilisation dérisoire ...
vu son etat on pourrait croire que ca fait 10 ans que tu l' utilises , sauf que non .
Dernière modification par iznobe (Le 13/03/2024, à 09:49)
retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne