Xfx 8300 - motherboard - Success!!!


Recommended Posts

This board is really nice, but the onboard SATA doesnt  [shadow=red,left]does now[/shadow] work with unRAID.  ;D bios 1.6 installed, all working correctly...

 

Is identified as MCP78S which is the XFX 8200 (MCP78S) chipset. Board boots fine with no SATA devices attached, boots windoze OK, in IDE and AHCI modes. MEMTest passed with flying colours. 

 

Unfortunately unRAID doesnt see the SATA devices. Also the onboard SIL3132 isnt seen.

Real shame  [glow=red,2,300]nice[/glow] as this board is a really good bit of kit.

 

Fast too. generating parity at just under 60MB/s (only 15% complete but this is faster than the Abit A-S78H ever did avg 38MB/s). Will post syslog when done.

 

Sep 29 17:16:35 Tower kernel: scsi1 : ahci

Sep 29 17:16:35 Tower kernel: scsi2 : ahci

Sep 29 17:16:35 Tower kernel: scsi3 : ahci

Sep 29 17:16:35 Tower kernel: scsi4 : ahci

Sep 29 17:16:35 Tower kernel: scsi5 : ahci

Sep 29 17:16:35 Tower kernel: scsi6 : ahci

Sep 29 17:16:35 Tower kernel: ata1: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76100 irq 28

Sep 29 17:16:35 Tower kernel: ata2: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76180 irq 28

Sep 29 17:16:35 Tower kernel: ata3: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76200 irq 28

Sep 29 17:16:35 Tower kernel: ata4: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76280 irq 28

Sep 29 17:16:35 Tower kernel: ata5: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76300 irq 28

Sep 29 17:16:35 Tower kernel: ata6: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76380 irq 28

 

Oct 11 00:12:07 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Oct 11 00:12:07 Tower kernel: ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01118, max UDMA7

Oct 11 00:12:07 Tower kernel: ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)

Oct 11 00:12:07 Tower kernel: ata1.00: configured for UDMA/133

Oct 11 00:12:07 Tower kernel: scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Oct 11 00:12:07 Tower kernel: sda: sda1

Oct 11 00:12:07 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk

 

Sep 29 17:16:35 Tower kernel: ata1.00: qc timeout (cmd 0xec)

Sep 29 17:16:35 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Sep 29 17:16:35 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 29 17:16:35 Tower kernel: ata1.00: qc timeout (cmd 0xec)

Sep 29 17:16:35 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Sep 29 17:16:35 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps

Sep 29 17:16:35 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Sep 29 17:16:35 Tower kernel: ata1.00: qc timeout (cmd 0xec)

Sep 29 17:16:35 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Sep 29 17:16:35 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Link to comment
  • 2 weeks later...

Well it has passed level one, it is considerably faster than the abit also, 56MB/s, vs 38MB/s for the same array, it also has less memory, not that should affect parity performance.

 

Oct 11 04:59:37 Tower kernel: md: sync done. time=17172sec rate=56881K/sec

Oct 11 04:59:37 Tower kernel: md: recovery thread sync completion status: 0

 

Going to run a parity check to see if that is faster a well.

 

 

Link to comment

Hdparam -tT figures for the sammy hdds, are in the same ballpark, 110MB/s. The seagates 500GB are up to 75MB/s from 65MB/s.

 

Parity check looks to be faster as well, holding 100MB/s (only done 5% so far).

 

Oct 11 05:20:13 Tower kernel: md: using 1152k window, over a total of 976762552 blocks.

Oct 11 08:45:37 Tower kernel: md: sync done. time=12324sec rate=79256K/sec

Oct 11 08:45:37 Tower kernel: md: recovery thread sync completion status: 0

 

Re-running with force ncq disabled to see if that makes any difference.

 

Guess that will be a no then,

 

Oct 11 13:46:20 Tower kernel: md: recovery thread checking parity...

Oct 11 13:46:20 Tower kernel: md: using 1152k window, over a total of 976762552 blocks.

Oct 11 17:11:39 Tower kernel: md: sync done. time=12319sec rate=79289K/sec

Oct 11 17:11:39 Tower kernel: md: recovery thread sync completion status: 0

 

 

 

 

 

 

 

 

 

Link to comment
  • 1 month later...

Level Two testing completed.

 

Partity check at the beginning middle and end of the month. No errors. No problems. Six disks tested as per the testing requirements. 75GB copied to the array, 4TB available array (3x1TB, 2x500GB, 1TB partity).

 

Syslog attached.

 

Both unraid 4.5b7 and the hardware have behaved impecably.

 

XFX8300 + AMD Sempron LE-1200 AMD CPU.

2GB DDR2 800Mhz DRAM - Toshiba

Marvel Yukon Ultra 2 Gb NIC

4 Samsumg 1TB HD103UJ

2 Seagate 500GB ST3500630AS

SIL 3124 PCI SATA (not used currently)

Kingston Data Traveller II USB

 

 

 

   

Link to comment
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.