blacklisted Posted July 11, 2021 Share Posted July 11, 2021 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 Quote Link to comment
blacklisted Posted July 11, 2021 Author Share Posted July 11, 2021 Parity drive SMART Extended Self-Test completed without error. Quote Link to comment
blacklisted Posted July 12, 2021 Author Share Posted July 12, 2021 Checked cables. Attempting to rebuild the parity disk once more.... Quote Link to comment
trurl Posted July 12, 2021 Share Posted July 12, 2021 Your diagnostics suggest both of your cache drives and your parity drive were disconnected. Are these on the same controller? Quote Link to comment
blacklisted Posted July 12, 2021 Author Share Posted July 12, 2021 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? Quote Link to comment
JorgeB Posted July 13, 2021 Share Posted July 13, 2021 Problem with the onboard SATA controller: Jul 10 05:04:11 Ribeye kernel: ahci 0000:02:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xdf604000 flags=0x0000] This is quite common with some Ryzen boards, look for a BIOS update or use and add-on controller. Quote Link to comment
blacklisted Posted July 13, 2021 Author Share Posted July 13, 2021 Thank you so much. I'll check for BIOS update but may just get a new board. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.