gigabyte k8ns on a sata 160gig seagate hdd, running a64 wiht teh latest iso i just downloaded from fedora.com for 64bit processors.


It can't read my hardrive, and it overs a list of alternatives drivers, none of which seem to relate to my brand of hdd at all. Can anyone tell me which one i should pick?

Seagate Barracuda and WD Raptor (SATA) runs fine under FC2.
till now, have no experience with FC3 and A64...

What chipset is the SATA controller ?
it will be in the motherboard instruction manual.

or, you could boot in rescue mode, and at a command line run "cat /proc/pci" or possably "lspci -a" and post the output here if you dont understand it.

I had the same problem with a Seagate SATA drive on an AMD 32 bit system. I have a MSI mother Board with Nforce 2 chipset and MCP-S southbridge chip that has Nvidia SATA native to the chip set. I tried using a Seagate Barracuda SATA drive with Fedora Core 3 and Anaconda would not recognize it at all. Anaconda recognized the NVIDIA SATA controller, but not the Seagate HD. BIOS recognized it. Windows XP Installer recognozed it. But Anaconda would not. I then used a SATA/PATA adapter on a Western Digital PATA hard drive and hooked it up to the SATA controller. Anaconda recognized the NVIDIA SATA controller, no drivers necessary, and then recognized the W.D. Hard drive. So I don't think it is a SATA controller / Core 3 compatibility problem. I think it is a Seagate SATA HD / Core 3 problem. More specifically, it seem to be an Anaconda / Seagate SATA Hard drive problem. I never did get the Seagate SATA HD to work.

My solution was to put Windows XP on that computer. BTW since the SATA controller is native to the chip set, Windows XP didn't need any drivers at all for the SATA hard drive. I then put Fedora Core 3 on my old ASUS A7N8X-Deluxe on a PATA drive. Not really what I wanted to do, but it solved the problem.

That Seagate Barracuda SATA with NCQ is really fast with the native SATA controller. I would eventually like to get Core 3 on that setup as I don't use Windows very much anymore. So I hope someone smarter than me can figure this out.

Pudge

so people heres solution is to by a new hardrive? and that is seagates fault? no its not! its fedoras. if the bios, and windows can pick up on it automatically surely fedora can figure it out!

Nobody said it was anybody's fault. I just said it SEEMS to be a compatibility problem between the Anaconda installer and Seagate SATA hard drives. But that has not been proven by any means. It's just been suggested as a possibility.

Pudge

I went through this thread again, and this time paid more attention to overlord73's post.
I thought ...Hmmmm, I wonder. So I inserted the first installation CD from Fedora Core 2 into my MSI computer and booted from it. Sure enough, overlord73 was right. The Fedora Core 2 installer went right through it's paces and properly recognized the Seagate Barracuda SATA drive, no problems.

Next I rebooted into the Fedora Core 3 DVD, and this is what happened in my case:
Just BEFORE the "CD Found" dialog box where it offers to Test your media, it came up with a box that said, "Loading SCSI Driver, sata_nv". This did NOT come up in Core 2. Next, I skipped testing my Media. Then I got a dialog box stating, : Warning, No hard drives have been found. You probably need to manually choose device drivers for the installation to succeed. Would you like to choose device drivers now?" I said yes. It again offered the "sata_nv" driver as a choice, I selected it. The installer went on, and said, "Running Anaconda" and brought up the GUI window. I clicked next, chose English, chose English again, I chose Workstation, I chose automatically partition, then I got a dialog box saying no drives were found. That was the end of the installation. I could go no farther.

So, same computer, same hardware, same Seagate SATA hard drive, everything the same except for Fedora Core 2 installer versus Fedora Core 3 installer. I think that prettty much proves where the problem is.

@unknownsoldier
I believe there was a AMD64 version of Fedora Core 2. Try booting from a Fedora Core 2 CD and see if it detects your Seagate on your AMD64 system. If it does, then MAYBE one way around this would be to install Fedora Core 2, then upgrade to Core 3? It MIGHT work, but I haven't tried it. I would much rather do a clean install of Core 3 as opposed to an upgrade from Core 2, but since the Core 3 installer isn't hacking it, this may be the only way. But, even with Fedora Core 2 on the hard drive, the Core 3 installer still might not recognize the hard drive again to do the upgrade. Who knows?

Pudge

output of lspi:


(11:01:54�michael@rizon)
[~ ]$ /sbin/lspci
00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
02:01.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
02:02.0 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem (rev 04)
02:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

output from dmesg of my sata:

(11:02:26�michael@rizon)
[~ ]$ dmesg | grep sd
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 sda6 > sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SELinux: initialized (dev sda3, type vfat), uses genfs_contexts
SELinux: initialized (dev sda4, type vfat), uses genfs_contexts
SCSI device sdb: 256000 512-byte hdwr sectors (131 MB)
sdb: assuming drive cache: write through
SCSI device sdb: 256000 512-byte hdwr sectors (131 MB)
sdb: assuming drive cache: write through
sdb: sdb1
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
ReiserFS: sda1: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sda1
sda2: rw=0, want=18, limit=2
ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 8, size 1024)
sda2: rw=0, want=130, limit=2
ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 64, size 1024)
ReiserFS: sda2: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sda2
ReiserFS: sda5: found reiserfs format "3.6" with standard journal
ReiserFS: sda5: using ordered data mode
ReiserFS: sda5: journal params: device sda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda5: checking transaction log (sda5)
ReiserFS: sda5: Using r5 hash to sort names
SELinux: initialized (dev sda5, type reiserfs), uses genfs_contexts

and that's on FC3 x86 though...

I've got the same problem.

Seagate 80gb sata
Gigabyte nforce3
Athlon64 3200+

Installer loads sata_nv, i manually select the hd and then it complains it can't find a place to install and exits.

I reported this as a bug to the Fedora Bugzilla as bug number 145263. I would suggest that anyone else having this problem go to Red Hat Bugzilla scroll down to "Simple Search" and enter 145263 in the search box and add your comment to the bug report.

Pudge

BTW, I never did list the hardware I am experiencing this problem with
MSI K7N2GM2-LSR Mother Board
Seagate ST3120827AS SATA Hard Drive

Pudge

seems pretty much the same setup as I have and same errors. I signed up for the bugzilla note, and am keeping my fingers crossed.

i had a linux friend come have a look. i had a secondary hdd plugged in at the time which was ide. Fedora clearly came up with how my drive was partitioned, event though it was sata. but apparantly the second drive was screwing something up and not allowing an install. Removed the ide drive and same problem. i gave up

It is also a problem with the SuSE 9.2 installer. Both installers find the SATA controller sata_nv but no drives! My config is a Gigabyte K8NS-939 with a Seagate 160GB. It is a new drive so I believe it has the NCQ feature (if that's significant.)

NOt just seagate. I have the same no hdd found with a supermicro X8DHE-G2 dual xeon nocona, 4gb ddr2 400, with 2 Western Digital 80gb drives. FC2 installs fine, not FC3.

poop
-jmral23