ESXi 5.x - pre-built VMDK for unRAID


Recommended Posts

I just have this in my GO file after emhttp to map the vmdk to a mount point:

mkdir /mnt/boothdd
mount -w -t vfat /dev/hda1 /mnt/boothdd 2>&1

 

I also share it with an smb-extra.conf:

[boothdd]
comment = Public Folder
path = /mnt/boothdd
public = yes
writable = yes

Then I just copy across the network to both the flash share and my boothdd share and reboot the unRAID VM - done.  The only time I have to do anything is when I need to run make_bootable.bat again.

 

How do you know what drive to mount?  I tried with /dev/hda1 and the share just shows empty.  When I do /dev/sda1 it seems be the flash drive.

You have to change that /dev/hda1 to the vmdk if yours is not the first IDE vmdk on your VM then you might need /dev/hdb1 for instance.  I only have a single IDE device defined in the VM hence the /dev/hda1.  You need the 1 so that it points at the partition not the drive for the mount point.  I got that part of the code from unMENU which is what you can also use if you only want to make this temporarily available.  unMENU will mount it and share it for you.  I just put it in my go file and smb-extra.conf to make it ALWAYS available.  I use IDE on my VMs for the vmdk because I've never been able to make unRAID boot off of a SATA vmdk.  To use unMENU to temporarily mount the drive just go to the Disk Management tab and scroll down to the bottom you will see something like attachment.  The buttons to mount and share are at the bottom.  You have to mount it twice.  The first time just mounts it read only then gives you the option to remount read/write.  Then share it out.  Next boot it will be gone or if you unshare and unmount it.

 

Edit: Also by making my vmdk IDE I don't have to worry about unRAID/Linux changing the boot device location since it is the ONLY IDE HDD on the VM.

 

Edit2: Must admit I didn't try too hard to find the problem with booting to a SATA vmdk since I had this in mind when I setup my first ESXi build.

unMENU_vmdk_drive.png.d11687cb11e1438daef03ac2504f98f7.png

Link to comment

BobPhoenix - I tired your method and I can't get it completely working.  First I had to use /dev/hda.  When I tried /dev/hda1, the boothdd share was empty.  Using /dev/hda, the boothdd share shows the expected contents, but whenever I try to write something it says I need permission.

 

When viewing the drive in unMenu, it only shows the hda, it doesn't show a hda1 below the hda like your screen shot does.  Any ideas?

Untitled.jpg.2d5d8314f44cbfc03f9923a932dcbdd8.jpg

Link to comment

BobPhoenix - I tired your method and I can't get it completely working.  First I had to use /dev/hda.  When I tried /dev/hda1, the boothdd share was empty.  Using /dev/hda, the boothdd share shows the expected contents, but whenever I try to write something it says I need permission.

 

When viewing the drive in unMenu, it only shows the hda, it doesn't show a hda1 below the hda like your screen shot does.  Any ideas?

I didn't use the vmdk's in this thread. I created my own in VMWare and formatted it in a Windows VM as FAT32 maybe that is why it is working as hda1 for me.  As to writing can you write to it using MC on unRAID directly?  If you can then it is in your smb-extra.conf file as that is where the permissions for writing from the network are controlled.  If you can't write to if from unRAID itself then it is the mount that needs to be changed in the GO file.  The -w on the mount command should make it writable.  I started out on this from unMENU.  I mounted it with unMENU and looked at the top of the screen to see the mount command used then copied it and changed the name of the mount point to be one I wanted and put it in my GO file and tested writes with MC.  Then I looked on the forum for smb-extra.conf directions and experimented until I got it working for write across the network.
Link to comment

My .vmdk maps fine as sda1 on my server.  The .vmdk appears as sda in the array screen, with the blue dot against it.  I couldn't get write access initially (trying to delete a file said I needed permission from TOWER\root, and I don't use the root account for any drive mapping.)

 

I then found I could copy the bzroot/bzimage over from within a SSH session, and since I store an unzipped copy of each unRAID release on the array, I'm happy with that.  As Bob mentions, it's probably the smb-extra.conf and network writing permissions, but I didn't bother investigating further.

 

Link to comment

If I add "force user = root" to smb-extra.conf then I can write to the share.  That's the only way I've found so far.  I created my own VMDK with WinImage.  Not sure why mine only works with /dev/hda, but I don't suppose it matters much.

 

BobPhoenix - Thanks so much for this tip!  Definitely useful.

Link to comment
  • 3 weeks later...
  • 2 weeks later...
  • 2 weeks later...

Very interesting thread. I Have my UNRAID esxi VM pro running without any disk only for testing.

 

With other VM guest I can Add new disk (.vmdk) and they show up as a new physical drive in the Guest OS.

 

I tryed that in the Unraid appliance. but disks dont show up in the Unraid web server.

 

lhjl.jpg

 

 

can you  use .Vdmk as  data Disks in UNRAID?

 

Should i Change LSI Logic parallel scsi controller?? which should I use?

 

Thank you!.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.