> Now to wait and see the drive produce the error.
OK, that doesn't work - it appears all get reset anyway. Both drives
here had -K1 and -k1 set with hdparm:
Mar 2 10:28:29 website2 kernel: blk: queue c033da3c, I/O limit 4095Mb
(mask 0xffffffff)
Mar 2 10:28:29 website2 kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 2 10:28:29 website2 kernel:
Mar 2 10:28:29 website2 kernel: hda: drive not ready for command
Mar 2 10:28:29 website2 kernel: hda: status timeout: status=0xd0 { Busy }
Mar 2 10:28:29 website2 kernel:
Mar 2 10:28:29 website2 kernel: hda: DMA disabled
Mar 2 10:28:29 website2 kernel: hdb: DMA disabled
Mar 2 10:28:29 website2 kernel: hda: drive not ready for command
Mar 2 10:28:29 website2 kernel: ide0: reset: success
[nick@website2 nick]$ sudo /sbin/hdparm /dev/hda
/dev/hda:
multcount = 16 (on)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 1 (on)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 784/255/63, sectors = 12594960, start = 0
[nick@website2 nick]$ sudo /sbin/hdparm /dev/hdb
/dev/hdb:
multcount = 0 (off)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 1 (on)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 525/255/63, sectors = 8439184, start = 0
Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]