Art Fore wrote:
> On Sun, 2007-09-16 at 16:39 +0800, Art Fore wrote:
>   
>> When I install 10.3 Beta3, it does not recognize the raid drive setup
>> from the previous beta2 install, same with beta2, it did not recognize
>> the beta1 install on raid. I have to go through and create the raid1
>> drives each time. Is there any secret to get these permanent? It does
>> recognize a backup raid and wants to install on it.
>>
>> Art
>>
>>     
> Well, this went from bad to worse. On initial reboot when it is
> installing the boot loader, it cannot find md3 which is where it just
> installed everything. Raid is as follows.
>
> md0   raid1   /boot   101 MB
> md1   raid0   swap    1 GB
> md3   raid1   /       20 GB
> md4   raid1   /home   267 GB
>
> When booting, it comes up it cannot find /dev/md3 for initrd
>
> Has procedures changed for installing on raid or is this a bug.
>   
Let me ask:   Does your system have any mixture of IDE or IDE and SATA
drives on it?   The reason I ask is that as of 10.3 (generally kernels
above 2.6.18-20 (not sure exactly which one)) IDE devices were renamed
to SDxx from their historical HDxx designations.   This has caused a
bunch of installation/conversion bugs, one of which sounds just like
what you are describing.   Check out bug 304657 and others like it on
the buglist.  It is possible with some manual GRUB editing to get 10.3
entirely onto a MD raid including the boot loader but at the moment due
to the IDE/SATA rename bugs, it doesn't happen automatically.   (yet). 
I have a 4 array setup MD0=swap/Raid0 MD1=/boot Raid1,  MD2=/ (root)
Raid1, MD3=/home Raid5 1TB.   The MBR is part of the drive containing
MD1which starts at track 0.   You will need to edit the partitions but
DO NOT FORMATthem if you want to preserve the data (such as home) but
you will have to reset the FSTAB mount points which don't get preserved
due to the name change bug.   Eventually, it does work but the bugs make
it frustrating.
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to