k5di at zianet.com
Wed Feb 20 22:46:05 UTC 2008
Felipe Figueiredo wrote:
> On Wed 20 Feb 2008 18:16:33 Karl Larsen wrote:
>> Using 'fdisk' I find an impossible situation. I have this hard drive
> AFAICT there is no problem. Let's see...
>> that is /dev/hda and that is fine. In BIOS it is the first HD in the
>> list. Way down the list is the second HD which is a SATA drive and must
>> be plugged into the proper SATA header. For some reason 'fdisk' in this
>> Ubuntu calls this HD /dev/sda!
> SATA is handled by libata, which in turn uses scsi emulation, so it's
> recognized as a scsi disk. This has nothing to do with the BIOS or even
> fdisk, but with the kernel itself. Check dmesg and you'll see it.
>> I have mounted a partition from the SATA HD /dev/sda7 to this system
>> and copied the whole system to the SATA HD. But grub gets confused. It
>> can't seem to see the SATA HD. I can't get grub to boot the new Ubuntu
> Again, "nothing to see here, move along". You have to do the grub dance when
> you change the system to another HD.
> You have to find out (don't know how) which of the HDs is recognized by grub
> as hd0 and which one as hd1. Assuming it is hd1 (mutatis mutandis if not):
> sudo grub
> grub> root (hd1,6)
> grub> setup (hd1)
> grub> quit
> This will set grub in the second HD, and look for boot information in the 7th
> partition (for this, I'm also assuming you don't have a separate /boot
The problem I am seeing is that even if I turn off the IDE HD in
Bios grub can't do the right thing to the SATA drive. When I do root
(hd0,6) it says no Linux found. This means it can't find grub setup files.
Karl F. Larsen, AKA K5DI
PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7
More information about the ubuntu-users