I am writing this topic because I made a big mistake.
I was previously with OMV, with a Raid 5 of 4 8TB disks in ext4, this one almost full.
I have now switched to TrueNas Scale and I wanted to transfer all my data to a RaidZ1 of 4 8TB disks in zfs.
But…
When creating the raid, I selected a hard disk from raid 5.
You can see on the screenshot, I put disk C instead of E.
Another curious thing, on this Raid created, disk i is unavailable.
There, I admit to being lost. What should I do to not lose my data?
Do I rebuild this Raid 5 with the new disk (sde) in it with OMV hoping to have no data loss?
Or is there a way to go back?
I hope in any case that there is a solution to get me out of this situation.
There’s not enough information to understand what you’ve done.
Transfer should be through the network, from one NAS to the other.
Have you put your OMV RAID5 array into TrueNAS?
And then selected one membre of this array to create a raidz1? (Raidz2 would be safer, by the way.)
The situation is not clear. Working on suppositions is only going to result in data loss.
It’s a DIY nas where I have my hard drives.
I installed TrueNas instead of OMV.
To put my data in ZFS I wanted to create a Raidz1 with 4 other hard drives (e, f, h, i) to then transfer Raid 5 (a, b, c, d) to Raidz1.
But I put disk C instead of disk I.
Here is what it gives me on the currently created Raidz1 (c, f, h, i)
You’ll need OMV to do the transfer.
Worse of all, drive letters can change across reboots so there’s no guarantee that sde:sdi were the four new drives. I hope you had them referenced by serial number.
I would put back the OMV boot drive (you installed TrueNAS on a new drive, right? not over OMV…), assess the damage and repair the RAID5 array if necessary.
The unavailable drive suggests a flaky connector or power supply, so a check of the hardware is advised.
Then we’ll try to set up a better strategy to move to TrueNAS.
I hope you had them referenced by serial number.