PDA

View Full Version : no hard drives found by fedora 8


glenngds2006
2007-11-08, 12:43 PM CST
Yet I have two physical drives there--a Maxtor 160GB USB drive and a Maxtor SATA-150 drive 200GB. I booted from a Fedora 8 x86_64 Live disk and everything went fine including the starting of gnome. When I double clicked the Fedora Installer--it went fine until time to choose the partitions/drives for the installation then I got an error that said no drives found. I have run fedora 6 and 7 successfully on my system and Ubuntu 7.04 and 7.10 and openSUSE 10.1 and 10.2 and I am currently running windows xp and vista. Should I download the fedora 8 dvd and give it a try???

kadambi
2007-11-08, 12:54 PM CST
I am runnning Fedora 8 test3 right now with a Samsung SATA 250GB drive. I will be installing Fedora 8 tonight and expect it to find the HDD!

Post the dmesg and your machine configuration.

glenngds2006
2007-11-08, 01:40 PM CST
the output of dmesg is as follows:
Unfortunely I will have to limit my dmesg output about 2/3 will have to go

Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 6291456 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 4831k freed
audit: initializing netlink socket (disabled)
audit(1194531233.565:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
ksign: Installing public key data
Loading keyring
- Added public key 2B02AABF702ECCF9
- User ID: Red Hat, Inc. (Kernel Module GPG key)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: VIA PCI bridge detected. Disabling DAC.
Boot video device is 0000:01:00.0
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU1] (supports 16 throttling states)
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.102
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input1
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ processors (2 cpu cores) (version 2.00.00)
powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x8
powernow-k8: 1 : fid 0xc (2000 MHz), vid 0xa
powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xc
powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
Magic number: 15:283:232
Freeing unused kernel memory: 324k freed
Write protecting the kernel read-only data: 1020k
SCSI subsystem initialized
loop: module loaded
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:10.0: irq 20, io base 0x0000d000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
libata version 2.21 loaded.
ACPI: PCI Interrupt 0000:00:10.1[C] -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.1: irq 22, io base 0x0000c800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.2: irq 21, io base 0x0000c400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.3[D] -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.3: irq 23, io base 0x0000c000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-1: new full speed USB device using uhci_hcd and address 2
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 22 (level, low) -> IRQ 22
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:10.4: debug port 1
ehci_hcd 0000:00:10.4: irq 22, io mem 0xf9fff800
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
pata_via 0000:00:0f.1: version 0.3.2
scsi0 : pata_via
scsi1 : pata_via
ata1: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x000000000001fc00 irq 14
ata2: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x000000000001fc08 irq 15
usb 1-1: device not accepting address 2, error -71
ata1.00: ATAPI: HITACHI GD-2000, 1000, max MWDMA2
ata1.01: ATAPI: Memorex DVD+/-RW Dual-X1, 1.05, max UDMA/33
ata1.00: configured for MWDMA2
ata1.01: configured for UDMA/33
scsi 0:0:0:0: CD-ROM HITACHI GD-2000 1000 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 8x/20x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
scsi 0:0:1:0: CD-ROM Memorex DVD+/-RW Dual-X1 1.05 PQ: 0 ANSI: 5
sr1: scsi3-mmc drive: 47x/47x writer cd/rw xa/form2 cdda tray
sr 0:0:1:0: Attached scsi CD-ROM sr1
ahci 0000:00:0f.0: version 2.3
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 21 (level, low) -> IRQ 21
ahci 0000:00:0f.0: controller can't do NCQ, turning off CAP_NCQ
PCI: Disallowing DAC for device 0000:00:0f.0
usb 5-1: new high speed USB device using ehci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
hub 5-1:1.0: USB hub found
hub 5-1:1.0: 4 ports detected
usb 5-2: new high speed USB device using ehci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ahci 0000:00:0f.0: AHCI 0001.0000 32 slots 4 ports 3 Gbps 0xf impl IDE mode
ahci 0000:00:0f.0: flags: 64bit pm led clo pmp pio slum part
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
scsi6 : ahci
ata3: SATA max UDMA/133 cmd 0xffffc2000032ed00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 2303
ata4: SATA max UDMA/133 cmd 0xffffc2000032ed80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 2303
ata5: SATA max UDMA/133 cmd 0xffffc2000032ee00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 2303
ata6: SATA max UDMA/133 cmd 0xffffc2000032ee80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq 2303
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
APIC error on CPU1: 00(08)
APIC error on CPU0: 00(08)
usb-storage: device scan complete
scsi 2:0:0:0: Direct-Access EPSON Stylus Storage 1.00 PQ: 0 ANSI: 2
sd 2:0:0:0: [sda] Attached SCSI removable disk
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
APIC error on CPU0: 08(08)
APIC error on CPU1: 08(08)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3: limiting SATA link speed to 1.5 Gbps
ata3.00: limiting speed to UDMA7:PIO5
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
APIC error on CPU0: 08(08)
APIC error on CPU1: 08(08)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3: EH pending after completion, repeating EH (cnt=4)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ISO 9660 Extensions: Microsoft Joliet Level 3
Unable to load NLS charset utf8
Unable to load NLS charset utf8
ISO 9660 Extensions: RRIP_1991A


