Rn104, X-RAID, Esata enclsure and 1014019997 error
Hello,
I thought it might save someone a few (or more) minutes of head scratching...
RN104, 2bay esata expansion attached with 2x2TB drives as one JBOD volume. When I tried to create an X-Raid volume on main device I got error 1014019997 - Cannot change volume mode to X-RAID. Doesn’t matter – one, two or three drives.
After some experiments (time consuming a bit) I'm guessing that volume existing on esata expansion is treated equally to volume created on main device – and that will / is obviously preventing creation of XRaid volume on ‘remaining’ disks. Anyway – it would be all acceptable but…. having flex Raid 5 on three drives and adding one more drive as parity (that is the only option available) Raid is switching from 5 to 6. In my case that is not wanted behaviour…. So I have to wait until fourth 4TB drive arrives and then rebuild entire volume as Raid 5 on 4 drives….
Re: Rn104, X-RAID, Esata enclsure and 1014019997 error
The option to add a disk as parity must be selected in the UI before adding a disk to a RAID-5 array to convert the array to RAID-6. Otherwise the disk will be added to the RAID-5 array leaving it at that RAID level.
Re: Rn104, X-RAID, Esata enclsure and 1014019997 error
I tested that once again on VirtualBox instance, but got inconsistent results. VirtualBox version of ReadOS seems to not reading correctly virtual hard drive size - RAID5 array of three 8GB disks gave me a volume with 35MB of data and 6.28GB of free space....
Anyway - my main point was actually about this specific error when esata enclosure is attached as I couldn’t find this documented anywhere.
And my 4th drive should be delivered today so I will create 4 drives array in one go on real RN104
