projectsunset

I'll try a power cycle next time instead of reboot or re-seat of the nvme. Unfortunately there's not a lot of selection of available boards that fit the bill for my 9th gen CPU build. Most recent BIOS update was released 4 years ago, so no luck there. I'm planning on building a new NAS later this year. I'll look into purchasing a different brand NVME for now that I can move into the new server once that's built. Thanks for you help Jorge.

Thanks for your help Jorge. Previous NVME was a Samsung 960 Pro 512GB. Current is 990 Pro 2TB. Some more info... Rebooted the server and checked the BIOS and the NVME drive was missing. Re-seated the NVME and booted up without issue. Short and long SMART self tests, no errors. Samsung_SSD_990_PRO_with_Heatsink_2TB-20250702-0932.txt Ran a scrub, no uncorrectable errors. UUID: 6fa168e8-ff47-4535-bd33-2e3897328848 Scrub started: Wed Jul 2 09:18:32 2025 Status: finished Duration: 0:03:06 Total to scrub: 179.68GiB Rate: 989.14MiB/s Error summary: verify=1964 csum=563248 Corrected: 565212 Uncorrectable: 0 Unverified: 0 Having encountered the same problem with two separate NVME drives, it seems unlikely that the issue is with the drives themselves. It also seems unlikely that the NVME wasn't seated properly as both times the server ran for months without issue before the NVME dropped offline.

Hello, This morning I received notifications from this BTRFS monitoring script from JorgeB that I had BRTFS errors on my cache drive. Main page shows the nvme device is offline. nas2-diagnostics-20250702-0815.zip This is my third time having this issue (previous threads here and here). Every time this happened, it was the NVME drive with the errors. After the last occurrence, I replaced the drive with a new Samsung 990 Pro. So I think it's unlikely a problem with the drive itself. What's the best course of action to figuring out why this keeps happening and how to fix it?

Thank you JorgeB, I appreciate you taking a look.

Thank for the reply JorgeB. Although I realize it's probably too late for these to be any use now that I've removed both of the cache drives I was using from my first post. nas2-diagnostics-20250224-1055.zip

I needed to get my server back up and running asap, so I removed both of the cache pool drives from my server, installed a fresh drive and set it as the cache drive, restored all the data from backups, and have re-setup my docker containers. I guess my question now is, what caused this and how do I prevent it from happening again?

This is a continuation from my previous thread This morning I woke up to notifications of BTRFS errors on my cache pool. I shutdown the server, removed the problem drive (A), rebooted, and everything started fine with the cache running on the other cache pool drive (B). After a bit of troubleshooting, I decided to re-seat the drive (A) and re-add it to the pool like I did last time I had this problem (in hindsight probably a mistake). I immediately saw a lot more BTRFS errors so I removed it from the cache pool again and rebooted. Now when I try to start the array using the good cache drive (B), I get a "Unmountable: wrong or no file system". Running a BRTFS check on the drive (B) shows many errors "parent transid verify failed on 1121019887616 wanted 565475 found 564570". Have I screwed up my cache? syslog-errors.txt btrfs-check.txt

Thanks Jorge. I've re-added the drive to the cache pool and everything is looking good so far. I'll mark this as solved and keep a closer eye on the logs to see if the problem resurfaces. Thank you so much for your help, I really appreciate it!

Thank you Jorge. I've added that to the "Unraid OS" Syslinux Config and rebooted my server. I've also added your monitor a btrfs or zfs pool for errors script to my User Scripts to run hourly. Since the cache has been running from a single drive for the past 17+ hours, should I wipe the nvme0n1p1 drive before re-adding back into the cache pool? Or is it safe to add back as is? Thank you so much for the help!

So I've got the array and docker back online by removing the nvme0n1 drive from the raid1 cache. I still don't have any idea how to diagnose what's wrong with the drive and if it's corrupted or failing? Should I format it and re-add it to the cache? I'm nervous to re-add it without knowing what the problem is.

Hello, I've been running Unraid for a few months and have had no issues. This morning, I received an error from Unraid /var/log is getting full (currently 82 % used) When I took a look at the log files, I saw syslog was very large. Viewing the syslog shows lots of BTRFS errors such as these... Nov 7 11:36:06 NAS2 kernel: BTRFS warning (device nvme0n1p1): lost page write due to IO error on /dev/nvme0n1p1 (-5) Nov 7 11:36:06 NAS2 kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 27450484, rd 49269, flush 322751, corrupt 0, gen 0 Nov 7 11:36:06 NAS2 kernel: BTRFS error (device nvme0n1p1): error writing primary super block to device 1 After rebooting the server, the array didn't start because it said the nvme0n1p1 was missing. Cache pool BTRFS missing device(s) I unplugged the server, re-seated the SSD, rebooted, and the drive appeared again. I ran short and extended SMART self tests which completed without errors. But Docker will no longer start because cache is in read only mode? Unable to write to cache Unable to write to Docker Image Is my nvme0n1p1 drive failing or corrupted? I'm a bit lost on where to go and any help would be greatly appreciated. Thank you! nas2-diagnostics-20241107-1135.zip Samsung_SSD_990_PRO_with_Heatsink_2TB-20241107-1205-SMART.txt

Damn, this sucks. After seeing the praise Unraid receives online, I've spent the last month researching and making a plan to move my home server to Unraid. Had I know they were moving to a subscription model, I wouldn't have even considered it. The very first words on the purchase page are "Buy Once, Use for Life. No subscription. No hidden fees." I guess I should be grateful to learn of this before actually pulling the trigger. Because if I had just purchased a license and they pulled this, I'd be pissed. I'll wait for official word first, but if they move to a subscription model, I'll move on.

FYI, a large amount of the links in the OP (every URL linking to wiki) are 404. Has the wiki moved to another location? I've looked in the Docs FAQ and Legacy FAQ, and don't see all the topics from OP.