On 04/16/2010 08:20 PM, Sarah Sharp wrote:
I'll see if I can find a contact for this. I need a couple more details
so they can reproduce this. Jonas, did you ever test the Buffalo drive with
Mark Lord's fix to set the sector count to "1"? Which version of hdparm
were you using? Is that version just in Lucid, or is it in Karmic too?
Yes, I did try it with Mark's latest version (9.29b) which uses a sector
count of "1" (version 9.29) and, in addition, uses ATA_12 (instead of
ATA_16) for IDENTIFY (9.29b). The issue exists in Karmic and Lucid.
It seems the report I sent back to Mark, once I tested 9.29b, didn't go
to all of you but just Mark. Here it is:
--------------------------------------------------------
The good news: It doesn't crash the chip anymore. The drive is still
mounted fine after executing hdparm.
The bad news: From the hdparm output it seems like the chip still
doesn't play nice.
/dev/sdb:
outgoing cdb: a1 08 2e 00 01 00 00 00 40 ec 00 00 00 00 00 00
data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_12 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: bad response (not CHECK_CONDITION)
Trying legacy HDIO_DRIVE_CMD
outgoing cdb: a1 08 2e 00 01 00 00 00 40 a1 00 00 00 00 00 00
data: 40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00
SG_IO: ATA_12 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00
ATA_12 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
I/O error, ata_op=0xa1 ata_status=0x51 ata_error=0x04
HDIO_DRIVE_CMD(identify) failed: Input/output error
readonly = 0 (off)
readahead = 256 (on)
geometry = 121601/255/63, sectors = 1953525168, start = 0
--------------------------------------------------------
I didn't get a reply from Mark on this yet. Alan, does this output mean
something to you?
-Jonas
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
