Re: status=0x50 { DriveReady SeekComplete } :: Something smarter than us is going to emerge


node:	Re: status=0x50 { DriveReady SeekComplete }
template:	4
parent:	status=0x50 { DriveReady SeekComplete }
owner:	ventYl
viewed by:
created:	31.05.2006 - 08:43:38

cwbe coordinatez:
101
63540
63542
2109677
63692
2416469
2417097

ABSOLUT
KYBERIA

permissions
you:	r,
system:	public
net:	yes

hdparm -d1 /dev/hda
hdparm -d1 /dev/hdb

ak to nepomoze, neviem, ci sa neporuca disk

0000010100063540000635420210967700063692024164690241709702417443

root@aramis:/ # hdparm /dev/hda /dev/hdb /dev/sda /dev/sdb

/dev/hda:
multcount = 0 (off)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 160086528, start = 0

/dev/hdb:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device

/dev/sda:
IO_support =256 (???)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 488397168, start = 0

/dev/sdb:
IO_support =256 (???)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 488397168, start = 0

DMA je zapnute by default. Este som zabudol spomenut ze tam mam 2xSATA

000001010006354000063542021096770006369202416469024170970241744302419110

skus disky otestovat cez smartctl (v debiane balicek smartmontools). ja tomu moc nerozumiem, ale z manualu som vyrozumel asi tolko, ze kazdy disk si uklada o sebe kopu informacii (kolkokrat bol zapnuty, kolko hodin spolu bezal, kolko a akych chyb sa vyskytlo atd.), a tie sa daju porovnat so "standardnymi" hodnotami (ktore to tiez vypise). na zaklade toho som zistil, ze jeden z mojich diskov sa chysta do vecnych lovisk...

00000101000635400006354202109677000636920241646902417097024174430241911002419601

SMART to je taka uchylarna, ktora si uklada statisticke udaje o behu disku (casy jedn. operacii, pocet opravitelnych, neopravitelnych chyb, pocet nenajdeni sektorov a pod.) a podla toho a nejakych vzorcov sa snazi jednak odhadnut, kolko zivota ostava disku a ak sa zapne smartd, je schopny interagovat s operacnym systemom a napriklad mu oznamit, ze by mohlo dojst k chybe a disku sa treba zbavit. ovsem to musi diskova jednotka podporovat, co by pri novych diskoch problem byt nemal...

000001010006354000063542021096770006369202416469024170970241744302417764

tie saty, to ti povedat neviem, ale viem, ze mne sa starucky HDD Quantum Fireball porucal prave takymto sposobom, najprv nevinne nahodne nefatalne chyby - stacilo retry a slo, potom ho z casu na cas neslo nadetekovat pri starte a nakoniec odisla elektronika uplne