My computer specs are as follows:
Motherboard:
ASUS A8V-VM Ultra Socket 939
CPU AMD 64 X2 4200+ Toledo
Memory WINTEC AMPO 3AMD1400-2GK-R
Hard Drives:
Maxtor SATA-150 200GB (not sure of model number)
Maxtor USB 160GB (not sure of model number)

kadambi
2007-11-08, 01:52 PM CST
I wonder why its not able to identify the HDD!

"ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)"

Obviously, you can see the HDD under F7, right?

I will be booting F x86_84 live image and see if I am able to see the HDD. Will get back to you.

glenngds2006
2007-11-08, 02:06 PM CST
That's right no problem with Fedora 7!?

glenngds2006
2007-11-08, 04:08 PM CST
follow up:
I reconfigured my bios settings for my hard drives and had the following happen:
SATA-IDE--boots up normal and finds no hard drives
SATA-RAID--boot up hangs and says kernel-panic
SATA-AHCI--boot up hangs and says kernel-panic

I am sticking with Fedora 7.

glenngds2006
2007-11-08, 04:25 PM CST
By the way Bugzilla is down. I normally report most problems as bugs such as I have found with Fedora 8 live, but I cannot get through to them, period.

Gentoo Bob
2007-11-08, 06:20 PM CST
i had a similiar issue with Ubuntu on my new machine. I had to change a setting in BIOS. look in your BIOS and see if your Hard Drive mode is IDE or AHCI. I had to switch mine to AHCI. Fixed! I'm running WD 300GB SATA II.

kadambi
2007-11-08, 08:21 PM CST
On my machine F7 never booted up. I have been running F8 Test 3. I just popped in F8 and it recognized the HDD in boh IDE and AHCI modes in BIOS.

However, X wouldn't comeup. Curious! since this is pretty similar to F8 Test3. I just tried a couple of times and F8 came up with X and I am trying to install it now.

glenngds2006
2007-11-09, 12:42 AM CST
I will try to reinstall using the fedora dvd and setting the bios sata setting to ahci. Will report back later.

glenngds2006
2007-11-09, 12:59 AM CST
It is a big no go--made no difference. With the full version dvd of x86_64 everything goes fine including the testing of the dvd then Anaconda starts and X starts and after a couple of screens asking questions such as language and keyboard settings it comes to the screen where it is supposed to ask what drive to put the installation on and it is supposed to show a list of drives and my list of drives is blank, period.

kadambi
2007-11-09, 07:49 AM CST
I was able to install it after a couple of (minor) issues. I am wondering if this kernel broke something with respect to your chipset.

