LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   MSI K8N Neo2 Platinum SATA (https://www.linuxquestions.org/questions/linux-hardware-18/msi-k8n-neo2-platinum-sata-507492/)

DaveQB 12-04-2006 05:22 PM

MSI K8N Neo2 Platinum SATA
 
I bought this mobo second hand, but nothing was mentioned that there was anything wrong with it, doesn't mean there isn't. So trying to work out if it is hardware or simply a BIOS setting/update in need.

My problem is the SATA1 and SATA2 ports. SATA3 and SATA4 work fine. I have tried cables and HDD's that work flawlessly on ports 3 and 4 on ports 1 and 2 and get these errors.


Code:

[17179688.416000] sda: Current: sense key: Aborted Command
[17179688.416000]    Additional sense: Scsi parity error
[17179688.416000] Info fld=0x30af
[17179688.416000] end_request: I/O error, dev sda, sector 12463
[17179688.416000] Buffer I/O error on device sda1, logical block 1550
[17179688.416000] lost page write due to I/O error on sda1
[17179688.624000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179688.624000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179688.624000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179688.812000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179688.812000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179688.812000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179689.004000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179689.004000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179689.004000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179689.192000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179689.192000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179689.192000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179689.384000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179689.384000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179689.384000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179689.576000] ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
[17179689.576000] ata1: status=0x51 { DriveReady SeekComplete Error }
[17179689.576000] ata1: error=0x84 { DriveStatusError BadCRC }
[17179689.576000] sd 0:0:0:0: SCSI error: return code = 0x8000002

Maybe a different controller for 1 and 2 compared to 3 and 4 ?
Well a lshw gives me these key information.

Code:

*-ide:1
            description: IDE interface
            product: CK8S Serial ATA Controller (v2.5)
            vendor: nVidia Corporation
            physical id: 9
            bus info: pci@00:09.0
            logical name: scsi0
            logical name: scsi1
            version: a2
            width: 32 bits
            clock: 66MHz
            capabilities: ide bus_master cap_list scsi-host
            configuration: driver=sata_nv
            resources: ioport:9e0-9e7 ioport:be0-be3 ioport:960-967 ioport:b60-b63 ioport:cc00-cc0f io
port:d000-d07f irq:177
        *-ide:2
            description: IDE interface
            product: CK8S Serial ATA Controller (v2.5)
            vendor: nVidia Corporation
            physical id: a
            bus info: pci@00:0a.0
            logical name: scsi2
            logical name: scsi3
            version: a2
            width: 32 bits
            clock: 66MHz
            capabilities: ide bus_master cap_list scsi-host
            configuration: driver=sata_nv
            resources: ioport:9f0-9f7 ioport:bf0-bf3 ioport:970-977 ioport:b70-b73 ioport:e400-e40f io
port:e800-e87f irq:185

Notice bus info lines and the logical name line. So the "bad" SATA controller is on bus pci@00:09.0 and the "good"


Code:

0000:00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
0000:00:09.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)
0000:00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)

So I can't see why there would be any software issue with the kernel, modules and the 2 SATA controllers.

So my conclusion is either a mis-config in the BIOS [searched high and low last night until 3am trying different settings with IDE,SATA and RAID options on and off] or a faulty SATA controller ?

Maybe a BIOS update ?

Anyone who has used this board, can you shed your experiences on this. Thanks.

DaveQB 01-02-2007 11:51 PM

The problem here seems to be with the board and overclocking. Apparently SATA3 and SATA4 are PCI bus locked but SATA1 & SATA2 are not.

So I either have to bring my overclock back [no way!]
or buy a PCI SATA card, which I have [eBay $20 for 3 SATA and 1 PATA ports]

Go figure.


All times are GMT -5. The time now is 07:31 AM.