Liebes Forum,
ich bräuchte hier mal ein paar Denkanstöße. Meine aktuelle Vermutung ist, dass mein USB-Adapter meine beiden mSATA-SSDs getötet hat. Allerdings ist mir unklar, wie es dazu kommen konnte.
Zur Vorgeschichte sei gesagt, ich musste das Supermicro Mainboard in die RMA schicken, weil das IPMI ohne ersichtlichen Grund gestorben war, sonst aber alles funktioniert hat.
Aufbau der besagten Platten war ein einfaches MDADM@RAID1 + Cryptsetup + LVM2
Während das Board bei der RMA lag, habe ich daher die beiden Platten per USB angeschlossen, um an paar Daten ranzukommen, welche ich vor dem Mainboardausbau vergessen hatte zu sichern.
Soweit kein Problem, nachdem ich mit MDADM das RAID1 aktiviert hatte, mit cryptsetup die Platten entschlüsselt hatte und via LVM die Volumes eingebunden hatte, konnte ich die Datei rauskopieren.
Bevor ich allerdings dazu kommen konnte, wieder die Platten unzumounten, hatte sich mein Rechner komplett aufgehangen. Und ab diesen Punkt fingen nun die Probleme an.
Die Probleme tauchen an JEDEM PC auf, wo ich die Platten ganz normal per S-ATA oder USB-Adapter anschließe. Daher die Vermutung, dass die Platten nun einen (elektrischen?) Schaden haben?
Es fängt damit an, dass die Platten sukzessive von SATA 6gb/s auf ATA/33 runtergestuft werden.
Das kann ich via "dmesg" sehen, passiert, wenn ich auf die Platten anfange zuzugreifen.
Direkt nach dem Booten sehe ich nur, dass zumindest diese am SATA 6gb/s Controller auf 3gb/s heruntergestuft werden.
Je länger der Zugriff stattfindet, desto weiter wird die Platte heruntergestuft.
Die Probleme fangen aber erst beim Zugriff auf die Partitionen an.
Ein Zusammenbau des RAID1 via MDADM wird noch kein Fehler in dmesg gemeldet.
Ebenfalls die Entschlüsselung via Cryptsetup und das LVM einbinden melden nichts in dmesg.
Es geht dann damit los, sobald ich dann ein Volume aus dem VG lokal mounten möchte.
Einige Volumes werden nach 10-20 Sekunden Wartezeit (in der Zeit wird dmesg zugespammt) doch gemountet, bei anderen hängt der Zugriff für immer und dmesg wird dauerhaft zugemüllt.
Im Log kommt immer wieder das selbe, egal welche der beiden Platten ich nutze:
Code:
Jan 19 13:13:02 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:02 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:02 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:02 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 18\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:02 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:02 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:02 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:02 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:02 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:02 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:02 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:02 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:02 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:02 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:02 sysresccd kernel: ata5: EH complete
Jan 19 13:13:02 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:02 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:02 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:02 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 20\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:02 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:02 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:02 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:02 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:02 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:03 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:03 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:03 sysresccd kernel: ata5: EH complete
Jan 19 13:13:03 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:03 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:03 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:03 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 23\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:03 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:03 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:03 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:03 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:03 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:03 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:03 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:03 sysresccd kernel: ata5: EH complete
Jan 19 13:13:03 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:03 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:03 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:03 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 26\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:03 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:03 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:03 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:03 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:03 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:03 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:03 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:03 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:03 sysresccd kernel: ata5: EH complete
Jan 19 13:13:03 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:03 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:03 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:03 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 29\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:03 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:03 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:03 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:03 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:03 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:04 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:04 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:04 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:04 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:04 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:04 sysresccd kernel: ata5: EH complete
Jan 19 13:13:04 sysresccd kernel: ata5.00: Enabling discard_zeroes_data
Jan 19 13:13:04 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:04 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:04 sysresccd kernel: ata5.00: failed command: FLUSH CACHE EXT
Jan 19 13:13:04 sysresccd kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:04 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:04 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:04 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:04 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:04 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:04 sysresccd kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 13:13:04 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:04 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:04 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:04 sysresccd kernel: ata5.00: device reported invalid CHS sector 0
Jan 19 13:13:04 sysresccd kernel: sd 4:0:0:0: [sde] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 19 13:13:04 sysresccd kernel: sd 4:0:0:0: [sde] tag#1 Sense Key : Illegal Request [current]
Jan 19 13:13:04 sysresccd kernel: sd 4:0:0:0: [sde] tag#1 Add. Sense: Unaligned write command
Jan 19 13:13:04 sysresccd kernel: sd 4:0:0:0: [sde] tag#1 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Jan 19 13:13:04 sysresccd kernel: print_req_error: I/O error, dev sde, sector 264208
Jan 19 13:13:04 sysresccd kernel: md: super_written gets error=10
Jan 19 13:13:04 sysresccd kernel: ata5: EH complete
Jan 19 13:13:04 sysresccd kernel: md0: detected capacity change from 509893148672 to 0
Jan 19 13:13:04 sysresccd kernel: md: md0 stopped.
Jan 19 13:13:04 sysresccd kernel: ata5.00: Enabling discard_zeroes_data
Jan 19 13:13:15 sysresccd kernel: ata5: limiting SATA link speed to 1.5 Gbps
Jan 19 13:13:15 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 19 13:13:15 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:15 sysresccd kernel: ata5.00: failed command: WRITE DMA
Jan 19 13:13:15 sysresccd kernel: ata5.00: cmd ca/00:80:00:00:00/00:00:00:00:00/e0 tag 10 dma 65536 out\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:15 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:15 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:15 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:15 sysresccd kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 19 13:13:15 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:15 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:13:15 sysresccd kernel: ata5.00: configured for UDMA/133
Jan 19 13:13:15 sysresccd kernel: ata5: EH complete
Jan 19 13:13:15 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:13:15 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:13:15 sysresccd kernel: ata5.00: failed command: WRITE DMA
Jan 19 13:13:15 sysresccd kernel: ata5.00: cmd ca/00:80:00:00:00/00:00:00:00:00/e0 tag 12 dma 65536 out\x0a res 71/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
Jan 19 13:13:15 sysresccd kernel: ata5.00: status: { DRDY DF ERR }
Jan 19 13:13:15 sysresccd kernel: ata5.00: error: { ABRT }
Jan 19 13:13:15 sysresccd kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV
Jan 19 13:13:15 sysresccd kernel: ata5.00: revalidation failed (errno=-2)
Jan 19 13:13:15 sysresccd kernel: ata5: hard resetting link
Jan 19 13:13:16 sysresccd kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Eine Sache speziell fällt auf, im Log fällt immer wieder ein spezieller Sektor:
print_req_error: I/O error, dev sde, sector 264208
Was mich wundert, BEIDE Platten melden genau diesen Sektor im Log. Das ist mir einfach wenig zuviel Zufall.
SMART-Tests kann ich zwar erfolgreich starten, aber diese bleiben bei 90% dauerhaft hängen:
Code:
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.20-std521-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron MX1/2/300, M5/600, 1100 Client SSDs
Device Model: Crucial_CT512M550SSD3
Serial Number: xxx
LU WWN Device Id: 5 00a075 10c00f26b
Firmware Version: MU02
User Capacity: 512,110,190,592 bytes [512 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: < 1.8 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Jan 19 20:39:49 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 32) The self-test routine was interrupted
by the host with a hard or soft reset.
Total time to complete Offline
data collection: ( 2380) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 6) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x0035) SCT Status 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 0x002f 100 100 000 Pre-fail Always - 96861
5 Reallocate_NAND_Blk_Cnt 0x0033 100 100 000 Pre-fail Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 29849
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 222
171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0
173 Ave_Block-Erase_Count 0x0032 094 094 000 Old_age Always - 185
174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always - 142
180 Unused_Reserve_NAND_Blk 0x0033 000 000 000 Pre-fail Always - 4403
183 SATA_Interfac_Downshift 0x0032 100 100 000 Old_age Always - 19
184 Error_Correction_Count 0x0032 100 100 000 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 064 033 000 Old_age Always - 36 (Min/Max 29/67)
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 100 100 000 Old_age Always - 0
202 Percent_Lifetime_Used 0x0031 094 094 000 Pre-fail Offline - 6
206 Write_Error_Rate 0x000e 100 100 000 Old_age Always - 0
210 Success_RAIN_Recov_Cnt 0x0032 100 100 000 Old_age Always - 0
246 Total_Host_Sector_Write 0x0032 100 100 000 Old_age Always - 49489268429
247 Host_Program_Page_Count 0x0032 100 100 000 Old_age Always - 4036082790
248 Bckgnd_Program_Page_Cnt 0x0032 100 100 000 Old_age Always - 4660825931
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Self-test routine in progress 90% 29849 -
# 2 Extended offline Completed without error 00% 29802 -
# 3 Short offline Completed without error 00% 29796 -
# 4 Extended offline Completed without error 00% 29633 -
# 5 Short offline Completed without error 00% 29627 -
# 6 Extended offline Completed without error 00% 29464 -
# 7 Short offline Completed without error 00% 29458 -
# 8 Extended offline Completed without error 00% 29295 -
# 9 Short offline Completed without error 00% 29289 -
#10 Extended offline Completed without error 00% 29126 -
#11 Short offline Completed without error 00% 29120 -
#12 Extended offline Completed without error 00% 28958 -
#13 Short offline Completed without error 00% 28952 -
#14 Extended offline Completed without error 00% 28789 -
#15 Short offline Completed without error 00% 28783 -
#16 Extended offline Completed without error 00% 28620 -
#17 Short offline Completed without error 00% 28614 -
#18 Extended offline Completed without error 00% 28451 -
#19 Short offline Completed without error 00% 28445 -
#20 Extended offline Completed without error 00% 28283 -
#21 Short offline Completed without error 00% 28277 -
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.
Code:
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.20-std521-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron MX1/2/300, M5/600, 1100 Client SSDs
Device Model: Crucial_CT512M550SSD3
Serial Number: xxx
LU WWN Device Id: 5 00a075 10dbc4b80
Firmware Version: MU02
User Capacity: 512,110,190,592 bytes [512 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: < 1.8 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Jan 19 20:39:58 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 2380) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 6) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x0035) SCT Status 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 0x002f 100 100 000 Pre-fail Always - 0
5 Reallocate_NAND_Blk_Cnt 0x0033 100 100 000 Pre-fail Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 11749
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 135
171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0
173 Ave_Block-Erase_Count 0x0032 089 089 000 Old_age Always - 347
174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always - 76
180 Unused_Reserve_NAND_Blk 0x0033 000 000 000 Pre-fail Always - 4403
183 SATA_Interfac_Downshift 0x0032 100 100 000 Old_age Always - 19
184 Error_Correction_Count 0x0032 100 100 000 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 061 026 000 Old_age Always - 39 (Min/Max 26/74)
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 100 100 000 Old_age Always - 0
202 Percent_Lifetime_Used 0x0031 089 089 000 Pre-fail Offline - 11
206 Write_Error_Rate 0x000e 100 100 000 Old_age Always - 0
210 Success_RAIN_Recov_Cnt 0x0032 100 100 000 Old_age Always - 0
246 Total_Host_Sector_Write 0x0032 100 100 000 Old_age Always - 29475772615
247 Host_Program_Page_Count 0x0032 100 100 000 Old_age Always - 1230460200
248 Bckgnd_Program_Page_Cnt 0x0032 100 100 000 Old_age Always - 10642295215
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Self-test routine in progress 90% 11741 -
# 2 Extended offline Completed without error 00% 11701 -
# 3 Short offline Completed without error 00% 11695 -
# 4 Extended offline Completed without error 00% 11533 -
# 5 Short offline Completed without error 00% 11526 -
# 6 Extended offline Completed without error 00% 11364 -
# 7 Short offline Completed without error 00% 11358 -
# 8 Extended offline Completed without error 00% 11195 -
# 9 Short offline Completed without error 00% 11189 -
#10 Extended offline Completed without error 00% 11026 -
#11 Short offline Completed without error 00% 11020 -
#12 Extended offline Completed without error 00% 10857 -
#13 Short offline Completed without error 00% 10851 -
#14 Extended offline Completed without error 00% 10689 -
#15 Short offline Completed without error 00% 10682 -
#16 Extended offline Completed without error 00% 10520 -
#17 Short offline Completed without error 00% 10513 -
#18 Extended offline Completed without error 00% 10351 -
#19 Short offline Completed without error 00% 10344 -
#20 Extended offline Completed without error 00% 10182 -
#21 Short offline Completed without error 00% 10176 -
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.
Auch in dmesg sieht man immer wieder vereinzelt, dass selbst der Zugriff auf SMART Fehler wirft:
Code:
Jan 19 13:20:26 sysresccd kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 19 13:20:26 sysresccd kernel: ata5.00: irq_stat 0x40000001
Jan 19 13:20:26 sysresccd kernel: ata5.00: failed command: SMART
Jan 19 13:20:26 sysresccd kernel: ata5.00: cmd b0/d5:01:06:4f:c2/00:00:00:00:00/00 tag 14 pio 512 in\x0a res 51/40:01:04:10:04/00:00:00:00:00/04 Emask 0x9 (media error)
Jan 19 13:20:26 sysresccd kernel: ata5.00: status: { DRDY ERR }
Jan 19 13:20:26 sysresccd kernel: ata5.00: error: { UNC }
Jan 19 13:20:26 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:20:26 sysresccd kernel: ata5.00: supports DRM functions and may not be fully accessible
Jan 19 13:20:26 sysresccd kernel: ata5.00: configured for UDMA/33
Jan 19 13:20:26 sysresccd kernel: ata5: EH complete
Jan 19 13:20:26 sysresccd kernel: ata5.00: Enabling discard_zeroes_data
Hat jemand eine Idee, was hier passiert sein könnte?
Ich habe die Platten für mich schon abgeschrieben, dass diese Sondermüll sind, aber ich hätte schon gerne eine Erklärung dafür, wieso..
