theamzngq

So I ended up replacing the backplanes (drive enclosures) as well as the power supply. Not very "scientific method" of me, but that seems to have settled things down. All appears to be well after 3-4 days now.

Ok, thx for the clarification

Strange, one drive was showing tons of seek errors…

Just noticed that my rebuild speed is down to 3MB/sec, it'll take 22 days to finish :-|

Well, a lot has happened since my last post. It would seem that something else is going on; I've had to rebuild a few times now. I've had multiple drive issues at this point, I'm thinking maybe I have a bad controller, bad hot swap bay, or bad power supply? One of my drives won't show up (Disk 10), so maybe bad hot swap bay (tried two at this point). Another is reporting seek errors, maybe from all the rebuilding? Not sure what to do. I'm concerned with all the drive issues that I may lose some data... I've got an Amazon cart locked and loaded with new hot swap bays and a new drive controller. What should I do next? server-diagnostics-20230629-0736.zip

I can replace the sata cable, but the drive is in a hot swap bay, so the power comes from the drive array unit.

Just noticed that parity check was taking a long, long time. I pulled up the logs, but I'm sure entirely what I'm looking at. There are lines like this: Jun 20 04:40:02 server kernel: ata6.00: exception Emask 0x50 SAct 0xef0 SErr 0x4890800 action 0xe frozen Jun 20 04:40:02 server kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jun 20 04:40:02 server kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jun 20 04:40:02 server kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 20 04:40:02 server kernel: ata6.00: cmd 60/00:20:70:fe:9a/04:00:ac:00:00/40 tag 4 ncq dma 524288 in Jun 20 04:40:02 server kernel: res 40/00:30:70:06:9b/00:00:ac:00:00/40 Emask 0x50 (ATA bus error) Jun 20 04:40:02 server kernel: ata6.00: status: { DRDY } Does this mean I need to find which drive is ATA6? Or is that a generic ATA error label? Disk 10 is also showing read errors and I've seen some posts that talk about replacing the SATA cable. What should I do? server-diagnostics-20230621-1854.zip

I prefer to store it on an unassigned USB drive so that if there are any issues with the array or the server, I can rebiuld without having to worry about recovering the backup from the array. I will disable compression from now on.

based on where I recall using that drive last, it must have been. Too bad I didn't get any notifications...but nothing I lost was earth-shattering luckily. On a related note, is it recommended to use compression on appdata backups (the default comes up with 'no' selected)? If the files had simply been copied and not compressed to tar.gz, the backups might not have failed because no individual files would have exceeded 4GB.

Thank you, that got me squared away. Turns out my backups kept stopping at 4GB, so I couldn't use them anyway! Not sure what file system was on it, but it must've had a limit of 4GB, would you say?

Because my appdata folder was on the cache drive (which is no longer mountable), none of my dockers will start (duh). But, the CA backup plugin wants to restore to /mnt/cache/appdata/. Do I need to recreate that share first somewhere else? Or do I need to add a new disk, recreate the cache, and then let it restore there? I'm assuming the Docker service needs to know where the appdata folder is, which is why it won't start... Any guidance would be appreciated!

Everything seems hosed, help! I've been avoiding clicking the friendly "upgrade to 6.9.2" link for months, and the day I decided to click it, now unraid seems to be screwed. It boots and gets to 'login' prompt, but there's no web interface and no services. I can ping it's IP address and I can SSH into it, but beyond that, I have no clue what to do. Help?!