nmills3

i rebooted last night, left the array rebuilding and it failed about 7% in, then this morning i tried testing it with no disk assigned to disk 3 which didn't work and then i got the reply from you so i restarted the array in maintenance mode and the test has been running on the emulated disk 3 since. I assume i should wait until after the test is done to start changing cables

tower-diagnostics-20221130-1108.zip

the gui. I followed the instructions for checking the drive on the link you sent. It says it's still running, is it meant to take this long?

currently it's showing this Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... and then it just has a line of many many dots

so the disk got 8% into a rebuild while having the previously mentioned issues and now stopped and has about 380 errors. i've attached the new logs. i have no idea what to do now and i'm very worried about losing data. what do i do? tower-diagnostics-20221129-2243.zip

Also on the "main" page, where it normally shows the drive capacity/used size is just saying "Unmountable wrong or no file system"

ok, so i stopped the array, un assigned the drive, started the array, stopped it again, then went to stop it again but it would stop so i had to restart the pc, now i got it running again and i'm rebuilding onto the same drive but the emulated contents of the drive seem to be completely empty, none of the data that was on the drive is showing anywhere

I just got an array error on disk 3, i've had some issues with errors on drives connected to the on board sata controller before but i fixed that by connecting to a hba instead, my drives are all only 1-2 years old so i'd be surprised if my drive is dead tower-diagnostics-20221129-2110.zip

ah ok, thanks for the explanation. for some reason when this happens the UI doesn't like to show me any drives offline so it can be a bit hard to understand what's happened but your explanation makes sense

this might be a really stupid question, but when a drive stops working like in this kind of situation. shouldn't unraid failover to using the parity data instead? I know that if you restart an array that's missing a disk it will emulate the contents but shouldn't it also do that "live" if a disk stops working for some reason?

i'm pretty sure you're the same person that told me it was probably that last time. I guess my theory of some ports being ok was wrong in the end. I'll just have to switch my ssds over to the hba and sacrafice trim support then

I've had this issue happen a few times now and i'm trying to work out what the exact cause is. The server will work fine for a few weeks and then just die. last time i had this issue, someone did suggest that it might be my sata controller as i'm using a ryzen board. I swapped a few bits around so i'm not sure if that's still the same issue or if something else has gone wrong tower-diagnostics-20220802-1844.zip

Well i've had 3 860 evos connected for 100 days without issue. thinking about it, i might have moved a drive about a month ago. i bet i moved disk 4 from one of the hot swap bays connected to the HBA to one of the ones connected to the mobo without realising. I'll probably switch it so all the hotswap ports are on the hba and i'll just move the ssds to somewhere else connected directly to the mobo

hmm. what i might do then, is connect all the hard drives to the hba and leave the ssds on the motherboard. I've had the cache drives connected to that controller for upto 150 days working fine but it seems that as soon as a hdd is connected, that's when it goes wrong. If I continue to have these issues after that, then i guess my only option is to connect everything to the HBA

So basically that sata controller pooped the bed and that broke disk 4 and i assume also messed up the cache drives connected to it causing the issues with my dockers dying then i assume? Is it safe for me to just connect everything via the HBA?

Should i delete one of them or do i just leave them? I noticed that every night the mover trys to move the files and then fails because they already exist on the cache so now i just seem to have 2 of the file

all the hard drives (sdb,sdd,sdc,sde and whatever disk 4 was) are connected via a HBA but all of the other drives (ssds) are connected directly to the motherboard because people said not to connect the ssds to a hba. should i just switch them over to all be on the hba?

Ok, the same or a very similar issue just happened again. I've not restarted the server this time and i've got the diagnostics tower-diagnostics-20220710-0904.zip Edit: I tried to stop the array to stop any further errors and now the array is failing to stop and is stuck on unmounting disks Edit 2: Just rebooted the system to get things running again and have the same issue as last time with disk 4 disabled

ok, i'll answer your questions in order. It's expected that it doesn't have much data. i have about 16TB of storage and only about 5TB used so that's normal for it. I'm unsure if the drive was disabled before the reboot. I just say a bunch of my docker containers stopped and some btrfs errors in the log and decided to reboot to try and fix it before posting and after that reboot i noticed that the drive was disabled (the drive didn't have any data being used by the docker containers so i have no idea why they stopped) I had an issue with filling the docker image in the past because i have a lot of game servers running on my tower so even with 50gb i end up using about 43% of it at all times I'll have to take a look at the connections. i'm using a hba with a sas to sata splitter thing so it's probably a bad connection there. After i redo the connections, would you say i'm probably safe to rebuild onto the same drive?

my bad. here you go. tower-diagnostics-20220627-2049.zip

Unfortunately i don't have the logs from before the reboot. here's the log from after tower-diagnostics-20220627-1824.zip

Just came back to find my server with half of the docker containers stopped and getting btrfs errors. I restarted the server and now one of my main array disks is disabled. I've attached it's smart report. What do i need to do to fix this? tower-smart-20220627-1817.zip

i think i fixed my issue. I switched the two cables plugged into the switch end and now it works. maybe it just wasn't quite in properly or something. but it now seems to work

well i guess i new get to find out what doesn't work. would you say that as i have a second of the same card running to the same switch that i can probably say the switch isn't the issue?

is there any reason the link would keep going down like that? did i configure something wrong?