jimwhite

Members
  • Posts

    597
  • Joined

  • Last visited

Posts posted by jimwhite

  1. A general tip for anyone running unRAID in ESXi (4.1 or 5.0) if you are looking for a very fast boot up.

     

    Make a .vmdk disk image of your thumb drive using WinImage.  I used a spare (non-licensed) 2gb flash drive I had laying around and deleted the config directory and created the image from it (change the name after the make bootable part to something other then UNRAID).  Upload it to your ESXi server and attach it to your unRAID VM.  Still do the USB passthrough like you normally would. 

     

    What happens is ESXi boots up from the vmdk image (very fast) and sometime during the boot unRAID mounts any flash drive with the name of "UNRAID" and reads the config/license data from it. 

     

    Pro:

    1. Boot up from the local HDD (less then 10 seconds on mine)

    2. Config and license still stored on the thumb drive

    3. Can do away with the plop boot manager/CD

    4. Never have to remove the thumb drive and attach it to a Windows machine again.  All "updating" is done on a spare thumb drive and the images created from it.

    5. Can have a boot vmdk of every version sitting on your server.  Booting a different version is as simple as attaching a different vmdk to the VM guest.

     

    Con:

    1. Haven't found any yet.

    2. Changes to your configuration, i.e. packagemanager changes have to be copied from the flash drive to the .vmdk disk....

  2. just thought I'd add what I posted in the ATLAS thread...

     

    I too, followed the lead of bryanr in his http://lime-technology.com/forum/index.php?topic=7914.0 thread, mapping each drive via command line manipulations, and with 16 drives it was a bit of a pain in the arse.  Not only that, but any time a disk is moved or swapped, it must be done again!!  Gotta be an easier way.

     

    I have 16 hot swap bays in my tower with 16 Samsung 2TB drives.  The first 6 are on the "Intel Controller", the next 8 on an LSI 2008 SAS controller.

    , and the last two on a Marvell 4 port Sata card (which ESXi has no drivers for).  I also have an LSI 4 port raid controller with 3 1TB Seagates in a Raid5 for my ESXi Datastor.

     

    While poking around in the GUI for ESXi (vSphere Client) I found a page where I could assign the entire controller to a VM (configuration/advanced-settings).  I created a new VM for unRAID and instead of going through all that commandline stuff, I assigned the 3 PCI-bus controllers as passthrough, then selected them in the unRAID VM settings.  Voilla.... the VM runs just as if it were (and it is) running on the bare bones.  The drives came right up, and they are not virtually mapped, so I'm free to swap them around and replace them just be re-booting the VM    :o;D

     

  3. I've been using Kingwin 3in2's and 4in3's for awhile with no problems... that is until I bought a mess of Samsung 2TB drives... they're 1/16" shorter than a Seagate and don't quite make a good connection.  Had to tape a piece of 1/16" lexan to the front of 16 drives!  :o

     

  4. I too, followed the lead of bryanr in his http://lime-technology.com/forum/index.php?topic=7914.0 thread, mapping each drive via command line manipulations, and with 16 drives it was a bit of a pain in the arse.  Not only that, but any time a disk is moved or swapped, it must be done again!!  Gotta be an easier way.

     

    I have 16 hot swap bays in my tower with 16 Samsung 2TB drives.  The first 6 are on the "Intel Controller", the next 8 on an LSI 2008 SAS controller.

    , and the last two on a Marvell 4 port Sata card (which ESXi has no drivers for).  I also have an LSI 4 port raid controller with 3 1TB Seagates in a Raid5 for my ESXi Datastor.

     

    While poking around in the GUI for ESXi (vSphere Client) I found a page where I could assign the entire controller to a VM (configuration/advanced-settings).  I created a new VM for unRAID and instead of going through all that commandline stuff, I assigned the 3 PCI-bus controllers as passthrough, then selected them in the unRAID VM settings.  Voilla.... the VM runs just as if it were (and it is) running on the bare bones.  The drives came right up, and they are not virtually mapped, so I'm free to swap them around and replace them just be re-booting the VM  :o;D

     

  5. I run virtualbox on unraid, and I am very happy with the result. Since there is no swap partition and the unraid kernel is not built to use a swap partition I would recommend having ample ram. I run two vms right now without issue on my unraid. All my vmdk files are on a partition that sit outside the protected array. Furthermore, I looked into the whole esxi situation and you need very specific hardware which makes the results with esxi very unpredictable.

     

    I wholeheartedly disagree.  Running Virtualbox on unRaid is a hack at best, while ESXi is designed precisely for the task at hand.  Given reasonable hardware, the results are VERY predictable.  Backing up the VM couldn't be simpler.  Turn the "power" off to the VM, browse to the VM in the datastor browser and export the VM as a file to wherever you'd like to keep it!  :o

  6. Or change the directory name so it's no longer a duplicate location. The message is a little misleading, as it doesn't really detect duplicate files, only a naming collision between files on different drives that are being mapped to the same file in a user share.

     

    Bingo! That's the "issue", but it would seem there would be a better way to disable this reporting (and hence "spamming") of my syslog.  :o

     

  7. I think that it would also allow me to solve a problem which I have just encountered ... it seems that the standard Linux distribution of mptsas (and, I'm guessing, mpt2sas) drivers appear to hit problems in some circumstances.  One proposed solution is to use the driver distributed by LSI.

     

    What problem would this be?

     

    ???

  8. I'm in the midst of a similar build on a Tyan S5512 board.  I have my first 6 drives on the southbridge motherboard "Intel" controller.  When raw-device-mapped to the unRaid VM, the temps don't appear to work whereas the drives mapped through from the LSI SAS controller report correct temps.  Have you seen the same?