boxer74

Thanks. I'll keep an eye on things. I have a scrub scheduled for Dec 1st. Does unraid send a notification for btrfs errors? I didn't get any with this recent error.

Ok, I found the affected file. Deleted and restored from a backup. I assume the process now is to run a scrub and see if it comes back clean for disk 1? Not sure what caused the file corruption.

My server recently locked up during update of a few docker containers. I was able to save a diagnostic. It appears that my docker.img had some corruption. I've since deleted it, created a new one and added back all my containers. I also ran a BTRFS scrub on my cache drive and it came back clean. What is concerning is that disk 1 in my array which has BTRFS filesystem reported 1 corruption. Nov 21 08:09:19 ur1 kernel: BTRFS warning (device dm-0): csum failed root 273 ino 9248 off 6311936 csum 0x1a753a94 expected csum 0x58a4bd31 mirror 1 Nov 21 08:09:19 ur1 kernel: BTRFS error (device dm-0): bdev /dev/mapper/md1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 btrfs dev stats -c /mnt/disk1 [/dev/mapper/md1].write_io_errs 0 [/dev/mapper/md1].read_io_errs 0 [/dev/mapper/md1].flush_io_errs 0 [/dev/mapper/md1].corruption_errs 1 [/dev/mapper/md1].generation_errs 0 I'm currently running a BTRFS scrub on disk 1 to see if I will learn what file has issues. I can restore from a backup if necessary. I'm not sure if scrubbing will give me this information. This experience has me questioning my choice to use BTRFS. Advice would be greatly appreciated. Thanks. ur1-diagnostics-20211122-0833.zip

I have a g10+. I'm currently reducing size of my media collection to attempt to consolidate onto 2 data disks with 1 parity disks. This will leave 1 of the 4 drive bays open for an SSD cache. My PCIe slot will be occupied by an Nvidia P400 GPU for plex and tdarr. I love the small form factor and build quality of the g10+ even though it limits drive expansion. With 16TB and 18TB drives out now, this is less of an issue.

This wouldn't be an issue for me. I may give this a go.

If this were used only for docker, would it be a concern? I have an HPE gen 10 plus with only 4 storage bays and the single PCIe slot will be populated with my GPU for HW transcoding. Therefore, no additional drive slots other than to use USB. Luckily it has two gen 3.2 slots on the front. I would just use a single USB SSD for docker on an unassigned device and backup weekly to the array. People use these as OS boot drives, so I'm thinking it would be okay. Thoughts?

Thanks. I actually got it worked by moving my docker containers to a separate VLAN. I have unifi network gear so this was pretty easy.

Unfortunately not.

I've got an hpe gen10+. It has 4 drive bays and 1 PCIe slot. The PCIe is populated with a GPU for hw transcoding. I am current using the server mainly as a docker/VM host with bulk media storage on a Synology. Eyeing some 16tb exos drives and considering buying 4 for the server but then I lose drive bays for my Unraid cache and VM/docker storage. The server has two usb 3.2 gen 2 ports. Would I be nuts to consider buying two external gen 2 usb SSDs to run my cache pool? Looks like near nvme speeds can be had with these but don't know about reliability

Power is definitely not cheap in Canada, but the Xeon is still pretty low power compared to the dual Xeon rackmount servers I used to run.

I'm using one with Unraid. Working nicely. I wish it had onboard nvme but otherwise it's great.

I've been trying to run most services on Unraid for ease of backup and to centralize everything. The ones that are causing me some grief are AdGuardHome for DNS and WireGuard for VPN. I love the WireGuard plugin for Unraid and it is my preference to run this. If I run AdGuardHome on a Rpi4, everythings works great, but then I need to keep the Pi4 running and maintained (not that big a deal really). If I spin up an AdGuardHome docker container, I need to run with a custom IP on br0 so that it can have free access to DNS type ports. When using a custom IP, WireGuard peers cannot access it. I've seen some complicated posts about setting up static routes on my router, or running docker containers in a VLAN. I can do this since I have a Unifi setup but the instructions aren't working for me. The other option is to run AdGuard in a VM on the unraid server. What is everyone's thought on this?

By chance do you use a xeon with quicksync with this board and have you tried plex hw transcoding. Not sure how that would work with a board that also has an ipmi gpu.

I'm assuming the ones grouped together are the x16 slot and adjacent? All others are isolated?

Did you dig further into this with the X9 board? Curious to know the result.

FCP doesn't flag this as an unclean shutdown and I have not set it to ignore that warning. On occasion would be one thing, but this is happening on every reboot. Wish there was something I could do.

Oops, here they are after a reboot. unraid-diagnostics-20180829-0925.zip syslog.zip

Ok, turned on troubleshooting mode, then stopped and started array. Here's a new diagnostic file and the syslog txt file. FCPsyslog_tail.txt unraid-diagnostics-20180829-0910.zip

I recently swapped my setup to new hardware. Now, everytime I stop the array I see a message at the bottom "Stopped. Unclean shutdown detected." A parity check runs after starting the array. I'm not sure what the problem is. Any suggestions? Diagnostics attached. unraid-diagnostics-20180829-0844.zip

Is the CUPS docker container still being updated?

You're welcome. And yes thanks for confirming it's working and thanks to gmk2. Guess I'm a little late to the party. Just noticed that X9 support was added. Nice, thanks! Can you confirm that it offers the same granularity to speed control as the AsRock boards? My X9 fan speed settings through IPMI only allow 3 settings. I'm hopeful I can have tight control of the speeds. Thanks!

My pihole docker is causing similar issues. Looks like I will move to a debian VM for this.

I have this board and after running 'configure', my board.json looks like this: { "ASRock": { "raw": "00 3a 01", "auto": "00 00 00 00 00 00", "full": "01 64 64 64 64 64", "fans": { "CPU_FAN1_1": "01", "REAR_FAN1": "01", "FRNT_FAN1": "01", "FRNT_FAN2": "01", "FRNT_FAN3": "01" } }, "ASRock1": { "raw": "00 3a 11", "auto": "00 00 00 00", "full": "01 64 64 64", "fans": { "FRNT_FAN2": "11" } } } Two of my fans are missing from the above config: CPU_FAN2_1 and REAR_FAN2. These fans do not respond in the GUI to any adjustments either, but the ones included above are fine. Any idea how I can get them all working?

Turns out it was actually a problem with the mariadb container. I think the database got corrupted with an unclean shutdown of the container. Restored from backup and all is well again including upgrade to v13.0 withing GUI.

Any luck finding a solution? I've got the HTTP 500 error as well.