[SOLVED] This might be why I never bought Seagate drives before

This is my first Seagate for my array, 3TB from when they were 90 bucks.  Pre-cleared and everything was good.  Was Syncing parity as it was my first 3 TB.  It has run for seriously 24 hours.  It was going slow, 24MB/sec slow and I just left it.  Figured I would just wait the 19 more hours it wanted (2 hours ago).

 

I thought might as well check how it was going when I was greeted with

 

Jan 3 18:44:53 Tower kernel: md: disk0 write error

Jan 3 18:44:53 Tower kernel: handle_stripe write error: 4294967640/0, count: 1

 

Disk disabled...is it worth starting the sync again on this drive, or try another drive?

 

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967296, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967304, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967312, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967320, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967328, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967336, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967344, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967352, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967360, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967368, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967376, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967384, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967392, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967400, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967408, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967416, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967424, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967432, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967440, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967448, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967456, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967464, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967472, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967480, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967488, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967496, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967504, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967512, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967520, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967528, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967536, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967544, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967552, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967560, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967568, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967576, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967584, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967592, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967600, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967608, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967616, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967624, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967632, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967640, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: attempt to access beyond end of device

Jan  3 18:44:53 Tower kernel: sdf1: rw=1, want=4294967648, limit=4294967295 (Drive related)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967288/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967296/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967304/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967312/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967320/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967328/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967336/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967344/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967352/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967360/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967368/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967376/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967384/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967392/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967400/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967408/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967416/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967424/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967432/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967440/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967448/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967456/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967464/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967472/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967480/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967488/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967496/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967504/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967512/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967520/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967528/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967536/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967544/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967552/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967560/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967568/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967576/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967584/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967592/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967600/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967608/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967616/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967624/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967632/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: disk0 write error (Errors)

Jan  3 18:44:53 Tower kernel: handle_stripe write error: 4294967640/0, count: 1 (Errors)

Jan  3 18:44:53 Tower kernel: md: md_do_sync: got signal, exit... (unRAID engine)

Jan  3 18:44:53 Tower kernel: md: recovery thread sync completion status: -4 (unRAID engine)

Jan  3 18:44:53 Tower kernel: md: recovery thread woken up ... (unRAID engine)

Jan  3 18:44:53 Tower kernel: md: recovery thread has nothing to resync (unRAID engine)

hmmm...doing some more digging and it appears my issue might actually be with 3TB drive support.

 

thoughts?

Please post full system log, or email to me [email protected]

Are you running early 5 or 4.7? Might be you are running a version that doesn't support 3 TB drives?

I believe I jumped the gun on attacking Seagate right away.  I think I was misled by the fact that unRAID was identifying my drive as 3TB and took this as them being supported.

 

The mobo is an Gigabyte GA-MA74GM-S2, which it seems has no support (if I understand it I need UEFI to support 3TB)

I have an AOC-SAT2-MV8 which I also believe has no support for 3TB.  I called SuperMicro and they confirmed this.

 

So, I assume my next option is an M1015 upgraded to p11 and then the newest P14.  If this is the supported route, I would need the SAS to SATA cable with which I ask what length is good.  While currently I do not yet have a Norco 4224, it is an obvious path beyond 10 drives for me, unless something else comes along.  Is the appropriate cable length .75m, such as this, http://www.monoprice.com/products/product.asp?c_id=102&cp_id=10254&cs_id=1025406&p_id=8187&seq=1&format=1#largeimage

 

thanks!

 

 

The mobo is an Gigabyte GA-MA74GM-S2, which it seems has no support (if I understand it I need UEFI to support 3TB)

EFI is only needed if you want to boot from a 3TB drive. You're booting from a USB flash drive.

OK, but otherwise still my mobo needs to list support for 3TB right?

The mobo is an Gigabyte GA-MA74GM-S2, which it seems has no support (if I understand it I need UEFI to support 3TB)

 

I have 3 x 3T drives connected to my ECS A740GM-M motherboard so the 740G chipset supports 3T drives just fine.

No use speculating.  Please try to reproduce the problem, and then post the system log.  Without the log, it's impossible to say what  might be wrong.

OK, I will crash the car this weekend.  Last night I had put back my old 2TB parity and told it to rebuild in fear of leaving the array unprotected.  I will do this this weekend and post the log for a full review.

 

Thanks

OK, I will crash the car this weekend.  Last night I had put back my old 2TB parity and told it to rebuild in fear of leaving the array unprotected.  I will do this this weekend and post the log for a full review.

 

Thanks

Thank you, much appreciated.  Please also make a note of the steps you take.

You can get all the fancy hardware like motherboards, harddisk controllers and all. But if you use a unraid version that doesn't support 3TB disks then you end up with a server without 3 TB support. A chain is as strong as the weakest link.

 

My first unraid server was built in a HP EX490 WHS case. Under WHS that came with HP never said it would support 3 TB drives. Unraid 5.0b12a worked fine with 3 TB disks.

