ConnerVT

Looks as the filesystem is corrupted on my NVMe cache pool drive. Formatted as btfs, and contains my system share (docker and libvrt images). Was finally able to get the array to stop (wouldn't unmount the cache drive, so needed to "umount -l /dev/loop2"). Restarted the array in Maintenance mode, and ran Check Filesystem Status (--readonly). Results below, as well as a diagnostic run after that. Short SMART test also run, no issues there). What is my next step in getting this server back up and running? TAI [1/8] checking log skipped (none written) [2/8] checking root items [3/8] checking extents ref mismatch on [183065169920 8192] extent item 1, found 0 data extent[183065169920, 8192] bytenr mimsmatch, extent item bytenr 183065169920 file item bytenr 0 data extent[183065169920, 8192] referencer count mismatch (root 5 owner 20159943 offset 2510848) wanted 1 have 0 backpointer mismatch on [183065169920 8192] owner ref check failed [183065169920 8192] ERROR: invalid generation for extent 183065362432, have 288230376153960935 expect (0, 2249226] ref mismatch on [183065362432 147456] extent item 1, found 2 data extent[183065362432, 147456] bytenr mimsmatch, extent item bytenr 183065362432 file item bytenr 183065432064 data extent[183065362432, 147456] size mimsmatch, extent item size 147456 file item size 8192 data extent[183065362432, 147456] referencer count mismatch (root 5 owner 20159943 offset 2510848) wanted 0 have 1 backpointer mismatch on [183065362432 147456] ref mismatch on [1194265329664 16384] extent item 144115188075855873, found 1 tree extent[1194265346048, 16384] root 5 has no backref item in extent tree tree extent[1194265346048, 16384] root 144115188075855877 has no tree block found incorrect global backref count on 1194265346048 found 2 wanted 1 backpointer mismatch on [1194265346048 16384] ERROR: errors found in extent allocation tree or chunk allocation [4/8] checking free space tree We have a space info key for a block group that doesn't exist [5/8] checking fs roots ERROR: unexpected condition, probably corruption: node refs 1 <= 1 check/main.c:2063: walk_up_tree: BUG_ON `ret` triggered, value -117 /sbin/btrfs() [0x492fe9] /sbin/btrfs() [0x49dc73] /sbin/btrfs(main+0x92) [0x411ee2] /lib64/libc.so.6(+0x2ad14) [0x15060f8c0d14] /lib64/libc.so.6(__libc_start_main+0x86) [0x15060f8c0dc6] /sbin/btrfs(_start+0x21) [0x4136e1] malta-tower-diagnostics-20251122-0931.zip

It may be. From what I understand, Nvidia cards typically boot in a high power state, and only drop to low power (p8) after they have been used for the first time. You don't currently have the card tasked to do anything, so this likely is why you see this. Try entering this in a terminal window: nvidia-persistenced This allows the GPU to go to low power when not in use. I have it in a small script file, set to run At Start of Array (via User Scripts)

Plus is 12 devices. Pro is unlimited.

Currently Cloudflare has a major outage. Many sites returning an Error 500: Internal server error Cloudflare System Status

Nope - MN10ADA10TS is CMR https://toshiba.semicon-storage.com/content/dam/toshiba-ss-v3/master/en/storage/product/internal-specialty/HDD-NSENC.pdf

When you have an unclean shutdown - as in the array did not complete it's shut down process before the server powered off. You should open a new thread in General Support if you need help diagnosing and resolving your issue. But this thread is a good place to start reading.

Oops - My bad. I meant the OTHER main tab. The one my server initally loads, called DASHBOARD. 😄 Sorry about that.

Clear the error by clicking on the fail icon on the Main Tab. Monitor, if you get more errors, post details and diagnostics.

Do you mean "CRC" count? If so, this is almost always a cabling issue. Check/replace the SATA cable, and monitor for increasing error count (as CRC error count does not reset to zero).

Well, it's only data. He probably didn't really need it anyway. 😜

Looks as all of your troubleshooting tired the kids out. 😀

I do something similar. I have an external USB drive attached to my server, which via a script that runs once a week, I rsync the folder which contains backups of several Windows machines in the house, my appdata backup folder (which has my Unraid flash drive backups), as well as a few other miscellaneous things. I actually have two of these drives, and I rotate them out every few months, keeping one offsite. Having the data on a drive I can grab and move to another machine is very convenient if any data recovery is needed.

Well, I took the plunge. Fortunately after being greeted by this screen, things seem to be working nominally after a power down restart and cancelling the parity check.

Other things to check: Inspect DRAM sockets on motherboard, connections are not bent or dirty/full of dust, DRAM snaps firmly into sockets. Remove CPU, clean/inspect socket and CPU connections. A poor connection between the CPU and DRAM module can result in what you are seeing.

Updated the 2nd server to 7.2.0. So far, so good. But it really doesn't do much, so I didn't expect issues. I'm feeling pretty good about this update. Enough that I will likely take the plunge and bring the main server up to date from 6.12.10 to 7.2.0. I have time the next day or two, so we will see how it goes. Those who know, I'm hesitant to update unless I have a compelling reason to do so. 7.2.0 looks like a stable point to take the plunge.

Perhaps he meant this?

Some hard drives conform to a newer SATA specification, where the drive is disabled when 3.3V are applied to Pin 3. There are several solutions if this is your issue: Tape over the pin, use a Molex to SATA power adapter (has only 12V and 5V), or purchase special data/power cables, or use a different drive. It all depends if this is your issue, the hardware involved, and your comfort level. https://www.instructables.com/How-to-Fix-the-33V-Pin-Issue-in-White-Label-Disks-/

I am glad to say, after several months of being basically unusable, the Lidarr team seems to finally have resolved their database issues and it is now possible to search/add new artists. I just spent the past 20 minutes adding music I've been wishing for. You do not need to use the lidarr:xxxxxxxx Musicbrainz format - a text search now works. A couple things to note: The Lidarr devs state that their server is still getting hit hard (by all of the users finally able to use it) so you may still get an error at times - Try again a little later (I did not have any issue this morning). I tried this a few days ago, and was still having issues. I updated my Lidarr container last night, and now all looks good. I recommend updating to the latest as well. Good luck, happy hunting.

I have run several AMD CPUs with Unraid for the past 5 years. Starting with my main server in 2020, it started with a 1500X, then 2600 and now a 5700G. Build a second server with a 5600GT for mostly backup duty but also runs Frigate. My experience with AMD processors has been issue free, except for intermittent system freezes when I first built my initial server on 2020, This was with the first generation 1500X. This was resolved with the BIOS setting typical current idle, which I now make sure I set on any Ryzen build. The issue this addresses generally only affects 1st gen Ryzen (and possibly some 2nd gen) but there is little reason not to use this setting, unless you in a "how low power can you go" contest. The Ryzen memory controller (Infinity Fabric) can be a little finicky. I use G.Skill Ripjaws V (F4-3200C16D-32GVK) in my builds. Don't get caught up in the industry's XMP marketing - run at the memory's JEDEC setting that corresponds with the tables in the Ryzen FAQ. If in doubt if your DRAM is Single or Dual Bank, choose the Dual setting. Unless you perform frequent CPU computational tasks, you won't notice the speed difference.

i-226-V works fine. Unraid has driver already in base installation. From my desktop (Realtek on MB, a little flaky) to my server (i226 on MB):

How mission critical is your server? What would be the impact if an issue came up and it took you time to troubleshoot and resolve? Do you have the time available to do it? Do you have the skills to do it? If you have answers for the above which make you feel good, then update. But then, 7.2.0-beta3 is the latest/greatest out there. I would at lease wait until a true 7.2.0 is available, then watch this forum for a few weeks to see what issues people may be having. There are always issues, so I generally focus on things which will impact my setup. If you note my siggy, I too am running 6.12.10 on my primary server. I've been waiting to upgrade this one since 7.0.0 first came out.

Correct me if I'm wrong, but I believe the OP has removed his Nextcloud docker, and MariaDB was installed during his setup of Nextcloud. So unless he is sharing MariaDB with another docker application on his server, neither the MariaDB container nor its appdata is needed.

Just a quick heads up for those who reset their password - After resetting my password and getting my server up and running, found my son could no longer connect as a guest user (he has Library access and has been using my server for several years). We tried a bunch of troubleshooting fixes, and found out if you are using an older release of Plex Server that Plex is blocking remote users (server owner can still connect). Solution is to update to the latest server version - 1.42.1 Source: Plex Media Server - Security Update - Announcements - Plex Forum

Just a quick heads up for those who reset their password - After resetting my password and getting my server up and running, found my son could no longer connect as a guest user (he has Library access and has been using my server for several years). We tried a bunch of troubleshooting fixes, and found out if you are using an older release of Plex Server that Plex is blocking remote users (server owner can still connect). Solution is to update to the latest server version - 1.42.1 Source: Plex Media Server - Security Update - Announcements - Plex Forum