Bug 148240 - mdadm fails with segmentation error at boot time
Summary: mdadm fails with segmentation error at boot time
Status: RESOLVED DUPLICATE of bug 146514
: 149640 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 3
Hardware: 32bit Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Marian Jancar
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-04 18:31 UTC by Ales Jagodnik
Modified: 2006-02-10 16:05 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ales Jagodnik 2006-02-04 18:31:10 UTC
mdadm fail with segmentation error when started "mdadm --assemble --scan", like in suse 10.1 default initrd image. Installation of additional CDs is not possible, as well as normal booting.

SOLUTION:
stable version of mdadm (in distribution or available as additional download)

WORKAROUND:
- after cd1 install boot rescue mode
- manualy assemble raid (ex. "mknod /dev/md0 b 9 0" etc., "mdadm -A /dev/md0 /dev/hda1 /dev/hdb1")
- mount / partition ("mount /dev/md0 /mnt")
- modify initrd ("mkdir /mnt/root/init", "cp /mnt/boot/initrd /mnt/root/init", "gunzip initrd", "cpio -i initrd", "rm /mnt/root/initrd", "vi init", find all lines that call mdadm with --scan option and comment them, add your custom raid assembly commands like "mdadm -A /dev/md0 /dev/hda1 /dev/hdb1" etc.)
- make new initrd ("cd /mnt/root/init", "find . | cpio -co | gzip > /mnt/boot/initrd_new")
- remove /boot/initrd link and replace it with a new one ("cd /boot", "rm initrd", "ln -s initr_new initrd")

That should do the trick to finish the installation.
Comment 1 Marian Jancar 2006-02-06 12:34:55 UTC

*** This bug has been marked as a duplicate of 146514 ***
Comment 2 Marian Jancar 2006-02-10 16:05:03 UTC
*** Bug 149640 has been marked as a duplicate of this bug. ***