I'm in the rather unlucky circumstances of trying to rebuild a md array, where the "good" drive is starting to report UNC errors, like this:
Apr 7 11:11:18 rollo kernel: [15659.604216] sd 0:0:0:0: [sda] Unhandled sense c ode Apr 7 11:11:18 rollo kernel: [15659.604243] sd 0:0:0:0: [sda] Result: hostbyte =DID_OK driverbyte=DRIVER_SENSE Apr 7 11:11:18 rollo kernel: [15659.604271] sd 0:0:0:0: [sda] Sense Key : Medi um Error [current] [descriptor] Apr 7 11:11:18 rollo kernel: [15659.604300] Descriptor sense data with sense de scriptors (in hex): Apr 7 11:11:18 rollo kernel: [15659.604317] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 7 11:11:18 rollo kernel: [15659.604343] 46 c0 8a 32 Apr 7 11:11:18 rollo kernel: [15659.604358] sd 0:0:0:0: [sda] Add. Sense: Unre covered read error - auto reallocate failed Apr 7 11:11:18 rollo kernel: [15659.604388] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 46 c0 8a 30 00 00 08 00 Apr 7 11:11:18 rollo kernel: [15659.604413] end_request: I/O error, dev sda, se ctor 1187023410 Apr 7 11:11:18 rollo kernel: [15659.604437] ata1: EH complete Is there a way to determine which file is residing in the affected block, so I can determine if the error can be corrected by forcing a block remap with hdparm, or if this is an essential file, that must be restored from the backup. -- //Wegge -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150407112238.1435b...@wegge.dk