UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed Ubuntu Edgy on a box with a single SATA hard disk and a single IDE DVD burner. Everything worked fine, the SATA disk showed up as /dev/sda and the IDE burner as /dev/hd?, where ? was a letter of the latin alphabet, I don't quite remember
Now I replaced the old DVD burner with two IDE drives (which definitely work, as I took them from another Ubuntu box), a CD burner and a DVD ROM drive, booted into Ubuntu and was happy to see that Ubuntu recognized the two drives as /dev/hd? respectively -- everything worked nicely out of the box, like I know my Ubuntu
Now the trouble starts: I partitioned and formatted my hard disk and installed a fresh Ubuntu Edgy. First strange thing I noticed was that during installation, the SATA drive showed up as /dev/sde instead of /dev/sda. When I boot the new Ubuntu, it hangs, the last kernel messages being
Code:
sd 4:0:0:0: Attached scsi removable disk sdb
sd 4:0:0:1: Attached scsi removable disk sdc
sd 4:0:0:2: Attached scsi removable disk sdd
sd 4:0:0:3: Attached scsi removable disk sde
UPDATE:
I had Ubuntu installed in text mode. I now tried the graphical live cd installer, which shows the disk correctly as /dev/sda! Here, however, I get the message "No root file system", although I definitely specified a root partition! I remember having had this problem with an Edgy install on another box, where it worked after senselessly change the partition order in the "Prepare mount points" installer dialog. This time it doesn't seem to work, though... help!?
You didn't specify what kind of mobo you have, and what kind of SATA controller you have. One thing you can try is, to load your modules manually when you boot from install CD. And in the Odd case try updating your BIOS, might help. It helped me. Now if you have an IDE hard drive around, just install it and install Ubuntu onto that, and see if your SATA gets recognized correctly after you log in. If it doesn't then try changing your BIOS settings.
Most BIOS allow you to set a boot sequence. For example try CD/DVD'd first then hard disk. Even a floppy could be in thye sequence if you had one. I still use IDE disks but would ask the question what is the hard drive sequence, IDE before SATA for example. Check your BIOS setup to see if IDE or SATA can be separately selected in the boot sequence. If you watch the lights on the drives that will tell you which disk is accessed first.
Thanks for your help! In the end, a little work-around did the trick: In the "Prepare mount points" dialog of the graphical installer, I went back one step to the partitioner and deleted and re-created the boot partition. After that, it was recognized as the root partition. This is a known bug, I guess they'll have it fixed soon. The graphical installation succeeded, yielding a correctly recognized /dev/sda and no booting problems.
Why the text mode installer cannot handle my SATA drive is a complete mystery to me -- shouldn't it behave exactly like the graphical installer...?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.