MartinQ

I just reverted back to 4.6 and got the blue dot back. Going to build parity on it and see how it goes.

Was just going to upgrade my parity drive from 1.5T to 2.0T with advanced-format so I figured I'd upgrade from 4.6 to 4.7 at the same time. 1. Did a parity check. OK 2. Shutdown server. 3. Swap drives. 4. Boot & check status. Parity drives shows up OK with blue-dot. 5. Copy over new bzimage & bzroot (overwrite 4.6 with 4.7) and reboot and now I've got four drives in the red! Feb 19 02:29:07 Watchtower kernel: md: unRAID driver 1.1.1 installed Feb 19 02:29:07 Watchtower kernel: md: import disk0: [8,128] (sdi) ST2000DL003-9VT1 5YD1DLK4 size: 1953514552 Feb 19 02:29:07 Watchtower kernel: md: disk0 wrong Feb 19 02:29:07 Watchtower kernel: md: import disk1: [8,32] (sdc) WDC WD5000AAKS-6 WD-WCAS85494000 size: 488386552 Feb 19 02:29:07 Watchtower kernel: md: import disk2: [8,48] (sdd) WDC WD5000AAKS-6 WD-WCAS85394666 size: 488386552 Feb 19 02:29:07 Watchtower kernel: md: import disk3: [8,16] (sdb) WDC WD5000AAKS-2 WD-WCAPW4129766 size: 488386552 Feb 19 02:29:07 Watchtower kernel: md: import disk4: [8,0] (sda) ST31500541AS 9XW02NFA size: 1465137492 Feb 19 02:29:07 Watchtower kernel: md: disk4 wrong Feb 19 02:29:07 Watchtower kernel: md: import disk5: [8,96] (sdg) WDC WD15EADS-00P WD-WCAVU0390002 size: 1465138552 Feb 19 02:29:07 Watchtower kernel: md: import disk6: [8,64] (sde) WDC WD5000AAKS-2 WD-WCAPW4107675 size: 488385492 Feb 19 02:29:07 Watchtower kernel: md: disk6 wrong Feb 19 02:29:07 Watchtower kernel: md: import disk7: [8,80] (sdf) WDC WD5000AAKS-2 WD-WCAPW4125131 size: 488385492 Feb 19 02:29:07 Watchtower kernel: md: disk7 wrong Feb 19 02:29:07 Watchtower kernel: md: import disk8: [8,112] (sdh) WDC WD5000AAKS-6 WD-WCAS85486418 size: 488386552

Bwaaahahahaaaa ... =] Good one!

So then they become Moberators, right?

No, starting at 64 is better.

Memtest86+ 4.10 is out as of 2010-04-05. To update: 1. download the "Pre-Compiled Bootable Binary" (either .zip or .gz) from here: http://www.memtest.org/#downiso 2. extract / rename / overwrite the file 'memtest' that is in the root directory of the UnRAID USB stick. Memtest86+ V4.10 changelog -------------------------- - Added support for Core i7 Extreme CPU (32nm) - Added support for Core i5/i3 (32 nm) - Added support for Pentium Gxxxx (32 mn) - Added support for Westmere-based Xeon - Added preliminary support for Intel Sandy Bridge - Added support for AMD 6-cores CPU - Added detection for Intel 3200/3210 - New installer for USB Key - Corrected a crash at startup - Many others bug fixes

Speaking of which, Parted Magic 4.10 is out now. http://partedmagic.com/

Very interested to hear your progress and results with this! My only criticism is that I don't think life-support functions (power, cooling) should rely on an OS to function.

The TC647B is non-progammable. I believe you set the temperature point with a resistor value. http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010733

I've looked at many of those cheapie fan controllers. Most do not have temperature control (only speed control) and are also very limited on power output per channel (I'd like to run a higher power fan or blower). The CFA633 can deliver a reasonable amount of power but cannot currently be used as a plug-in appliance (even after programming). The fan controller kit (TC647B) has lots of power control but is very limited at temperature control (analog, one sensor, one output).

Here are some ideas: Fan Controller Kit (TC647B) http://store.fundamentallogic.com/ecom/index.php?main_page=index&cPath=25 http://spiffie.org/kits/tc642/start.shtml "These are easy to build, use, and understand fan controllers based around Microchip's TC64x series of chips. It's designed to control 12V computer fans based on the temperature, but can be easily adapted for any voltage of fan and a selection of sensors. " ===== I've also been bugging CrystalFontz to make a fully autonomous version of their CFA633. It currently requires serial communication to provide good functionality. http://www.crystalfontz.com/product/CFA633TMCKU - Temperature monitoring: up to 32 channels at up to 0.5 deg C absolute accuracy. - Four fan connectors with RPM monitoring and variable PWM fan power control. - Maximum continuous current draw must be no more than 1.5 A per fan connector, no more than 4 A total. Pulsed current may be up to 5 A per connector, the pulse width must be less than 50 mS. This pulse specification allows for the fan's start-up current spike. http://www.crystalfontz.com/products/633usb/datasheets/169/CFA_633_k1.9b.pdf

