Newsgroup: it.comp.os.linux.iniziare
Titolo: Problemi dischi: controller o software?

Ciao a tutti,
sto usando un controller Promise FastTrak TX2300 per gestire 2 dischi 
SATA su Debian Testing in software-RAID (Mirroring).
Ora ho trovato questo nel log di sistema:
May  3 00:57:01 storebox kernel: [201459.736003] md: data-check of RAID 
array md0
May  3 00:57:01 storebox kernel: [201459.736003] md: minimum 
_guaranteed_  speed: 1000 KB/sec/disk.
May  3 00:57:01 storebox kernel: [201459.736003] md: using maximum 
available idle IO bandwidth (but not more than 200000 KB/sec) for 
data-check.
May  3 00:57:01 storebox kernel: [201459.736003] md: using 128k window, 
over a total of 976759936 blocks.
May  3 04:52:13 storebox kernel: [215571.760069]          res 
40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May  3 04:52:13 storebox kernel: [215571.760089] ata2: hard resetting link
May  3 04:52:13 storebox kernel: [215571.764055]          res 
40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May  3 04:52:13 storebox kernel: [215571.764073] ata1: hard resetting link
May  3 04:52:18 storebox kernel: [215577.120026] ata2: link is slow to 
respond, please be patient (ready=-19)
May  3 04:52:18 storebox kernel: [215577.124020] ata1: link is slow to 
respond, please be patient (ready=-19)
May  3 04:52:23 storebox kernel: [215581.768036] ata2: hard resetting link
May  3 04:52:23 storebox kernel: [215581.772028] ata1: hard resetting link
May  3 04:52:28 storebox kernel: [215587.128018] ata2: link is slow to 
respond, please be patient (ready=-19)
May  3 04:52:28 storebox kernel: [215587.132020] ata1: link is slow to 
respond, please be patient (ready=-19)
May  3 04:52:33 storebox kernel: [215591.776037] ata2: hard resetting link
May  3 04:52:33 storebox kernel: [215591.780028] ata1: hard resetting link
May  3 04:52:38 storebox kernel: [215597.136020] ata2: link is slow to 
respond, please be patient (ready=-19)
May  3 04:52:38 storebox kernel: [215597.140021] ata1: link is slow to 
respond, please be patient (ready=-19)
May  3 04:53:08 storebox kernel: [215626.816034] ata2: limiting SATA 
link speed to 1.5 Gbps
May  3 04:53:08 storebox kernel: [215626.816044] ata2: hard resetting link
May  3 04:53:08 storebox kernel: [215626.820029] ata1: limiting SATA 
link speed to 1.5 Gbps
May  3 04:53:08 storebox kernel: [215626.820037] ata1: hard resetting link
May  3 04:53:13 storebox kernel: [215631.840040] ata2.00: disabled
May  3 04:53:13 storebox kernel: [215631.840065] ata2: EH complete
May  3 04:53:13 storebox kernel: [215631.840104] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.840158] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.840184] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.840211] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.840230] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.840244] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.844058] ata1.00: disabled
May  3 04:53:13 storebox kernel: [215631.844084] ata1: EH complete
May  3 04:53:13 storebox kernel: [215631.844120] sd 0:0:0:0: [sda] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.844159] sd 0:0:0:0: [sda] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.844192] raid1: Operation 
continuing on 1 devices.
May  3 04:53:13 storebox kernel: [215631.844513] md: md0: data-check done.
May  3 04:53:13 storebox kernel: [215631.844640] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.844794] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.844968] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.845004] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.845021] md: super_written gets 
error=-5, uptodate=0
May  3 04:53:13 storebox kernel: [215631.845625] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.845644] md: super_written gets 
error=-5, uptodate=0
May  3 04:53:13 storebox kernel: [215631.845761] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:53:13 storebox kernel: [215631.845779] md: super_written gets 
error=-5, uptodate=0
May  3 04:53:13 storebox kernel: [215631.845795] RAID1 conf printout:
May  3 04:53:13 storebox kernel: [215631.845798]  --- wd:1 rd:2
May  3 04:53:13 storebox kernel: [215631.845801]  disk 0, wo:1, o:0, 
dev:sda1
May  3 04:53:13 storebox kernel: [215631.845804]  disk 1, wo:0, o:1, 
dev:sdb1
May  3 04:53:13 storebox kernel: [215631.848669] RAID1 conf printout:
May  3 04:53:13 storebox kernel: [215631.848678]  --- wd:1 rd:2
May  3 04:53:13 storebox kernel: [215631.848684]  disk 1, wo:0, o:1, 
dev:sdb1
May  3 04:54:59 storebox kernel: [215738.000190] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:54:59 storebox kernel: [215738.000222] md: super_written gets 
error=-5, uptodate=0
May  3 04:54:59 storebox kernel: [215738.000883] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:54:59 storebox kernel: [215738.001209] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:54:59 storebox kernel: [215738.001234] lost page write due to 
I/O error on md0
May  3 04:54:59 storebox kernel: [215738.001498] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:54:59 storebox kernel: [215738.001522] lost page write due to 
I/O error on md0
May  3 04:55:00 storebox kernel: [215738.204098] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:55:00 storebox kernel: [215738.204129] md: super_written gets 
error=-5, uptodate=0
May  3 04:55:32 storebox kernel: [215770.632218] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:55:32 storebox kernel: [215770.632250] md: super_written gets 
error=-5, uptodate=0
May  3 04:55:32 storebox kernel: [215770.636077] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:55:32 storebox kernel: [215770.636108] lost page write due to 
I/O error on md0
May  3 04:55:32 storebox kernel: [215770.840109] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 04:55:32 storebox kernel: [215770.840140] md: super_written gets 
error=-5, uptodate=0
--------------------------------------------
E poi una ripetizione quasi infinita di:
May  3 08:01:39 storebox kernel: [226938.142928] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.143199] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.143525] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.143762] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.143986] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.144251] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May  3 08:01:39 storebox kernel: [226938.144586] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
--------------------------------------------
Che diavolo sta succedendo? Sarï¿œ rotto il disco sdb (tra l'altro 
*nuovissimo*, installato da appena 1 settimana? Oppure ï¿œ il controller 
che danneggia? Mi ï¿œ successo infatti di dover sostituire entrambi i 
dischi che vi erano connessi precedentemente per errori su disco 
(confermati poi dal software di test usato su Windoze: ho fatto RMA e li 
ho sostituiti, ma quelli attuali *non* sono quelli tornati dalla RMA).
Grazie!

 che danneggia?
Secondo me e' il disco.
Davide
-- 
"Cynical" is a term invented by optimists to describe realists.
-- Gregory Benford

 Secondo me e' il disco.
Adesso li levo dal server e li controllo. Perï¿œ possibile che mi sono 
"fumato" 2 dischi Western Digital 2 settimane fa (ed erano su questo 
controller, versione "Green" dei dischi, 2x1TB) ed oggi scopro che anche 
uno dei *nuovi* dischi, sempre WD ma Caviar da server (24x7) si sia cremato?
Saluti!

> Secondo me e' il disco.
Levati dal server, testati con WD Diagnostics: il "Quick Test" ha dato 
esito positivo (nessun problema/errore). Fare un "Long Test" su 1 TB mi 
sembra eccessivo... che ne dite?