#1 Aujourd'hui à 12:33
- laslack
disque interne non accessible apres modification partition
Bonjour ;
Avec 24.04 j'ai un disque interne de 2To SAMSUNG HD204UI (1AQ10001)
Disque me donne ;
Le disque est sain, un secteur endommagé (27 ℃ / 81 ℉)En modifiant les partitions de ce disque et reformatant j'ai eu l'erreur:
" error wiping device :failed to probe the device /dev/sdb/(udisk-error-quark 0"
J'ai essayé :
jeanpaul@jeanpaul-MS-7846:~$ sudo e2fsck /dev/sdb
[sudo] Mot de passe de jeanpaul :
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Erreur d'entrée/sortie lors de la tentative d'ouverture de /dev/sdb
Le superbloc n'a pu être lu ou ne contient pas un système de fichiers
ext2/ext3/ext4 correct. Si le périphérique est valide et qu'il contient réellement
un système de fichiers ext2/ext3/ext4 (et non pas de type swap, ufs ou autre),
alors le superbloc est corrompu, et vous pourriez tenter d'exécuter
e2fsck avec un autre superbloc :
e2fsck -b 8193 <périphérique>
ou
e2fsck -b 32768 <périphérique>et
jeanpaul@jeanpaul-MS-7846:~$ e2fsck -b 32768 /deb/sdb
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Aucun fichier ou dossier de ce nom lors de la tentative d'ouverture de /deb/sdbC'est comme si le disque n'existait pas
j'ai regardé un peu partout sur le forum , mais je n'ai pas trouvé de solutions pour reparer le secteur endommagé
Pourriez vous m'aider
Merci
Hors ligne
#2 Aujourd'hui à 13:04
- ylag
Re : disque interne non accessible apres modification partition
Bonjour,
jeanpaul@jeanpaul-MS-7846:~$ e2fsck -b 32768 /deb/sdb
Sauf s'il s'agit d'une erreur de copie dans ton message, il faut /dev/sdb au lieu de
/deb/sdb dans la commande ...
A+
Dernière modification par ylag (Aujourd'hui à 13:06)
Hors ligne
#3 Aujourd'hui à 14:40
- geole
Re : disque interne non accessible apres modification partition
Bonjour
Peut-être que ton disque est partitionné. Donne ce retour
sudo fdisk -l /dev/sdbet donc
sudo e2fsck /dev/sdb1Tu indiques que le disque a un secteur fichu donc
sudo smartcl -s on -a /dev/sdbIl te faudra peut-être installer le logiciel
A mon avis, on y verra que le secteur 0 est fichu. C'est lui qui contient la table de partition
Donne aussi ce retour.
journalctl -b | grep "I/O error" | grep "sector" | cut -d" " -f9-12 | sort | uniq -c | sort -k 1n -k 5n | tail -100Dernière modification par geole (Aujourd'hui à 14:53)
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
#4 Aujourd'hui à 18:41
- laslack
Re : disque interne non accessible apres modification partition
Bonjour et merci
@ ylag :effectivement c'est une erreur de frappe.
@ geole :
J'ai installé (par snap) Gsmart control.
Mais voilà les réponses :
jeanpaul@jeanpaul-MS-7846:~$ sudo smartcl -s on -a /dev/sdb
sudo: smartcl : commande introuvableet
jeanpaul@jeanpaul-MS-7846:~$ journalctl -b | grep "I/O error" | grep "sector" | cut -d" " -f9-12 | sort | uniq -c | sort -k 1n -k 5n | tail -100
34 sdb, sector 0 opJ'ai ouvert gsmart et voilà ce que ça donne :
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-52-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F4 EG (AF)
Device Model: SAMSUNG HD204UI
Serial Number: S2H7J9KB616775
LU WWN Device Id: 5 0024e9 20587dc3c
Firmware Version: 1A
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
De plus , la mise en route du PC est très longue avant d'arriver à l'écran du choix du système , puis en core après ...
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sat Feb 1 18:16:41 2025 CET
==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Disabled
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (20760) 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: ( 346) minutes.
SCT capabilities: (0x003f) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 593
2 Throughput_Performance -OS--K 252 252 000 - 0
3 Spin_Up_Time PO---K 065 042 025 - 10862
4 Start_Stop_Count -O--CK 092 092 000 - 8888
5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
7 Seek_Error_Rate -OSR-K 252 252 051 - 0
8 Seek_Time_Performance --S--K 252 252 015 - 0
9 Power_On_Hours -O--CK 100 100 000 - 22355
10 Spin_Retry_Count -O--CK 252 252 051 - 0
11 Calibration_Retry_Count -O--CK 252 252 000 - 0
12 Power_Cycle_Count -O--CK 092 092 000 - 8965
181 Program_Fail_Cnt_Total -O---K 100 100 000 - 418054
191 G-Sense_Error_Rate -O---K 100 100 000 - 69
192 Power-Off_Retract_Count -O---K 252 252 000 - 0
194 Temperature_Celsius -O---- 064 058 000 - 21 (Min/Max 8/42)
195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
196 Reallocated_Event_Count -O--CK 252 252 000 - 0
197 Current_Pending_Sector -O--CK 100 100 000 - 1
198 Offline_Uncorrectable ----CK 252 252 000 - 0
199 UDMA_CRC_Error_Count -OS-CK 100 100 000 - 2
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 41
223 Load_Retry_Count -O--CK 252 252 000 - 0
225 Load_Cycle_Count -O--CK 100 100 000 - 8965
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 2 Comprehensive SMART error log
0x03 GPL R/O 2 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 2 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 304 (device log contains only the most recent 8 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 304 [7] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.598 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.661 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.661 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.661 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.661 IDENTIFY DEVICE
Error 303 [6] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.593 READ FPDMA QUEUED
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.656 READ FPDMA QUEUED
ec 00 00 00 01 00 00 00 00 00 00 00 08 00:00:00.656 IDENTIFY DEVICE
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.656 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.656 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 302 [5] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.588 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.651 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.651 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.651 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.651 IDENTIFY DEVICE
Error 301 [4] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.519 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.645 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 18 40 08 00:00:00.645 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.645 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.645 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 300 [3] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.514 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.640 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.640 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.640 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.640 IDENTIFY DEVICE
Error 299 [2] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.509 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.635 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.635 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.635 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.635 IDENTIFY DEVICE
Error 298 [1] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.370 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.630 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.630 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.630 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.630 IDENTIFY DEVICE
Error 297 [0] occurred at disk power-on lifetime: 22355 hours (931 days + 11 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 08 00:00:00.369 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.625 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.625 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.625 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.625 IDENTIFY DEVICE
SMART Extended Self-test Log Version: 1 (2 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
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.
SCT Status Version: 2
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 21 Celsius
Power Cycle Min/Max Temperature: 16/21 Celsius
Lifetime Min/Max Temperature: 10/62 Celsius
Specified Max Operating Temperature: 80 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 5 minutes
Temperature Logging Interval: 5 minutes
Min/Max recommended Temperature: -5/80 Celsius
Min/Max Temperature Limit: -10/85 Celsius
Temperature History Size (Index): 128 (14)
Index Estimated Time Temperature Celsius
15 2025-02-01 07:40 21 **
16 2025-02-01 07:45 27 ********
... ..( 4 skipped). .. ********
21 2025-02-01 08:10 27 ********
22 2025-02-01 08:15 28 *********
23 2025-02-01 08:20 27 ********
... ..( 4 skipped). .. ********
28 2025-02-01 08:45 27 ********
29 2025-02-01 08:50 17 -
30 2025-02-01 08:55 19 -
31 2025-02-01 09:00 20 *
32 2025-02-01 09:05 21 **
33 2025-02-01 09:10 22 ***
34 2025-02-01 09:15 23 ****
35 2025-02-01 09:20 24 *****
36 2025-02-01 09:25 25 ******
37 2025-02-01 09:30 25 ******
38 2025-02-01 09:35 26 *******
39 2025-02-01 09:40 26 *******
40 2025-02-01 09:45 26 *******
41 2025-02-01 09:50 27 ********
42 2025-02-01 09:55 28 *********
43 2025-02-01 10:00 27 ********
... ..( 12 skipped). .. ********
56 2025-02-01 11:05 27 ********
57 2025-02-01 11:10 28 *********
58 2025-02-01 11:15 28 *********
59 2025-02-01 11:20 27 ********
60 2025-02-01 11:25 28 *********
61 2025-02-01 11:30 27 ********
62 2025-02-01 11:35 28 *********
63 2025-02-01 11:40 29 **********
64 2025-02-01 11:45 30 ***********
... ..( 2 skipped). .. ***********
67 2025-02-01 12:00 30 ***********
68 2025-02-01 12:05 31 ************
... ..( 3 skipped). .. ************
72 2025-02-01 12:25 31 ************
73 2025-02-01 12:30 30 ***********
74 2025-02-01 12:35 30 ***********
75 2025-02-01 12:40 30 ***********
76 2025-02-01 12:45 29 **********
77 2025-02-01 12:50 29 **********
78 2025-02-01 12:55 29 **********
79 2025-02-01 13:00 28 *********
... ..( 5 skipped). .. *********
85 2025-02-01 13:30 28 *********
86 2025-02-01 13:35 27 ********
... ..( 27 skipped). .. ********
114 2025-02-01 15:55 27 ********
115 2025-02-01 16:00 26 *******
116 2025-02-01 16:05 26 *******
117 2025-02-01 16:10 26 *******
118 2025-02-01 16:15 17 -
119 2025-02-01 16:20 19 -
120 2025-02-01 16:25 20 *
121 2025-02-01 16:30 21 **
122 2025-02-01 16:35 23 ****
123 2025-02-01 16:40 24 *****
124 2025-02-01 16:45 25 ******
125 2025-02-01 16:50 25 ******
126 2025-02-01 16:55 26 *******
... ..( 4 skipped). .. *******
3 2025-02-01 17:20 26 *******
4 2025-02-01 17:25 27 ********
... ..( 7 skipped). .. ********
12 2025-02-01 18:05 27 ********
13 2025-02-01 18:10 19 -
14 2025-02-01 18:15 20 *
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0003 4 0 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x0006 4 0 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 0 Device-to-host non-data FIS retries
0x0009 4 21 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 20 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00 4 0 Vendor specific
0x8e01 4 0 Vendor specific
0x8e02 4 0 Vendor specific
0x8e03 4 0 Vendor specific
0x8e04 4 0 Vendor specific
0x8e05 4 0 Vendor specific
0x8e06 4 0 Vendor specific
0x8e07 4 0 Vendor specific
0x8e08 4 0 Vendor specific
0x8e09 4 0 Vendor specific
0x8e0a 4 0 Vendor specific
0x8e0b 4 0 Vendor specific
0x8e0c 4 0 Vendor specific
0x8e0d 4 0 Vendor specific
0x8e0e 4 0 Vendor specific
0x8e0f 4 0 Vendor specific
0x8e10 4 0 Vendor specific
0x8e11 4 0 Vendor specificpour info le contenu du disque est sauvegardé.et il ny a plus de données sur celui ci.
Par ailleurs ,depuis ce pb, la mise en route du pc est très longue,pour arriver à la page du choix du système , puis encore très long avant la mise en route .
J'ai l'impression d'avoir ouver tla boite à emmm
Hors ligne
#5 Aujourd'hui à 18:53
- iznobe
Re : disque interne non accessible apres modification partition
==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/e … Q/223571en
https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks
faudrait en profiter pour mettre à jour le firmware puisqu ' il ne contient plus de données
Dernière modification par iznobe (Aujourd'hui à 18:54)
retour COMPLET et utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne