Hardeschijf defect?

[smeerbartje]

Ik heb een servertje in de meterkast staan, in zo'n superkleine behuizing (Minibox M350). Daarin zit een Samsung Spinpoint MT2 harde schijf. Echter nu krijg ik regelmatig een foutmelding, zie onderstaande logging. Het lijkt erop dat de schijf nogal wat problemen heeft, komt dit jullie bekend voor? En hoe kan ik zeker weten dat de schijf defect is, zodat ik 'm terug kan sturen naar Samsung? Ik heb namelijk standaard drie jaar garantie.

code:

Jan  1 19:43:10 server kernel: [ 1295.852851] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:10 server kernel: [ 1295.853055] ata3.00: BMDMA stat 0x24
Jan  1 19:43:10 server kernel: [ 1295.853167] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:10 server kernel: [ 1295.853320] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:10 server kernel: [ 1295.853325]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:10 server kernel: [ 1295.853752] ata3.00: status: { DRDY ERR }
Jan  1 19:43:10 server kernel: [ 1295.853870] ata3.00: error: { UNC }
Jan  1 19:43:10 server kernel: [ 1296.084458] ata3.00: configured for UDMA/133
Jan  1 19:43:10 server kernel: [ 1296.084501] ata3: EH complete
Jan  1 19:43:12 server kernel: [ 1298.592628] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:12 server kernel: [ 1298.592796] ata3.00: BMDMA stat 0x24
Jan  1 19:43:12 server kernel: [ 1298.592872] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:12 server kernel: [ 1298.592974] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:12 server kernel: [ 1298.592977]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:12 server kernel: [ 1298.593261] ata3.00: status: { DRDY ERR }
Jan  1 19:43:12 server kernel: [ 1298.593340] ata3.00: error: { UNC }
Jan  1 19:43:13 server kernel: [ 1298.816445] ata3.00: configured for UDMA/133
Jan  1 19:43:13 server kernel: [ 1298.816490] ata3: EH complete
Jan  1 19:43:15 server kernel: [ 1301.321356] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:15 server kernel: [ 1301.321524] ata3.00: BMDMA stat 0x24
Jan  1 19:43:15 server kernel: [ 1301.321600] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:15 server kernel: [ 1301.321702] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:15 server kernel: [ 1301.321705]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:15 server kernel: [ 1301.321990] ata3.00: status: { DRDY ERR }
Jan  1 19:43:15 server kernel: [ 1301.322068] ata3.00: error: { UNC }
Jan  1 19:43:15 server kernel: [ 1301.552451] ata3.00: configured for UDMA/133
Jan  1 19:43:15 server kernel: [ 1301.552497] ata3: EH complete
Jan  1 19:43:18 server kernel: [ 1304.050064] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:18 server kernel: [ 1304.050261] ata3.00: BMDMA stat 0x24
Jan  1 19:43:18 server kernel: [ 1304.050373] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:18 server kernel: [ 1304.050525] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:18 server kernel: [ 1304.050530]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:18 server kernel: [ 1304.050957] ata3.00: status: { DRDY ERR }
Jan  1 19:43:18 server kernel: [ 1304.051075] ata3.00: error: { UNC }
Jan  1 19:43:18 server kernel: [ 1304.280464] ata3.00: configured for UDMA/133
Jan  1 19:43:18 server kernel: [ 1304.280511] ata3: EH complete
Jan  1 19:43:20 server kernel: [ 1306.778781] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:20 server kernel: [ 1306.778951] ata3.00: BMDMA stat 0x24
Jan  1 19:43:20 server kernel: [ 1306.779041] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:20 server kernel: [ 1306.779163] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:20 server kernel: [ 1306.779167]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:20 server kernel: [ 1306.779508] ata3.00: status: { DRDY ERR }
Jan  1 19:43:20 server kernel: [ 1306.779603] ata3.00: error: { UNC }
Jan  1 19:43:21 server kernel: [ 1307.008468] ata3.00: configured for UDMA/133
Jan  1 19:43:21 server kernel: [ 1307.008513] ata3: EH complete
Jan  1 19:43:23 server kernel: [ 1309.507501] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:23 server kernel: [ 1309.507697] ata3.00: BMDMA stat 0x24
Jan  1 19:43:23 server kernel: [ 1309.507809] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:23 server kernel: [ 1309.507962] ata3.00: cmd 25/00:00:00:25:de/00:01:54:00:00/e0 tag 0 dma 131072 in
Jan  1 19:43:23 server kernel: [ 1309.507967]          res 51/40:58:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:23 server kernel: [ 1309.508439] ata3.00: status: { DRDY ERR }
Jan  1 19:43:23 server kernel: [ 1309.508605] ata3.00: error: { UNC }
Jan  1 19:43:23 server kernel: [ 1309.732461] ata3.00: configured for UDMA/133
Jan  1 19:43:23 server kernel: [ 1309.732513] sd 2:0:0:0: [sda] Unhandled sense code
Jan  1 19:43:23 server kernel: [ 1309.732537] sd 2:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  1 19:43:23 server kernel: [ 1309.732551] sd 2:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Jan  1 19:43:23 server kernel: [ 1309.732567] Descriptor sense data with sense descriptors (in hex):
Jan  1 19:43:23 server kernel: [ 1309.732574]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jan  1 19:43:23 server kernel: [ 1309.732607]         54 de 25 a8 
Jan  1 19:43:23 server kernel: [ 1309.732621] sd 2:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Jan  1 19:43:23 server kernel: [ 1309.732637] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 54 de 25 00 00 01 00 00
Jan  1 19:43:23 server kernel: [ 1309.732667] end_request: I/O error, dev sda, sector 1423844776
Jan  1 19:43:23 server kernel: [ 1309.732897] ata3: EH complete
Jan  1 19:43:24 server dhcpd: DHCPREQUEST for 192.168.1.158 from 70:73:cb:c8:2e:52 (AppleTV) via eth0
Jan  1 19:43:24 server dhcpd: DHCPACK on 192.168.1.158 to 70:73:cb:c8:2e:52 (AppleTV) via eth0
Jan  1 19:43:26 server kernel: [ 1312.424480] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:26 server kernel: [ 1312.424676] ata3.00: BMDMA stat 0x24
Jan  1 19:43:26 server kernel: [ 1312.430450] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:26 server kernel: [ 1312.436725] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:26 server kernel: [ 1312.436733]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:26 server kernel: [ 1312.448445] ata3.00: status: { DRDY ERR }
Jan  1 19:43:26 server kernel: [ 1312.454619] ata3.00: error: { UNC }
Jan  1 19:43:26 server kernel: [ 1312.660444] ata3.00: configured for UDMA/133
Jan  1 19:43:26 server kernel: [ 1312.660487] ata3: EH complete
Jan  1 19:43:29 server kernel: [ 1315.153144] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:29 server kernel: [ 1315.158941] ata3.00: BMDMA stat 0x24
Jan  1 19:43:29 server kernel: [ 1315.164701] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:29 server kernel: [ 1315.170346] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:29 server kernel: [ 1315.170353]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:29 server kernel: [ 1315.181879] ata3.00: status: { DRDY ERR }
Jan  1 19:43:29 server kernel: [ 1315.187620] ata3.00: error: { UNC }
Jan  1 19:43:29 server kernel: [ 1315.392447] ata3.00: configured for UDMA/133
Jan  1 19:43:29 server kernel: [ 1315.392492] ata3: EH complete
Jan  1 19:43:32 server kernel: [ 1317.881855] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:32 server kernel: [ 1317.887630] ata3.00: BMDMA stat 0x24
Jan  1 19:43:32 server kernel: [ 1317.893351] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:32 server kernel: [ 1317.899008] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:32 server kernel: [ 1317.899016]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:32 server kernel: [ 1317.910494] ata3.00: status: { DRDY ERR }
Jan  1 19:43:32 server kernel: [ 1317.916248] ata3.00: error: { UNC }
Jan  1 19:43:32 server kernel: [ 1318.120401] ata3.00: configured for UDMA/133
Jan  1 19:43:32 server kernel: [ 1318.120446] ata3: EH complete
Jan  1 19:43:34 server kernel: [ 1320.610559] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:34 server kernel: [ 1320.614478] ata3.00: BMDMA stat 0x24
Jan  1 19:43:34 server kernel: [ 1320.618319] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:34 server kernel: [ 1320.622111] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:34 server kernel: [ 1320.622116]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:34 server kernel: [ 1320.629816] ata3.00: status: { DRDY ERR }
Jan  1 19:43:34 server kernel: [ 1320.633671] ata3.00: error: { UNC }
Jan  1 19:43:35 server kernel: [ 1320.836461] ata3.00: configured for UDMA/133
Jan  1 19:43:35 server kernel: [ 1320.836506] ata3: EH complete
Jan  1 19:43:37 server kernel: [ 1323.328188] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:37 server kernel: [ 1323.333959] ata3.00: BMDMA stat 0x24
Jan  1 19:43:37 server kernel: [ 1323.339672] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:37 server kernel: [ 1323.345319] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:37 server kernel: [ 1323.345327]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:37 server kernel: [ 1323.356790] ata3.00: status: { DRDY ERR }
Jan  1 19:43:37 server kernel: [ 1323.362536] ata3.00: error: { UNC }
Jan  1 19:43:37 server kernel: [ 1323.552425] ata3.00: configured for UDMA/133
Jan  1 19:43:37 server kernel: [ 1323.552471] ata3: EH complete
Jan  1 19:43:40 server kernel: [ 1326.045807] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:40 server kernel: [ 1326.051577] ata3.00: BMDMA stat 0x24
Jan  1 19:43:40 server kernel: [ 1326.057304] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:40 server kernel: [ 1326.062932] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:40 server kernel: [ 1326.062938]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:40 server kernel: [ 1326.074444] ata3.00: status: { DRDY ERR }
Jan  1 19:43:40 server kernel: [ 1326.080176] ata3.00: error: { UNC }
Jan  1 19:43:40 server kernel: [ 1326.284444] ata3.00: configured for UDMA/133
Jan  1 19:43:40 server kernel: [ 1326.284491] sd 2:0:0:0: [sda] Unhandled sense code
Jan  1 19:43:40 server kernel: [ 1326.284504] sd 2:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  1 19:43:40 server kernel: [ 1326.284531] sd 2:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Jan  1 19:43:40 server kernel: [ 1326.284546] Descriptor sense data with sense descriptors (in hex):
Jan  1 19:43:40 server kernel: [ 1326.284554]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jan  1 19:43:40 server kernel: [ 1326.284586]         54 de 25 a8 
Jan  1 19:43:40 server kernel: [ 1326.284600] sd 2:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Jan  1 19:43:40 server kernel: [ 1326.284617] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 54 de 25 a8 00 00 08 00
Jan  1 19:43:40 server kernel: [ 1326.284647] end_request: I/O error, dev sda, sector 1423844776
Jan  1 19:43:40 server kernel: [ 1326.290439] ata3: EH complete
Jan  1 19:43:43 server kernel: [ 1328.852167] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:43 server kernel: [ 1328.857989] ata3.00: BMDMA stat 0x24
Jan  1 19:43:43 server kernel: [ 1328.863714] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:43 server kernel: [ 1328.869446] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:43 server kernel: [ 1328.869453]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:43 server kernel: [ 1328.880973] ata3.00: status: { DRDY ERR }
Jan  1 19:43:43 server kernel: [ 1328.886695] ata3.00: error: { UNC }
Jan  1 19:43:43 server kernel: [ 1329.076441] ata3.00: configured for UDMA/133
Jan  1 19:43:43 server kernel: [ 1329.076485] ata3: EH complete
Jan  1 19:43:45 server kernel: [ 1331.580884] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:45 server kernel: [ 1331.586644] ata3.00: BMDMA stat 0x24
Jan  1 19:43:45 server kernel: [ 1331.592357] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:45 server kernel: [ 1331.598002] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:45 server kernel: [ 1331.598009]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:45 server kernel: [ 1331.609457] ata3.00: status: { DRDY ERR }
Jan  1 19:43:45 server kernel: [ 1331.615195] ata3.00: error: { UNC }
Jan  1 19:43:46 server kernel: [ 1331.820439] ata3.00: configured for UDMA/133
Jan  1 19:43:46 server kernel: [ 1331.820484] ata3: EH complete
Jan  1 19:43:48 server kernel: [ 1334.309609] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:48 server kernel: [ 1334.315365] ata3.00: BMDMA stat 0x24
Jan  1 19:43:48 server kernel: [ 1334.321082] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:48 server kernel: [ 1334.326729] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:48 server kernel: [ 1334.326737]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:48 server kernel: [ 1334.338197] ata3.00: status: { DRDY ERR }
Jan  1 19:43:48 server kernel: [ 1334.343936] ata3.00: error: { UNC }
Jan  1 19:43:48 server kernel: [ 1334.548440] ata3.00: configured for UDMA/133
Jan  1 19:43:48 server kernel: [ 1334.548485] ata3: EH complete
Jan  1 19:43:51 server kernel: [ 1337.049411] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:51 server kernel: [ 1337.053310] ata3.00: BMDMA stat 0x24
Jan  1 19:43:51 server kernel: [ 1337.057151] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:51 server kernel: [ 1337.060918] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:51 server kernel: [ 1337.060922]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:51 server kernel: [ 1337.068616] ata3.00: status: { DRDY ERR }
Jan  1 19:43:51 server kernel: [ 1337.072448] ata3.00: error: { UNC }
Jan  1 19:43:51 server kernel: [ 1337.276401] ata3.00: configured for UDMA/133
Jan  1 19:43:51 server kernel: [ 1337.276446] ata3: EH complete
Jan  1 19:43:53 server kernel: [ 1339.767034] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:53 server kernel: [ 1339.770929] ata3.00: BMDMA stat 0x24
Jan  1 19:43:53 server kernel: [ 1339.774760] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:53 server kernel: [ 1339.778544] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:53 server kernel: [ 1339.778549]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:53 server kernel: [ 1339.786224] ata3.00: status: { DRDY ERR }
Jan  1 19:43:53 server kernel: [ 1339.790067] ata3.00: error: { UNC }
Jan  1 19:43:54 server kernel: [ 1339.992433] ata3.00: configured for UDMA/133
Jan  1 19:43:54 server kernel: [ 1339.992478] ata3: EH complete
Jan  1 19:43:56 server kernel: [ 1342.484664] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 19:43:56 server kernel: [ 1342.490426] ata3.00: BMDMA stat 0x24
Jan  1 19:43:56 server kernel: [ 1342.496149] ata3.00: failed command: READ DMA EXT
Jan  1 19:43:56 server kernel: [ 1342.501803] ata3.00: cmd 25/00:08:a8:25:de/00:00:54:00:00/e0 tag 0 dma 4096 in
Jan  1 19:43:56 server kernel: [ 1342.501811]          res 51/40:08:a8:25:de/40:00:54:00:00/e0 Emask 0x9 (media error)
Jan  1 19:43:56 server kernel: [ 1342.513297] ata3.00: status: { DRDY ERR }
Jan  1 19:43:56 server kernel: [ 1342.519150] ata3.00: error: { UNC }
Jan  1 19:43:56 server kernel: [ 1342.724404] ata3.00: configured for UDMA/133
Jan  1 19:43:56 server kernel: [ 1342.724455] sd 2:0:0:0: [sda] Unhandled sense code
Jan  1 19:43:56 server kernel: [ 1342.724467] sd 2:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan  1 19:43:56 server kernel: [ 1342.724484] sd 2:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Jan  1 19:43:56 server kernel: [ 1342.724504] Descriptor sense data with sense descriptors (in hex):
Jan  1 19:43:56 server kernel: [ 1342.724515]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Jan  1 19:43:56 server kernel: [ 1342.724557]         54 de 25 a8 
Jan  1 19:43:56 server kernel: [ 1342.724576] sd 2:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Jan  1 19:43:56 server kernel: [ 1342.724599] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 54 de 25 a8 00 00 08 00
Jan  1 19:43:56 server kernel: [ 1342.724649] end_request: I/O error, dev sda, sector 1423844776
Jan  1 19:43:56 server kernel: [ 1342.728546] ata3: EH complete

