Re: Further testing a drive with dd running -current

2010-01-03 Thread David Vasek
On Sat, 2 Jan 2010, Scott McEachern wrote: The second was your suggestion, and interestingly, it produces the error. Partition e starts at 43 022 070, the problem is at 268 435 455, so we'll skip 225 413 380 to start just before that spot: # dd if=/dev/rwd0e of=/dev/null skip=225413380 dd:

Further testing a drive with dd running -current

2010-01-02 Thread Scott McEachern
Sorry if this shows up again. I sent this twice yesterday and for some reason it hasn't appeared on the list. David Gwynne wrote: id try this on a sili(4), ahci(4), or mpi(4) controller and see what happens. my guess is you're hitting issues in the ata stack, specifically to do with the

Re: Further testing a drive with dd running -current

2010-01-02 Thread David Vasek
On Sat, 2 Jan 2010, Scott McEachern wrote: # date; time dd if=/dev/rwd0c of=/dev/null; date Thu Dec 31 23:44:32 EST 2009 dd: /dev/rwd0c: Input/output error 268435455+0 records in 268435455+0 records out 137438952960 bytes transferred in 23954.900 secs (5737404 bytes/sec) 399m14.93s real

Re: Further testing a drive with dd running -current

2010-01-02 Thread Scott McEachern
David Vasek wrote: Out of curiosity, does the same happen if you dd from /dev/rwd0d? As Matthew Szudzik pointed out, dd is failing when it attempts to read (2^28)th sector of the current device you are reading from. Up to, including, 2^28-1 everything is ok. Regards, David I made an