January 31, 20242 yr I recently purchased 2x 8tb Toshiba MG6 12Gbps SAS disks (MG06SCA800EY) from a seller. Whilst they are second hand, I didn't pay much for them so was keen to try them our in my array. I've always had SATA disks (x8) up until now, running through an LSI 9211-8i 6Gbps card. I moved 4 of the SATA disks over to the onboard (X99) SATA ports, and left the other 4 SATA disks on one of the SAS-SATA cables. The existing disks all run fine and the array continued to function as normal after reboot. The issue is with the 2 'new' SAS drives. They are both seen by the LSI card in its config utility, and by Unraid (6.12.4) as unformatted disks, but when I try to format or preclear them I get errors preventing the action. I have attached the preclear log file. I few things I am thinking; - update firmware on both the LSI card (circa 2011 FW I believe) and the HDD's (EH0B FW, latest is EH0D) but doing this is not as straight forward as I would have liked. - I've heard that some 12Gbps SAS drives won't work with 6Gbps HBA cards - The disks were somehow nuked before they were taken from their last array. Is this even a thing??? - I've only got these 2 SAS cards off the single Mini-SAS to 4x SFF-8482 cable. Can't see why this would be an issue though??? - I don't think they are dead drives as they are both coming up with exactly the same error, and are only 3 years old. These drives are enterprise class and are rated for 2,500,000 MTBF hours. For what I paid for the drives ($75AUD each) I would be willing to drop another $100AUD on a newer 12Gbps HBA card if I really have to, but of course I'd rather get the current hardware working if I can. Appreciate any help. Preclear Log of disk 70X0A00AF1GF.html
January 31, 20242 yr Community Expert It might be worth posting the full diagnostics to see if we can spot anything. Ideally this should be after trying a format of one of the drives. As you said these are enterprise drive they may have 'type 2' protection that needs removing before Unraid can use them.
January 31, 20242 yr Author Thanks, I'll do this tonight as I disconnected the drives to prevent any further issues.
February 1, 20242 yr Author Right, diagnostics attached. Hopefully someone can provide some guidance. Thanks tower-diagnostics-20240201-2039.zip
February 1, 20242 yr Community Expert The syslog shows: Feb 1 20:38:20 Tower kernel: protection error, dev sdi, sector 15628053160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 when you try to format. I do not have a link to hand but you should be able to find how to remove this by googling something like "Remove type 2 protection" or maybe someone else will chime in with the relevant forum link.
February 1, 20242 yr Community Expert These should have more info: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
February 2, 20242 yr Author Ok, so it looks like I got the read protection off using the sg_format --format --fmtpinfo=0 /dev/sd* function, but I still can't format via the GUI to mount. Both drives are giving the same error. tower-diagnostics-20240202-2117.zip
February 2, 20242 yr Community Expert They are reporting hardware errors: Feb 2 21:06:56 Tower kernel: scsi_io_completion_action: 74 callbacks suppressed Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1235 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1235 Sense Key : 0x3 [current] Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1235 ASC=0x31 ASCQ=0x1 Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1235 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 Feb 2 21:06:56 Tower kernel: blk_print_req_error: 74 callbacks suppressed Feb 2 21:06:56 Tower kernel: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1250 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1250 Sense Key : 0x3 [current] Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1250 ASC=0x31 ASCQ=0x1 Feb 2 21:06:56 Tower kernel: sd 5:0:1:0: [sdg] tag#1250 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Feb 2 21:06:56 Tower kernel: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 It's possible they are still write protected/locked, SAS devices can be a pain because of those options.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.