On Fri, 28 Mar 2008, Mark Lord wrote:
One thing to try, to verify that my interpretation was correct, is to
try and read that exact sector. It should fail, I think.
The hex values are in low:middle:high order, so that translates to
0xf9240a, or decimal 16327690.
So you could try this, with the latest hdparm (from sourceforge.net):
hdparm --read-sector 16327689
hdparm --read-sector 16327690
hdparm --read-sector 16327691
At least one of those ought to fail, if we've done this correctly.
envy:/usr/src/hdparm-8.6# for i in 16327689 16327690 16327691 ; do ./hdparm --read-sector $i /dev/sdb ; done | egrep ^reading
reading sector 16327689: succeeded
reading sector 16327690: succeeded
reading sector 16327691: succeeded
(and just to be sure, i also tried 664825 (ie: 0x0a24f9 instead), works
fine too.)
On Fri, 28 Mar 2008, Mark Lord wrote:
cat /dev/zero > /dev/sdX
sync
hdparm -F /dev/sdX
kicked disk from array and running it now. didnt want to wait for results
before i posted this because of the hdparm --read-sector results...
//tlund
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
