Hello everyone,
I am a new OMV user, but I have a good experience with computers in general.
Until now, I was using an ASUSTOR AS1004 NAS containing a RAID 5 volume consisting of 4 6TB disks.
For performance and openness reasons, I migrated to a DIY NAS (Mobo N100).
My disks appear well, but which one(s) to mount?
And in what order if it matters?
Thanks for your help
The disks: (system disk is nvme0n1)
The candidate partitions to mount :
You need to install the md (multiple device) plugin to manage the raid.
Mount the md filesystems. Looks like you have at least 2
it seems to work, but fs are not mounted...
do i mount ?
do i need to do "recover" on each "md"?
Should I use LVM?
do i need to do "recover" on each "md"?
Why? The MD devices are in clean state.
Should I use LVM?
Why do you want to do that?
do i mount ?
If you want to access your data on this devices you need to mount the file systems on the MD devices.
Why? The MD devices are in clean state.
Ok
Why do you want to do that?
Because my asustor was using lvm, but it was just a question.
If you want to access your data on this devices you need to mount the file systems on the MD devices.
Ok and thx for helping, but do i mount all fs ? or just RAID 5 volume (md127) ?
What is md125 ?
And what are other ext2 fs ?
If you had created your array on OMV and not an ASUSTOR, you RAID device would show as as consisting of /dev/sda, /dev/sdb, /dev/sdc and /dev/sdd as it uses whole disks.
The AUSSTOR created something more complex using individual disk partitions rather than whole disks, this shows as three MD devices in OMV with partitions from the same disk appearing in more than one RAID.
While this may allow you to recover any data that existed on what was the ASUSTOR RAID, it does not fit with how OMV works if you needed to replace a disk or deal with other possible RAID failures in OMV.
Display More
If you had created your array on OMV and not an ASUSTOR, you RAID device would show as as consisting of /dev/sda, /dev/sdb, /dev/sdc and /dev/sdd as it uses whole disks.
The AUSSTOR created something more complex using individual disk partitions rather than whole disks, this shows as three MD devices in OMV with partitions from the same disk appearing in more than one RAID.
While this may allow you to recover any data that existed on what was the ASUSTOR RAID, it does not fit with how OMV works if you needed to replace a disk or deal with other possible RAID failures in OMV.
Ok, it's much clearer now, many thx.
If I follow you: if I want to fully use OMV and the RAID support it integrates, I have to save my data elsewhere, recreate a RAID volume with OMV and transfer my data to this new volume?
Yes, I think recreating the RAID vol in OMV is the better option.
Yes, I think recreating the RAID vol in OMV is the better option.
Ok, I will try to get more information about the other partitions (ext2) present on these disks.
Use this command at the CLI blkid and post the output here between "Code marks </>".
After a bit of digging it seems ASUSTOR creates a system partition (the first) and a swap partition (the last) on every disk so if you lose a disk you never lose the system. I'm guessing ASUSTOR creates a "data" partition across each disk for every RAID "volume" you then create. So possibly, you created two RAID volumes in ASUSTOR. The output of "blkid" will help sort that out.
After a bit of digging it seems ASUSTOR creates a system partition (the first) and a swap partition (the last) on every disk so if you lose a disk you never lose the system.
It seems similar to Synology, but Synology's disk format is more complex. I'm not sure if ASUSTOR is the same.
Finally, everything works fine. I still made a backup before 🤔.
The md plugin does the job and recognizes the raid volume by itself.
Lvm(2) is not useful indeed.
Disks appear:
md detect raid 5 volume:
Filesystem is mounted:
Share the FS:
md126 contains nothing (maybe a buffer partition due to disks size difference ?)
md125 seems to be a not valide FS and is not mountable
Other ext2 fs are unusable
Don’t have an account yet? Register yourself now and be a part of our community!
