gm6147

Sorry, inferred from this statement So is it the fact that they are part of a pool that is a problem? My single cache disk is on btrfs and that still mounts just fine after the update. Since my previous response, I found some other threads that explained how to restore the previous version since I did upgrade via the GUI. Did that and both btrfs drives re-mounted and working perfectly. I would like to continue to upgrade when possible but what is my best options for pools & btrfs then?

Woah woah woah wait... couple things. Are you saying that at some point UnRAID no longer supports btrfs as a file system?? I feel like there should have been much stronger announcements around this. Possibly even going so far as emailing those with licenses and contact info in their system just as a heads up. Granted, I don't go out of my way to find and read changelogs and just hit the upgrade button usually but still, that's huge! 1) Is there no way to roll-back the OS to a previous version where these drives would mount again? 2) If not, I believe I would prefer the second option; but would need some specific instruction on how to do this. I'm fine with pointing me to a previous thread so long as it is highly applicable to my situation and detailed enough.

To re-iterate my novice knowledge here, thank you for the detailed instructions! And good to know I'm not crazy. Thought those two drives running on btrfs had all my Plex media on them. And all is confirmed while giving my best attempt to browse the directories on the disk. I really just need that Photos folder recovered somehow as you can see it has been my pseudo-backup solution for photos for the last 8 years or so. Not ideal, I know... Read-Only Manual Mount Browse.txt

****@FBServer:~# btrfs check /dev/md1p1 Opening filesystem to check... Checking filesystem on /dev/md1p1 UUID: 2bcde74f-b59d-4324-a47f-b08c7d64403f [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) found 739187720192 bytes used, no error found total csum bytes: 719988480 total tree bytes: 845774848 total fs tree bytes: 9355264 total extent tree bytes: 8781824 btree space waste bytes: 100989142 file data blocks allocated: 750168219648 referenced 738341859328

Pretty sure, yeah. The Main tab in the GUI is still reporting that along with the unmountable error. I'm no expert in Linux or CLI but output and Main tab screenshot attached for your reference. command output.txt

6 drives total: two drives in one pool (xfs), two drives in another pool (btrfs), a cache disk and a parity disk. Everything has been running stable for months. Only recent major event was updating UnRAID. Issue may have existed before that but I did not notice, only noticed since doing the update and looking around afterward for new features and such. Unsure how to proceed. Diagnostic info attached to start. Really need to recover some of the files off either one of the drives, so reformatting or recreating the file system may not be an option since they were both part of a pool and both will not mount. fbserver-diagnostics-20230923-2242.zip

Where is this stored by default? Unless, by notifications set up, you mean have them sent to me via SNTP or something else. In which case, then no I did not have notifications set up. I would get the pop-up at log in about the array health check every day. But didn't have it sent anywhere special if that's what you mean.

Both solutions suggested from trurl and limetech on that thread rely on the flash media being accessible. To retrieve the config file. Mine is completely unusable at this time. Have gotten a quote for data recovery so I could simply get my config file back off the USB drive for anywhere between $700-3900 USD. This is not something I can reasonably afford to do.

I did have notifications set up. Where can I find this report? Created a new bootable media to get into web GUI again, has all my drives unassigned. Should I just start mounting unassigned devices and looking around? As a reminder, previous flash drive is 100% unusable at the moment.

Looking back through screenshots shared with friends showing off, it's not looking too good. Is that my only other chance?

Not sure exactly what happened but started getting the "kernel panic - not syncing VFS: unable to mount root fs" error earlier today. Searching that online, led me to believe the flash drive was corrupted or having issues, tried plugging it into a Windows machine hoping to pull the old config file off and re-write the rest of the bootable media and copy the config file back. But upon plugging it in, it just makes the Windows device plug-in sound non-stop and never comes up in file explorer. Almost seems like the flash drive is having some sort of electrical failure/shorting. I have never read anything about a best practice of "make sure you back up your flash drive/config file" until now that it is an issue. Am I completely screwed?