I agree in general... But: 1. In his configuration (in this case), the same hardware are used, therefore the type of each hardware remains fixed, and since we're talking about 2 drives connected to the same (I presume) built-in Channel 1 EIDE Master/Slave, we don't have to deal with the drive shifting issue and thus the order of appearance between different hardware interface is irrelevant. 2. We're not talking about SCSI here. 3. Hardware are recognized in particular order, based on whether they are internal (built-in) or add-on (via buses such as SCSI, PCI, PCI-X, PCIe, etc.), and whether the built-in feature(s) is enabled or not. 4. The order of loading by the POST is typically internal first, then external. So the order of appearance of drives is dependent on which driver is loaded first, which is also dependent upon the bus position. The loading order is dependent upon whether that feature's state (enabled or disabled). 5. Typically if internal IDE/EIDE is enabled, along with SCSI, and SATA, IDE drive(s) is recognized first, then SCSI, then SATA (BIOS implementation specific). When this happens, one must take the appropriate steps to modify each boot loader, one at a time, sequentially, to rectify the shifted hardware position. For this case, the proper OS installation process is XP first, then Fedora. Therefore, the Fedora boot loader is the first one to be loaded, followed by the XP boot loader. 6. Once an OS is loaded, its configuration is already implicitly based on the order of appearance of the hardware as recognized during the POST and is effective at time that OS is loaded. These hardware-specific info is recorded in the appropriate configuration files for each OS for that OS' boot loader to use. Many people do not fully understand this point and can mess up running system badly by introducing new hardware that have the potential of changing hardware order for a multi-OS, multi boot systems. 7. SCSI and FC are not susceptible to this problem (if handled correctly). 8. And yes, to perform the complete analysis, one would need to know all the hardware connected to the motherboard, all the hardware connected to the expansion cards (SCSI, FC, EIDE, SATA, PATA, etc.), the state (enabled or disabled) of each one, along with the specific settings for each controller. This is way outside the scope of this email forum. Regards, -----Original Message----- From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On Behalf Of Georges Giralt Sent: Wednesday, December 19, 2007 10:44 AM To: LVM general discussion and development Subject: RE: won't dual boot: 2 disks and LVM Selon pham_cuong@emc.com: > Instead of discussing back and forth w/o real data to discuss/explore with > concrete evidences, could you: > > A. Post the content of both the grub.conf and boot.ini files ...........Heavilly snipped................. Hi Pham ! I think this is not totally sufficient. You have to check the BIOS to see how and in what order it sees the disks. Some Bioses have a strange behavior especially when you have a SCSI card or USB disks. On my Mobo, if I plug a Sata drive, the first master IDE came in third position, right after the sata disk and the SCSI DVDrom which is still lugged on. Do not ask me why it sees this as a disk (and even if there is nothing into it). So I admire the Grub people as they've made a terrific job ;-) -- _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
