Jump to content

[SOLVED] for now - slow web response, flatout doesnt work, before I give up...


GoZags

Recommended Posts

Not sure what is going on.  I thought I had the kinks out and the system was running correctly but apparently not.  This is my last go at unRAID before I dump it for FreeNAS, Windows Home server or whatever else is out there.

 

I have 4 2TB EARS drives, plus a 80gb barracuda as a cache (only part that works well, R/W to the cache seems fast).  All new drives, ordered from two locations, two have been RMA'd because they were slow to preclear and then one had a SMART error.  I can order 250 machines from Dell at work (and I do) and not one will have a bad HDD out of the box, but whatever...

 

I have attached the syslog, the errors that stand out are:

Sep 13 20:14:48 Tower kernel: ata7.00: status: { DRDY ERR }
Sep 13 20:14:48 Tower kernel: ata7.00: error: { ABRT }
Sep 13 20:14:48 Tower kernel: ata7.00: configured for UDMA/66
Sep 13 20:14:48 Tower kernel: ata7: EH complete
Sep 13 20:14:48 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 13 20:14:48 Tower kernel: ata7.00: BMDMA2 stat 0x686d0009
Sep 13 20:14:48 Tower kernel: ata7.00: failed command: READ DMA
Sep 13 20:14:48 Tower kernel: ata7.00: cmd c8/00:00:f0:56:04/00:00:00:00:00/e0 tag 0 dma 131072 in
Sep 13 20:14:48 Tower kernel:          res 51/04:00:f0:56:04/00:02:00:00:00/e0 Emask 0x1 (device error)
Sep 13 20:14:48 Tower kernel: ata7.00: status: { DRDY ERR }
Sep 13 20:14:48 Tower kernel: ata7.00: error: { ABRT }

 

And the fact that going from page to page on the web interface and bringing up unMenu takes anywhere between 10-30 seconds each. After a reboot its quick, for a bit - but then it is back to it's normal slow response.

 

I also attached a screen cap from unMenu that shows some errors.

 

A broader question:

Is it always so difficult?  I have bought all new gear based off the approved hardware listed.  The 'machine' runs fine. Loaded Win 7 on it just to see and everything loaded fine, drivers for my SATA cards went on fine, the drives could be formatted and written and read to just fine, including the ones that took 48 hours to preclear in unRAID.

 

I replaced the SATA cables, relaxed the power being pulled from the PSU by removing empty drive carriages (and their prospect fans) and just ran the 4 drives in my array, still the same issue.  In fact all the SATA cables came from desktops that had been in use for years. BIOS on MB and SATA controllers are fine (in fact, haven't even GOTTEN to the SATA cards - the MB runs 6 drives by itself).  Confirmed AHCI, etc, etc, etc.  Defaulted the BIOS settings, no luck (no new BIOS version, unfortunately).

 

The ONLY thing I haven't done is wiped out the unRAID config on the flash drive or jumped to a beta (4.7)... frankly, all I read on the board are problems people have with beta versions, etc - instead of being on the bleeding edge. How would I go about doing that?  My array is useless, in reference to data - still got everything on loose drives, DVD and another box - so I can start over, no problem.  Would love suggestions.

 

I think that if I had just tried the 3 drive version I would probably have chalked it up to something that didnt work for me and moved on, but unfortunately I jumped in with both feet and bought the full license.

 

 

 

 

 

image.gif.04dad80182ac9f89a64476172e1242de.gif

Untitled.pdf

Link to comment

Hello,

 

Sorry to hear about all the trouble you are having.

 

I can tell you that I began researching unRaid last summer by reading the forums for about 3 months before deciding that this is the system I wanted to try.  I am using it to serve up about 1000 movies and for file backups.  I used a configuration I found from one of the users and when I got home last fall I ordered it all. I have built a few computers in my time so that part was easy. I bought the pro license and the two key option. Spent 3 months ripping movie collection and storing on unRaid without parity drive. After all data burned added parity drive and it's been running smooth since then.

 

The only issues I have seen have been a buggy on board LAN connection that caused me some headaches until I intalled an intel nic that solved some very strange issues for little cost and little time. The other issue was when I had reused a sata cable that was flaky.  Replaced it and all is well.

 

Whenever I have had questions this board has always helped either by step by step directions or by searching for related issues from other members.

 

I work away from home the entire summer every year so this system has to work without fail for the wife. I remotely monitor the system to keep an eye on drive status and monthly parity checks. System consists of 6 seagate 2 tb drives. Pre clear times are 24 hrs each. Monthly parity checks are about 5.5 hours. I keep the second USB key ready with an exact copy of the original and I tested it before leaving home and showed wife how to swap. Also have a spare seagate drive that is pre cleared standing by.

 

I realize this info might not help you but I wanted to show you that the system does work and that it can run unattended for months with high reliability. Having it hooked to a solid UPS is also a must. I know that at home we have had 23 power blips since I left. I will not get to see or use my system for another month. Wife uses it every day for streaming movies to tv and iPad.

 

I am using 4.7 by the way but started with an earlier version and upgrade before leaving home in June. Speeds have always been high. Could stream to tv and watch movies on two iPads at same time.

 

I know that for the money spent this is the best way to finally make my movie library available to all in the house and even to me while away from home.

 

Don't give up yet. I can get you a list of the hardware I used if it would help.

 

Have a good one,

 

Jim S.

Link to comment

Yeah stick with it a little bit more, its great when its running :).

