Description of problem:
Attempted to do a local install from the F7 DVD on an 8-year-old eMachines
333cs using a new, 120 GB hard drive (WDC WD1200BB). Upon reaching the page
where it asks how to partition the drive, the list of available devices is
empty. Upon clicking "Next", got the following error: "No drives found. An
error has occurred - no valid devices were found on which to create new file
systems. Please check your hardware for the cause of this problem." I
subsequently did a successful install with the same hardware using the FC6 CD
set (the FC6 DVD bombed out before even getting to the boot: prompt), with the
120 GB hard drive being detected correctly.
Version-Release number of selected component (if applicable):
always - tried several times
Steps to Reproduce:
1. Attempt either graphical or text install with said hardware and F7 DVD.
Hard drive not detected at all.
Hard drive should be detected.
I subsequently put an older, 8.6 GB drive in instead and when attempting the
install, that drive was detected correctly, though the install failed later with
bug #242546. I tested the F7 media both with mediacheck and by verifying the
sha1sum of the burned DVD image before using. Since the machine is 8 years old,
its BIOS seems confused as to how big the 120 GB drive actually is, but since
the FC6 installer detected it properly, clearly the OS should be able to work
same problem on an soekris 4801 box
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Is there any chance
that you can test with Fedora 8 Test 2, available from:
As this is an installer bug I'm adding a blocker bug because its important this
issue does not recur for the next release.
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Unfortunately, I'm unable to even boot the F8t2 DVD - after seeing the
ISOLINUX message, and a several-line text page for a fraction of a second, I get
isolinux: Disk error 10, AX=42B5, drive EF
boot failed: press a key to retry...
I had the same problem with the FC6 DVD, although the FC6 CD set worked
(unfortunately that's no longer an option). Hopefully someone else who has the
same problem can test for it.
This sounds like either a media problem or a problem with your burner. Did you
media check with shasum?
I would be inclined to try a different burner using different media and if it
still fails then try a different DVD drive if you have one available.
I'm an expert at burning Fedora media - I verified the signature on the
SHA1SUM file, then verified the sha1sum on the downloaded ISO, then padded it
using the isopad script (though with the new drivers introduced in F7 that's not
really necessary anymore), then verified the sha1sum on the media after burning
it. It's not a media or DVD drive problem. It may have something to do with
the fact that the 1999 BIOS on the machine doesn't seem to understand that a HD
can be bigger than 64 GB, but that didn't stop me from being able to install
from the FC6 CD set, with the installer detecting the HD properly, so there must
be more to it than that.
I'm assuming you're running the latest available BIOS then. Am I correct in
saying the only difference between a successful install and a failed one is that
it fails when using a DVD and works with a CD? If that is the case then perhaps
jumper settings on the drives - are they mastered and slaved correctly for example?
Does it boot with acpi=off kernel parameter (I think there is a moment in the
installer where you can edit the boot flags)?
It's the latest BIOS as far as I know (eMachines doesn't have any official
BIOS updates, but I found a slightly newer version years back). The drives are
jumpered properly. I can't edit kernel options, since the page with the command
line only shows for a fraction of a second. I tried typing blind before it
displayed, but that was no help.
I just downloaded and burned the Fedora Live CD. Can it run on a machine with
only 256 MB of RAM, and if so, if I tell it to install to the HD, does the
installer work essentially the same as that for the DVD? If so I could try
that. I'd prefer to run the installer just to the point where it asks how to
partition the disk, so I can back out - at the moment FC6 is installed and I
don't want to change that.
If you have the bandwidth and a little patience, you could try an install over
HTTP, you just need to d/l the boot cd:
and then run the install from that. This would be perfect for what you wish to
do - ie. back out at HD detection time.
I think you will be struggling with 256MB on the live cd.
I just successfully booted the Live CD (it is indeed extremely slow, though).
When I double-clicked on the install on HD icon, there was some activity, which
eventually stopped without anything else happening. There were also two lines
in dmesg output, something like
ata1: port is slow to respond, please be patient (status 0xd0)
ata1: SRST failed (errno=-16)
(ata1 is the HD). When I boot up from the HD, there is a long pause before it
gets to the grub screen, which I suspect has something to do with the BIOS being
confused. I'm guessing that the Live CD installer didn't find the HD, but am
not sure. I may try the network install later.
Also, this box is just so old, and has had so many install-related problems
(audio, video, hardware detection, etc.) that if you can't find anyone else who
can reproduce this bug, it should probably not be a blocker, though I'd
appreciate it if you could at least keep it open a while longer. I could try
again with test3.
Also try adding some options to the kernel boot line. Add
I will try this tomorrow as I have to shut down my regular machine, boot up
the eMachine, and then endure long waits for each boot. BTW, this machine has
never had problems with ACPI, though it does have a BIOS bug that causes
problems with APM, and so I've actually had to use acpi=force (because of the
BIOS's age, Fedora won't use ACPI by default).
I successfully started the install using the boot.iso and HTTP. When it got
to the page asking me how to partition the drive, the list of devices was again
empty, so this bug still exists in F8t2. BTW, since I already had a F8t2
install DVD, I tried selecting the "local CD/DVD" install method, and then
swapping in the install DVD, but it didn't accept that. Is it supposed to work?
(In reply to comment #13)
> I successfully started the install using the boot.iso and HTTP. When it got
> to the page asking me how to partition the drive, the list of devices was again
> empty, so this bug still exists in F8t2. BTW, since I already had a F8t2
> install DVD, I tried selecting the "local CD/DVD" install method, and then
> swapping in the install DVD, but it didn't accept that. Is it supposed to work?
Yes but as there seems to be gremlins in the system with regards to DVD boot on
your system its doubtful in this instance.
I completely forgot to say that if you hit "Escape" twice at install ie. at the
point where you said:
(In reply to comment #7)
> jumpered properly. I can't edit kernel options, since the page with the command
> line only shows for a fraction of a second. I tried typing blind before it
> displayed, but that was no help.
then you should be able to edit the boot options and add switches as Chuck
similar problem over here: i'll boot with the dvd image then it kinda dedects
both harddisks i have, and the installer doesnt likes the partition table an
wants to initialize it, but i don't want to do this because there is also a
windows xp installed.
after clicking twice "no" it only detects the second harddisk (sdb). both are
Western digital disks, one is 160gb (which gets recognized) and the other is
~250gb, which is not found... any hint in this matter?
i forgot: these disks are plain old ata disk, always worked before.. :(
(In reply to comment #15)
> similar problem over here: i'll boot with the dvd image then it kinda dedects
> both harddisks i have, and the installer doesnt likes the partition table an
> wants to initialize it, but i don't want to do this because there is also a
> windows xp installed.
> after clicking twice "no" it only detects the second harddisk (sdb). both are
> Western digital disks, one is 160gb (which gets recognized) and the other is
> ~250gb, which is not found... any hint in this matter?
I don't think yours is a duplicate Benjamin - the installer wants to initialise
the partition table but won't overwrite the windows partition unless you
expressly ask for it do so. If you refuse it write-access to the first disk and
its partition table then most likely it excludes this from the rest of the
In the "Additional info:" I should have mentioned that my father has a machine
which is almost identical (same MB, different CPU, DVD drive and HD) and he
could install properly from the F7 DVD, including detecting the HD, which in his
case is only 20 GB (and I do have the same model DVD drive as him, just in a
different machine, so I could try swapping it into the eMachine to see if it can
boot from that). The BIOS seems to have a limitation of 65535 MB on how big a
HD it can recognize, since I see that number on the BIOS screen when booting up,
instead of 120 GB (though at least it does recognize that the drive is there).
So that's two cases of it working with a drive smaller than 65535 MB. It still
shouldn't prevent the OS from recognizing the drive properly, though, since it
worked with the FC6 installer and when running FC6 which is installed currently.
I just realized that the problem I have booting from DVD didn't happen when I
tried installing using the 8.6 GB HD. So it may be that the failure to boot
from DVD may be somehow caused by the HD being too big, and not by the model of
DVD drive (which is also consistent with my father being able to install using a
20 GB HD) - of course this isn't a Fedora issue, though, since it happens before
I even get to the GRUB screen.
Bad hardware seems to be the main cause of your problems however as you
installed FC6 okay it would be beneficial to get an output from the following
commands in FC6:
dmidecode (you may need to install this)
and attach them to this bug. I will then re-assign to the relevant maintainer,
add an F8 blocker bug and people more able to comment may then wish to do so.
Alternatively if you feel that it is faulty hardware then you may wish to close.
Since the FC6 installer detected my HD properly, I think it is a Fedora bug,
so it shouldn't be closed. On the other hand, it may only be triggered with
very old hardware such as mine, in which case it probably shouldn't be a F8
blocker (unless someone with better hardware can reproduce it). I will attach
the output of the three commands shortly.
Created attachment 197571 [details]
output of "lspci -vvxx"
Created attachment 197581 [details]
current output of "dmidecode"
Created attachment 197591 [details]
old output of "dmidecode" created on June 29, 2001
At the time, my machine had 128 MB of RAM. It currently has 256 MB. The
motherboard and CPU are the same.
Created attachment 197601 [details]
output of "dmesg"
Changed the summary since the bug appears to have nothing to do with the
installation method (occurs for me with either DVD or network install).
(In reply to comment #2)
> There hasn't been much activity on this bug for a while. Is there any chance
> that you can test with Fedora 8 Test 2, available from:
> As this is an installer bug I'm adding a blocker bug because its important
> issue does not recur for the next release.
> If the problem no longer exists then please close this bug or I'll do so in a
> few days if there is no additional information lodged.
I tried again the network installation on my Soekris 4801-box,
this time with Fedora 8 Test 2. The problem still exists -- no diskdrives
(pata/ide drive) found.
Having the same problems with F8t3. The DVD doesn't boot properly. I can
successfully start a network install with a CD containing the boot.iso image,
but again it doesn't find the HD.
(In reply to comment #29)
> Having the same problems with F8t3. The DVD doesn't boot properly. I can
> successfully start a network install with a CD containing the boot.iso image,
> but again it doesn't find the HD.
What is displayed on console 4 when it fails to find the disk?
Do you mean virtual console 4 (Ctrl-Alt-F4)? I've never accessed any of the
VCs during an install. What type of information is supposed to be there?
(In reply to comment #31)
> Do you mean virtual console 4 (Ctrl-Alt-F4)? I've never accessed any of the
> VCs during an install. What type of information is supposed to be there?
Logs showing what drivers were loaded are in there. Try installing in text mode,
then it's easier to switch among the consoles.
Created attachment 216691 [details]
graphical screen when failing to find hard drive
Created attachment 216701 [details]
virtual console 3 after failing to find hard drive
Created attachment 216711 [details]
virtual console 4 after failing to find hard drive
(In reply to comment #35)
> Created an attachment (id=216711) 
> virtual console 4 after failing to find hard drive
Can you scroll back in console 4 and see what it says when it loads the ATA drivers?
Normally it's something like this (from machine with working pata_amd driver):
scsi2 : pata_amd
scsi3 : pata_amd
ata3: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma
0x0000000000013080 irq 14
ata4: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma
0x0000000000013088 irq 15
ata3.00: ATAPI: HL-DT-ST DVDRAM GSA-T20L, NC08, max MWDMA2
ata3.00: configured for MWDMA2
ata4: port disabled. ignoring.
Sorry if this is a dumb question, but how do I scroll back? I don't think the
mouse does that (or does it?). Also, is there some easier way to capture this
information than taking photos of the screen?
(In reply to comment #37)
> how do I scroll back?
Shift-PgUp / Shift-PgDn
> Also, is there some easier way to capture this
> information than taking photos of the screen?
Not if the disk isn't found. There should be a working console in tty2 but I
doubt any useful tools are available. Booting in rescue mode should work better,
ssh should be available then.
Created attachment 216911 [details]
dmesg output during attempted F8t3 install not finding hard drive
The Shift-PgUp/PgDn trick didn't work during the install, even though it
works when running Fedora normally, so I couldn't scroll up. However, I was
able to go to the shell in VC2, mount a floppy, and copy the output of dmesg to
it, which I've attached here. It appears to include the information you
Related to this possibly?
It doesn't look like this patch was actually ever merged.
It was merged in a different form (at least its in -mm). We try a couple of
times to follow the precise spec and if that fails we just carry on and see what
happens in the hope its just a spec compliance issue on the drive (or raid
Drive reports itself busy and never comes back from the reset. Looks like a very
machine specific derangement as I've not seen other reports like that with a
workable pattern of debug.
When I boot the machine into FC6, there are two points before getting to the
GRUB screen where there is a long pause (maybe 30 seconds to a minute). On one
of them, I can see a BIOS screen where it appears that the BIOS detects the HD
as only 65535 MB, even though it's actually 120 GB. (As I mentioned earlier, my
father has an almost identical machine with an identical MB but with a 20 GB HD
which is detected normally by the F7 installer and he installed it
successfully.) After getting to the GRUB screen, everything works normally
without the long pauses (at least no longer than expected with such a slow
machine). Could this be a BIOS issue? If you want I could take pictures of the
two screens where it pauses so you know what I'm talking about.
Also, these pauses only happen after I installed the 120 GB drive. They
didn't happen with my old 8.6 GB drive.
Created attachment 217781 [details]
first pause in bootup (just over 30 seconds)
Created attachment 217791 [details]
second pause in bootup (just over 30 seconds)
Note the hard drive being detected by the old 1999 BIOS as 65535 MB instead
of the correct value of 120 GB. Despite this, FC6 detects the size of the
drive properly after bootup.
Right so the BIOS doesn't properly support LBA48. That explains the boot
problem, and may well explain the big drive + ISOlinux failure early on.
Once Linux is booted however it then resets the controller and reprobes the
devices. I'm not aware of any hardware limits on the older VIA controllers, and
the fact FC6 worked for you suggests there aren't.
Given what seems to occur is that the drive simply never comes back from a reset
I'm not sure there is much I can do about this specific box.
Does that account for why my father's 20 GB drive with essentially the same
hardware works, and would a drive less than 64 GB be likely to work? If
necessary I can just buy a smaller one, though that's not ideal. Also, do you
think the hardware limits in the present software are likely to be removed some
time in the future? This is a backup machine only, and I could also just leave
FC6 on it even after it goes EOL and hope it gets fixed by F9.
In response to today's call for testing of pata_via: I have a 3-year newer
machine (2002) that uses pata_via and claims to have a
"VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE" controller. (This is
not the same as "via82c596a" [note the '9' in the summary of this bugzilla
report, but the '8' in mine.]) I used pungi to create a 3-CD set from Fedora 8
rawhide of Wed.Oct.24 and installed successfully. I'm using the installed
system now to enter this Comment.
I will attach lspci and lsmod output next.
Created attachment 236941 [details]
Created attachment 236951 [details]
Created attachment 236961 [details]
Linux f8i0-32.localdomain 220.127.116.11-31.fc8 #1 SMP Tue Oct 23 14:42:19 EDT 2007
i686 athlon i386 GNU/Linux
FWIW, I have a box that uses pata_via for a hard drive and a CD drive (K8M800
chipset), and it works OK in F8; so it's not something common to all pata_via
Dropping from kernel blocker - everyhing seems to indicate this is machine/drive
I'm having the same problem with F8 - I used the Fedora Unity F8 CD set for
the install attempt (didn't bother trying the DVD). I also noticed bug #372281
from someone else experiencing the same problem with F8, but with much newer
I had the same problem with my Compaq Deskpro EN.
It's running FC6 but exactly the same thing happenned when I tried installing
FC7 and, now, FC8.
I never followed it up before but would really like to sort it as this machine
is my file server and FC6 is no longer being updated.
I'm pasting in more information from a question I asked at Fedora Forums:-
FC7 & FC8 installers don't detect my ide hard drive on Compaq Deskpro. FC6
I'm running FC6 on a Compaq Deskpro EN with only two drives: a 120 GB standard
ide drive and a DVD drive.
The drives are on separate controllers, both masters.
I've been using this Compaq as my file server at home for about a year.
When I try to install either FC7 or FC8 from the DVD, the installer never
detects my hard drive.
When it gets to the point where I need to choose where to install, there is no
drive to choose from in the box.
With FC7 I also tried a Live install and still the drive was not detected.
Other things I've tried:-
Replacing the old 40-wire ATA cable with an 80-wire one.
Swapping the drives around
These boot options:-
The result is always exactly as I've written above.
Also, I installed a second instance of FC6 on the same drive yesterday - just
to be sure that FC6 installation still works.
A bit more information.
I tried upgrading my spare instance of FC6 using yum and these instructions:-
I found that trying to boot into the FC7 kernel gives me:
ata: SRST failed (errno=-16)
Booting into the old FC6 kernel works.
So that partition is now FC7 with an FC6 kernel.
I did a comparison of an attempted install of FC7 and an install of FC6.
I stopped the FC6 install at the point where the FC7 one fails - the screen
that should show the hard disks available for the installation).
In each case I then took a dmesg, a dmidecode and an lspci -xxvv.
(I used Andre's method, from comment #39, of opening a shell in virtual
2 with ctrl-alt-F2, mounting a floppy and saving the output on the floppy).
They all are attached below:-
Created attachment 290514 [details]
dmesg for FC6
Created attachment 290515 [details]
dmesg for FC7
Created attachment 290516 [details]
lspci -vvxx for FC6
Created attachment 290517 [details]
lspci -vvxx for FC7
Created attachment 290518 [details]
dmidecode for FC6
Created attachment 290519 [details]
dmidecode for FC7
The thing that stood out to my inexpert eye was the lack of a probe of the IDE
interface in the dmesg for FC6.
(The 2 dmidecode files are identical).
Error in comment #65:
I should have written
... the lack of a probe of the IDE interface in the dmesg for FC7.
(FC6 did do the probe).
Further information. I found I can install FC6 from the hard drive using the
instructions here: http://forums.fedoraforum.org/forum/showthread.php?t=164188
The really interesting thing is that I can also boot the F8 isolinux from the
hard drive. As before, when booting from the DVD, the F8 installation fails to
detect the hard drive
... even though that's where it's running from!
This is where it ends up:-
"Unable to find any devices of the type
needed for this installation type.
Would you like to manually select your
driver or use a driver disk."
[Select driver] [Use a driver disk] [Back]
Created attachment 290566 [details]
Text copied from the VC4 screen
Here's the final VC4 screen for the F8 installation from the hard disk (at the
point were its asking for the driver).
I found a solution! After reading
I changed the jumper on my HD from master to cable select. Now, not only does
the installer find the HD, but the machine now boots properly from the install
DVD, so I don't need to use CDs or network install anymore. But why in the
world would this work, since the HD is indeed the primary master?
Thanks Andre, that worked for me too. I'm currently configuring my new F8
I noticed you (Alan) just changed the name of this bug. From the comments in
the link in comment #69, it appears the issue is that Western Digital drives
have to be jumpered differently from all other brands, so it's not even clear to
me whether this is a kernel bug at all, although it's interesting that FC6 is
able to find the drive (after a long delay), even with the "wrong" jumpering.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As you can see in the comments, this is just as much of a problem in Fedora 8 as
As I experience the exact same problem with Fedora 8 as with Fedora 7, the
version needs changing to 8.
Unless Alan has fixed it, it will doubtless still be a problem in 9. Checking
this would require opening the computer and moving the drive jumper.
I would be prepared to do this if there is any reason to believe the the bug
might be fixed in 9 - but not otherwise.
As I mentioned above in comment #71, Western Digital specifies that their drives
should be jumpered differently than the standard way, so I suspect (but am not
sure) that this is not actually a bug.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.