Hello, On 01/30/2010 04:43 AM, Robert Hancock wrote: > kazimir:~# mount /cdrom > sr 1:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08 > sr 1:0:0:0: [sr0] Sense Key : 0x5 [current] > sr 1:0:0:0: [sr0] <<vendor>> ASC=0xa8 ASCQ=0x1ASC=0xa8 ASCQ=0x1 > sr 1:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 00 00 10 00 00 02 00 > end_request: I/O error, dev sr0, sector 64 > Buffer I/O error on device sr0, logical block 8 > > The kernel tried to read some sectors off the disk (command 0x28) and > the drive returned an error. ASC of 0xa8 is a vendor-specific error > code, so only Pioneer can likely say what that error means. > > You're sure that 2.6.22 is still able to successfully access this drive? > Any unusual dmesg output there? One thing which could affect this is the change in the isofs code. Locating the anchor blocks for isofs involves some guesswork and that part has changed somewhat during past several releases. Different kernel versions would request different sequence of blocks. It could be that access to certain sectors is confusing the drive. Thanks. -- tejun -- 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