Also keep in mind you are going to have hardware issues wtih freenas (freebsd) or zfs on solaris too...  your sas card won't work with them for one..

They are even more fussy about hardware....

 

Hardware is an issue with all these systems.. the weakest point.. but usually things can be sorted out eventually :)

Someone will know what is wrong I am sure.  I had to use a beta straight off because my network card wasn't supported in the release version but have had no issues with the beta 11..

I went to 12 and 12a and things went downhill but 11 seems pretty nice, i mean no harm in trying it if things arent working at all now anyway :)

 

 

 

Link to comment

 

I have 4 2TB EARS drives, plus a 80gb barracuda as a cache (only part that works well, R/W to the cache seems fast). 

 

 

May want to reconsider as that is the drive that is giving you the errors.  I would do a few things.  First smart report on the cache drive; check connections from the drive to the MV8, then move the drive to an onboard port.

Link to comment

Thanks for the responses, guys. Truthfully I was just livid last night when I went to use it and it was all over the place performance-wise.

 

So it is the 80gb acting up then?  I have difficulty with the syslog, not all the references make sense to me yet. I can ditch it.  I was trying to get fancy so I could (ultimately) do some photo backups and some DVR recordings during the day at quick clip.  I will try that next.

 

Is there a way to see what plugins are using what resources?

Link to comment

Your 80 GB drive is only connected at 1.5 GB (SATA 1) is that all the drive supports or is there a jumper on it limiting the speed?

 

---------------------------------------------

Sep 13 19:58:51 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113

SControl 310)

Sep 13 19:58:51 Tower kernel: ata7.00: ATA-7: WDC WD800ADFS-75SLR2, 21.07Q21

---------------------------------------------

 

Does also appear to be a problem with that drive as was mentioned previously:

 

---------------------------------------------

Sep 13 19:58:51 Tower kernel: sd 8:0:0:0: [sdf] 156250000 512-byte logical

blocks: (80.0 GB/74.5 GiB)

Sep 13 19:58:51 Tower kernel: ata8: link is slow to respond, please be

patient (ready=-19)

Sep 13 19:58:51 Tower kernel: ata8: COMRESET failed (errno=-16)

Sep 13 19:58:51 Tower kernel: ata8: link is slow to respond, please be

patient (ready=-19)

Sep 13 19:58:51 Tower kernel: ata8: COMRESET failed (errno=-16)

Sep 13 19:58:51 Tower kernel: ata8: link is slow to respond, please be

patient (ready=-19)

Sep 13 19:58:51 Tower kernel: ata8: COMRESET failed (errno=-16)

Sep 13 19:58:51 Tower kernel: ata8: COMRESET failed (errno=-16)

Sep 13 19:58:51 Tower kernel: ata8: reset failed, giving up

Sep 13 19:58:51 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0

action 0x0

Sep 13 19:58:51 Tower kernel: ata7.00: BMDMA2 stat 0x686c0009

Sep 13 19:58:51 Tower kernel: ata7.00: failed command: READ DMA

