heredago

I rebooted but I still cannot access the webui, the array doesn't seem started because the shares aren't showing in \\TOWER\ I can only see the USB Flash key at \\TOWER\flash and even with disabling the plugins & extras & using a stock go file, and rebooting, it still doesn't work. I guess I will have to try a fresh "install" on the USB key when I get back. From my understanding, I think that I shouldn't really be too worried about my data.

I just completed these steps: but I still cannot access the Webui, I can only access \\TOWER\ and only \\TOWER\flash shows up in there and here is attached the full system log syslog_2012-02-11_17-46.txt

I've tried different things to restart the webui to no success but I received: root@Tower:~# killall emhttp root@Tower:~# nohup /usr/local/sbin/emhttp & [1] 24575 root@Tower:~# nohup: ignoring input and appending output to `nohup.out' then, I tried the Powerdown script from cmd line but received:

Clean and first install of unRAID in June (5.0 rc4) (VM of an ESXi server with MV8 HBA's) This is the second time that this exact same thing has happened but except for this, everything has worked perfectly for the last 4-5 months (initial clean install) I haven't changed a single thing since the initial install in June (except for a permission on a share) and the last (and only other) time that unRAID became unresponsive like this must have been 2 months ago. (I don't know if it was at the time of the Sept 2nd parity check or not) So the monthly parity check of October 2nd finished fine without any problem. But the one of this month (Nov 2nd) made my unRAID unresponsive: I can still Telnet into the server cannot acccess the web menu cannot acccess the smb share unraid_syslog_nas_2012-02-11_outage_.txt

After restarting my Windows machines, the share is there but it doesn't really connect automatically. If I click on it, it turns to green and it works but it needs a manual action. I got around it with a startup scheduled "net use" task but I was wondering if there was something even easier or if I wasn't getting something right!?

can you tell us which instructions did you follow? is it dhy8386's linked tutotial? http://blog.phonicuk.com/post/2012/07/30/Running-Mac-OS-X-108-Mountain-Lion-in-VMware-ESXi-5.aspx

Maybe I configured it wrong... but on my setup, I need to use "workgroup\username-you-created" (without the quotes) as the actual username when connecting to the SMB share. By default, I'm pretty sure that Unraid's workgroup is called Workgroup but you could have changed that setting so just double check it in your Unraid config if it doesn't work. Just also make sure that you're not already connected / have the same network share mapped anonymously. (http://www.7tutorials.com/how-delete-mapped-drives-windows-7)

Enjoy your vacations!

haven't upgraded to 5.1 yet, I was thinking of waiting something like a month to make sure there are no surprises like the 5.0 U1 no vm auto-start lol

this guy is QUICK!

Hi Zeron, I'm getting "not found" on all the links, maybe you changed host or something? Thanks!

I am interested in this as well. I read that auto-start was broken in the 5.0 Update 1 http://blogs.vmware.com/vsphere/2012/03/free-esxi-hypervisor-auto-start-breaks-with-50-update-1.html THANK YOU, I may not be crazy! I'm effectively running 5.0 Update 1 (VMware-VMvisor-Installer-5.0.0.update01-623860.x86_64.iso) Update 1 was released in March, more than 3 months ago... Why isn't this fixed yet? It's kind of ridiculous!? I can't revert back as explained in the Blog post as I have a 5.0 Update 1 clean install. There's a sketchy workaround in the comments but I would prefer not to mess with that. So I guess that I will have to start all over from scratch with a 5.0 install (VMware-VMvisor-Installer-5.0.0-469512.x86_64.iso) Should I be careful about anything in doing this? (except for unplugging every drives when re-installing ESXi) Looking at the Update 1 release notes, I should be fine downgrading; my OSX VM wasn't working anyway.. And then VMware is gonna release Update 2 / a fix in a week haha

that's awful one weird thing is that every time that I change a value in the Auto start menu, when I press ok, my VMs are multiplied by 3. And then, when I click on any other menu and that I come back to the Auto start menu, everything is back to normal. I even restarted my whole ESXi from scratch because of this de-multiplication and the VMs not auto starting but they're still not auto-starting

this will look crazy but I can't get my VM to auto-start :'( is there any other setting to tweak?

According to the manual and what's written on the MB, the card is in the "Slot7 PCI-E 2.0 x8". It's the closest one to the CPU so I guess it's more commonly called Slot #4? I had read that people had trouble with any Bios but 1.0c so that's what I'm running. I will use your suggestion and try the other slots tonight. Just an update of what I did last week: I realized that I had forgotten to disable the "INT 13h" setting in the MV8 bios card settings No more lock-ups!

just a suggestion: whenever a site is down, a lot of people will check their Twitter feed for updates

not only that BUT at least we know why the is no release... thank you thank you thank you for keeping us in the loop... ;D ;D ;D +1

According to the manual and what's written on the MB, the card is in the "Slot7 PCI-E 2.0 x8". It's the closest one to the CPU so I guess it's more commonly called Slot #4? I had read that people had trouble with any Bios but 1.0c so that's what I'm running. I will use your suggestion and try the other slots tonight.

I have just added my MV8 to my X9SCM-F build and I'm trying to migrate from physical -z RDMs to just using them with VMDirectPath Hardware Passthough. -added the card and plugged the drives to it -added the card to VMDirectPath Passthough settings in ESXi -added the PCI device in my Unraid VM settings & removed the old RDMs -applied the MV8 hack requiring to edit the 2 files using winscp -restarted ESXi and restarted the Unraid VM But then when I access the interface, it's super slow and at some point, ESXi crashes like this: I don't even have anything on my Unraid array hds and I could start all over but I'm just wondering if anybody has an idea?

Results: /vmfs/volumes/4fb7d1cd-20448c10-4510-002590736374/RDMs # vmkfstools -r /vmfs/devices/disks/vml.01000000002020202020204d4a31333131594e47344b563041486974616368 HTC3TB-01.vmdk -a lsilogic Failed to create virtual disk: The destination file system does not support large files (12). /vmfs/volumes/4fb7d1cd-20448c10-4510-002590736374/RDMs # vmkfstools -z /vmfs/devices/disks/vml.01000000002020202020204d4a31333131594e47344b563041486974616368 HTC3TB-01.vmdk -a lsilogic /vmfs/volumes/4fb7d1cd-20448c10-4510-002590736374/RDMs # ls HTC3TB-01-rdmp.vmdk TBA1TB-01-rdm.vmdk HTC3TB-01.vmdk TBA1TB-01.vmdk @BetaQuasi: with -z, I was successfully able to create a XXX.vmdk & XXX-rdmp.vmdk files. using -z, there is a difference in the file name, it adds a "p" in one of the 2 files. -z and -r also don't act the same way when I add them in a ESXi VM, ie: a SCSI controller is NOT created when I add a -z RDM. what I mean is I don't / can't complete the last step of the below's instructions as no SCSI controller is getting added in the VM settings at the same time as the RDMs -z hard drive. It then shows up in unRAID and I've just assigned 1x3TB to parity an 1x3TB to disk1 and I've started the array so I can update this topic tomorrow. I had enver done anything in unRAID up to now so I guess it has to start the array and do a parity check first.

I don't really understand your point but both my MB & CPU support VT-d: SUPERMICRO X9SCM-F Intel Xeon Quad-Core E3-1230

Thanks guys, I've ordered an AOC-SASLP-MV8 with cables.

Do I need a MV8/M1015 or can I do Raw Device Mapping to the 6 SATA ports of my onboard X9SCM-F mb controller? Keep in mind this if for 3.0TB drives. Because I keep getting :'(

I should and will probably create my own thread but in the meantime... First, I want to give you Johnm (and BetaQuasi and everybody else too ) a BIG BIG BIG thank you for your instructions. I, for sure, wouldn't have learned so much about building this box and how to install everything (it looks so simple once you "know" how to do it, but for a newb like me, all those instructions with the print-screens helped me so much Everything went better than expected! I was able to install ESXi and unRAID with Plop and everything. I use a X9SCM-F-O mb (my build) with currently only 3 disks directly attached to the SATA ports to begin with (1xSSD for datastore, 1x3TB for parity, 1x3TB for Data (and this will grow when I transfer files from my current full HDs to the array when it's ready!) BUT I get the following error when I try to create a RDM mapping in /vmfs/volumes/SSD1/RDMs: vmkfstools -r /vmfs/devices/disks/vml.01000000002020202020204d4a31333131594e4737384b5341486974616368 HTC3TB-01.vmdk -a lsilogic As I'm using VMFS-5, there's no choice but to use 1MB block size which should be fine? When I research for this error, it always points to the block size but it's always for people running VMFS-3... :'( EDIT#1: I've just tried this with VMFS-3 and 8MB block size and I get the same error so I'm definitely doing something else wrong :'( Anybody has a suggestion!?

Oh, just realized that when I had searched for VT-d CPU compatibility list, I was in fact on the VT-x Intel's compatibility page :\ I also hadn't realized that the E3-1220 didn't have HT, E3-1230 it is! I just ordered all my parts (2012-04-26), I realize this must be way overkill for my needs but I want something that will last me for a long time and that I will have fun with it! I added a SSD for use as a Datastore, I understand it's a basic consumer one without any "advanced garbage collection" or "auto trim", but for my needs, I hope it's gonna be fine. The ESXi part is a lot more for fun and testing than for real use, but maybe that will change when I have my system up and running, who knows!