[linux] Chybny disk v RAID - ako najst pricinu resp. chybny sektor

[patrik na foral.sk]

Matus UHLAR - fantomas napsal(a):

> ake boli chyby v logu ked to padlo?

daemon.log
May  7 13:03:18 gnu-linux mdadm: Fail event detected on md device
/dev/md0, component device /dev/sdb1
May  7 13:34:46 gnu-linux mdadm: RebuildStarted event detected on md
device /dev/md0
May  7 13:35:31 gnu-linux mdadm: RebuildFinished event detected on md
device /dev/md0
May  7 13:35:31 gnu-linux mdadm: SpareActive event detected on md
device /dev/md0, component device /dev/sdb1

v kern.log som v danom case nenasiel nic podozrive, udivil ma ale 
sposob ukladania logov. kern.log.0 obsahuje len jeden den (dnesok) ale 
kern.1.gz je stary niekolko tyzdnov (24.3.).

> (kontrolovat SMART stav ti radili, s tym suhlasim).

zial S.M.A.R.T mi nefunguje.

apt-get -y --force-yes -f install smartmontools

Setting up smartmontools (5.36-8) ...
Enabling S.M.A.R.T..../dev/sda...unable to fetch IEC (SMART) mode page
[unsupported field in scsi command]
(failed)...done.
Starting S.M.A.R.T. daemon: smartd failed!
invoke-rc.d: initscript smartmontools, action "start" failed.
dpkg: error processing smartmontools (--configure):
  subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
  smartmontools

SMART je v BIOS-e povoleny, disk je WD VelociRaptor, cipset je nForce 
410 MCP s podporou SATA-II

> nemountuj ho, postvi na neho badblocks vo write mode. Samozrejme ked bude
> odpojeny z RAIDu. badblocks ma dva write mody - nedestruktivny a
> destruktivny, druhy trva 4-krat tolko ale je spolahlivejsi.

 > badblocks -swv /dev/sdb1
Checking for bad blocks in read-write mode
 From block 0 to 4192933
Pass completed, 0 bad blocks found.

> Pokial ten disk mozes vymenit za zalozny, urob to, a badblocks skusaj v
> druhom compe.

Fyzickemu kontaktu so strojom som sa chcel vyhnut, no asi to pre
istotu vymontujem a testnem utilitou od vyrobcu.

-- 
Patrik Jan (pa3k)