gbdesai

What? Sure it made sense in some language pre-translation... Sent from my iPad using Tapatalk HD

Thanks buxton. exactly, tempting to just start using them, but i trust all of you, and i'll preclear them before using them. when you say 2-3 at a time, you mean 2-3 drives, right? If i decide to do 3 drives at the same time, i can run 2 cycles per drive? so total of 6 preclear cycles i guess. correct me if i'm wrong. Yes but they will run in parallel. Ideally you use screen so that you can start and keep 3 preclear sessions running simultaneously, one for each drive. If you use a terminal windows or three in this case, an d he window closes due to a network failure, etc. the preclear will stop. Screen will allow you to close the terminal and have preclear continue operating... Hope that makes sense. Sent from my iPad using Tapatalk HD

I had a full install running with 25tb of data and followed Johnm's directions. To be safe especially be cognizant of his warnings of disconnecting ALL drives during the initial ESXi install. Works perfectly if you follow the instructions exactly. Sent from my iPad using Tapatalk HD

Not sure about the other things, but you don't need the client to use IPMI, it's web-based and for KVM it launches a Java session and works great...

I concur, one M1015 in LSI IT mode connected to a RES2 expander all running in a ESXi (ATLAS like setup). Works great, no errors.

Thanks for the heads up. I downloaded and installed the patch, it's a bitch to figure out how to install without the paid Update Manager. This blog post was invaluable... it worked like magic... here's a link in case it helps someone else... http://www.itadmintools.com/2012/02/howto-patch-vmware-vsphere-esxi-50-free.html

What Beta said.. I would look into possibly getting a Supermicro X9SCM-IIF (Updated X9SCM-F with 2 ESXI compatible NICs and V2 Bios fr IVY Bridge CPU's). otherwise you might have problems if you do not have a compatible sandy bridge CPU about. I would also consider buying 2x 8GB stick instead of 4 4GB sticks. unless you can reuse that ram, it seems silly to throw it away. EDIT and he sniped in before me.. I updated teh front page yesterday to show that I am recommending the X9SCM-iiF now I saw here http://lime-technology.com/forum/index.php?topic=17936.0 a solution to use the second nic (i haven't tested it myself yet though). Any other reason to recommend the X9SCM-iiF, it's almost twice the price than the X9SCM-F? Sent from my GT-P7500 using Tapatalk 2 I just bought one from http://SuperBiiz.com/ for $189 and also 4 x the SuperTalent sticks (for total ram of 32gb) john posted about for $101 each... I live near them so I can go kick their asses if they aren't for real... Sent from my iPad using Tapatalk HD

Very interested in your findings, I ordered 3 x SAS2LP for a ESXi build before I saw that no one has tested it in such a config. I'm hoping it works with the same hack as the SASLP... Thanks! I don't think I'll start before next week, pretty busy at work at the moment, but I'll keep you posted Sent from my GT-I9100 using Tapatalk 2 I may get to it before you... perhaps this weekend. I'll let you know if I do...

Very interested in your findings, I ordered 3 x SAS2LP for a ESXi build before I saw that no one has tested it in such a config. I'm hoping it works with the same hack as the SASLP... Thanks!

As far as I have seen, the speed of the parity check has never been constant if is limited by disk speed - this is due to the variable density of data across disk cylinders. My checks always begin at a high rate (115 - 120MB/sec) and slow down as the check progresses. I would think that is normal - certainly I would not expect anything different. As you say, one does have to refresh the display to get an up to date figure. When I had much slower hardware (Atom CPU, PCI bus SATA controller as opposed to PCI-e) the speed was pretty much constant thought the parity check. I can add a piece of data, I am running RC6 with 23 total drives in the array plus a cache drive. I have 3 x AOC-SASLP-MV8s. I was getting slower parity checks in the RC3 and RC5 builds at around 65MB/sec at the start of a check vs. closer to 80-90MB/sec in prior betas. With RC6 I just ran a parity check and let it go for a bit and am averaging 25MB/sec. Something's up. Could we be saturating the bus or something with so many drives going at one time? G P.S. And yes, Joe L, how do you find the kernel/module names you were asking about?

Anyone thinking about building this all into a plugin for us lazy types?

I'm also interested in knowing the compatibility of rc4 with the AOC-SAS2LP-MV8 and AOC-SASLP-MV8 cards. Thank you! I've had no issues with the AOC-SALSP-MV* card and rc4 Why don't you try it and see? I've had no issues with the AOC-SALSP-MV* card and rc4 Same here, running since 22 hours. I was going to post the same, but realized that he is asking about the AOC-SAS2LP-MV8 not just the AOC-SASLP-MV8, I have 3 of the SASLP (not SAS2LP) working fine with RC4 (and RC3, b14, b12a).

What makes you think that? To others- You can not kill emhttp and then restart, it is not designed to do that and you will get a segfault every time. Actually you can do a powerdown with the script by opening a terminal session with the server and entering "powerdown" that's the only way I've been able to get WebGUI back, is a powerdown and reboot. I had an issue like this on Saturday and of course hard to check wiki and doc when there is a site outage. What do you do if emhttp has died/become unresponsive and can't be restared if you want to shut the server down. I believe the powerdown script requires the web interface to be running, is there another way to safely shutdown?

That explains that part of the problem. Thanks. I haven't seen this since I upgraded from b14 to rc3, but on b14 it was constantly happening.

You have /user/local/sbin/emhttp vs. /usr/local/sbin/emhttp - that's at least why you get the error..