Drive identification problem SOLVED!

[T J Tulley]

I installed a second "Felicia2" in hd2, at partitions it identifies as sdc11 & sdc12 on Sunday and set it up as I like it. Recovered from hibernation yesterday but today -> BusyBox!

Tried Recovery mode, boot log on screen says sdc11 not found. Higher up, it has scanned drives and found what it calls sdd with partitions 1, 2, (5, 6, 7, 8, 9, 10, 11, 12) - That is clearly hd2.

So I have booted into "Felicia1" in hd0, at partitions it sees as sdb2 & sdb4. (No extended partition). [Swap partitions ignored in this report].

Felicia1 in hd0 has /boot/grub/device.map showing sdb,c,d; Felicia2 in hd2 has /boot/grub/device map showing sda,b,c. There is no sdd here.

So why did the bootloader working from grub in Felicia2 see hd2 as sdd?

This question links with erratic behaviour of installer: sometimes it sets /boot/grub/device.map with my 3 hd's identified as sda, sdb, sdc; sometimes as sdb, sdc, and sdd.

[Husse]

I'm not quite sure but I think it has to do with the problems described here
http://www.linuxmint.com/wiki/index.php ... annot_boot

[T J Tulley]

Thanks a lot Husse - that certainly looks like the explanation.

There's a lot to puzzle out - I always boot from hd0 (IDE) but I've had trouble even with Elyssa or Felicia installed also on hd0; hd2 is SATA so there may be an issue about disk order - can't think about that at this time of night!

A complication about UUIDs is that 3 of my partitions are ntfs disk copies with identical UUIDs - however these are never Linux partitions, but I can't use UUIDs to mount them. They have Labels.