FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 08-21-2008, 03:09 PM
Christopher Mocock
 
Default Anaconda (or libata?) device detection order

Hi,

I've been creating a custom spin with revisor and it's going very well,
except for one fairly major problem...

It seems that when booting an installed system, /dev/sda corresponds to
a PATA device, but during installation (via anaconda), /dev/sda
corresponds to a SATA device.

To clarify... when anaconda runs I would like it to install to the
primary master PATA drive if present. Strangely (or strange to me
anyway), it seems that SATA devices get detected first. I thought that
PATA devices would be detected first, so that in my kickstart file I
could specify my desired partitioning to be on disk /dev/sda.

When there are only PATA devices installed this works fine, it goes on
the primary master. However if SATA devices are present as well as PATA,
it installs to the first SATA device.

If I set grub.conf of the installed system to boot from /dev/sda, it
tries to boot from the PATA disk rather than the SATA disk to which it
installed. I can get around this by pointing grub.conf to the UUID of
the disk to which it installed. However, I'm surprised that /dev/sda
seems to be a SATA disk during installation, and a PATA disk during boot.

Any thoughts as to why this might be? What decides the device detection
order? Is it libata or something else?

Thanks,

--
Chris

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 08-21-2008, 04:06 PM
Alan Cox
 
Default Anaconda (or libata?) device detection order

> installed. I can get around this by pointing grub.conf to the UUID of
> the disk to which it installed. However, I'm surprised that /dev/sda
> seems to be a SATA disk during installation, and a PATA disk during boot.
>
> Any thoughts as to why this might be? What decides the device detection
> order? Is it libata or something else?

Module load order. That would imply that your different setups are
loading drivers in a different order which is moving the devices around.

It ought not to matter to grub because grub uses the BIOS interfaces and
the first hard disk the BIOS finds is what defines that interface - at
least as far as finishing loadind grub and hunting for kernels .

Alan

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 09:50 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org