> I configured sda3 and sdb3 to a raid 1(mirror) with no problem.
>
> Now I want to change the configuration to raid0,
> so I edit the /etc/raidtab file,
> issue mkraid --force /dev/md0,
> everything seems fine, but when "raidstart" and check the status,
> the raid is still running in old raid1.
Once it is set up and working, linux raid it is very stable. In a "production
environment" , the type of re-configuration you are doing is not very common
and I agree that the raid tools don't handle every possible situation.
As for your problem, I think you could still use my suggestion. Boo
On Thu, 25 Nov 1999, Dong Hu wrote:
> Now I want to change the configuration to raid0,
> so I edit the /etc/raidtab file,
> issue mkraid --force /dev/md0,
I suppose you did stop the raid device ('raidstop /dev/md0') first? Then I
think you should use --really-force (this is not in the document
I am only using a partition of the disk (sda3, sdb3) for the raid,
so I don't want to reinstall everything. Any other way to wipe out
the persistent "superblocks"? I tried to "mke2fs" on the patition, which did
not work.
When I tested "raidsetfaulty, raidhotremove, raidhotadd" on raid1,
I also g
This (almost same) problem happened to me as well. It was solved with a
wipe of all information from the disk by using DOS fdisk to eliminate the
partitions and overwrite the MBR with fdisk /mbr . That worked and I was able
to create the new raid configurations.
Could it be that the "persiste
