By the process of elimination I'm humbly lead to suspect a problem somewhere between HW and BIOS; because the same problem occurs with SATAa and SATAb. (And because there is no POST beep with new mobo bundle of components in my pc.)...
I have installed Ubuntu 10.04 twice now on SATAa but it halts during boot with:
Gave up waiting for root device: Common Problems:
-Boot args (cat /proc/cmd line )
-Check root delay = (did the system wait long enough?)
(Yes I think it did)
- Check root= (did the system wait for the right device?)
(again BIOS seams set up ok)
- Missing Modules (cat /proc/modules; ls /dev)
These scroll of the pge.
ALERT! /dev/disk/by=uuid/45fba1ab-2864-4e2f-97a7-be780f8e355d does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:22.214.171.124-1ubuntu11) built in shell (ash)
Enter help for list of commands.
On advice, I've edited the Grub menu several times; See:
"I don't see a problem with your results. (Of a Boot script.) I'd like you to try to boot by editing the menuentry from the Grub2 prompt.
1. Remove the entire "search" line.
search --no-floppy --fs-uuid --set 45fba1ab-2864-4e2f-97a7-be780f8e355d
2. On the "linux" line, change the part "root=UUID=<long number>" to "root=/dev/sda1" with X being your Ubuntu drive and Y being your Ubuntu partition. Leave the rest of the line as is.
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=45fba1ab-2864-4e2f-97a7-be780f8e355d ro quiet splash
linux /boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 ro quiet splash
3. CTRL-x to boot."
I have also tried the edit:
linux /boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 ro single
But Ctrl_x doesnt lead to a sucessfull boot.
Now I find SATAb with a perfectly functioning os previously installed on another pc from the same live cd, halts on the same problem pge only with an Alert for a different UUID.
Doesn't that mean the problem is not with the SATAs?
Thanks for your interest.
My new mobo is GeForce6100PM-M2