blacklisted

Replacing the cable fixed it. Thanks.

Hi all, I tried transferring data from my cache drive to Disk 6 using Dynamix File Manager today but the transfer was horribly slow, and UNRAID eventually hung. I tried shutting UNRAID down via terminal but it would not shut down. I ended up pulling the plug, rebooting, and starting a parity rebuild. Parity rebuild, however, has been unacceptably slow: 1.6 MB/sec. 98 days to rebuild. I checked my logs and am getting "failed command: READ FPDMA QUEUED." I don't know what this means. Can anyone offer insight and help? ribeye-diagnostics-20230716-2116.zip

Thank you so much. I'll check for BIOS update but may just get a new board.

I believe they may be on the same controller. I have parity building and don't want to open the case while UnRaid is up and running, just in case there is a faulty connection. Once parity completes, I'll open the case and check to see where the drives are connected. Is there a way to check which drives are connected to which controller via command line or any other place in UnRaid?

Checked cables. Attempting to rebuild the parity disk once more....

Parity drive SMART Extended Self-Test completed without error.

My parity drive suddenly became disabled. I stopped the array, removed the parity drive, started/stopped the array, and re-added the parity drive. I then started parity rebuild. After many hours, rebuild failed and the parity drive became disabled again. I checked the disk log and found BTRFS Errors. System log starts showing: BTRFS error (device sdg1): bdev /dev/sdg1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0 1) I ran: btrfs scrub status /mnt/cache Scrub started: Sun Jul 11 09:07:33 2021 Status: finished Duration: 0:15:58 Total to scrub: 781.81GiB Rate: 835.66MiB/s Error summary: no errors found 2) I ran: btrfs dev stats /mnt/cache [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0 [/dev/sdh1].write_io_errs 0 [/dev/sdh1].read_io_errs 0 [/dev/sdh1].flush_io_errs 0 [/dev/sdh1].corruption_errs 0 [/dev/sdh1].generation_errs 0 I removed the parity drive from the array and started running a SMART Extended Test. I've attached Diagnostics from yesterday when the problem occurred. Can someone look at the diagnostics and let me know what the problem may be? It seems the problem starts July 10 at 5:04 How can I stop the errors and rebuild parity? The array is currently without the parity drive. Thanks. ribeye-diagnostics-20210710-0835.zip

Ah, yes, thanks. I just figured that out and was going to post my finding. I reset my router the other day. The reset changed the subnet from 192.168.1.1 to 192.168.0.1. It also cleared my address reservation for my unRAID server. I reset the subnet and re-added the address reservation. Now I can access unRAID GUI via the LAN! Smacking my forehead... Thanks for the help : )

Thanks. I've attached the zip file. I appreciate all the help I can get : ) ribeye-diagnostics-20210530-0802.zip

Noob here. I awoke this morning and found my unRAID server offline. I rebooted the server, but it was still showing as offline. I attached a monitor to the unRAID server and rebooted. The text/command-line boot sequence went through its sequence but ended with username/password request. I entered my username and password and was able to “sign-in,” but the GUI was still inaccessible on my LAN. I rebooted the server and chose unRAID GUI mode from the list of options at boot. The GUI booted, and I am able to access the GUI via the monitor attached to the server, but I cannot access the GUI via the LAN. On top of that, the parity drive is listed as “disabled.” I ran a SMART quick test on the parity drive and it returned no errors, a good drive. I checked power and SATA cables to all drives. All cables are attached and correct. Thinking it may be a corrupt OS, I copied all OS files from the flash drive to another disk. I re-imaged the flash drive. I copied the Config file back to the re-imaged flash drive. I rebooted with the re-imaged flash drive and experienced the same problems: inaccessible GUI via the LAN and parity drive showing as “disabled.” USB Flash drive is a 32GB Samsung Fit. Less than a year old. Anyone have suggestions on how to fix this problem?

When I set-up Let's Encrypt w/ Nginx, I didn't realize Let's Encrypt created a certificate and locked it to those subdomains. After set-up, I attempted to add an "ombi" subdomain in the edit GUI, but, when I restarted Let's Encrypt, I found I could no longer access my other subdomain services. It seems adding the "ombi" subdomain had broken the certificate. So, I removed the new subdomain from the edit GUI and everything returned to normal, certificate not broken. How can I add more subdomains to Let's Encrypt? BTW, This is my first post/question to UnRaid's Forum. I hope I'm doing it right.