I'm glad to see you recovered some of your data.
Your loss has nothing to do with the beta release however. I'm afraid that assigning a data disk as parity would clobber it in ANY raid system and any OS, regardless of version, beta or not.
Joe L.
I did know that. I just wanted to point it out before anyone else told me what a fool I am keeping important data on beta software. This one was all MY fault.
(My job is actually as an engineer working with SAN and disk systems. (So plase dont tell anybody of my blunder )).
Just a few more questions. Can I format the drive to get rid of all the faulty data?
I cannot find a way to format a formatted drive, other than first use it as a paritydisk for some seconds. Than it becomes unformatted.
But this does not feel like the right way to do it.
The disk has now 1.8TB of garbage.
Is the disk as good as "newly formatted" (But with data) when I have completed the reiserfsck after my mistake?
Should I just delete all the data and continue using the disk as it is?
If I remove the disk completely can I than move disk2 to slot1, Disk3 to slot2 and so on after doing a reset config?. (Avoiding the Parity disk of course)
Finaly, I can see that my disks dev name has different value:
sdb, sdc, sde, and finaly hdc. All are connected to the internal sata contoller. It has a total of 6 sata connections.
Is there any good reason for the "HDC" instead of sda to sdf.
When i set the function of the SATA controller to IDE instead of raid, I can only see the first four drives.
So I suspect it to be somting special with the last two connections and maybe that is the reason for the "hdc"?