Mattlevant

it does and i had all my drives plugged into them, when one drops off i swap them onto an expansion card to get them back online and then back to the onboard sata when they next drop off ive tried the onboard and also the expansion card, same results i know its probably power at this point but i dont understand how, the psu is 850w rated it should be plenty the read errors happen during parity check, i hear the hard drive start clicking then i see read errors, no problem when writing. i have also had the errors when trying to play media via plex although less common

so i have 2 strings from the psu, they come with 4 sata connectors on, i then also have 2x molex strings with 1x molex to sata adapter with 2 connectors on making 4 sata connectors. 2 of my sata strings was using 1 connector each, parity and 5, then both the molex to sata were running 2 drives each (12,34 drives) this morning i took off 3&4 from the molex to sata and now have 3,4,5 on the 2nd sata string, im now getting read errors on 1&3 while rebuilding #4

i dont think it was a actually advertised as a gaming psu, just i dont consider it server grade (it definately isnt) Gigabyte P850GM

no im not sure i dont, its possible, but its a good branded psu and 800w it sould be able to handle the amount of drives i have it is though a 'gaming' psu probably not designed for 24/7 operation

Recently been struggling with drives just dropping out and its beginning to wind me up. i keep getting read errors then 1 drive will get disabled and then another will just disappear without being disabled. if i reboot i usually get the one that wasnt disabled back and i can rebuild the one that was but its becoming a real hassle rebuilding 2-3 times a week. right before a drive drops out i will hear clicking but it is not always the same drives, the drive failures change randomly currently its drive 3&4 (4 disabled, 3 dropped out), 2 days ago it was 1&2 (2 dropped out and 1 disabled), and before that it was 2&4 (2 disbaled and 4 dropped out) theres no real pattern to it im not sure what if anything the diagnostics show, if there is any cause of them going offline? tower-diagnostics-20241003-2113.zip

so i have worked out that docker has decided to kill itself i lost disc 5 today (disabled but emulated) wondering if that is related?

i also get this error when i try restart my Prowlarr docker container which went offline

cabling ended up being the issue, old possibly broken cable, bought a new one and connected right away

only noticed this today but i have lost access to some of my docker containers, they wont come online, i also cant install from the apps page i get this error i saw on another thread that changing DNS to 8.8.8.8 would help but my dns is already 8.8.8.8 with other backups such as 8.8.4.4, 9.9.9.9, 1.1.1.1 i beleive first 2 are googles dns, then quad9 and cloudflares dns tower-diagnostics-20230802-2032.zip diags attached

okay so i have reseated all my drives again and it is now showing in the array and rebuilding the drive

sorry disk 5 serial number ends R1YK if that helps identify it? I did move my server last night to be higher in my rack (it was powered down) as i added a UPS to the rack but i did reseat the cabling to the drives then but i will try reseat it again

disc 5 just got disabled, i rebooted, removed it from the array, start maintenance mode, readd it and then it totally disappears, unable to see it in unassigned devices and it doesnt show in the pool, 5 slot shows unassigned it is detected by the bios on reboot tower-diagnostics-20230801-0800.zip

Definitely plugged in correctly, I'll have to order another B to A cable as I'm not sure if this cable is any good, been sat in a drawer for years from an old printer Do I have to reboot for it to detect usb changes?

I have just bought a UPS APC SUA1000rmi2u Server is receiving power and has the usb cable connected between the UPS and server but the server can't communicate with the ups Not sure what I have done wrong? Diagnostics attached incase that helps tower-diagnostics-20230731-2151.zip

Makes sense I suppose But it was random which got the errors, it's not like it was the last drive on the string every time Anyway I've currently got 4 powered via my bodged molex to sata power The way I've connected it I've got 2 on each string on a Y split from 1 molex 4 pin The other 2 drives are on a single string from the dedicated sata power cable from the PSU So 3 strings of 2 now also totally bypassed the lsi card Now I'm unsure if it was power related or the LSI card was at fault but it's currently online and ran a whole parity check took 18 hours without any drive errors (quite a few parity errors 500k or so which Im running a correcting check to fix currently)