Ubuntu 8.04 (64 bit original disk) will not boot after changing to sata drive

Machine also has 2 GB 667mhz memory (on 1 stick).

I'm now running Intrepid 64 from a SATA II disk in AHCI configuration and Ubuntu never failed. I think the solution to your problem is in the error the kernel prints during the hardware detection phase....
Could you copy here the message/s??

Hmmm, this looks vaguely familiar. Is it a "Raided" sata drive?
https://help.ubuntu.com/community/FakeRaidHowto
If so this link should help

Note that linux has had support for properly raided drives for ages but when Windows decided it sounded like a major revolutionary step forwards it didn't go for the full proper deal and made a sort of cludge of it. Linux sees these drives as 2 separate drives and ignores the bios mess that Windows tries to use to raid them with software. Hopefully the link there should help sort it out for the dual-boot.

Good luck and regards from
Tom :)

32 bit desktop Ubuntu tends to be the best version to use in most cases i think. My 64bit machine seems to prefer the 32bit version (which runs faster than it did under the old 32bit chip i used to have not so long ago)

Thanks for fast response guys.

The problem is resolved with Ubuntu 7.10 (32 bit) and dual booting into Windows is also working fine.

After giving some thought to the original error, I suspect that installing a 64 bit System onto a drive that has its first primary partion set as 32 bit NTFS may be the culprit in the first attempt.

I also suspect that the UltraDMA ribbon cable (80 wire) that connected the CD/DVD to IDE port may have caused the failure to install 7.10 (32 bit) on my next attempt. The dialog said there was a I/O copy error that is usually caused by an overheated harddrive or a dirty optical lens in the CD/DVD drive.

At this point I wasn't sure if the 500 GB Seagate had a heating problem so I removed the side panels and set a 15 inch box fan to blow directly into the case.

Well, after replacing the 16X CD/DVD with a 52X CD ROM drive and connecting it with a standard IDE ribbon cable (40 wire) the installation took less than 20 minutes!

By the way I'm now writing this message from Ubuntu 7.10 (32 bit) and things are much, much better :-)

PS: it's time to upgrade to 8.04 LTS...

Yes i was about to say that 7.10 is no longer supported, so your 'PS' was timely as it saved me from typing that out ;) heheheheh

8.04 does have the advantage of having LTS, particularly advantageous now we have 9.04 fast approaching making 8.10 out-of-date. However i still think that jumping straight to 8.10 might be better and more fun.

I have a bad feeling that the only way you might be able to upgrade to either 8.04 or 8.10 now, is via a downloaded Cd. Manual Partitioning - make sure each partition is UNticked in the column "Format Partition?". It's still be wise to make sure your data is safely on an separate partition or even better - backed up on external drive or dvd's.

At least you'll not need to worry about updating before upgrading :)

A 20minute install has got to beat Windows by a long way even without considering Office Apps and all else that makes Ubuntu usable right from the start without any extra expense or time installing programs ;) Don't start me off on one about updates either lol.

Good luck and regards from
Tom :)

It sounds like we could really use your help in here as another volunteer helping answer some of these questions! Even a little helps a lot as people sometimes search through "Solved" questions before posting their's. It's usually fairly easy to quickly search through for good ones you can answer with your expertise.

in any case thanks for getting back to us with your answer. It's bound to help someone later :)

Thanks and regards from
Tom :)

OK, I admit it, I was a little hasty about not being able to install 8.04( 64 bit) on a sata drive with 32 bit Windows XP already installed.

Turns out it was the blasted CD/DVD connected with the 80 wire UltraDMA cable that was the root of all my problems.

This morning about 8 a.m. said WTH and gave it another shot...and woulsn't you just know it, Hardy 64 bit just flew through the whole thing in exactly 28 minutes from boot up to reboot! It didn't flench and I got a boot menu with Window XP as "Other Operating Systems" to top it all off.

Man, it doesn't get any better than this...

PS: Sure, I'd like to help if I can, how do I get started? :)

Explore around the launchpad site and you'll soon start working it out. I tend to click on the colourful "Answers" 'tab' at the top and then hunt through for something that looks good and then post a comment in to try to help the person fix the problem. There's a guid to launchpad somewhere but i'm not sure where ;)

Good luck and happy hunting :)

Greetings,

I am having a very similar problem.
I have ubuntu running on a 40 G IDE drive.
When I try to install a 500G SATA it will not boot.

Can you clarify your solution?
What did you do ?
You stated
"Turns out it was the blasted CD/DVD connected with the 80 wire UltraDMA cable that was the root of all my problems."

did you remove the DVD cable?

Thanks for any help you can provide...

Los you might have more luck posting this as a new question as there are more people at the front desk whereas there are only 4 people reading posts to this question and one of them is me. Granted that 1 person here does seem to fully understand their way around this problem but there may be others at the front desk that have more time to get involved with answering this
https://answers.launchpad.net/ubuntu/+addquestion

Good luck and regards from
Tom :)

Tom,