What happens when you simply press "refresh" on the unRAID main screen. (The actual unRAID screen, not the one in the unMENU menu's window.) Nothing. I was [Refreshing] as well as reloading the browser (Chrome) at each step and there was no change.

Just playing with disk spin-up/down. If I spin-up one disk using UnMenu it does not show active in UnRAID Main. If I click the [spin Down] button nothing happens. Clicking [spin Up] and then [spin Down] does work though. The response is the same spining-up all the drives one by one using UnMenu. None of it registers on the UnRAID Main menu until I click [spin Up].

Looks like the Memtest86+ version is still at 2.11. Info for the current 4.00 version is here: http://lime-technology.com/forum/index.php?topic=4406.0

Memtest version still needs to be updated.

I haven't tried it yet but it looks like the Memtest version included is 2.11 based on the file size (116,508 bytes). Details on Memtest 4.00 are in this post: http://lime-technology.com/forum/index.php?topic=4406.0

Memtest86+ 4.00 has been released and can be downloaded here: http://www.memtest.org/#downiso Download the "Pre-Compiled Bootable Binary" (either .zip or .gz) and extract / rename / overwrite the file 'memtest' that is included with UnRAID. Here are the changes (copied from the site): New Features Major Architectural changes First pass twice faster (reduced iterations) Detect DDR2/3 brands and part numbers on Intel DDR2/3 chipsets Added detection for Intel "Clarkdale" CPU Added detection for Intel "Gulftown" CPU Added detection for AMD "Magny-Cours" CPU Added detection for Intel XMP Memory Added for CPU w/ 0.5/1.5/3/6/12/16/18/24MB L3 Added "clean" DMI detection for DDR3/FBDIMM2 Better detection of Integrated Memory Controllers Bug Fixes Corrected detection for Intel "Lynnfield" CPU Corrected detection for AMD 45nm K10 CPU Solved crash with AMD Geode LX Complies with SMBIOS 2.6.1 specs Fixed compilation issues with gcc 4.2+ Many others bug fixes

Thanks for the tip. For anyone looking for a reliable power supply, I suggest they visit the guru: http://www.jonnyguru.com/modules.php?name=NDReviews

It's not confusing once you realize that both parallel ATA and serial ATA drives are intefaced via IDE (Integrated Drive Electronics).

Agreed. I have three of these and have successfully flashed the BIOS on all. I cannot remember if it was via boot-disk or in Windows though.

In testing out 'cache_dirs' by Joe I've found a few strange behaviors in spinning drives up/down. If some drives are spun up and I click [spin Down], then the remaining drives are spun up first, and then all are spun down except the parity drive. Re-clicking [spin Down] has no effect after that. If I click [spin Up] first and then click [spin Down] it seems to work correctly.

I found the following three 750W gold rated supplies on that site: Sea Sonic Electronics Co., Ltd. - SS-750KM, ATX12V & EPS12V, 750W, 90.25%, Gold Channel Well Technology Co. - DSG750V, ATX12V, 750W, 90.22%, Gold Thermaltake - W0350 TP-750AH3NCS, ATX12V, 750W, 90.22%, Gold

Tuesday Update Part II I changed the FSB from 133 (266MHz) to 166 (333MHz effective) so I am no longer underclocking the CPU. The AthlonXP 1900 is now a 2500 and here is what I've noticed. - Parity check has bumped up a MB or two. It now hovers around 30 - 31MB/s. - Writing data to a Share has gone up maybe 2MB/s. It seems to be around 11 - 14MB/s. I also did some PCI hopping of the second 3114 controller and found that using PCI slots 4 & 5 showed significant drops in READ throughput across the network. I also noticed a slight improvement setting the disk read-ahead cache to 2048 but it was very slight.

Some more observations using the 'top' command: These are the top processes when accessing a Disk and the approx CPU usage: Reading: - smbd 8 - 12% - unraidd 0.7 - 2% Writing: - smbd 12 - 40% - unraidd 5 - 10% ... but when accessing a Share: Reading: - shfs 30 - 53% - smbd 7 - 14% - unraidd 1% Writing: - shfs 30 - 70% - smbd 13 - 30% - unraidd 4 - 9% From this is looks like I am maxing out the CPU while doing writes to a share. I am assuming that these numbers are normal. Any perspective on the high CPU usage of shfs? Using 'bwm-ng' to monitor network traffic I see about 10MB/s while writing to a share. I also see frequent dips or momentary stops in traffic.

Hi Rob. The version I'm using is in the thread title. The load averages were obtained by using the 'uptime' command via telnet. I would update them several times while doing a transfer to get an idea of what was going on. You can also monitor them using the 'top' command and they're also accessible via UnMenu > System Info. I have read over the 'Improving unRAID Performance' page a few times and have done everything there.