On Sunday 28 January 2007 14:22, Greg Freemyer wrote:
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39876480, sector=39876480 ide: failed opcode was: unknown
and:
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39941759, sector=39876480 ide: failed opcode was: unknown
If I boot to the Suse 9.1 drive in this box I don't see that error. Also, if I boot to hdb, XP works fine. So, I ask: what in Suse 10.2 is causing the messages?
Fred
Fred,
Boot to SuSE 9.1 and report the number of sectors your drives have. The numbers above seem very close to if not past the end of the drive.
ie. use hdparm or cat /proc/..... to get the number of sectors. I don't have a 9.1 system running so I can't remember the exact command to do it.
Greg --
Greg: 9.1's Yast hardware reports sectors=39876480. I guess he can't find the last one? Whatever, it is less of a bug and more of an irritant. Maybe the sector read starts at "1" instead of "0"? What's a digit between friends ;-) Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org