Red Hat Bugzilla – Bug 473244
Mirroring does not work after installation.
Last modified: 2008-12-03 09:11:12 EST
Created attachment 324859 [details]
Mirroring on RAID1 in RH 5.3 Snap 3 don't work after installation and PC restart.
Steps to reproduce:
1. Create RAID1 in OROM. Use default settings.
2. Boot RH from DVD
3. Choose New Installation. Use default settings on all pages.
4. On Suggested Partitioning page use configured RAID for installation.
5. Instalation finish with successfull result (booting and os is working fine)
5. Turn off PC and disconnect second hdd from RAID1 (only first hdd left).
6. Start PC again - OS is starting from only one hdd.
7. Turn off PC and connect second hdd (disconnected 2 steps before) and disconnect first hdd from RAID1 (only second hdd left).
8. Start PC again - OS will start but from strange state- eppears installator which wants to finish installation
OS correctly started (loaded) from both hdd.
OS is starting normally only from one hdd but from next installer wants to finish installation.
It is look like mirroring works only during first stage of installation- after PC restart and finish installation mirroring not works- only one hdd is using to finish installation.
Logs in attachment.
-CRB: Intel DQ35JO
dmraid version: 1.0.0.rc13 (2007.09.17) debug
dmraid library version: 1.0.0.rc13 (2006.09.17)
device-mapper version: 4.11.5
Yes mirroring/raid1 on intel isw does not work in RHEL53 snapshot3, this is a known issue, which is being tracked in bug 471689. The problem is that the initrd fails to bring the raid set online, after which the system boots using just one disk of the set (so no mirroring).
Please do not misunderstand me when I say "this is a known issue", I do NOT mean by saying that, that we do not care about this. Intel ISW raid0 / raid1 not working in the current RHEL53 snapshots is an issue which we take very seriously.
And we've been working hard to fix this, as you can see from the discussion in bug 471689, we believe we've tracked the cause of this down. and we've prepared a fix which will be in snapshot5, which will be made available next Monday.
As I understand that this issue is very important to you, I've made the fixed mkinitrd packages available for you on my personal webspace here:
The updated nash one is the one you need, the others might be needed for inter package dependencies.
Using this unfortunately is less then trivial, so you might want to wait till snapshot5 becomes available. If not, you need to do a fresh install and then NOT boot the installed machine, booting will write to one of the 2 disks making the mirror go out of sync, without degrading the raid array, as the OS does not know its a raid array.
Then immediately after the install, start the installer again in rescue mode. Now copy the updated packages to the installed system, and chroot into the installed system.
When chroot-ed into the installed system update nash using rpm, and then do:
mount /proc /proc -t proc
mount /sys /sys -t sysfs
mkinitrd -f /boot/initrd-XXXXX.img XXXXX
Where XXXXX is the version of the exisiting initrd file. Then do:
Now the system should recognize the raid array as such and use both disks.
*** This bug has been marked as a duplicate of bug 471689 ***
Thank you for an in-depth reply.
We are waiting impatiently for Snapshot 5 to test installation on raid.