Sep 13 19:58:51 Tower kernel: ata7.00: cmd c8/00:20:c8:2e:50/00:00:00:00:00/

e9 tag 0 dma 16384 in

Sep 13 19:58:51 Tower kernel: res 51/04:20:c8:2e:50/00:00:00:00:00/

e9 Emask 0x1 (device error)

Sep 13 19:58:51 Tower kernel: ata7.00: status: { DRDY ERR }

Sep 13 19:58:51 Tower kernel: ata7.00: error: { ABRT }

Sep 13 19:58:51 Tower kernel: ata7.00: configured for UDMA/100

 

Sep 13 20:07:01 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0

action 0x0

Sep 13 20:07:01 Tower kernel: ata7.00: BMDMA2 stat 0x686d0009

Sep 13 20:07:01 Tower kernel: ata7.00: failed command: READ DMA

Sep 13 20:07:01 Tower kernel: ata7.00: cmd c8/00:00:60:44:04/00:00:00:00:00/

e0 tag 0 dma 131072 in

Sep 13 20:07:01 Tower kernel: res 51/04:00:60:44:04/00:00:00:00:00/

e0 Emask 0x1 (device error)

Sep 13 20:07:01 Tower kernel: ata7.00: status: { DRDY ERR }

Sep 13 20:07:01 Tower kernel: ata7.00: error: { ABRT }

Sep 13 20:07:01 Tower kernel: ata7.00: configured for UDMA/100

Sep 13 20:07:01 Tower kernel: ata7: EH complete

Sep 13 20:07:01 Tower kernel: ata7: drained 32768 bytes to clear DRQ.

Sep 13 20:07:01 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0

action 0x6 frozen

Sep 13 20:07:01 Tower kernel: ata7.00: failed command: READ DMA

Sep 13 20:07:01 Tower kernel: ata7.00: cmd c8/00:00:60:46:04/00:00:00:00:00/

e0 tag 0 dma 131072 in

Sep 13 20:07:01 Tower kernel: res ff/ff:ff:ff:ff:ff/00:00:00:00:00/

ff Emask 0x2 (HSM violation)

Sep 13 20:07:01 Tower kernel: ata7.00: status: { Busy }

Sep 13 20:07:01 Tower kernel: ata7.00: error: { ICRC UNC IDNF ABRT }

Sep 13 20:07:01 Tower kernel: ata7: hard resetting link

Sep 13 20:07:01 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113

SControl 310)

Sep 13 20:07:01 Tower kernel: ata7.00: configured for UDMA/100

---------------------------------------------

 

I'd definitely disconnect that 80 gb drive and try it again

 

Link to comment

The drive is older, I got a box full of them - so maybe that one is acting up.  The RAID card is just a $15 -port from NewEgg (PCI not PCIe). The other one, a SY-VIA-150R based card didn't work for me for some reason (using various drives).  It was on the list, but maybe there was a compatibility issue between my board, the SATA card and unRaid (it would show up in post though, so I would lean to unraid). Raj or somebody recommended the one I have now (basically a whitebox item, brandless). It doesn't have jumpers, but it does have a BIOS and it was a little flaky, not seeing the HDD on the first couple boots. Reseated, reseated the sata cable (swapped it) and it came up in POST and then in unRAID.  It's actually my '15th' drive - I only put the cache on that card so I could put it in the last drive bay (3 bays with 5 slots).  At this point I don't care - 14 drives is/will be enough.

 

