Hard disk boot sequence problem
seth at integratedsolutions.org
Thu Mar 11 18:00:10 UTC 2004
> From: fedora-list-admin at redhat.com
> [mailto:fedora-list-admin at redhat.com] On Behalf Of Jeff Vian
> Sent: Wednesday, March 10, 2004 6:48 PM
> To: fedora-list at redhat.com
> Subject: Re: Hard disk boot sequence problem
> Seth Bardash wrote:
> >I am trying to build a disk duplicator. Boot disk is SCSI.
> Only want to
> >duplicate ide disks.
> >When FC1 is installed (or any redhat for that matter) on the
> SCSI boot
> >disk and I have another RH based bootdisk installed on the
> same system
> >- either on a 3ware card or on the motherboard IDE ports,
> FC1 finds the
> >other /boot partition and tries to decide between the boot
> disk and the
> >other disk that has an FC1 image on it. This confuses the
> system while
> >booting and causes it not to mount any /boot partition.
> This is likely a problem with using labels in the fstab for
> mounting. 2
> or more disks with the same label confuse the mount procedure.
> If you change those entries to use the /dev/<device> type entry
> should fix this confusion.
> >How can I stop the probing of ide disks at boot time but be
> >access them later? noprobe=idex causes the system to not probe
> >device and therefore not see the device after boot. Is there
> a way to
> >reprobe???? I have the motherboard set to only boot from
> SCSI but this
> >does not stop FC1 from probing all devices during boot up.
> >Any suggestions would be helpful.
> >Seth Bardash
Tried this - Does not work
System config: Opteron 146, 1G memory, Asus SK8N MB, 9G SCSI disk
on a 53c875 LSI card - /dev/sda: boot disk, /dev/hda - source disk
to copy , SIIG dual IDE PCI card for ide2 and ide3 (hde - hdh)
Promise TX2 for ide4 and ide5 (hdi - hdl).
Same thing occurs on a single and dual XP/MP machine with a
Same thing occurs even if the system is set to boot into single
user mode, the system still tries to mount multiple /boot
partitions and then gives up.
Was wondering if any of the system kernel init people out there
have any idea how kudzu or the rc.d/rc.xxx files go through and
sequence the disk init functions so I can change this to stop it.
I was going to try to build a kernel with ide drivers as modules
and then noprobe all the ide devices so I can modprobe them
later???? Has anyone else run into this problem?? Maybe if you set
up your machine to boot multiple versions of FC1 ? IE: FC1 i386 on
one disk and FC1 x86_64 on the second disk???
More information about the users