I had the identical problem that jmcracken had...
I need real information about how to solve it.
His post does not explain how he actually solved the problem. :-/
So if he is interested in helping then clarifying this for all concerned will help a great deal :)

Thanks for interest.

Los

Sorry if I wasn't clear...I changed the 80 wire UltraDMA ribbon cable to a 40 wire standard IDE ribbon cable. After that, all went as well as could be expected.

Note: My BIOS allows me to set the boot drive order...it also has a boot drive selection menu that can be displayed by pressing the F8 key at start up. This allows me to choose my boot drive without first going into the BIOS itself.

As I stated at the beginning of the thread, my BIOS sets up the 4 SATA ports as first & second tier devices while the single IDE port is registered as 3rd tier (the last to be recognized). I was recently informed by my brother that the IDE port is considered a legacy application now and is closer to a PATA port because of some special access timings setup in the board and chipset! Don't quote me on that, but that is the way I understood him, and he is way up on me in that respect.

Please forgive the wait... I've had some personal problems (caring for a elderly pet) recently and this is the first chance I've had to get back to forum.

Important! if your are trying to install Windows XP (on the first partion so you can duak boot after installing Ubuntu) on a newer motherboard and your Windows XP CD is older than Service Pack 3 it may fail to install due to a lack of drivers for later model motherboards with SATA ports! Yes, been there done that, got me a T-shirt, a ball cap and a Bulwinkle decorder ring! In these cases you will have to either perform the installation with a drivers update disk or you will have to "Slipstream" the XP CD. In either case it's not as hard as it sounds (go to theeldergeek.com for details about the slipstream option).

Good luck guys, jmccracken ;-)

Thanks Jm :)

Jm,

Thanks for the reply.
I should have read your earlier posts with a little more care.

I have the correct IDE cable, my DVD drive is working fine.

I have ubuntu running on a 40 G IDE drive.
When I added a SATA drive it will not boot.
I unplug the SATA drive and it works fine.
When it does not boot with the SATA cable connected
I get a message from the bootloader that it timed out waiting for root device and the it is running "BusyBox" with a (initramfs) prompt.

I am going to check the jumpers on the IDE drive...

My bios allows me to control the order of the boot drives
I have:
 GeForce 8200 motherboard
 AMD 64 Dual Core CPU
 Hitachi 500G SATA II

When I boot with logs in recovery mode
I get a message like this...
[ 113.349227] ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x4)

If I let it sit
then I get some a bunch of "SATA LINK Down" messages for the various SATA ports...

Busybox is the command-line

Thanks...

Booting from the ubuntu live cd ...

the partition step fails to see a drive...
drive is plugged into motherboard slot labeled SATA1 (there are SATA1 thru SATA4 connections)

I get these messages in syslog:
                            .

Mar 21 01:38:18 ubuntu kernel: [ 3.092416] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
Mar 21 01:38:18 ubuntu kernel: [ 3.092418] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
Mar 21 01:38:18 ubuntu kernel: [ 3.252515] usb 2-1: device not accepting address 2, error -62
Mar 21 01:38:18 ubuntu kernel: [ 3.256821] ata1.00: ATAPI: SONY DVD RW DRU-V200A, 1.60, max UDMA/66
Mar 21 01:38:18 ubuntu kernel: [ 3.256831] ata1: nv_mode_filter: 0x1f39f&0x1f01f->0x1f01f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:900:0x11)
Mar 21 01:38:18 ubuntu kernel: [ 3.272258] ata1.00: configured for UDMA/66
Mar 21 01:38:18 ubuntu kernel: [ 3.272290] ata2: port disabled. ignoring.

Mar 21 01:38:18 ubuntu kernel: [ 5.304344] usbcore: registered new interface driver usbhid
Mar 21 01:38:18 ubuntu kernel: [ 5.304347] usbhid: v2.6:USB HID core driver
Mar 21 01:38:18 ubuntu kernel: [ 8.756023] ata3.00: qc timeout (cmd 0xec)
Mar 21 01:38:18 ubuntu kernel: [ 8.756030] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 21 01:38:18 ubuntu kernel: [ 9.240019] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 19.240023] ata3.00: qc timeout (cmd 0xec)
Mar 21 01:38:18 ubuntu kernel: [ 19.240030] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 21 01:38:18 ubuntu kernel: [ 19.724016] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 49.724023] ata3.00: qc timeout (cmd 0xec)
Mar 21 01:38:18 ubuntu kernel: [ 49.724029] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 21 01:38:18 ubuntu kernel: [ 50.208016] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 50.528021] ata4: SATA link down (SStatus 0 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 50.848016] ata5: SATA link down (SStatus 0 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 51.168016] ata6: SATA link down (SStatus 0 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 51.488021] ata7: SATA link down (SStatus 0 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 51.808016] ata8: SATA link down (SStatus 0 SControl 300)
Mar 21 01:38:18 ubuntu kernel: [ 57.216905] aufs 20080922
Mar 21 01:38:18 ubuntu kernel: [ 57.227054] loop: module loaded

