http://bugzilla.kernel.org/show_bug.cgi?id=14577 --- Comment #7 from Anonymous Emailer <anonymous@xxxxxxxxxxxxxxxxxxxx> 2009-11-16 01:58:08 --- Reply-To: Ganapathy_Sridaran@xxxxxxxxxxx *** Copying the bugzilla email in the email address *** Hi James, We'll look into this issue and get back to you. I wonder if they are genuine write errors due to the medium errors. Is this problem seen with other RAID volumes or just with this one particular volume? Are you running Adaptec Storage Manager Software on this system? If so, can you please collect the support.zip file? Support.zip can be collected by clicking "support.zip" under the "actions" menu. The Support.zip file provides us additional information on any disk errors that might have happened in the system. Thanks, Gana Gana S. Sridaran Engg., Manager - RAID FW/Drivers Adaptec Inc., 691, S. Milpitas Blvd., Milpitas, CA 95035 408.957.4985 -----Original Message----- From: James Bottomley [mailto:James.Bottomley@xxxxxxx] Sent: Tuesday, November 10, 2009 6:04 AM To: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx Cc: linux-scsi@xxxxxxxxxxxxxxx; AACRAID Subject: Re: [Bug 14577] New: Data Corruption with Adaptec 52445 On Tue, 2009-11-10 at 13:31 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=14577 > [ 21.903794] sd 0:0:0:0: [sda] Unhandled sense code > [ 21.903865] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [ 21.903998] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] > [ 21.904219] sd 0:0:0:0: [sda] Add. Sense: Internal target failure > [ 21.904382] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 01 bf 00 00 08 00 > [ 21.905051] end_request: I/O error, dev sda, sector 447 > [ 21.905122] Buffer I/O error on device dm-0, logical block 0 > [ 21.905191] lost page write due to I/O error on dm-0 > [ 21.905271] EXT3 FS on dm-0, internal journal > [ 23.263958] sd 0:0:0:0: [sda] Unhandled sense code > [ 23.264029] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [ 23.264162] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] > [ 23.264368] sd 0:0:0:0: [sda] Add. Sense: Internal target failure > [ 23.264531] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 bc 11 cf 00 00 08 00 > [ 23.265186] end_request: I/O error, dev sda, sector 12325327 > [ 23.265257] Buffer I/O error on device dm-1, logical block 492034 > [ 23.265327] lost page write due to I/O error on dm-1 > [ 23.364800] kjournald starting. Commit interval 5 seconds > [ 23.423871] sd 0:0:0:0: [sda] Unhandled sense code > [ 23.423874] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [ 23.423877] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] > [ 23.423880] sd 0:0:0:0: [sda] Add. Sense: Internal target failure > [ 23.423886] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 80 01 bf 00 00 08 00 These are sense codes (Hardware error and Target Failure) generated by the driver when it encounters some type of firmware related failure in the RAID ... the only people who can really debug and fix this are the aacraid people (cc'd). It may be a simple matter of a support call if it's a hardware error. James -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
