ogi

I posted what I did to get temperatures working on the X9SCM-F board in the webGUI thread, when at a PC I'll copy that post here, but in case anyone with that board tries to get it working, the solution is in that thread.

Just looked at the drive caddies and oh-lord, not sure how/why I didn't think temperature would be a problem. xxredxpandaxx, you're going to have to perform some wizardry to keep these hard drives at appropriate temperatures. As a mechanical engineer, I don't envy that task at all.

Wow, that's a major temperature difference, and that occurred even with the backplanes removed?

Just ran this utility for the first time, my parity check speeds have increased by ~15-20% ... thanks for making an awesome utility!

I think you may benefit if you are able to rotate the black fan so it is at an angle, going from the corner of the motherboard to the corner between the back-plane and the case (hope that makes sense). You are right though, the fan layout here is not optimum, I don't know how realistic it would be to attach the fans to the top cover of the tray (the part you have removed in these pictures) so they sit above the motherboard, but have a long enough power cables so you can connect them and then put the cover on. What mATX board are you using?

Worst case you have some drive bays for virtualization

Was just thinking, if you had a M1015 in the xserve (which has 2 SAS connectors on there) and you have one RAID expander card in each xserve RAID enclosure, the entire setup would work quite well, not to mention look amazing (and give you 28 drives of storage). You'll have to post the detailed guide for getting the LEDs working the way you want and everything

the only limitation it has is that it can only hold 14 drives, With the way I am setting this up it is just like plugging the drive into a sata port so if your motherboard/controller can handle 4TB drives you could use those. It isn't using any of the original RAID setup, I am just using the hardware that is there to pass the signals along. (hope this makes sense) Makes perfect sense, I wasn't sure if you were keeping the internal guts of it or using your own motherboard/cpu/etc. That's too bad the limitation is only ~14 drives, it's a gorgeous piece of hardware, probably pretty quiet as well. I suppose you could stack two of these on top of each other and link them with a SAS cable (or whatever that cable is that can link several of the boxes together without requiring redundant motherboard/CPU/memory/etc). Ogi

What are the limitations of this chassis? I don't imagine it can handle hard drives greater than 2TB? How noisy would you describe it? Looking forward to seeing more info for sure!

I would just try renaming the Windows username and certainly not have any spaces in it. With Windows 8, that's a little more difficult :-/ EDIT: actually with windows 8 it was super easy. I followed the guide here: http://www.thewindowsclub.com/user-account-name-change and rebooted the PC, and everything fired right up after.

Ok problem, how do I create a user when the first letter is a capitol letter for the username?

Hey Joe, not sure if you missed my post, but given the weird results of this preclear, I could use your input Thanks! Sorry, I did miss it. This line is weird... 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 1. I would not expect for sectors to be pending re-allocation after being written. (and it is the highest count I've ever seen) Makes me want to RMA the disk for buggy firmware. (did you perhaps run two pre-clears on it at the same time, with one writing, while another was reading?) In any case, there were still 47 sectors that it could not re-allocate, and on that I'd RMA the drive. You should, if you decide to keep the drive put it through at least one more preclear cycle, and if cannot come through with all the sectors re-allocated, and no new ones detected as unreadable, RMA it. Well, instantly that number calls out to me, 65535 being the maximum number a two byte integer (short) can be, that alone (being exactly 2^16-1) sounds dodgy. Yeah, I saw this comment somewhere else on this forum, but regardless of that number not being a coincidence, is there anything that can be done in terms of identifying the cause, or is it a potentially an issue with the preclear script?

Hey Joe, not sure if you missed my post, but given the weird results of this preclear, I could use your input Thanks! Sorry, I did miss it. This line is weird... 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 1. I would not expect for sectors to be pending re-allocation after being written. (and it is the highest count I've ever seen) Makes me want to RMA the disk for buggy firmware. (did you perhaps run two pre-clears on it at the same time, with one writing, while another was reading?) In any case, there were still 47 sectors that it could not re-allocate, and on that I'd RMA the drive. You should, if you decide to keep the drive put it through at least one more preclear cycle, and if cannot come through with all the sectors re-allocated, and no new ones detected as unreadable, RMA it. Didn't run 2 preclears at the same time... I decided to RMA the drive, as I already had a different drive ready to RMA, just needed to drop it off. I like a column of 0's on the preclear report and when I see large numbers like this, I figured RMA was the likely suggestion. Thanks again!

Hey Joe, not sure if you missed my post, but given the weird results of this preclear, I could use your input Thanks!

I could also use some help with some preclear result interpretations ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdr == WDC WD20EARS-00MVWB0 WD-WCAZA0358422 == Disk /dev/sdr has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:06:00 (78 MB/s) == Last Cycle's Zeroing time : 5:57:45 (93 MB/s) == Last Cycle's Post Read Time : 13:49:47 (40 MB/s) == Last Cycle's Total Time : 26:54:32 == == Total Elapsed Time 26:54:32 == == Disk Start Temperature: 22C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdr /tmp/smart_finish_sdr ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 117 128 0 ok 33 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was pending re-allocation after pre-read in cycle 1 of 1. 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 48 sectors are pending re-allocation at the end of the preclear, a change of 47 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ I've attached the other relevant preclear files to this post. preclear_finish__WD-WCAZA0358422_2013-02-26.txt preclear_rpt__WD-WCAZA0358422_2013-02-26.txt preclear_start__WD-WCAZA0358422_2013-02-26.txt

When booting, enter The BIOS and select the UEFI shell as a boot device. From there, you can flash the M1015. Ogi

I found a utility for dos, but now I got this errot Failed to initialize PAL Any clue what that means ?? //Peter That sounds similar to flashing a M1015 on an incompatible MB. Yup, However it's simple enough to get around. That portion of the flashing procedure should be done in a UEFI shell.