You are using Gigabyte motherboard with with SEVEN different hardware revisions. The earlier ones have a BIOSes that are susceptible to the HPA bug- adding a controller, or a disk may result of a copy of the motherboard BIOS written somewhere on some disk resulting in smaller size.

 

You may be suffering from this one.

 

 

Vendors will only report what they have tested. It does not mean that 3T drive won't work, only that the vendor has not tested the configuration. Supermicro does make the components used in their products so they don't know the full capabilities. The AOC-SAT2-MV8 is an old model that Supermicro is not going to test with 3T drives. I have a AOC-SAT2-MV8 and I'm pre-clearing a 3T drive on it currently. I'll let you know how it goes.

 

 

yeah, no idea why they need 7 revisions, but luckily I have the second and to the best of my knowledge bit the whole HPA thing in the butt, having cleared it from a bunch of my drives, so lets hope that is not it.

 

I am running the latest beta, so 3TB support is there with unRAID.

 

Tonight, I did this;

 

1. stopped the new parity build on the old 2TB parity drive

2. re-named the extra folder, disabling the plugins

3. commented out the unmenu stuff

4. shut down

5. installed new 3TB and rebooted

6. told unraid of the new parity drive replacing the missing one

7. started the array and sync

 

One question I have is, should I have started in maintenance mode?

Another is do I need to do anything special with the partition format?

default is set to MBR 4k alligned, for the longest time I was doing WD drives with the advanced formatting.  Most recently was the addition of the hitachi drive and I did nothing special, I think all is well, but now I question my doings.

 

The seagate 3TB I am adding is showing GPT: 4K-aligned

 

parity is rebuilding now, attached is the current syslog given the current state of things.

 

 

syslog.zip

Unless I'm confused, the drives >2T do not utilize that MBR alignment setting so it doesn't matter. At any rate, using 4k-aligned works for any drive except WD drives with the alignment jumper.

which I believe is how I have it.  jumpered drives are MBR: unaligned

yeah, no idea why they need 7 revisions, but luckily I have the second and to the best of my knowledge bit the whole HPA thing in the butt, having cleared it from a bunch of my drives, so lets hope that is not it.

 

I am running the latest beta, so 3TB support is there with unRAID.

 

Tonight, I did this;

 

1. stopped the new parity build on the old 2TB parity drive

2. re-named the extra folder, disabling the plugins

3. commented out the unmenu stuff

4. shut down

5. installed new 3TB and rebooted

6. told unraid of the new parity drive replacing the missing one

7. started the array and sync

 

One question I have is, should I have started in maintenance mode?

Another is do I need to do anything special with the partition format?

default is set to MBR 4k alligned, for the longest time I was doing WD drives with the advanced formatting.  Most recently was the addition of the hitachi drive and I did nothing special, I think all is well, but now I question my doings.

 

The seagate 3TB I am adding is showing GPT: 4K-aligned

 

parity is rebuilding now, attached is the current syslog given the current state of things.

 

Everything in the system log looks exactly right, including the various sizes.  What rate are you getting for parity-sync?  Obviously it will take a while for this to finish.  If you don't mind, let it run and if you see the same errors get generated, please post back here, or better yet send me an email so we can figure out why this is happening (btw this is the first case of this happening that I'm aware of).

[email protected]

 

The sync is the worst part, 22-23 mb/sec...2000 minutes. Left 9%in

The sync is the worst part, 22-23 mb/sec...2000 minutes. Left 9%in

 

I notice from the log you have a pretty weak CPU.  What motherboard do you have?  The low parity-sync rate is probably due to memory bandwidth limit.

Running an AOC-SAT2-MV8 in a PCI slot will be very slow. It is a PCI-X card and will support only a single drive in a PCI slot with good speed. In a PCI-X slot it works well, but motherboards with PCI-X are no longer manufactured.

 

My pre-clear of a 3T drive with a AOC-SAT2-MV8 in a PCI-X slot has completed the pre-read and is zeroing at 81MB/s. This is about the speed of a parity check with this system.

The sync is the worst part, 22-23 mb/sec...2000 minutes. Left 9%in

 

I notice from the log you have a pretty weak CPU.  What motherboard do you have?  The low parity-sync rate is probably due to memory bandwidth limit.

 

It is a sempron 140. Memory is 1gb I think. Had some go bad but couldn't justify the high ddr2 prices.  Been debating he upgrade path to get ddr3 support and support for 2 m1015 PCI e cards to replace the mentioned PCI x card as mentioned performance can be bad...

 

I guess I know what to do if this completes OK this time.

The Sempron and the memory are fine. The PCI slot is the bottleneck. If you get a PCI-eX4 (or higher) card, e.g., AOC-SASLP-MV8, the parity check/build speeds will increase dramatically (~4X). The AOC-SAT2-MV8 can still be used in a PCI slot for a single drive without issue. The AOC-SAT2-MV8 are selling for $27 on e-bay so you may as well keep it.

Or get a board with PCI x eh?

Or get a board with PCI x eh?

 

If you can find one with CPU and RAM for less than $50. Otherwise, it makes more sense to get a new SATA card.