martinjuhasz Posted February 21, 2023 Share Posted February 21, 2023 Hello, over night my disk2 came into error state Disk 2 in error state (disk dsbl) - WDC_WD80EZAZ-11TDBA0_JEH74D8M (sde) array has errors - Array has 1 disk with read errors I've checked the drive and it was powered down. these are shucked WD drives where i had to cover this 3rd pin to make it run. i suspect this became loose, but no way to confirm. i used an adapter to fix this issue permantently and the drive works again. I've ran a full SMART extended check which resulted in no errors. So i suspect the drive might not be faulty but just lost power. I'm unsure how to proceed. Should i run a preclear on the drive and if this is ok add it back to the array? How would that work? Stop Array Remove Drive from the Array Start Array Do a preclear on the unassigned drive Stop Array Add Drive again Start Array Any help appriciated. I added the SMART report of said drive2 and my diagnostics file. winston-smart-20230221-0952.zip winston-diagnostics-20230221-0952.zip Quote Link to comment
JorgeB Posted February 21, 2023 Share Posted February 21, 2023 Diags are after rebooting so we can't see what happened, disk looks OK, since the emulated disk is mounting and assuming contents look correct you can rebuild on top, IMHO preclear will be a waste of time, you want to make the array protected ASAP. Quote Link to comment
martinjuhasz Posted February 21, 2023 Author Share Posted February 21, 2023 Ah damn, should have grabbed the diag before checking the disk, well. Thanks for your insight. Will start to rebuild on top of it and see if anything is looking good. thanks! Quote Link to comment
martinjuhasz Posted March 4, 2023 Author Share Posted March 4, 2023 ok something weird happened. now disk1 is in error state. Quote Unraid Disk 1 error: 04-03-2023 13:48 Alert [WINSTON] - Disk 1 in error state (disk dsbl) WDC_WD80EZAZ-11TDBA0_7HK6NAHF (sdd) That is another disk. which makes me suspicious that these errors are NOT the disks. i've downloaded diagnostics before a reboot this time. any idea what could happen here @JorgeB since now this error is across disks apparently ? winston-diagnostics-20230304-2232.zip Quote Link to comment
JorgeB Posted March 5, 2023 Share Posted March 5, 2023 Disk dropped offline, this is usually a power/connection problem, on the power side can be a bad connection or a bad PSU. Quote Link to comment
martinjuhasz Posted March 22, 2023 Author Share Posted March 22, 2023 I've put my disks on different rails on my PSU and also changed connectors just to make sure. Today it happened again. @JorgeB does this look again like a power isse? If it is so, it seems i might need to replace the PSU and see if this (hopefully) resolves it. Mar 22 07:45:09 Winston emhttpd: spinning down /dev/sdc Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 07:56:43 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:27:26 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 08:58:08 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:28:51 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 09:59:47 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 10:30:29 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:00:02 Winston emhttpd: read SMART /dev/sdc Mar 22 11:00:13 Winston emhttpd: read SMART /dev/sdb Mar 22 11:00:25 Winston kernel: sd 3:0:0:0: [sdd] tag#15 access beyond end of device Mar 22 11:00:25 Winston kernel: I/O error, dev sdd, sector 12915028112 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028048 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028056 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028064 Mar 22 11:00:25 Winston kernel: md: disk1 read error, sector=12915028072 Mar 22 11:00:25 Winston emhttpd: read SMART /dev/sde Mar 22 11:00:35 Winston kernel: sd 3:0:0:0: [sdd] tag#16 access beyond end of device Mar 22 11:00:35 Winston kernel: I/O error, dev sdd, sector 12915028112 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028048 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028056 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028064 Mar 22 11:00:35 Winston kernel: md: disk1 write error, sector=12915028072 Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 22 11:01:38 Winston kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO I'm happy for any hints since this is so hard to debug Quote Link to comment
martinjuhasz Posted March 22, 2023 Author Share Posted March 22, 2023 @JorgeB sure, thanks! winston-diagnostics-20230322-1210.zip Quote Link to comment
JorgeB Posted March 22, 2023 Share Posted March 22, 2023 Mar 22 05:45:59 Winston kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 22 05:46:05 Winston kernel: ata3.00: qc timeout (cmd 0xec) Mar 22 05:46:05 Winston kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 22 05:46:05 Winston kernel: ata3.00: revalidation failed (errno=-5) Mar 22 05:46:05 Winston kernel: ata3.00: disable device Mar 22 05:46:05 Winston kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] Sense not available. Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] Sense not available. Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] 0 512-byte logical blocks: (0 B/0 B) Mar 22 05:46:05 Winston kernel: sd 3:0:0:0: [sdd] 4096-byte physical blocks Mar 22 05:46:05 Winston kernel: sdd: detected capacity change from 15628053168 to 0 Disk dropped offline again, still looks like a power/connection problem, if you haven't replaced the SATA cables yet do it, if you already did that then best to try with a different PSU, could also be a bad board, but that's much less likely. 1 Quote Link to comment
martinjuhasz Posted March 22, 2023 Author Share Posted March 22, 2023 (edited) i've run the board for years in another desktop computer without problems. I'll get some new SATA first and hope for the best. If not, i'll grab another PSU (uhg). We are talking about the SATA Cables (for data), not the power connector to the PSU right? Thanks again for your awesome support Edit: Since both drives failed already at some point, it might be the PSU, damn Edited March 22, 2023 by martinjuhasz Quote Link to comment
itimpi Posted March 22, 2023 Share Posted March 22, 2023 28 minutes ago, martinjuhasz said: We are talking about the SATA Cables (for data), not the power connector to the PSU right It can be either, particularly if you are using splitters on the power cabling. Quote Link to comment
Recommended Posts
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.