I couldn't decide if this went in hardware or software, as it is both in a way. If I try to install 9.04 (I've been trying for a few months, and 9.10 is kind of slow) it doesn't see my hard drive. It's not even listed in the fstab! It's like it's invisible. However, If I install ubuntu 6.06 it can see it fine! This is a kernel problem, as it occurs with other flavours of linux as well, but openSolaris and any BSD See it just fine.

One other interesting factor is this: If I update to 8.10 LTS and choose the third kernel on the list, it runs fine! There is another snag though. In that kernel of 8.10 it can't see my keyboard, unless I bring up a terminal!

The preferred solution would be this. Find a way to make it work, possibly incorporating it into the kernel. Also, It's not a bad disc. I used the same one for two other pcs, and there were no issues whatsoever.

Any info would be appreciated!

What sort of hard drives do you have?
Which motherboard?
Have you looked in the syslog to see if there are any messages about the missing drives?

A slow 9.10 suggest you have an older machine - perhaps with a mix of pata and sata drives?
How did you install each of the oses you mention?

I have a DGIZ-something Intel motherboard with a Pentium D processor, and a western Digital caviar 160gb that is detected in other cases, same make and model. Oh, and I missed something last I posted. I install 6.06 with netInstall option, then upgrade to 8.04 LTS, and then 8.10 so as to get 9.04. 8.10 is where the problem occurs. Will 9.04 be going LTS? I hope so. And ues, the 9.10 was on an old P4 with only 512 mb of ram, and no sata available, plus an old radeon 9200. Different pc from this, though. This one has 1G, and an nvidia 7200 gs. Wonderfully, both are supported out of the box by linux. If 9.04 goes lts, I can skip 8.10 directly, and have 9.04.

By the way, I've reinstalled 6.06 and I'm upgrading to 8.04 Right now.

8.04 works great, as expected. If there isn't a simple solution, I'll probably just hold out till April for the 10.04 LTS, for a straight upgrade to awesome (10 second Boot time!)

Sorry, hard to make out what you mean in your last posts.

It looks like you have an older mobo as expected - but you only list a single drive. How then can it be undetected and also listed in fstab? Is there another drive or was this tried from a live session?

Note: if an LTS edition works for you, and with another one very close now, best advise is, indeed, to update the system, then upgrade distro when the update manager gives you the option. (I usually leave it a week or so for initial bugs to get ironed out and the servers to settle down.)

I said it doesn't show in fstab, so it wasn't some weird mounting problem.

Atcually, the Mobo isn't that old. This is a SATA drive, and the PC was only made around the time of 8.10. i have many other pcs much older that work wonderfully!

Also, it's an issue with the linux kernel. It happens with all distros, and started in 7.04. The part that works is the secondary kernel options in grub. As long as those stay available, I'm all set, but unfortunately, I have to use 6.06 so that the CD can see the Hard drive.

I guess I can wait till april. It makes me so Impatient, though!

I have this problem aswell.
I try installing the latest Ubuntu but it does not detect my HardDrive
http://reviews.cnet.com/desktops/hp-...-30969217.html
Anyone have a solution?

@LinuxPowered
The drive does not show up in the installer?
Does it show up in the live session?
Is the situation similar to:
http://ubuntuforums.org/showthread.php?t=1349898

@Willrandship
Please be patient, I am having trouble parsing your statements - I realise they are obvious and clear to you

How are you trying to detect the drive? eg - in a live session or by installer, or from an ubuntu install on another disk?

Have you examined the syslog (dmesg) for messages associated with your drive?

Have you tried fdisk -l

You suspect a kernel bug? Please point me to the bug report you believe is appropriate here.

@both
most common reason karmic does not detect HDDs on newer boards is that RAID is somehow being triggered - turn raid options off in bios if they are not otherwise used. Also:

apt-get remove dmraid

@LinuxPowered

You may or may not have the same problem. I would recommend starting your own question so more people are shown your problem, as it may have different issues.

@Simon

I try to detect by live cd.
Also, I have tried syslog, dmesg, and tried disabling dmraid to no avail. I have tried fdisk -l.

My motherboard's bios does not have any raid options whatsoever.

This is not a problem with karmic. It's been around a long time, and occurs in other linux systems, such as fedora or openSUSE.
It does not occur with PC-BSD or other BSD and non linux OSs.

I do not know of any bug reports involved, but I submitted it to launchpad's Ubuntu bug thing.

The only way I can get it to be detected is to use alternate kernel versions listed in grub, after installing via 6.06 and upgrading to 8.04 via LTS versions. I am planning, if no solution arises, to do the same up to lucid lynx.

This the one?
The team needs more information from you before they can move forward on this bug. It has been getting attention so, with feedback, there is likely to be a fix soon.

Suggest - dual-boot with the latest development release, and provide the missing information.

Sounds exactly like mine. I submitted a similar report, referring to 8.04 LTS rather than 9.04. I still think it lies in the kernel, and for me it only works in the 686 kernel versions, never with the generic. Maybe it's a processor issue! I have a pentium D supporting 64 bit (I think, never really messed with it. It says it is on the package) and I think it's dual core, but I'm not sure.

cat /proc/cpuinfo

what is the link to your bug report? - have you updated it for 9.10? Have you tried the most recent?

the reason I'm wanting the bug report is that your feedback has been unhelpful.

please try to avoid self-contradictory replies, and provide data. eg. you said you were unaware of any bug reports, but you know you have submitted one - so you were aware of one bug report - and you do not provide a link.

please show what you have done and the manner of the failure - copy and paste for preference: eg. you reported that you have tried a list of utilities, but do not say how you have tried them or the manner of their failure. In fact, nothing, but "to no avail". The outputs provide information.

please look at your statements to see if there is information you have left out which could be used to narrow down the problem: eg. you have stated that this is a kernel issue which shows up in many other distros - yet you also say that choosing "an alternate kernel in grub" allows it to work after you have upgraded through LTS editions ... so some recent kernels have worked and some have not - don't you think it would help to know which ones?

before posting again, please visit the advise link in my sig and read that page. This will help you understand how to improve your feedback and so help me to help you.

I can't dual boot to anything that I can't update to grom 6.06. The installer, and the entire system itself, make no mention of any attached storage except any ide Drives. Please note that I can currently run the system fine. It just runs in a different kernel, the one that doesn't run the installer.

Also, I did list which kernel I was using. It is the only one in the entire 8.04 list that says 686 in it, rather than kernel generic. fdisk -l shows only my cdroms and floppy, no others mentioned. (this is all from the Live cd, as I can't actually install and run the proper kernel) It can also see any usb devices, and network properly.

It seems that my computer can only see hard drives when it runs a 686 kernel. Do you know of a way to force it to always do so?
Is 686 anything to do with 64-bit or am I completely off? Maybe I just need to run the 64-bit versions of ubuntu!

Also, I don't have access to the pc very often, so it's hard to get outputs....

Update: I am currently downloading 9.10 64 but, and it should be done within the hour. I'll play warcraft 3 in the meantime.