Red Hat Bugzilla – Bug 442853
Fedora 9/Anaconda Fails to detect disks
Last modified: 2013-07-02 22:35:33 EDT
Description of problem:
When booting from the Live CD or the boot.iso of F9 Beta (and the boot.iso of
13th April), the system fails to detect any hard disks. Obviously, Anaconda can
not install Fedora as no hard disks are present.
Version-Release number of selected component (if applicable):
Every time I boot either boot.iso or Live CD.
Steps to Reproduce:
2. Try to install or use hard disk
No hard disks available.
Hard disks to be detected and the system to be installable.
As suggested on Fedora-test-lit, I've attached the output from lshal and dmesg
while running the Live CD. If more information is needed please feel free to let
me know and I'll do my best to get it!
Created attachment 302723 [details]
Output of dmesg
Created attachment 302724 [details]
Output of lshal
What kind of hard disks are attached and what connectors are they attached to?
It's a 160GB Serial ATA at 5400rpm...I don't know what kind of connectors are
used - it's the internal drive on my laptop (Sorry for the useless info!). Is
there someway I can check this for you? I use Fedora 8 on this system day to
day, so anything I can do on there is possible.
Can you attach the dmesg from Fedora 8?
Created attachment 302931 [details]
Fedora 8 dmesg
I've attached the dmesg from my F8 system...
The Fedora 9 driver thinks the controller SATA links are down.
Fedora 9 (2.6.25-rc 12 April):
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0x60f8 ctl 0x611c bmdma 0x6020 irq 18
ata4: SATA max UDMA/133 cmd 0x60f0 ctl 0x6118 bmdma 0x6028 irq 18
ata3: SATA link down (SStatus 0 SControl 0)
ata4: SATA link down (SStatus 0 SControl 0)
Fedora 8 (18.104.22.168):
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0x60f8 ctl 0x611c bmdma 0x6020 irq 20
ata4: SATA max UDMA/133 cmd 0x60f0 ctl 0x6118 bmdma 0x6028 irq 20
ata3.00: ATA-8: Hitachi HTS542516K9SA00, BBCAC3GP, max UDMA/133
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA Hitachi HTS54251 BBCA PQ: 0 ANSI: 5
I'm also encountering this problem on the computers we have at our university.
These are HP DC7700's.
When trying to install rawhide (using PXE boot and installation from a download
mirror), anaconda fails to detect the SATA harddrive. In the dmesg I'm also
seeing the 'SATA link down' messages but with different values for the SStatus
However, sometimes the SATA harddrive is detected normally. Most of the time I
need to switch desktops (ALT+F3) and move the mouse a bit right before the SATA
initialisation is started to make the SATA harddrive detection succeed.
I'll try to generate a dmesg for both the working and non-working situation
Created attachment 303295 [details]
dmesg of a HP DC7700, sata detection fails
ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x10e0 irq 14
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x10e8 irq 15
ata1: SATA link down (SStatus 621 SControl 300)
ata2: SATA link down (SStatus 611 SControl 300)
With the latest anaconda (available on your local mirror) I can't even get the
SATA drive to detect anymore..even with the workaround I described.
With kernel 2.6.25-0.218.rc8 my installed Fedora 9 system boots fine (without
any workarounds), but with kernel 2.6.25-1 it doesn't boot any more: unable to
find the root partition...
Another thing I noticed with kernel 2.6.25-0.218.rc8 was that the DVD drive
(which is also connected by SATA) isn't detected..
Created attachment 303337 [details]
dmesg of a HP DC7700, sata detection succeeds
This dmesg is from the preview release of F9 and sata detection succeeds with
I think this bug can be considered a duplicate of bug 436099.
With kernel 2.6.25-6 the SATA problems are solved for me. I'm now waiting for a
new anaconda build with this kernel, but I don't expect problems with it anymore.
*** This bug has been marked as a duplicate of 436099 ***