[Thralas]

Lijkt erop dat je wat bad sectors hebt. Post eens de output van smartctl -a /dev/sdX?

[smeerbartje]

Thralas schreef op dinsdag 01 januari 2013 @ 20:21:
Lijkt erop dat je wat bad sectors hebt. Post eens de output van smartctl -a /dev/sdX?

Zie hier:

code:

smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-35-generic-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint MT2
Device Model:     SAMSUNG HM100UI
Serial Number:    S2HAJDQZ701189
LU WWN Device Id: 5 0024e9 003d21ef0
Firmware Version: 2AM10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Tue Jan  1 20:22:04 2013 CET
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:  (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:        (14100) 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:    ( 235) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       353
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   084   081   025    Pre-fail  Always       -       4974
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       34
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       18033
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       26
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       41
181 Program_Fail_Cnt_Total  0x0022   100   100   ---    Old_age   Always       -       162
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       55
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   057   055   000    Old_age   Always       -       43 (Min/Max 17/51)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       40
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       1
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       26
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       119

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
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.

[Verwijderd]

Kijk naar de Raw value van Current Pending Sector. Daar staat 40, en dat zijn dus 40 onleesbare sectors. Dat is je probleem.

Wat je zou kunnen doen is alle gegevens die je wilt behouden van de schijf afhalen (wat soms niet volledig lukt door de bad sectors) en deze vervolgens zero-writen. Een lange format onder win7, of een zero write onder Linux met dd is voldoende om die 40 bad sectors weg te krijgen. Je Current Pending Sector staat dan weer op 0.

Hou dan in de komende weken de SMART en in het bijzonder de Current Pending Sector in de gaten. Als deze weer hoger dan 0 komt, zou ik de schijf afschrijven en met garantie retour sturen.

Je kunt er ook voor kiezen om hem nu gelijk voor garantie op te sturen, maar weet dat je niet altijd een nieuw exemplaar terug krijgt, maar een refurbished exemplaar. Als je schijf correct werkt na een zero-write, zou het mijn eigen voorkeur om je huidige schijf te houden. Jij weet hoe je hem gebruikt hebt; dat weet je niet bij een gebruikte schijf.

[smeerbartje]

Verwijderd schreef op dinsdag 01 januari 2013 @ 20:47:
Kijk naar de Raw value van Current Pending Sector. Daar staat 40, en dat zijn dus 40 onleesbare sectors. Dat is je probleem.

Wat je zou kunnen doen is alle gegevens die je wilt behouden van de schijf afhalen (wat soms niet volledig lukt door de bad sectors) en deze vervolgens zero-writen. Een lange format onder win7, of een zero write onder Linux met dd is voldoende om die 40 bad sectors weg te krijgen. Je Current Pending Sector staat dan weer op 0.

Hou dan in de komende weken de SMART en in het bijzonder de Current Pending Sector in de gaten. Als deze weer hoger dan 0 komt, zou ik de schijf afschrijven en met garantie retour sturen.

Je kunt er ook voor kiezen om hem nu gelijk voor garantie op te sturen, maar weet dat je niet altijd een nieuw exemplaar terug krijgt, maar een refurbished exemplaar. Als je schijf correct werkt na een zero-write, zou het mijn eigen voorkeur om je huidige schijf te houden. Jij weet hoe je hem gebruikt hebt; dat weet je niet bij een gebruikte schijf.

Dankje, dat is een heldere uitleg! Echter ik zie bij Current Pending Sector het volgende staan: 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always -

Ik zie nergens de waarde "40" staan. Kun je iets meer info geven?

[Thralas]

smeerbartje schreef op dinsdag 01 januari 2013 @ 20:52:
Ik zie nergens de waarde "40" staan. Kun je iets meer info geven?

Iets naar rechts scrollen, er staat wel degelijk 40 in die regel.

Alternatief voor een zero fill is iets als [url=http://unix.stackexchange.com/questions/37119/find-which-files-are-affected-by-bad-blocks-on-ext4-filesystem], maar dat is wel meer werk (zeker zodra de bad sectors buiten file data vallen).

Je kunt eventueel ook enkel de bad blocks overschrijven, zie hier.

[timberleek]

hoe gaat het met die garantie icm veel draaiuren.

zou die 3 jaar niet gelden bij 'redelijk' gebruik.
Bij die smart data staat ook dat hij al ruim 2 jaar heeft gedraaid, zou dat niet uitmaken voor de garantie? (onder het mom van redelijke slijtage)

[smeerbartje]

Ik heb eigenlijk geen idee hoe dat werkt. 3 jaar is 3 jaar denk ik... of dat ding nu 24/7 draait of "gemiddeld".

[smeerbartje]

Gecheckt bij leverancier; gewoon gevalletje garantie .