Regardless of the cache drive though I have always got terrible preclear times (well 2 went quick, 2 went slow - a couple I did more than once as a test) and that was with the drives on the Mobo ports (using the first 4 of 6 total, haven't gotten to the SAS card) or if I used the SAS card. 

 

 

Link to comment

Best to take the problems 1 at a time... You stated the web interface would take a long time to come up and moving from page to page is slow.  Have you tried it again with the cache drive removed? 

 

Concerning the preclears, while it can take a long time (over 24 hours) to check a 2 TB drive, its best to find out at the beginning if they are suspect, rather than after you have data on them.  How long did it take to run your preclears?  Do you have the jumper on or off on those EARS drives?

 

As far as problems running Unraid, only one I had was when I added drives 5 & 6 (onboard).  That was because the controller for those ports shared an IRQ with the onboard nic and the server would lock up during large file transfers.  As the other poster stated, adding a dedicated Intel nic solved that issue.

Link to comment

According to your signature you are using an AMD Sempron 140 Sargas 2.7GHz and according to the syslog this is transformed into AMD Phenom II X2 545 Processor

stepping 02.

 

1.Have you messed around with the cores? This is one way to end with the instability...

And do not forget about the memtest here...

 

2.The 80GB drive is toasted or does not work well with the controller where is is attached. Try without cache drive.

Link to comment

bcb,

Yes, a buddy who plays with OC'ing was showing me when we had the Windows 7 install.  We put it back, but maybe not all the way.  I am not familiar with those settings (I don't bother, normally) but I can take a look at either default the whole setup (easiest, but I am pretty sure I set optimal defaults previously...) or roll those settings back.  Just to get a baseline it should be set back to normal, so I will, but I only ever had this working ok after those changes (decent r/w speeds). 

 

The 2nd SATA and cache drive should probably come out, problems seem to be tied to that drive.

 

Also, I have the NIC off and am using an Intel 10/100/1000 card (couple years old)... but that seemed to improve things (transfer speed).

 

I will try those things this evening, maybe start a mem test in the AM.  I will be interested to see if it's just that push to get that 15th drive slot available that is killing me...

Link to comment

Are you 100% sure that you have ASUS M4A78LT-M ???

 

According to the Asus specs it uses Realtek® 8112L, 1 x Gigabit LAN Controller(s)

 

And you are not using an Intel card either as according to your syslog you are using Broadcom based LAN:

 

Sep 13 19:58:51 Tower kernel: tg3.c:v3.102 (September 1, 2009)

Sep 13 19:58:51 Tower kernel: tg3 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

Sep 13 19:58:51 Tower kernel: tg3 0000:03:00.0: setting latency timer to 64

Sep 13 19:58:51 Tower kernel: eth0: Tigon3 [partno(BCM95721A211) rev 4101] (PCI Express) MAC address 00:10:18:18:2c:45

Sep 13 19:58:51 Tower kernel: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1])

 

Bring back this knowledgeable friend and tell him to:

 

1. Undo the CPU core unlocking if possible and lets hope the mobo and CPU are not damaged by the possible higher TDP.

2. Check out the exact model for the motherboard - should be printed somewhere, also from the white label on the box...

3. Flash the motherboard with the latest BIOS.

4. Load the default values and reboot.

5. Go back into the BIOS and disable any unused hardware features - serial and parallel ports, audio, firewire, even the onbaod IDE controller if you are not going to use any of the older PATA hard drives.

6. Make sure that the onboard SATA drives are set to AHCI mode.( there may be two settings - one for SATA1 to4 and another for SATA5and6)

7. Go into the Supermicro card BIOS and disable INT13H.

 

After all that reboot the computer for an overnight memory test.

 

If successful you will be able to enjoy your Unraid server (but I do not know how good the onboard Broadcom Lan chip is with Unraid)

Link to comment

Are you 100% sure that you have ASUS M4A78LT-M ???

Yes, this is from the invoice with NewEgg: ASUS M4A78LT-M AM3 AMD 760G HDMI Micro ATX AMD Motherboard - I was avoiding the LE, which had NIC problems supposedly.

According to the Asus specs it uses Realtek® 8112L, 1 x Gigabit LAN Controller(s)

Correct, and it worked, but I turned it off during a trouble shooting spree and got better performance from the add-in card.  And I mispoke, it is a Broadcom and not an Intel. I first put in the Intel 10/100 as a test... just had that in my had that it the Gig one was Intel as well

And you are not using an Intel card either as according to your syslog you are using Broadcom based LAN:

 

Sep 13 19:58:51 Tower kernel: tg3.c:v3.102 (September 1, 2009)

Sep 13 19:58:51 Tower kernel: tg3 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

Sep 13 19:58:51 Tower kernel: tg3 0000:03:00.0: setting latency timer to 64

Sep 13 19:58:51 Tower kernel: eth0: Tigon3 [partno(BCM95721A211) rev 4101] (PCI Express) MAC address 00:10:18:18:2c:45

Sep 13 19:58:51 Tower kernel: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1])

 

