Hi, all
Found this old thread while trying to solve own hda/sda problem.
I have installed SL5 on "hda" drive (and it was actually an IDE drive).
Now I took the content of the root partition and cloned it to a second
machine. This second machine also has an IDE drive, but a different
brand, which is recognized as sdb (sda is bootable usb stick), not
hda.
Ok, so after I boot the second machine from the stick, partition the
hard drive and close the image, I do chroot into the cloned partition
and install mbr with grub shell. At the same time I notice that in
chroot'ed env I have "/" mounted on /dev/hda, as reported by "df".
While fdisk -l would still report /dev/sdb.
This is what I don't understand - where in the system it remembers
that it was on /dev/hda before? I have only labels in /etc/fstab and
grub.conf.
Now, when I boot from the hard drive of the second mchine, is starts
ok, loading the splash screen and boot image, but later it wont find
the root partition and kernel panic in the process of boot. I suspect
it's related to this fact that system remembers /dev/hda drive it was
originally installed
Any words of wisdom from SL gurus?
If I clone to a machine whose HD is recognized as hda as in the case
or ogriginal installation, all goes well. Only when a new HD is sda,
it fails.
cheers
Artem.
On Mon, Oct 20, 2008 at 6:06 AM, Troy Dawson<[log in to unmask]> wrote:
> Hello,
> I still don't have any authoritative kernel links, but this is a good
> summary that I found
>
> "the IDE subsystem in the linux kernel has been functionally replaced by the
> PATA subsystem which uses just that naming convention (sdX instead of hdX).
> IDE is still included in the linux kernel, but is considered legacy.
> However, some distributions still default to IDE."
>
> I'm pretty sure that SL5 is going to continue to use hda instead of switch
> to everything being sda, but I bet that SL6 will be all sda.
>
> I know that Fedora 10 Beta uses the sda only, as does the beta of Ubuntu
> that is currently out.
>
> Troy
>
> John Summerfield wrote:
>>
>> Ken Teh wrote:
>>>
>>> I'm getting confused with the sda/hda naming conventions. I thought all
>>> SATA disks were sd devices. They were a while back but apparently, not
>>> anymore. And, I can't seem to make any sense of when an sda is an hda.
>>> I'm currently installing a system with a SATA system disk that has a IDE
>>> CDROM. A systemrescuecd (Gentoo based kernel) identifies the disk as an
>>> sda. But the 5.2 installer says it's an hda. There's a single IDE
>>> connector on the MB on which hangs a CDROM drive. Apparently, it's not
>>> an
>>> hda. What is it? An sda?
>>>
>>> What gives?
>>>
>>
>> The real answer is, "It depends."
>>
>> It depends on which driver is used.
>>
>> I have an all SATA system. By default, on SL5 the first drive is hda.
>> However, as I recall performance sucked so someone here suggested I tell
>> the kernel "hda=noprobe." With this argument, the drive appears as sda.
>>
>> On a similar system running Fedora, the first drive is normally sda, and
>> I don't know whether I can make it appear as hda without rebuilding the
>> kernel.
>>
>> I note that the new naming convention is causing problems with somewhat
>> randomised naming of drives, particularly when installing with Anaconda.
>>
>
>
> --
> __________________________________________________
> Troy Dawson [log in to unmask] (630)840-6468
> Fermilab ComputingDivision/LCSI/CSI DSS Group
> __________________________________________________
>
|
