Go Back   nV News Forums > Linux Support Forums > General Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 03-21-09, 10:06 PM   #1
prm
Registered User
 
Join Date: Mar 2009
Posts: 1
Default Problem w/ SATA, nforce430, fedora 10 x86_64

Im new here.
I have a Gigabyte motherboard with an nForce430 SATA2/RAID chipset.

I just switched my os from windows 2003 64 to fedora 10 x86_64 (2.6.27.19-170.2.35.fc10.x86_64). Im having issues with the SATA controller that I never experienced with windows.

Im not running raid, neither mdraid or through the bios.
I have 4 new SATA2 drives w/ new SATA2 cables.
my OS is installed a on a regular IDE drive.
I didnt have a problem with linux not detecting the SATA drives; it has always managed to detect&load the sata_nv module during boot (version 3.5, I believe).

The drives apparently work fine, they correctly mount at boot with no apparent errors showing up in dmesg output. SMART tests pass with no errors on all four drives.

The problems occur with high IO on 1 or more drives; a heavily used drive (or drives) will completely hang, and the process that caused the IO will also hang; I cannot even kill the process once this occurs. The drive will still be visible to the system, yet it simply wont respond/function properly. I can even 'cd' into a directory mounted on the drive(s), but running 'ls' will just sit there & hang. At this point, Im forced to reboot, after which the drives come back online again, and work fine, until I start placing heavy loads on them.

More specifically, Im running mysql, with one drive dedicated to the database store, and another dedicated to indexes. on a heavy index creation for a 2.5GB database, the drives will apparently hang/die about half way through the index ops. mysql will show the index operation as "DEAD" since its completely lost/locked up waiting for the drive to respond.

I believe this to be a driver issue, since I never experienced this with windows. I ran 2 bios-based raid-0 arrays under windows and placed very high loads and never had the drives just hang as they are doing now.

Ive read elsewhere about issues with the sata_nv module, and how it might be prefered to run 'ahci' instead, though I dont know if this also applies to the older nforce430 chipset. Ive also read about problems with ncq related to the sata_nv driver, but they seemed somewhat dated/old, so I dont know if this could even be an issue anymore.

My basic questions:
has anyone else experienced anything like this? Is this a known issue?
Should I upgrade or replace the sata_nv driver that shipped with my fedora 10 x86_64 distro?
Can I, or should I, run "ahci" instead, and how would I go about setting this up?
Is there anything else I can try ?
Could this be an issue with the x86_64 kernel, or should sata_nv work fine with this type of kernel?

Im not very experienced with linux, so please let me know what diagnostic output I should provide.

For now, here's output from lspci:

00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6150SE nForce 430 (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

dmesg | grep ata

BIOS-e820: 00000000dbff3000 - 00000000dc000000 (ACPI data)
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
PERCPU: Allocating 65184 bytes of per cpu data
Memory: 3990884k/4718592k available (3307k kernel code, 137432k reserved, 1840k data, 1296k init)
libata version 3.00 loaded.
Write protecting the kernel read-only data: 4752k
pata_amd 0000:00:06.0: version 0.3.10
pata_amd 0000:00:06.0: setting latency timer to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
ata1.00: HPA detected: current 156299375, native 156301488
ata1.00: ATA-6: WDC WD800BB-00JHC0, 05.01C05, max UDMA/100
ata1.00: 156299375 sectors, multi 16: LBA
ata1.01: ATAPI: ATAPI iHAP122 8, UL02, max UDMA/66
ata1: nv_mode_filter: 0x3f39f&0x3f01f->0x3f01f, BIOS=0x3f000 (0xc6c50000) ACPI=0x3f01f (20:30:0x1f)
ata1: nv_mode_filter: 0x1f39f&0x1f01f->0x1f01f, BIOS=0x1f000 (0xc6c50000) ACPI=0x1f01f (20:30:0x1f)
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/66
ata2: port disabled. ignoring.
pata_acpi 0000:00:08.0: PCI INT A -> Link[APSI] -> GSI 21 (level, low) -> IRQ 21
pata_acpi 0000:00:08.0: setting latency timer to 64
pata_acpi 0000:00:08.0: PCI INT A disabled
pata_acpi 0000:00:08.1: PCI INT B -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
pata_acpi 0000:00:08.1: setting latency timer to 64
pata_acpi 0000:00:08.1: PCI INT B disabled
EXT3-fs: mounted filesystem with ordered data mode.
sata_nv 0000:00:08.0: version 3.5
sata_nv 0000:00:08.0: PCI INT A -> Link[APSI] -> GSI 21 (level, low) -> IRQ 21
sata_nv 0000:00:08.0: setting latency timer to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xd000 irq 21
ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xd008 irq 21
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-7: SAMSUNG HD160JJ, ZM100-41, max UDMA7
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: WDC WD3200AAJS-00VWA0, 12.01B02, max UDMA/133
ata4.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
sata_nv 0000:00:08.1: PCI INT B -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
sata_nv 0000:00:08.1: setting latency timer to 64
scsi4 : sata_nv
scsi5 : sata_nv
ata5: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe400 irq 20
ata6: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe408 irq 20
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-7: SAMSUNG HD160JJ, ZM100-41, max UDMA7
ata5.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata5.00: configured for UDMA/133
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: ATA-7: SAMSUNG HD160JJ, ZM100-41, max UDMA7
ata6.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata6.00: configured for UDMA/133
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: mounted filesystem with ordered data mode.
Modules linked in: ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand powernow_k8 freq_table dm_multipath 8139cp snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device k8temp 8139too sata_nv mii ppdev snd_pcm_oss snd_mixer_oss parport_pc snd_pcm firewire_ohci snd_timer snd_page_alloc snd_hwdep hwmon snd soundcore firewire_core crc_itu_t parport i2c_nforce2 i2c_core forcedeth pcspkr floppy ata_generic pata_acpi pata_amd [last unloaded: scsi_wait_scan]


please help, thanks...
prm is offline   Reply With Quote
Old 03-22-09, 01:17 PM   #2
Dizzle7677
Registered User
 
Dizzle7677's Avatar
 
Join Date: May 2008
Location: Relativity
Posts: 194
Default Re: Problem w/ SATA, nforce430, fedora 10 x86_64

Things off the top of my head ....

Check that the power/SATA-IDE cables are correct and solidly in place also that they're the right type. I have this type of bug sometimes when I don't get the power cables to my drives in the just right position. One will bomb out under high load. Is the power supply wattage enough for all the drives? The scsi_mod isn't getting along with sata_nv/pata_amd/libata somewhere or vice-versa.

Upgrade to XFS version 2 from Ext3 for better performance and defrag ability.
__________________
Elephants can fly but they have no reason to.
------------------------------------------
Phenom II X3 720 @ 3.5Ghz | Asus M4A785-M | 2 Gig Crucial DDR2 @ 960 Mhz | GeForce GT 440 1024 MB | Linux 3.6.1 / Ubuntu 12.04 / W.I.N.E v1.5.14
Dizzle7677 is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 05:21 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.