bit2bytes4fun

Changed Status to Solved

Thanks, I will wait and see if the developers confirm if its a problem.

Thanks for checking, I am running the latest BIOS/BMC versions

Bare metal hardware info Motherboard:ASRockRack - E3C236D2I Processor:Intel® Xeon® CPU E3-1240 v5 @ 3.50GHz HVM:Enabled IOMMU:Enabled Cache:L1 Cache = 128 kB (max. capacity 128 kB) L2 Cache = 1024 kB (max. capacity 1024 kB) L3 Cache = 8192 kB (max. capacity 8192 kB) Memory:32 GB (max. installable capacity 32 GB)

unraid is not a router. When placing a VM on a VLAN, it is a single host on a single network. Layer 2 VLANs logically separate the layer 3 subnets from subnets on the same physical device. You need a router connect to all VLANs to route IP traffic from the VM to each other and if need be, provide DHCP services for each VLAN from a router or DHCP server. Hope this helps

I'm interested in the answer to that as well. I suspect the answer is No => my original thought was that this is what they wanted to do, which is why I suggested setting bridge mode ... which I believe WOULD allow that. But I suspect with the bonded "broadcast" setting the two networks only "see" the server. The answer would be "NO" The server is not configured as a router. Server has (2) Network Interface Cars (NICs) NIC #1 172.16.1.10/24 NIC #2 192.168.1.10/24 (Gateway 192.168.1.1) Any devices on the 172.16.1.0/24 network would NOT be able to communicated with other devices on the 192.168.1.0/24 through 172.16.1.10 host. The devices on the 172.16.1.0/24 network have their gateway set to 172.16.1.1. The 172.16.1.1 router does not have a route for the 192.168.1.0/24 network. Also the server is not running some type of routing protocol. The server can communicated with devices on either network for it is directly connected to it. For communications out to the internet, it will do so via its configured default gateway

VMware released an update to 5.5 on 12/8. Has anyone tested these updates for the issue? ESXi-5.5.0-20151204001-standard (Build 3248547)

Unfortunately, I am getting exactly the same error message. Any ideas? I ran into the same issue. It appears that the sas2flash is a 32 bit executable file, not a 64 bit version. I built a separate 5.x unRaid USB drive and copied the linux SAS2Flash and firmware/bios files to it.

Seagate Barracuda 7200.14 ST3000DM001 3TB 7200 RPM RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive http://www.newegg.com/Product/Product.aspx?Item=N82E16822148844 use Promo Code: EMCYTZT3444 Expires 5/16/2013

Bob Success!! I was able to transfer a 7G file to unRAID and on to the cache drive and no PSOD. I need to do more testing. It used to crash when TM ran on my MacBook. Is this the best way to move the drives from the MB SATA ports (RDM) to the SASLP controller (pass-through)? [*]verify that unRAID parity is good [*]bring down the array [*]shutdown the unRAID guest [*]move the RDM files in the datastore/unraid folder to a temp folder (done via ssh) [*]shut down the ESXi host [*]disconnect the MB SATA cables from the drives [*]connect the SASLP cables to the drives [*]power up the ESXi host [*]power up the unRAID guest (array off) [*]verify that unRAID sees ALL the drives [*]start the array [*]verify parity and test Thanks again for everyone's help.

Beta Yes, I have it in the bottom slot. For the ASUS P8H77-I Motherboard has a single "PCIe 3.0/2.0 x16 slot". Hopefully that is not a show stopper.

Thank you! I will try that today after work and post back the results.

Screen shot

This forum is great! Such great help. Beta I ssh into into the ESXi host and used vi to edit the file. Bob Not sure how to do that. Can you provide a link on how to do it? Thanks for the quick response.

I been reading this post and almost everyone post on building a ESXi host. I would like move away from RDM and use a dedicated SATA controller for unRAID to get better performance. After installing the AOC-SAS2LP-MV8 and added the hack, I get a PSOD when ever I write to the array. The only drive connected to MV8 is the cache drive. All others drives (Parity/Data) is using RDM through the motherboard SATA interfaces. I am a little leery about moving all unRAID drives to the controller. PSOD screen unRAID as a guest - MV8 (cache), works, but performance sucks. unRAID native + MV8 (cache), performance is good. Any ideas? Use M1015 instead?

