Intel SSD S3610 S.M.A.R.T Werte. SSD defekt?
- Ersteller fantozzi
- Erstellt am
Simanova
Rear Admiral
- Registriert
- Dez. 2012
- Beiträge
- 5.489
Die Intel S3610 SSD ist ein Datenträger, keine Festplatte.
Die Roh-Werte der SSD sehen erstmal gut aus, bis auf den SRER Wert.
SRER Fehler sind nicht korrigierbar. Sprich, tritt ein SRER auf, gibt es unsinnige Datenwerte.
Die normalisierten Werte sind Softwareabhängig, also je nach Ausleseprogramm mehr oder weniger sinnvoll.
Du könntest versuchen mit dem Intel Tool nochmal auszulesen
https://www.intel.de/content/www/de/de/download/19543/intel-memory-and-storage-tool-gui.html?v=t
Die Roh-Werte der SSD sehen erstmal gut aus, bis auf den SRER Wert.
SRER Fehler sind nicht korrigierbar. Sprich, tritt ein SRER auf, gibt es unsinnige Datenwerte.
Die normalisierten Werte sind Softwareabhängig, also je nach Ausleseprogramm mehr oder weniger sinnvoll.
Du könntest versuchen mit dem Intel Tool nochmal auszulesen
https://www.intel.de/content/www/de/de/download/19543/intel-memory-and-storage-tool-gui.html?v=t
Also die Version 2.5 erkennt den Datenträger nicht, und die Version 1.7 erkennt zwar den Datenträger, gibt aber leider keine SMART-Werte aus. Möglicherweise liegt es daran, dass ich den Datenträger extern per USB angeschlossen habe. Unter Linux und Smartmontools konnte ich leider auch nichts auslesen.
[ 2.075757] sd 3:0:0:1: [sdb] 1562820608 512-byte logical blocks: (800 GB/745 GiB)
[ 2.075810] sd 3:0:0:1: [sdb] Write Protect is off
[ 2.075813] sd 3:0:0:1: [sdb] Mode Sense: 63 00 00 08
[ 2.075967] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.081980] sdb: sdb1
[ 2.082064] sd 3:0:0:1: [sdb] Attached SCSI disk
[ 7.339966] EXT4-fs (sdb1): recovery complete
[ 7.339978] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Quota mode: journalled.
[21918.683578] sd 3:0:0:1: [sdb] tag#117 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[21918.683589] sd 3:0:0:1: [sdb] tag#117 Sense Key : Hardware Error [current]
[21918.683593] sd 3:0:0:1: [sdb] tag#117 Add. Sense: Internal target failure
[21918.683597] sd 3:0:0:1: [sdb] tag#117 CDB: Write(10) 2a 00 00 01 3c 78 00 00 68 00
[21918.683599] critical target error, dev sdb, sector 81016 op 0x1
WRITE) flags 0x800 phys_seg 7 prio class 2
[21918.684165] EXT4-fs warning (device sdb1): ext4_end_bio:343: I/O error 5 writing to inode 31326216 starting block 10127)
[21918.684171] Buffer I/O error on device sdb1, logical block 9871
[21918.684628] Buffer I/O error on device sdb1, logical block 9872
[21918.685123] Buffer I/O error on device sdb1, logical block 9873
[21918.685553] Buffer I/O error on device sdb1, logical block 9874
[21918.685987] Buffer I/O error on device sdb1, logical block 9875
[21918.686413] Buffer I/O error on device sdb1, logical block 9876
[21918.686831] Buffer I/O error on device sdb1, logical block 9877
[21918.687255] Buffer I/O error on device sdb1, logical block 9878
[21918.687658] Buffer I/O error on device sdb1, logical block 9879
[21918.688068] Buffer I/O error on device sdb1, logical block 9880
[21918.688486] sd 3:0:0:1: [sdb] tag#116 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[21918.688491] sd 3:0:0:1: [sdb] tag#116 Sense Key : Hardware Error [current]
[21918.688494] sd 3:0:0:1: [sdb] tag#116 Add. Sense: Internal target failure
[21918.688497] sd 3:0:0:1: [sdb] tag#116 CDB: Write(10) 2a 00 59 84 08 28 00 00 10 00
[21918.688499] critical target error, dev sdb, sector 1501825064 op 0x1WRITE) flags 0x800 phys_seg 1 prio class 2
[21918.688915] EXT4-fs warning (device sdb1): ext4_end_bio:343: I/O error 5 writing to inode 31326216 starting block 187728133)
[21924.500290] sd 3:0:0:1: [sdb] tag#228 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Das wäre die Ausgabe, wenn ich den Befehl dmesg | grep 'sdb' eingebe.
[21924.500302] sd 3:0:0:1: [sdb] tag#228 Sense Key : Hardware Error [current]
[21924.500306] sd 3:0:0:1: [sdb] tag#228 Add. Sense: Internal target failure
[21924.500309] sd 3:0:0:1: [sdb] tag#228 CDB: Write(10) 2a 00 2e 84 17 58 00 00 10 00
[21924.500312] critical target error, dev sdb, sector 780408664 op 0x1WRITE) flags 0x9800 phys_seg 2 prio class 2
[21924.503076] Aborting journal on device sdb1-8.
[22218.722903] EXT4-fs error (device sdb1): ext4_journal_check_start:83: comm portainer: Detected aborted journal
[22218.728765] EXT4-fs (sdb1): Remounting filesystem read-only
[109352.016055] EXT4-fs (sdb1): error count since last fsck: 1
[109352.016123] EXT4-fs (sdb1): initial error at time 1721853767: ext4_journal_check_start:83
[109352.016163] EXT4-fs (sdb1): last error at time 1721853767: ext4_journal_check_start:83
[201627.168133] EXT4-fs (sdb1): error count since last fsck: 1
[201627.168214] EXT4-fs (sdb1): initial error at time 1721853767: ext4_journal_check_start:83
[201627.168239] EXT4-fs (sdb1): last error at time 1721853767: ext4_journal_check_start:83
[ 2.075810] sd 3:0:0:1: [sdb] Write Protect is off
[ 2.075813] sd 3:0:0:1: [sdb] Mode Sense: 63 00 00 08
[ 2.075967] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.081980] sdb: sdb1
[ 2.082064] sd 3:0:0:1: [sdb] Attached SCSI disk
[ 7.339966] EXT4-fs (sdb1): recovery complete
[ 7.339978] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Quota mode: journalled.
[21918.683578] sd 3:0:0:1: [sdb] tag#117 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[21918.683589] sd 3:0:0:1: [sdb] tag#117 Sense Key : Hardware Error [current]
[21918.683593] sd 3:0:0:1: [sdb] tag#117 Add. Sense: Internal target failure
[21918.683597] sd 3:0:0:1: [sdb] tag#117 CDB: Write(10) 2a 00 00 01 3c 78 00 00 68 00
[21918.683599] critical target error, dev sdb, sector 81016 op 0x1
WRITE) flags 0x800 phys_seg 7 prio class 2[21918.684165] EXT4-fs warning (device sdb1): ext4_end_bio:343: I/O error 5 writing to inode 31326216 starting block 10127)
[21918.684171] Buffer I/O error on device sdb1, logical block 9871
[21918.684628] Buffer I/O error on device sdb1, logical block 9872
[21918.685123] Buffer I/O error on device sdb1, logical block 9873
[21918.685553] Buffer I/O error on device sdb1, logical block 9874
[21918.685987] Buffer I/O error on device sdb1, logical block 9875
[21918.686413] Buffer I/O error on device sdb1, logical block 9876
[21918.686831] Buffer I/O error on device sdb1, logical block 9877
[21918.687255] Buffer I/O error on device sdb1, logical block 9878
[21918.687658] Buffer I/O error on device sdb1, logical block 9879
[21918.688068] Buffer I/O error on device sdb1, logical block 9880
[21918.688486] sd 3:0:0:1: [sdb] tag#116 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[21918.688491] sd 3:0:0:1: [sdb] tag#116 Sense Key : Hardware Error [current]
[21918.688494] sd 3:0:0:1: [sdb] tag#116 Add. Sense: Internal target failure
[21918.688497] sd 3:0:0:1: [sdb] tag#116 CDB: Write(10) 2a 00 59 84 08 28 00 00 10 00
[21918.688499] critical target error, dev sdb, sector 1501825064 op 0x1
WRITE) flags 0x800 phys_seg 1 prio class 2[21918.688915] EXT4-fs warning (device sdb1): ext4_end_bio:343: I/O error 5 writing to inode 31326216 starting block 187728133)
[21924.500290] sd 3:0:0:1: [sdb] tag#228 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Das wäre die Ausgabe, wenn ich den Befehl dmesg | grep 'sdb' eingebe.
[21924.500302] sd 3:0:0:1: [sdb] tag#228 Sense Key : Hardware Error [current]
[21924.500306] sd 3:0:0:1: [sdb] tag#228 Add. Sense: Internal target failure
[21924.500309] sd 3:0:0:1: [sdb] tag#228 CDB: Write(10) 2a 00 2e 84 17 58 00 00 10 00
[21924.500312] critical target error, dev sdb, sector 780408664 op 0x1
WRITE) flags 0x9800 phys_seg 2 prio class 2[21924.503076] Aborting journal on device sdb1-8.
[22218.722903] EXT4-fs error (device sdb1): ext4_journal_check_start:83: comm portainer: Detected aborted journal
[22218.728765] EXT4-fs (sdb1): Remounting filesystem read-only
[109352.016055] EXT4-fs (sdb1): error count since last fsck: 1
[109352.016123] EXT4-fs (sdb1): initial error at time 1721853767: ext4_journal_check_start:83
[109352.016163] EXT4-fs (sdb1): last error at time 1721853767: ext4_journal_check_start:83
[201627.168133] EXT4-fs (sdb1): error count since last fsck: 1
[201627.168214] EXT4-fs (sdb1): initial error at time 1721853767: ext4_journal_check_start:83
[201627.168239] EXT4-fs (sdb1): last error at time 1721853767: ext4_journal_check_start:83
Ähnliche Themen
