Support > User Customizations
UnRAID on VMWare ESXi with Raw Device Mapping
axeman:
--- Quote from: Johnm on January 15, 2012, 11:51:00 AM ---So for I have only installed some of my New guests as VM8's.
My existing guests need none of the new features (that I am aware of).
i have the "Why fix what aint broke?" mentality when it comes to my (virtual) servers.
I play with servers at work to much to want to deal with them at home.
--- End quote ---
lol if that was the case, i'd still be on WHSv1, adding low 1TB drives. here i am now running esxi, unraid, and even an Openvpn appliance. so much has changed over the last 6 or so months.
i upgraded all the other machines, including an sbs 2011, and a win7 w.o. issue, but didn't want to touch the unraid machine.
i'll leave this one alone though :-)
thanks for ur replies!
Johnm:
LMAO.. You know what i meant.
I did not upgrade my 2011 or my 2008r2 DC guests.. there was no performance increase if i did.
BobPhoenix:
--- Quote from: Romir on November 03, 2010, 09:07:41 PM ---Unfortunately I wasn't able to get the pci device pass-through working on the X7SBE tonight. VT and VT-D are both enabled in the bios so I don't know what else to do.
A quick search found a mailing list conversation aboutX7SBE VT-D problems in Xen:
--- Quote ---after a few tests, i can confirm that VT-d on Supermicro X7SBE/X7SB4
doesn't work at all.
I assume this has to do with invalid ACPI table content.
--- End quote ---
Searching for X7SB4 & VT-D also yields a few posts about it not working with that similar board.
--- End quote ---
Not sure if you've tried updating to the latest bios or not but I just got VT-d working on my X7SBE with the September 2011 bios (2.0). Passthrough appears to be working with 2.0 just fine. I haven't actually set anything up yet but just spent all weekend trying finally just an hour ago I upgraded the bios and got it to work. I got it from this list.
ehfortin:
Hi all,
I tried to do some search on this now lenghty topic but without success. I've installed Unraid under ESXi 5. I have an LSI 1068E based card which is recognized by VMware. However, as I don't have a VT-d supported board, I have to use RDM. So, I created my RDM and assign those to the Unraid VM. After booting in Unraid, I can see all the drives but without much details (I only see the drive name and the size). This is very different from the complete identification I'm getting when booting directly Unraid on bare metal. My problem is that I have identified all my drives correctly and know exactly which sd device is which physical drive but when I select one of those in the select box in Unraid (those under the column "Identification"), it reload the page and I'm back to the "no device" selection.
At first, I was thinking it was related to problem with /dev/disk/by-path but 1) apparently it is not used anymore (now using /sys/dev/block) and 2) I can see my drives on both place anyway.
I've looked at the log and there is nothing. Each time I select a device, the log refresh with the following:
--- Code: ---May 8 12:05:57 fileserver kernel: md: unRAID driver removed
May 8 12:05:57 fileserver kernel: md: unRAID driver 2.1.3 installed
May 8 12:05:57 fileserver kernel: mdcmd (1): import 0 0,0
May 8 12:05:57 fileserver kernel: md: disk0 missing
May 8 12:05:57 fileserver kernel: mdcmd (2): import 1 0,0
May 8 12:05:57 fileserver kernel: md: disk1 missing
May 8 12:05:57 fileserver kernel: mdcmd (3): import 2 0,0
May 8 12:05:57 fileserver kernel: md: disk2 missing
May 8 12:05:57 fileserver kernel: mdcmd (4): import 3 0,0
May 8 12:05:57 fileserver kernel: md: disk3 missing
May 8 12:05:57 fileserver kernel: mdcmd (5): import 4 0,0
May 8 12:05:57 fileserver kernel: md: disk4 missing
May 8 12:05:57 fileserver kernel: mdcmd (6): import 5 0,0
May 8 12:05:57 fileserver kernel: md: disk5 missing
May 8 12:05:57 fileserver kernel: mdcmd (7): import 6 0,0
May 8 12:05:57 fileserver kernel: md: disk6 missing
May 8 12:05:57 fileserver kernel: mdcmd (8): import 7 0,0
May 8 12:05:57 fileserver kernel: md: disk7 missing
May 8 12:05:57 fileserver kernel: mdcmd (9): import 8 0,0
May 8 12:05:57 fileserver kernel: md: disk8 missing
May 8 12:05:57 fileserver kernel: mdcmd (10): import 9 0,0
May 8 12:05:57 fileserver kernel: md: disk9 missing
May 8 12:05:57 fileserver kernel: mdcmd (11): import 10 0,0
May 8 12:05:57 fileserver kernel: mdcmd (12): import 11 0,0
May 8 12:05:57 fileserver kernel: mdcmd (13): import 12 0,0
May 8 12:05:57 fileserver kernel: mdcmd (14): import 13 0,0
May 8 12:05:57 fileserver kernel: mdcmd (15): import 14 0,0
May 8 12:05:57 fileserver kernel: mdcmd (16): import 15 0,0
May 8 12:05:57 fileserver kernel: mdcmd (17): import 16 0,0
May 8 12:05:57 fileserver kernel: mdcmd (18): import 17 0,0
May 8 12:05:57 fileserver kernel: mdcmd (19): import 18 0,0
May 8 12:05:57 fileserver kernel: mdcmd (20): import 19 0,0
May 8 12:05:57 fileserver kernel: mdcmd (21): import 20 0,0
--- End code ---
Doesn't say much except that it doesn't recognize the disk I'm selecting. Even if I use a VMDK that I assign as a drive, I get the same result.
Is this something that has been reported before? Is there a known fix?
Thank you.
ehfortin
ehfortin:
Found the problem. If you someone has the issue where Unraid is showing sd drives but no mention about the serial number of the disk (which make it impossible to add in Unraid), you just have to use "vmkfstools -z /vmfs/devices/disk/vml.xxxx diskname.vmdk -a lsilogic" while creating the RDM instead of the "- r" switch that is documented in the official procedure that is published at http://lime-technology.com/forum/index.php?topic=14695.0
Hope this is useful.
ehfortin
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version