September 12, 201213 yr Precleared (3 times) a 3TB drive to use for parity drive. no errors Had been running unRaid without parity for a couple days (old parity drive went Tango Uniform). Stopped array Assigned new drive as parity drive and Started array to build parity got the following. Sep 12 09:30:46 Tower kernel: mpt2sas2: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 12 09:30:46 Tower kernel: sd 4:0:0:0: [sdq] Device not ready Sep 12 09:30:46 Tower kernel: sd 4:0:0:0: [sdq] Result: hostbyte=0x00 driverbyte=0x08 Sep 12 09:30:46 Tower kernel: sd 4:0:0:0: [sdq] Sense Key : 0x2 [current] Sep 12 09:30:46 Tower kernel: sd 4:0:0:0: [sdq] ASC=0x4 ASCQ=0x0 Sep 12 09:30:46 Tower kernel: sd 4:0:0:0: [sdq] CDB: cdb[0]=0x2a: 2a 00 00 12 5d 88 00 04 00 00 Sep 12 09:30:46 Tower kernel: end_request: I/O error, dev sdq, sector 1203592 Sep 12 09:30:46 Tower kernel: md: disk0 write error Sep 12 09:30:46 Tower kernel: handle_stripe write error: 1203528/0, count: 1 Fortunately I had a 2nd 3TB drive I had precleared also and made that the parity drive and all is well so far (26% done in parity build) What are my next steps regarding the "bad?" drive?
Archived
This topic is now archived and is closed to further replies.