emhttpd: device /dev/sdx problem getting id

[mrmeeper]

Having an issue re-inserting a previously used disk. Once I hot-swap it back into the array, I get the following error:

emhttpd: device /dev/sdd problem getting id

Unfortunately, this log package is after a reboot and the same error persists. I seem to get this error any time I remove a disk and try to use it again which makes the disk un-usable. Is there any way to "forget" about this drive and re-initialize it?

 

This disk in question is my parity drive. I'd like to add it back into the array but it will not show up in Array Device options or Unassigned Devices.

Drives are connected to a LSI SAS 9211-8i 

 

Any direction would be helpful. I'm new to unraid and this is my first homebuilt server.

Thanks in advance.

 

appstation-diagnostics-20200112-1301.zip

[mrmeeper]

This is what the log shows when the disk is inserted:

Jan 12 23:26:41 AppStation kernel: scsi 1:0:10:0: Direct-Access     ATA      WDC WD120EMFZ-11 0A81 PQ: 0 ANSI: 6
Jan 12 23:26:41 AppStation kernel: scsi 1:0:10:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x5000cca258c2dbb2)
Jan 12 23:26:41 AppStation kernel: scsi 1:0:10:0: enclosure logical id (0x500605b009b8c354), slot(3) 
Jan 12 23:26:41 AppStation kernel: scsi 1:0:10:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: Power-on or device reset occurred
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: Attached scsi generic sg3 type 0
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: [sdd] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB)
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: [sdd] 4096-byte physical blocks
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: [sdd] Write Protect is off
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: [sdd] Mode Sense: 7f 00 10 08
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 12 23:26:41 AppStation kernel: mpt2sas_cm0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)
Jan 12 23:26:41 AppStation kernel: sd 1:0:10:0: Power-on or device reset occurred
Jan 12 23:26:42 AppStation kernel: mpt2sas_cm0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)
Jan 12 23:26:42 AppStation emhttpd: device /dev/sdd problem getting id
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: Power-on or device reset occurred
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: [sdd] tag#1039 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: [sdd] tag#1039 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Jan 12 23:26:42 AppStation kernel: print_req_error: I/O error, dev sdd, sector 0
Jan 12 23:26:42 AppStation kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Jan 12 23:26:42 AppStation kernel: mpt2sas_cm0: log_info(0x31110630): originator(PL), code(0x11), sub_code(0x0630)
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: rejecting I/O to offline device
Jan 12 23:26:42 AppStation kernel: print_req_error: I/O error, dev sdd, sector 0
Jan 12 23:26:42 AppStation kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Jan 12 23:26:42 AppStation kernel: ldm_validate_partition_table(): Disk read failed.
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: rejecting I/O to offline device
Jan 12 23:26:42 AppStation kernel: print_req_error: I/O error, dev sdd, sector 0
Jan 12 23:26:42 AppStation kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Jan 12 23:26:42 AppStation kernel: sdd: unable to read partition table
Jan 12 23:26:42 AppStation kernel: sd 1:0:10:0: [sdd] Attached SCSI disk
Jan 12 23:26:42 AppStation rc.diskinfo[5959]: SIGHUP received, forcing refresh of disks info.
Jan 12 23:26:43 AppStation emhttpd: device /dev/sdd problem getting id

I'm able to add this disk back into it's USB enclosure and it works just fine. My concern is that this has happened with another disk recently in the past which I have replaced. I'm not sure what unraid is complaining about here and if there's any way to fix it since it's offline.

[JorgeB]

14 hours ago, mrmeeper said:

I seem to get this error any time I remove a disk and try to use it again which makes the disk un-usable. Is there any way to "forget" about this drive and re-initialize it?

Doesn't look related to that, disk is failing to initialize properly, it could be the 3.3v issue, make sure there's no 3.3v on that SATA plug, google "wd 3.3v sata"