strikeforce
2007-11-09, 07:56 AM CST
Looks like you might be stuck with ATA :(

David1980
2007-11-09, 09:49 AM CST
It is a big no go--made no difference. With the full version dvd of x86_64 everything goes fine including the testing of the dvd then Anaconda starts and X starts and after a couple of screens asking questions such as language and keyboard settings it comes to the screen where it is supposed to ask what drive to put the installation on and it is supposed to show a list of drives and my list of drives is blank, period.

Go the same issue, only difference is i'm using the i386 DVD... So solution yet...



D.

glenngds2006
2007-11-09, 11:47 AM CST
Strange enough the Bugzilla starting again--so I reported the problem I was having to Bugzilla--hopefully they can find a solution and will tell us what it is.

glenngds2006
2007-11-09, 12:28 PM CST
Just for kicks I put an old IDE drive into my machine. Fedora 8 had no problem finding it, but did not see the other two drives. What gets me is that windows xp and windows vista had no trouble finding and using my SATA drive and my USB drive--no need to use a driver disk or any special drivers involved.

glenngds2006
2007-11-09, 04:05 PM CST
Just a follow up--I physically put an old maxtor 40GB IDE drive into my computer on a temporary basis and booted both the Fedora 8 live DVD and Fedora 8 DVD and both saw only the older IDE drive, but neither saw most importantly my USB external hard drive nor my SATA drive. I have repeatedly changed settings in my bios and even flashed my bios to different bios for my MB. I definitely say they should ditch what they now have on the mirrors and try to come out with let say Fedora 8.1 I cannot believe they released a major release with a broken installer.

Is there any possible way to upgrade Fedora 7 to Fedora 8 by using yum???????

strikeforce
2007-11-09, 04:10 PM CST
http://fedoraproject.org/wiki/YumUpgradeFaq#head-56b13936246769f517ac488a0098d193c7fc3600

Does this thread help you http://forums.fedoraforum.org/showthread.php?t=171230

glenngds2006
2007-11-09, 04:31 PM CST
I know what the answer is fedora 8.1, well maybe 8.2 or 8.3

glenngds2006
2007-11-09, 07:31 PM CST
Bugzilla came through for me. The answer is to use libata.dma=0 as a boot option

kadambi
2007-11-10, 09:42 AM CST
So, did it work for you?

glenngds2006
2007-11-10, 04:12 PM CST
Anyway everything eventually worked out for me as I am now running Fedora 8. Anyway for the newbies that are having the same problem what you do is to boot the Fedora 8 DVD and when it comes to a screen that gives options is to hit <TAB> and then enter <space>libata.dma=0 at the end of the text box that appears and then hit enter.

h.arpad
2007-11-15, 04:17 PM CST
Could you please give me a direct link to that Bugzilla page? I have only found relevant issues at https://bugzilla.novell.com/show_bug.cgi?id=331610 and I'm curious what the Fedora solution is (can be.)

craigmilleruk
2007-11-21, 04:34 AM CST
I've got a similar problem. 4 sata disks all 500Gb. 2 are Seagate Baracuda and 2 are Maxtor branded seagate baracuda's. Basically they are all the same disks apart from Maxtor sticks its own version of firmware on its disks. Anyway Fedora8 can see the Seagate disks but not the maxtor ones. This goes for both the 64bit and i386 versions. I tried running Suse 10.3 which saw all 4 disks but my raid stripe breaks on the Maxtor disks after a while. Think I'm going to get a couple more Seagate disks and see what happens when they are all identical. Weird problem though.

h.arpad
2007-11-21, 06:17 AM CST
Are you sure you have a SiS RAID controller? Because I tried with OpenSUSE 10.3 and it still couldn't handle my SATA HDD. :rolleyes: The problem is about you can't use your SATA drives _at all_ .

There is a kind of solution >>here (http://forums.fedoraforum.org/forum/showthread.php?t=171137&page=2) <<, by the way. It can work for you, too.