On 11/21/07, Andrea Righi <[EMAIL PROTECTED]> wrote: > In some distro the mdadm.conf file is not needed at all. You could try to > auto-generate it with "mdadm --detail --scan > /etc/mdadm/mdadm.conf". If this > resolves you can add this command in a post-install script to create the > configuration file at the end of the imaging process (just before the reboot > in > the installed image). See /var/lib/systemimager/scripts/post-install/README > for > details about post-install scripts.
Tried that, the issue is that upon first boot up fsck is trying to run but can't because /dev/sda7 is locked by another process (or in use), yes RAID. No other volume complains just the root volume, all other volumes come up with both disks cleanly (/proc/mdstat), just my root partition is coming up as though 1 disk was removed and I can't get beyond single user mode, since it feels it needs to fsck it. I've tried to force the raid configuration to believe the volume is clean, but no avail. Still workin it. BTW redhat Fedora core 6 (may not need the mdadm.conf file), but I continue to tweak to see what's happening Thanks tory ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