Are both drives connected to the motherboard at the same time? If yes, try disconnecting the IDE drive.

Are you trying to install Ubuntu or just using the Live CD to boot with?

Does your BIOS allow you set the order of your boot devices?

What is your objective?

You might check the jumpers on the SATA drive also.

Any drives being set to CableSelect can cause confusion even if placed correctly along the data cable in my experience

Roger that!

I still think there will be trouble trying to boot to the IDE drive if it's recognized last though.

I tried the SATA standalone...
No dice.
So I punted and put it in a USB - to- SATA external case.
I am able to format it and use it that way.

I'd like to run it from the internal SATA connector internal but ubuntu is having none of that...

Thanks for your time and help..

This may need a bug report, sorry I couldn't be more help.

Good luck and regards from jmccracken :-)

los that is a great solution i did not even think of that

I have a similar error, well no its IDENTICAL to yours and I have been trying to solve it for almost 2 weeks now but no luck. Seems we even put our failing drive in the same SATA port. (But it fails just as equally in any other port.)

Dmesg after boot gives me this:
[ 3.600022] ata1: SATA link down (SStatus 0 SControl 300)
[ 3.920018] ata2: SATA link down (SStatus 0 SControl 300)
[ 4.404017] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9.404019] ata3.00: qc timeout (cmd 0xec)
[ 9.404025] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 9.888017] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 19.888018] ata3.00: qc timeout (cmd 0xec)
[ 19.888025] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 20.372016] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 50.372019] ata3.00: qc timeout (cmd 0xec)
[ 50.372025] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 50.860020] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

But heres the rub. Is it ironic that you have an NVIDIA 8200 mGPU and I have the NVIDIA 750i mobo which have ALMOST IDENTICAL CHIPSETS?

Another bit of irony... you have a HITACHI 500GB SATA II? im guessing its the P7K500? I have a HITACHI 1TB SATA II the 7k1000!!!

The live CD for me also will not recognize the device to be partitioned. fdisk will not list it, cfdisk spits out a "fatal error: cannot open drive". No 'fstabbin' for me. Other computers have readily recognized this drive, partitioned, and even installed on it, but it just will not work on our setups.

I have AMD 64 CPU also, but the quad 9550.

Same chipsets, (nearly) same HD, same error. I have literally been driven to insanity by this overwhelming conundrum. This needs to be fixed. Badly.

Oh heck. It's a shame that this wasn't started as a new question because then all this valuable information could easily be sent to bug report with about 2 mouse clicks.

Please can one (or both) of you post this as a bug-report and then add your info to the bottom of the other one's report. One of them will get marked as a duplicate bug, don't worry about that part. When posting into the other persons bug-report notice at the top-right there's a "This doesn't affect me", make sure to click on the "change" link beside that.

Actually posting it directly from your machine, rather than from Answers, might have a slight bonus because sometimes you see extra attachments of relevant info sent automatically from your machine. Makes for very dry reading but you can check through it if its sent.

Good luck and regards from
Tom :)

Ok so how do i make this bug report? Do i paste my problem over the original one that pops up when I click bug report?

Sorry but what do you mean from the machine? I have never posted a comment through the machine directly... Is there already a shell script somewhere for this somewhere? Or do I need to write my own?

Sorry, i'm getting muddled. Usually there's an application that suffers and clicking the "Help" button allows you to post a bug report and because the bug-report is being created from your machine extra data about machine specs and relevant version numbers gets sent as attachments that you can then read through.

However, in this case i think you'll just need to use
https://bugs.launchpad.net/ubuntu/+filebug
brief summary first and then space to copy and paste something from above. Later someone may ask for addiional information and you can always add attachment in there which is hugely helpful.

I made it sound waaay more complicated than it really is!

Apols, thanks and regards from
Tom :)

Hi :)

Have you been able to test the new Ubuntu 10.04 before it gets officially released?
http://www.ubuntulinux.org/testing/lucid/beta1
Trying it as a LiveCd or as an extra dual/multi-boot would be ideal. Developers and everyone are keen to try to iron out any problems before 10.04 gets officially released so you might find faster & more effective answers to your bug reports which would make 10.04 work better on your system for you

Thanks and regards from
Tom :)

Hi Tom,

I haven't gotten to Lucid yet. I've been a very busy fellow lately. I was wondering how to get in on the testing phase but like I said I have been very busy.

Thanks for the links I'll get on it ASAP!

Thanks again,

jgm

Hi :)

Don't worry if you haven't got the time but if you do want to test it quite quickly then just download, make a Cd and boot up as a LiveCd session
https://help.ubuntu.com/community/LiveCD

If you already have a virtual machine then you could avoid making a Cd and just boot-up a virtual LiveCd session using the iso file that you downloaded. But virtual machines are only approximations to the real thing so it's generally more accurate if you try out the LiveCd session on the real hardware.

As i said tho it doesn't matter if you don't have time but i thought it might be interesting to have a sneak preview

Good luck and regards from
Tom :)