I installed a SASLP-MV8 and have it configure setup as a pass-through to unRAID. I then added a cache drive and bingo! I have the get spin up/spin down and temp readings. I will look at moving all the unRAID drives from the on-board SATA ports to the SASLP-MV8. I don't think there will be a performance hit. Thanks BetaQuasi!

I have the drives connected directly to the on board SATA ports. I then created a RDM vmdk file of each disk with the -z option instead of the -a. I figured I had done something wrong, since the spinup/spindown was not working as I had expected, if that's normal, then I am not going to worry about it. What would recommend to use to monitor/track the vitals of a ESXi system? Thanks!

Thanks BetaQuasi I've been working on setting up unRAID 5.0rc12a as a VM. With your vmdk image file it was pretty easy. I got hung up on trying to getting the drives visible in unRAID. I originally configured the ESXi SCSI controller as "LSI Logic Parallel", with no luck. Then I read on another that someone switch theirs "LSI Logic SAS". unRAID was now to seeing the drives in the array!! When I used the PVSCSI or "LSI Logic SAS", unRAID's main menu shows the all drive devices spun down. Flashing green. Which is false, for I can read and write to the array. With them flashing, I cannot get "TEMP" readings. Do you loose this feature when you use a virtual SCSI controller? VMware PVSCSI driver - version 1.0.2.0-k vmw_pvscsi: using 64bit dma vmw_pvscsi 0000:0b:00.0: vmw_pvscsi: host->max_id: 16 vmw_pvscsi 0000:0b:00.0: irq 74 for MSI/MSI-X vmw_pvscsi: using MSI-X scsi0 : VMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=64 vmw_pvscsi 0000:0b:00.0: VMware PVSCSI rev 2 host #0 scsi 0:0:0:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2 scsi 0:0:1:0: Direct-Access ATA ST3000DM001-1CH1 CC24 PQ: 0 ANSI: 5 scsi 0:0:2:0: Direct-Access ATA ST3000DM001-1CH1 CC24 PQ: 0 ANSI: 5 scsi 0:0:3:0: Direct-Access ATA ST3000DM001-1CH1 CC24 PQ: 0 ANSI: 5 scsi 0:0:4:0: Direct-Access ATA ST3000DM001-1CH1 CC24 PQ: 0 ANSI: 5 scsi 0:0:5:0: Direct-Access ATA WDC WD5000KS-00M 07.0 PQ: 0 ANSI: 5

A XEON in my case would be a little risky, so I will play it safe and go with a i7-3770. From what I have seen from other ESXi forum posts, the i7-3770 works just fine for a home build. Thanks.

BetaQuasi From the Esxi 5.0 pointer thread you posted the following: I built my system just like Spencers and Dirty Sanchez (LandFill) but added a AOC-SASLP-MV8 controller. I am looking to do a ESXi system now to minimize plug-in conflicts/problems (been burned enough) and the ability to virtualize hosts for specific apps. I know I need to upgrade the i3 2100 processor with one that supports VT-d and the memory from 4GB to 16GB. Since I only have a single PCIe slot for the controller card, I need the integrated video from the CPU. I don't think I should run it headless. I was considering a Xeon E3-1230 v2 (77w) till I saw your post. I am now thinking to use a i7-3770 (ivy-77w) or Core i7-2600 (sandy-95w). Since I have a small enclosure, I like to keep the wattage as low as possible. From what I have read, sandy is better then ivy for stability/compatibility issues. But I am not sure if that matters to me since I have a single controller card. I would be interested in your thoughts/suggestions on a CPU to use. Here is the list of CPUs that the ASUS PH877-i supports. I am not sure if it's current. Since its ASUS, I am sure its close. Appreciated your thoughts.

I did, but I will do it again tonight and post back

I too have the same issue. I removed openssh from /boot/plugins and from /boot/packages and no luck. What additional steps did you do to remove openssh? Did upgradepkg re-installed itself or was always there but failed to execute from the search path.

Thanks! I will do that.

Thanks. That's what happened. #1 - SOLVED #2 - SOLVED #3 - unresolved