Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About pjneder

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. A quote from my friend who had problems and read this thread: Bottom line: mSATA's and BIOSes can have problems. D'uh.
  2. I have a few questions/comments. How are you powering the drives? I realized that there are a few differences from what I did. I started with a DQ77KB and then I couldn't figure out how to get the HDD's to spin up when they were connected to the power supply and SMC HBA. I also had started with the wrong i3 CPU to do VT-d. I knew I could easily re-purpose the 77KB and i3 to something else, so I kind of started over a bit. I went to the DQ77KM (u-ATX) and i5-3470S, all with VT-d capabilities. Eventually I figured out that my SASLP had a bad port 5 on the board. Well, now that I had a PCIEx8 slot I jumped up to a M108 card. That being said, what are you trying to do *seems* like it should work. I never did any of that 13h disabling stuff, so not sure about that. What are you booting/running ESXi from? Is the mSATA disk your boot + datastore for ESXi? I have a buddy also running ESXi but not doing unRAID so he skipped the VT-d parts. He had terrible problems with an mSATA drive, but I forget the details. I'll point him to this thread and see if he will send me some comments. You could easily be having a mPCI issue. In my setup I boot ESXi from a USB stick and have an old laptop 2.5" HDD as my datastore. You could consider taking the mSATA out of the picture for a while and see if that helps. There are plenty of guides on how to put ESXi on a USB stick then any old HDD connected to the mobo ICH sata port for your DS. Your almost there, don't give up yet...
  3. [sOLVED]! OK, I figured out what the problem was. I had selected "Other (32b)" as the type of Linux. Hence ESXi would never allow me to assign a VMXNET3. Once I switched that to "Ubuntu (32b)" I got that choice in the drop down and unRAID (with http://lime-technology.com/forum/index.php?topic=11449.0 installed) found the interface just fine. Now I'm working all sweet like. P.S. FWIW pfSense is another story. Figured out how to do the necessary custom install of VMWare tools, but traffic shaping is acting all fussy so I've dropped back to E1000 until I can sort that out.
  4. Thanks for the response. I follow everything you are saying and I'm pretty familiar with how that works. Attached are a few snips from the VM summary tabs. I understand how *nix generally enumerates interfaces. In the case of pfSense and unRaid both it will automatically find the interfaces, even if it does renumber them. For me, I must still be missing something simple because the VMXNET3 don't show up at all on unRAID or pfSense. I have an Ubuntu appliance VM from Bitnami running Wordpress and in that VM it does show up as VMXNET3. On that VM the tools show as "Installed (current)" and not as 3rd party. Same in my Win7 VM running apcupsd. Therefore the real question is: How have folks gotten VMXNET3 adapters to work on unRAID? thanks!
  5. I wonder if I got the *right* non-standard driver. Both of the interfaces work fine, as E1000's, but I haven't gotten VMXNET3 to work on any VM so far...
  6. I am not getting the option to assign a VMXNET3 NIC to my unRAID VM. Furthermore, although not unRAID related directly, if I assign VMXNET3 NICS to my pfSense VM they do not show up. For reference the NICs on this mobo are both Intel. 82574L and 82579LM When I look in the vSwitch properties under Network Adapters tab I see that the driver is listed a e1000e. Curious if anyone has thoughts on what I need to fix. Thanks!
  7. BQ, Thanks for the excellent summary on how to do this!! While doing my own hunting around I came across another interesting page that provides some great background for those considering whether to buy the M1015. http://www.servethehome.com/ibm-m1015-part-1-started-lsi-92208i/ On the page about cross-flashing here: http://www.servethehome.com/ibm-serveraid-m1015-part-4/ He mentions leaving off the -b mptsas2.rom piece in order to get the card to boot faster at start. Seems kind of handy to me. Not that you will start your ESXi server very often, but it might be interesting to some, especially native unRAID installs. Cheers.
  8. What do you guys do to start things back up when the power is restored? In particular I am thinking about the very common situation where I would be away on business and then the router, file-server, etc are all offline. I could set the BIOS to always boot when power is restored. However that does not solve the scenario where ESXi gets shutdown and power is restored before UPS is empty. Maybe don't shut down ESXi until 1% or whatever the lowest amount is that apcupsd can monitor? Or just keep ESXi up and let the host go down with the power. Have BIOS set to "restore last state" or even "power on with A/C"? What do you guys do?
  9. Joe, Handy advise that... In my structure, under "Media" is only directories. You have to go another level deeper to see files and thumbs. I'm wondering what could be getting accessed? Thanks!
  10. Read the first post in this thread. It has all of the instructions.
  11. I'm new to cache_dirs. Don't know why I didn't use it before except that I was lame... Anyway, running it under the plug-in interface on 5.0-rc12a. This is all on a VM. When I open my "Media" share in Windows, disk #2 always spins up. Media is spread across several disks. I'm using pure default config on the plug-in interface. root@Floater:~# free -l total used free shared buffers cached Mem: 2074512 739824 1334688 0 334304 211760 Low: 890824 511788 379036 High: 1183688 228036 955652 -/+ buffers/cache: 193760 1880752 Swap: 0 0 0 Doesn't look like I'm running into memory limits. ESXi also shows way below the 2GB commit limit for the VM. Where can I look for more debug data? Thanks, Paul
  12. As mentioned in this thread (http://lime-technology.com/forum/index.php?topic=11449.msg237858#msg237858) I cannot get the VMTools plugin to completely agree with ESXi. I will go the script route. Still wish I could solve the other problem with VMTools though....
  13. Bad port 5 on the SASLP-MV8. It will be on it's way back to Newegg soon. I'll probably replace it with a M1015 instead.
  14. I making some progress on this. It is either 2 ports on the SATA4-7 connector or it is 2 cables on the SFF8087 cable. A few more experiments should yield the final results. Either way an RMA of something is in my immediate future. Sigh..... :'( :'( :'( :'(