November 2, 2025Nov 2 A few months back I saw my pool device (a single M.2 drive) was showing as "Unmountable: Unsupported or no file system". After researching as best I could, I figured my drive had simply given up the ghost. It didn't seem absurd since I'd bought the cheapest drive with decent enough reviews I could find and it seemed to have lasted ~2.5 years. I took the opportunity to upgrade and get some parity in my pool by grabbing a couple WD Black SN850X's.Fast forward to today and I notice our Plex was acting weird. I rebooted the Unraid server as one of my first troubleshooting steps and after a bit I noticed my installed-two-weeks-ago pool devices were showing as unmountable.Diagnostics attached, I'd appreciate any help or insight. I am not terribly experienced with servers or unix stuff beyond the basics of navigating and fiddling with files.Thanksollertonserver-diagnostics-20251101-1748.zip Edited November 2, 2025Nov 2 by weaselwoop
November 2, 2025Nov 2 Community Expert There's a log problem, type btrfs rescue zero-log /dev/nvme0n1p1 then post new diags after array start
November 2, 2025Nov 2 Author Entered btrfs rescue zero-log /dev/nvme0n1p1, stopped and then restarted my array, then pulled diagnostics. Interestingly my drives came back and appear to be working as expected again. I'd still appreciate any understanding into what might be going on and what I can do to prevent the issue. ollertonserver-diagnostics-20251102-0911.zip
November 3, 2025Nov 3 Community Expert Nov 2 08:10:15 OllertonServer kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0Nov 2 08:10:15 OllertonServer kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0Btrfs is detecting data corruption on both devices. It's a good idea to run memtest first, then scrub the pool and post the results from the GUI.
November 4, 2025Nov 4 Author Left memtest going for a couple hours. I'm guessing my RAM is toast, does this indicate anything else?
November 17, 2025Nov 17 Author Solution For posterity, it does appear the simple answer was bad RAM. My cache drives showed unmountable again sometime after the memtest. Swapped in some new RAM and things have been working fine.
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.