shire

I use something like https://www.icydock.de/product/mb455spf_frame.html this. The cable is not directly connected to the drive itself. The metal clip fits just fine to the HD case. Thanks!

Yes..those UDMA CRC errors cause an error in the drive overwiev. I acknowledged them and they are back to normal (green).

I ordered those. Especially for the breakout cables we don't have a lot of choices in Germany...

Hello together, to have a proper connection between harddrive and controller I would like to buy new cables. My existing red break out cables don't have metal holders/clips at the end of the cable for example. Any recommendations? I found the following on amazon: YIWENTEC Mini SAS 36P sff-8087 zu 4-SATA-Festplatte mit Kabel 0.5m deleyCON 3x 50cm SATA 3 Nylon Kabel Set Datenkabel 6 Gbit/s Anschlusskabel Verbindungskabel Mainboard HDD SSD Festplatte 2 S-ATA Stecker Gerade Rot This is in Germany (amazon). Bye.

The I/O errors happened during the last reboot. I rebooted again and they did not reappear. So...I gues I have to observe both 'problems'... Thanks...

Hello, after I replaced a drive (one with reallocated sectors) I did a rebuild. This worked without any problems. I also decided to check on the SMART status of my other drives. Two are problematic. Both have ‘UDMA CRC error counts’ in the 4xx (/sdu, /sdl). Besides that, drive /sdu wrote some errors into the logfile while rebooting. Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907029160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907029104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907028176 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907028216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907026080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 120 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 29 prio class 2 I did an extended SMART test on both drives afterwards (passed both). Could anyone check the logfiles? I have another new drive ordered that will arrive today. I would like to decide on which one to replace next. I will check the cabeling on both drives. I have also the complete diagnostic if needed. Bye. WDC_WD20EARS-60MVWB0_WD-WCAZA4043525-20230830-1012.txt WDC_WD20EARS-22MVWB0_WD-WCAZA6163992-20230830-0924.txt

I rebooted the server after I reseated all the drives in their drive caches. I also use pushover on my phone to monitor the server. This drive reported reallocated sectors before the reboot. So in other words (to understand it for the future): - A drive reports an error (like reallocated sectors) - unRAID sees it and takes down the drive (red indicator) - The drive might pass the SMART test nevertheless I found a few posts on how to reenable drives on this forum. I will skip this one and just buy a new drive...

Hello, I have one red drive in my array. I did a long SMART test and it passed. Should I change it (I don't see another solution)? Bye. WDC_WD30EZRZ.txt

After the parity check was finished (the one with errors) I started it again with 'Write corrections to parity' unchecked. That worked without any errors. The next parity check I activated 'Write corrections to parity" and it also finished whithout errors. Very weird.

The drive passed. Hm... tower-smart-20230104-0902.zip

Hello, happened during the monthly parity check. Drive 12 is quite new. Any ideas? Bye. tower-diagnostics-20230103-1606.zip

HA! A few month ago I installed unraid fresh on the usb stick. I had a unusal problem with a disk not going in standby (which was solved by reinstalling the OS). Seems I have forgotten to activate SSH and Telnet. Works fine now.

Hello, I use the web gui for almost all my work on the server. Due to other problems (now solved) I tried to connect via SSH and Telnet to the server via putty. I always get the message 'Network Error: Connection refused' I deleted the SSH keys in putty (regedit). That changed nothing. I can access the server via the gui, smb in Win10 and NFS from my streaming device just fine. Any other ideas how to solve this....?

Everything is there:-))))

@trurl: Thank you for your help! You saved me a lot of pain!!