Bring back this knowledgeable friend and tell him to:

 

1. Undo the CPU core unlocking if possible and lets hope the mobo and CPU are not damaged by the possible higher TDP.

I will give him a buzz, but I can probably figure out how to default it all somehow.

2. Check out the exact model for the motherboard - should be printed somewhere, also from the white label on the box...

3. Flash the motherboard with the latest BIOS.

Has it already

4. Load the default values and reboot.

That's the plan  ;D

5. Go back into the BIOS and disable any unused hardware features - serial and parallel ports, audio, firewire, even the onbaod IDE controller if you are not going to use any of the older PATA hard drives.

I had some off, I am pretty sure but I can do that after the default. No need to run sound, etc, etc.

6. Make sure that the onboard SATA drives are set to AHCI mode.( there may be two settings - one for SATA1 to4 and another for SATA5and6)

Did that first day and correct on how the board treats the SATA ports as 4+2

7. Go into the Supermicro card BIOS and disable INT13H.

Had already done that, and the BIOS is the 'optimal' one (the newest one, I believe) according to several threads I read on here.

 

After all that reboot the computer for an overnight memory test.

I will mess with it tonight, maybe see if I can get it up and going and check web interface performance and do some writing directly to disk shares, then start the mem test before I head out the door.

 

If successful you will be able to enjoy your Unraid server (but I do not know how good the onboard Broadcom Lan chip is with Unraid)

Personally, I think the Realtek was fine, but plenty of suggestions came in to try an add-in card (original issues were basically about r/w speed).  I just left it in after that.

 

Thanks for the help.

Link to comment

Attached Syslogs are with the CPU settings as they were and then with clockspeed, voltage, etc all set as Auto in the BIOS.  It seems like the core unlocking is a one-way door?  I am not too familiar with OC'n machines and def not the current crop of processors so I am not too sure what is going on there.  I basically defaulted everything and then turned off cores 2,3,4,5,6 (only has '2' though I think) in the BIOS. Shows up as the Athlon either way, though I am certain that the unlocked cores are off.  Read a little on the chip and it seems like it is one that people mess with, unlocking the cores, raising the clockspeed, etc. - it seems to be able to be pushed pretty far, though it's not needed in this case.

 

Couldn't get a hold of my friend but I am fairly confident that is is not overclocked and if there are more cores unlocked they are off. I remember my friend saying that 2-cores was fine and overclocked those was fine if I put in a bigger heatsink and fan (on it is just the retail AMD one).

 

Maybe someone more familiar with ASUS boards will now what I mean here but when it is booting you see 'Press 4 to unlock cores' and you can hit '4' on the keyboard and it  shuts off.  When it boots up again the 'Press 4 to unlock cores' is not there and it says something like 'Cores unlocked'. You can then go into the BIOS and selectively shut down the cores.  Funnily enough, it always says 4 are unlocked after the initial 'Press 4 to unlock cores' message comes up and you hit 4.  The POST screen has a 4(up arrow) icon next to it. Pretty sure it only has 2...

 

Where I am at now:

 

Did the BIOS changes, plus made sure all the audio and unnecessary comm ports are off.  Enabled the Realtek NIC and pulled the Broadcom. Pulled the M8 SAS for now, there are no drives on it. Pulled the 2-port that the Cache drive was on.

 

unRAID booted up, I was able to get around the web interface OK.  No red in unMenu and all my existing drives were there and the shares were available.

 

Went to my Movies (ISO) folder where I had copied 8 movies... only one was there (though it was a complete file and useable). The errors were probably the cache drive like was mentioned above and it was probably trying to copy from the cache to the regular array but was having issues.

 

Wrote directly to a couple of the disks from a USB 2 HDD connected to a laptop that was connected to the LAN, around 26Mb/s average.  When I copied from the HDD on the laptop to the disks it was around 32 or so.  Read from the share shifted between 90-105, so that seems about right.

 

Rebooted and started the memtest, which is where it is at now.

 

Feel better about where it is at, given how it was behaving. I will probably add the SAS card and put a different drive on there and ensure that unRAID can see it and add it to the array.  Like I mentioned, I don't care about the 15th drive slot at this point so a replacement PCI stat card isn't a concern (though I could try it with some other drives I have).

 

