nia

I like the fact that she has gone for redundancy on the cats as well...

+1 for Logmein free. I has served me well for years. Sent from my iPhone using Tapatalk

I'm currently 118 days since we had a power outage longer than my UPS could handle. I have been in the 200+ range Its my first non- win machine, and its amazing how its just works. Essentially it runs until You tell it not to Sent from my iPhone using Tapatalk

A welcome return, thanks (got the e-mail also)

Was so happy to see this annoncement today on my birthday Only to find: That really is a disappointment :'( - I was setting my hopes that this quite widespread card would be supported during/after the beta cycle :'( Only encouragement is, that the latest version to support it (12a) works quite well for me for the basic stuff. Still hope card support will make it into the final product or a not too distant future release.

Great to have more at the Atlas party The pins bent on your board are different than the one that was bent on mine related to the memory controller. Can't say if you have other lurking problems from those pins, but luckily you have another board coming to remove any doubt as I read your post. That being said, my unbending appears to have been sucessful, as I have had no issues since. So you could very well have a successful run with board #2 as well Enjoy your building efforts - may you have a smooth run at it...

I guess this means that the LSI issue in not reported in then...? How can we who have the issues establish an error report to the kernel folks, as I assume that will be our only way to get this fixed except if we are lucky that this impacts other useage patterns an hence will get reported through their experiences?

I see the exact same behaviour on the same version, no simple features.

I realise now, that I missed this step when I flashed my first card: 6. Program SAS address in IT-mode: sas2flsh -o -sasadd 500605bxxxxxxxxx where "500605bxxxxxxxxx" SAS address from small green sticker on yor card, without "-" Despite me missing this, it is humming away nicely in my now converted production box on 5.0.12a. BUT - I now have a second card, that I 'm intending to integrate. I did the reflash including step 5 on the only machine I have been able to. Then I figured I would reboot to do step 6 - also to read the sticker for the number. Unfortunately, that machine now can not boot, as it is hanging at the BIOS of the adapter. So I have no option at my disposal to do step 6 on any of the cards. Will I have any issues in an unRAID scenario by having two cards that has both not been through step 6 to get individual addresses?

+1 Please

You mean apart from "This promotion is only available to end user customers based in the UK" ? D'OH! Note to self: Don't try to read small print on excitingly good offers at 2:30 AM...

But I see nowhere in the terms that this is UK only. And with EU regulations and all, I should be able to buy one to Denmark. I regularly buy other stuff from the UK (even 17" tires!!!), so it should be absolutely possible... Hmmm.. better finish my build first. But £150 - that's just too cheap to pass on

OK - so today I pulled apart the olf unRAID server, and prepared the case for new occupants. I will build tomorrow. It will be great I'll take some pictures along the way. I believe I will boot the 4.7 server first, and then do the upgrade. Objections or comments? I also did some preliminary testing with the UPS plugin for vs. 5. Unfortunately, there seems to be something not quite right with the pasthru. It sees the UPS, but reports odd data. Haven't tested the actual shut-down yet. The beeping will wake the whole house here. So that will be for tomorrow.

Sorry, but no idea what exact card you are referring to. If you can post that info it would be helpful. Thanks. Sorry - I realised the actual card model is only mentioned in my Pleiades build not in my reflash post above Card to be flashed: IBM M1015 Method: DOS boot disk. P11 firmware. Zerons batch file. Successful on: HP Workstation XW9300 - chipset nForce Professional PAL error on: Supermicro X9SCM-F AsRock P45R2000 Not recognised on (did not do a huge investigation here, maybe it can be under certain conditions): A8N-SLI Premium

I like my X9SCM just fine. I was just putting it out there there that the X8SIL can run ESXi with 32GiB of RAM now (for a hefty price), while the X9SCM is lacking 8GiB RAM sticks. Honestly, for casual use, the 16 Gib is OK. (...) ESXi tends to run out of RAM before CPU. Again, for home use, unless you are going crazy, 16GiB Is fine. As far as using SSD for a datastore, I am sort of an oddball that I use SSD's for my datastore. It is worth mentioning in this context, that ESXi 5 identifies SSDs natively and uses them for fast swap space when it runs out of RAM. That also alleviates the need for more than 16GB RAM, in particular given a quick SSD on SATA3 on the X9SCM board with the fast processors it supports

Ah - I completely missed that the 1260L had graphics - it's supposed to be the 12x5-models... That certainly explains the power consumption I agree with you on the 1220/1230. I also tested the E3-1220, but it really makes no sense to me - at least not in this configuration and with its pricetag.

Final pieces are coming together. Datastore I realised that 60GB SSD for main datastore was really not enough. So I have moved the VM's to a 120GB OCZ Agility3 SSD (after FW upgrading to 2.15). I used the built in mover in the data store browser. One disk was locked, and after several attempts (even after reboots), the only way I was able to copy it was using cp from the command line interface. That worked. CPU Surprisingly, the E3-1230 idles at 3-4 watts LESS than the E3-1260L. And performance is significantly higher. Maybe it peaks at higher watts, but it gets the job done - FAST! The 1230 stays in. PSU The gold rated SeaSonic X660 has yet to start its fan. And it is completely modular, which is something I like - in particular with my cabinet. The Corsair and M12II both have the motherboard and CPU cables fixed. One of them even a SATA string. And even though it idles at 60W just 1W lower than the M12II, already at a load where the M12II showed 103-104W the X-series shows 96-97W. I guess at higher loads its even more. X-series stays.

Maybe there will soon be progress for the second NIC on the MoBo for ESXi 5 if the guys over at Hardforum succeed in making an updated version: http://hardforum.com/showthread.php?t=1607992&page=4 . Apparently the needed source code is now available...

sosdk: Thanks, but I have my uncles HP available here to use for reflash if needed. Besides that, i have now successfully precleared the 2 new 2TB drives on the reflashed M1015 controller. Went without a hitch. Meanwhile, the b13 got some kind of Münchhausen-by-Proxy syndrome, and claimed that the 400GB drive was now 756TB . I will now try a simple install with 3*400GB drives on b12a, and add some of the add-ons like Zerons vmWare-tools and SimpleFeatures. My other VMs are moving forward as planned. I now have prepared the nPVR and WeatherDisplay machines, and I have a 'clean' machine, that I have copied to my 400GB datastore. It will be my template for creating new machives. I found out that it was really easy to log on to the command line interface and do an internal copy of my template machine from the SSD to my 400GB secondary datastore. I'm sure there are other ways, but this is quick, clean and easy. SSH into the server using putty or like product. go to /vmfs/volumes and go into the volume in which you want to move your data: cd /vmfs/volumes/Datastore2 mkdir <Name of VM directory> cd / Now switch back to source datastore cd /vmfs/volumes/Datastore1 cp *.* /vmfs/volumes/Datastore2/<Name of newly created VM directory> Remember to put "" around e.g. datastore names with spaces. E.g. my SSD is called "60GB SSD" which I would put in in stead of Datastore1 above Ref: http://www.n2networksolutions.com/2009/02/26/moving-a-virtual-machine-from-one-datastore-to-another/ If needed, you then register the newly copied machine like described over in the Atlas thread.

My test server has now finished with 2*2TB preclearing. Preclearing went down nicely, and took approx. 24 hrs. One odd observation I noticed was, that my 400GB drive is reported to be 756TB! (I wish ). I have attached syslog, preclear log and screendump displaying the wrong size. All drives are attached to an ESXi 5.0 hardware-passthrough mapped M1015 reflashed to the P11 firmware. I will now go back to test b12a on the test setup due to the spindown issue , unless there is something specific somebody wants me to test with b13. syslog-duringpreclear.zip preclear_2x2TB_b13_M1015.zip

I did eventually succeed with flashing, and it was with P11. As can be seen in the beta13 thread, there are issues with spindown and this controller - also with P11. Allegedly it is related to the kernel...

Look at the Atlas build thread. http://lime-technology.com/forum/index.php?topic=14695.0 It has a set of very comprehensive instructions. Done right, there will be no significant (if any) performance hit.

Thanks BRiT. I suspected that. Really too bad with an issue outside limetechs control I think I will then rather try beta12a first before recompiling with a different kernel. The steps to build a new unRAID are not entirely clear to me (to say the least!). Unless there is a step-by-step guide to do this somewhere?

Got access to an old HP machine (will edit the HP model number in here later EDIT: HP Workstation XW9300 - chipset nForce Professional) at my uncle, and finally got the firmware updated using Zerons P11 package http://lime-technology.com/forum/index.php?topic=12767.msg149129#msg149129. Now I can start to get some real stuff done on unRAID. Truying to see if beta 5.0.13 is any good

Did a very first boot with a couple of fresh 2TB disks (one was actually precleared) and one leftover 400 GB pulled at an earlier upgrade from my production system with some files left on it. This is on the Pleiades build (see sig) with a M1015 direct passthru (like from the Atlas build thread) reflashed to phase 11 using Zerons batch http://lime-technology.com/forum/index.php?topic=12767.msg149129#msg149129 No addons installed. Seems to boot allright, but goes on with a problem that I don't know if it is related to the old 400GB drive, the unformatted drive or something completely different. Maybe it is related to when I tried pressing the spindown button? It worked on the drives, but maybe it crashed something else. Just wanted to put the syslog in here if that would be useful for someone to see. I'll do a proper configuration of an array later. If there is anything I can try for someone, I'm open. As long as instructions are pretty fool-proof If there actually are problems with spindown related to the M1015, can it then be reflashed to something else (eg 9240-8i) and be expected to work with this new kernel? I will let the M1015 do a preclear on the 2TB drives, and we'll see where it goes from there. Syslog-firstboot.zip