BTRFS RAID WILL NO LONGER MOUNT FILESYSTEM

Hello OMV Forum. I've been using OMV 4 for about 4 years now and it has been great. I have although come across an issue recently and can't find a solution. I've been researching a lot. My Raid 10 array has become unable to be Mounted and it gives a error code. If it's at all possible please help assist in restoring the ability to mount the filesystem. Thanks.

Here is the Error Code.

Error #0:

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-label/Raid10Storage' 2>&1' with exit code '32': mount: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error

In some cases useful info is found in syslog - try dmesg | tail or so. in /usr/share/php/openmediavault/system/process.inc:182

Stack trace:

#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(733): OMV\System\Process->execute()

#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(920): OMV\System\Filesystem\Filesystem->mount()

#2 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)

#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)

#6 {main}

Thank you for the reply. The raid state says clean. So the story is I was writing data to the array from a Windows share a last week and it suddenly stopped allowing me to write. So at the time I was still able to read my data, but the uploads failed. After that I decided to restart as a first step and apon boot up the filesystem would no longer mount. I've spent a while trying to figure out a solution. Some of my data I didn't have backed up, so I would really like to fix it or recover my data someway.

Well it was at a degraded state before this with one drive failing, but I put I different one in and rebuild the array. After that everything was working fine until this current situation happened. Any ideas?

Cool. I gave it a try and I unfortunately didn't have any success. I plan to keep working on it or I might try to use some data recovery software if all else fails. I plan to rebuild everything anyway as I just bought new drives. Those drives I have been using are very old which is what probably caused the problem in the first place. Thank you so much for your help here, but If you possibly have any other ideas definitely let me know. Maybe you possibly know of any docker installed data recovery software that can be used to scan the whole pool. That would be really cool.

Quote from ryecoaaron

Why are you using btrfs on top of mdadm? btrfs can do raid10 natively.

Hello ryecoaaron. So today I will be working on Installing OMV 5 and I bought some new Hard drives to get this back up and running. Some of those drives I was using were like 5 or 6 years old. So I had my server running very good for 2 and a half years without issues and haven't really been reading and up to date on the best setup processes. When I originally set it up I followed The Techno Dad Life's omv 4 youtube install video by setting up raid through the gui and mounting the raid as a btrfs file system. I realize now that that is not the best way to setup a btrfs raid of course. I definitely should have been using snapshots. So do you possibly have a suggestion of a command line guide to setup a btrfs Raid 10 and use the great features of the btrfs filesystem? Btrfs is definitely the filesystem I would like to use. Thanks in advance.

Cool. Thanks for the reply. I will definitely look into it. I also came across this video on youtube