If anyone has info about ASUS boards and the Sempron 140 and where it should be as far as cores and clockspeed let me know.

syslog.txt

syslog2.txt

Link to comment

Can't access my unRAID bios...but here is a comparison of what is being posted in the syslog:

M4A785-M and Sempron 140 CPU (mine)

Aug 31 20:26:16 Tower kernel: Detected 2712.372 MHz processor.

Aug 31 20:26:16 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5424.74 BogoMIPS (lpj=27123720)

Aug 31 20:26:16 Tower kernel: Mount-cache hash table entries: 512

Aug 31 20:26:16 Tower kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)

Aug 31 20:26:16 Tower kernel: CPU: L2 Cache: 1024K (64 bytes/line)

Aug 31 20:26:16 Tower kernel: mce: CPU supports 6 MCE banks

Aug 31 20:26:16 Tower kernel: using C1E aware idle routine

Aug 31 20:26:16 Tower kernel: Checking 'hlt' instruction... OK.

Aug 31 20:26:16 Tower kernel: SMP alternatives: switching to UP code

Aug 31 20:26:16 Tower kernel: ACPI: Core revision 20090903

Aug 31 20:26:16 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1

Aug 31 20:26:16 Tower kernel: CPU0: AMD Sempron 140 Processor stepping 02

Aug 31 20:26:16 Tower kernel: Brought up 1 CPUs

Aug 31 20:26:16 Tower kernel: Total of 1 processors activated (5424.74 BogoMIPS).

 

Yours...

Sep 15 06:31:40 Tower kernel: Detected 3013.992 MHz processor.

Sep 15 06:31:40 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6027.98 BogoMIPS (lpj=30139920)

Sep 15 06:31:40 Tower kernel: Mount-cache hash table entries: 512

Sep 15 06:31:40 Tower kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)

Sep 15 06:31:40 Tower kernel: CPU: L2 Cache: 512K (64 bytes/line)

Sep 15 06:31:40 Tower kernel: CPU: Hyper-Threading is disabled

Sep 15 06:31:40 Tower kernel: mce: CPU supports 6 MCE banks

Sep 15 06:31:40 Tower kernel: using C1E aware idle routine

Sep 15 06:31:40 Tower kernel: Checking 'hlt' instruction... OK.

Sep 15 06:31:40 Tower kernel: SMP alternatives: switching to UP code

Sep 15 06:31:40 Tower kernel: ACPI: Core revision 20090903

Sep 15 06:31:40 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1

Sep 15 06:31:40 Tower kernel: CPU0: AMD Phenom II X4 B45 Processor stepping 02

Sep 15 06:31:40 Tower kernel: Brought up 1 CPUs

Sep 15 06:31:40 Tower kernel: Total of 1 processors activated (6027.98 BogoMIPS).

Link to comment

Sweet, so mine is faster...  8)

 

;)  I haven't had it lock up or shut down, even when it was slow on the web interface I could log in via telnet or get on the console on the machine and shut it down.  Looking online it looks like that its pretty popular chip to run at 3.5+ (even with the standard heatsink).  I will resign myself to the fact that it's at least stable from the CPU standpoint, unless someone sees a reason it might be unstable. 

 

Here is some info about unlocking and overclocking:

 

http://www.techpowerup.com/reviews/AMD/Sempron_140/12.html

 

ASUS as an 'unleashed' option, that's what unlocks the additional cores on certain AMD chip families (gleamed from skimming a couple sites). The clock speed on mine us up though, so not sure what the deal is there.  I will investigate more tonight.

Link to comment

It seems stable.

 

Writing to it at 22mb/s (writing TB's of data).  Pulling over gig averages 105 or so. Peaks of 120 or so now and again.  This is to a Win 7 box and the file transfer speed being reported is probably not super accurate...

 

At any rate, it seems fine as is.  Left to do is to bring on the SAS card and a few more drives next week.

 

Of course, I got my 4th disk (already a refurb from WD - it precleared real slow) showing DISK_DSBL and writing errors.  Parity, Disk 1 and Disk2 are fine.  Can I just pull that 4th and pop in a new one (when I get it)?  Is it best to just pull it right now so it doesnt get more data written to it?

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...