Ash I think bonienl was referring to no news from LT not the users.

 

Sent from my LG-H815 using Tapatalk

 

Indeed... LT can't respond to everybody, users are encouraged to report as much as possible!

Since the beta has ESXi support, has anyone managed to create a VM successfully running vmware esxi 5.x or 6.x?

If so, what template is best to use? thanks.

Just wondering... just do it "because you can"?  Or some specific reason ?  It sounds like asking for trouble having a hypervisor run on a hypervisor..

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

syslog.txt

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

from the console,

diagnostics

  will be saved to the flash drive.

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

 

Diagnostics is built into the system. Nothing for you to do but execute diagnostics and then copy the resulting zip file from the flash drive.

Just wondering... just do it "because you can"?  Or some specific reason ?  It sounds like asking for trouble having a hypervisor run on a hypervisor..

 

because I come from vmware esxi to unraid and what to get back in to it for learning and practice. Got a VCP6 to take!

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

from the console,

diagnostics

  will be saved to the flash drive.

 

Oh, whoops. I was looking at the WiKi and it was mentioning I had to download something. I ran it and attached

tower-diagnostics-20160419-1149.zip

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

from the console,

diagnostics

  will be saved to the flash drive.

 

Oh, whoops. I was looking at the WiKi and it was mentioning I had to download something. I ran it and attached

What would happen if you set /boot/config/network.cfg and BONDING="NO"

Since the beta has ESXi support, has anyone managed to create a VM successfully running vmware esxi 5.x or 6.x?

If so, what template is best to use? thanks.

I don't think Unraid has ever officially supported ESXI. In fact now it includes it's own hypervisor I think it's even less likely to "officially" support ESXI.  Doesn't mean you can't get it working of course...

 

Sent from my LG-H815 using Tapatalk

 

 

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

from the console,

diagnostics

  will be saved to the flash drive.

 

Oh, whoops. I was looking at the WiKi and it was mentioning I had to download something. I ran it and attached

What would happen if you set /boot/config/network.cfg and BONDING="NO"

 

There's only one NIC on the VM, so there's no bonding available

 

But it's not a network configuration issue, it's an issue with the passthrough. It's affecting other passed through devices, 6.2 doesn't see the drives on my RAID card either, which pick up just fine on 6.1.9. The network thing was just the first issue I noticed, because I couldn't even get into the system right off the bat

Since the beta has ESXi support, has anyone managed to create a VM successfully running vmware esxi 5.x or 6.x?

If so, what template is best to use? thanks.

I don't think Unraid has ever officially supported ESXI. In fact now it includes it's own hypervisor I think it's even less likely to "officially" support ESXI.  Doesn't mean you can't get it working of course...

 

Sent from my LG-H815 using Tapatalk

 

So, anyone tried it and had success then?

For a second time now I get the server runing 6.2b21 locked while running SyncBack between two unraid servers.

Source is running 6.2beta21 and destination is running 6.1.9.

The system GUI freezes, Dockers and VM's are not responding, ssh is still working but when launching powerdown the command freezes at: "Starting diagnostics collection..." see picture attached.

Luckily the cp /var/log/syslog /boot command worked so I can share the syslog file attached.

 

syslog-freeze.txt

Just wondering... just do it "because you can"?  Or some specific reason ?  It sounds like asking for trouble having a hypervisor run on a hypervisor..

 

I love unRAID, but it's not a full blown hypervisor. Sometimes, unRAID gets cranky and unresponsive. I need OpenVPN to be up. I need pfSense to be up. ESXi does that and does it well. unRAID does NAS, HTPC and bells and whistles well (docker containers for many useful things, that are not mission critical for home), so that's what I use unRAID for.

Same here... But if you run esxi within unraid you are increasing complexity on a platform that does not fully work for you... Would it then be not a better idea to run unraid in esxi? Instead of esxi in unraid?

 

I have run for years with unraid in esxi, worked great... I switched to unraid hypervisor to try it out and for me it works without any glitches.. Several Ubuntu and Windows vm"s.. I also use a lot less resources this way.

 

 

Verzonden vanaf mijn iPhone met Tapatalk

FYI

 

I just tried FreeBSD template, changed VIRTIO to SATA and used the following interface  <model type='e1000-82545em'/>

ESXI 6.0 boots and installs fine so I'm happy.

 

;D

I have no idea what the last 2 posters are doing, but unRAID is a guest VM on my ESXi. I don't think anyone in their right mind would do the reverse.

I have no idea what the last 2 posters are doing, but unRAID is a guest VM on my ESXi. I don't think anyone in their right mind would do the reverse.

 

From the OP of the Beta 18 thread:

 

Nested virtualization support

 

Now you can install VMWare on unRAID as a VM itself!  Yup!  It really works!

I have no idea what the last 2 posters are doing, but unRAID is a guest VM on my ESXi. I don't think anyone in their right mind would do the reverse.

 

I'll need to do so when my VCP comes up for renewal now that i'm running unraid on bare metal.

I have no idea what the last 2 posters are doing, but unRAID is a guest VM on my ESXi. I don't think anyone in their right mind would do the reverse.

 

I tend to agree... it might be possible but it really sounds like the wrong way around... Unraid is really great with VM's, personally I have no need for esxi anymore, but -should- I have that need I would also opt for an esxi host with unraid running as a guest, probably with dockers in the unraid guests and esxi vm's for everything I would feel the need for a vm..

 

But as said: unraid with dockers and several vm's, runnin on both my primary and secundary system is running absolutely flawless.. I litterally have had -no- issues with unraid since I moved away from esxi.. But that kind of has been the case with unraid since I started using it in the beginning, no issues.. Maybe I have a very favourable hardware setup.

But it's not a network configuration issue, it's an issue with the passthrough. It's affecting other passed through devices, 6.2 doesn't see the drives on my RAID card either, which pick up just fine on 6.1.9. The network thing was just the first issue I noticed, because I couldn't even get into the system right off the bat

 

Confirmed issue: http://lime-technology.com/forum/index.php?topic=48374

 

Can limetech or jonp chime in? Hopefully something that can be fixed, but it's been around for all 6.2 betas

But it's not a network configuration issue, it's an issue with the passthrough. It's affecting other passed through devices, 6.2 doesn't see the drives on my RAID card either, which pick up just fine on 6.1.9. The network thing was just the first issue I noticed, because I couldn't even get into the system right off the bat

 

Confirmed issue: http://lime-technology.com/forum/index.php?topic=48374

 

Can limetech or jonp chime in? Hopefully something that can be fixed, but it's been around for all 6.2 betas

The last time something like this happened, the official response was, we don't support unraid as a guest, if it works fine, if not, and you can troubleshoot why and tell us what needs to be changed to fix it we will consider making the change, but we are not going to spend the time to troubleshoot it. They don't break ESXI support on purpose, they just aren't going to spend any time making it work.

 

Maybe that stance has changed, and Tom or Jon will help with ESXI support, but I seriously doubt it with all the other things going on right now.

For a second time now I get the server runing 6.2b21 locked while running SyncBack between two unraid servers.

Source is running 6.2beta21 and destination is running 6.1.9.

The system GUI freezes, Dockers and VM's are not responding, ssh is still working but when launching powerdown the command freezes at: "Starting diagnostics collection..." see picture attached.

Luckily the cp /var/log/syslog /boot command worked so I can share the syslog file attached.

 

Some comments, many probably unrelated to your issues, but ... -

 

* Several devices report only 32 bit DMAR, r8169 (your Realtek NIC) and certain USB ports.  I'm not very knowledgeable in this, but I don't believe that's going to work correctly, especially virtualized.

 

* NerdPack reports installing Python 2.7.9.  I believe you need 2.7.11 for 6.2 betas.  Edit: Later 2.7.11 is installed also.

 

* The packages libevent-2.0.22-x86_64-1 and ncurses-5.9-x86_64-4 are already installed, but the Preclear beta *upgrades* them with /boot/config/plugins/preclear.disk.beta/libevent-2.0.21-x86_64-1.txz and /boot/config/plugins/preclear.disk.beta/ncurses-5.9-x86_64-2.txz.

 

Apr 19 02:36:57 Tower kernel: DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.

Apr 19 02:36:57 Tower kernel: DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.

Apr 19 02:36:57 Tower kernel: DMAR-IR: Enabled IRQ remapping in xapic mode

Apr 19 02:36:57 Tower kernel: x2apic: IRQ remapping doesn't support X2APIC mode

* Don't know if it's important but kernel people are recommending the options above.  You might also check the BIOS settings, and check for a BIOS update.

 

* Strongly recommend you switch to static IP (192.168.0.40).  That should clean up some of the errors.  The first renewal does not seem to proceed completely correctly when virtual networking is involved, not the first time I've seen that.  Can't say it caused your problems, but it would be interesting to see how it behaves when changed.

 

* USB devices were disconnected near the end.  That's fine if you did it, not good if you didn't.

 

* Powerdown started but got nowhere.  What ever the first actions, they didn't happen.  Possibly user or system kill scripts to stop VM's and Dockers?

Obviously can't share any logs since I can't get into the system, but, thoughts?

So it doesn't boot at all? Do you get a local console prompt? If so, log in and run the diagnostics script at the local console, then post the resulting zip file. Just because the network doesn't appear to be working doesn't mean the system isn't booting.

 

It boots, and looks totally fine, outside of the fact that the network (and presumably other passed through devices) aren't being picked up. I can get into the console, but have no way of downloading the diagnostic tool, so best I can do is copy the normal unRAID log to the flash drive so I can access and share it

from the console,

diagnostics

  will be saved to the flash drive.

 

Oh, whoops. I was looking at the WiKi and it was mentioning I had to download something. I ran it and attached

 

I'll start by admitting I'm probably out of my depth here, this was one of the more confusing setups I've ever seen.  You are running this on a VMware base and passing everything through, and then expecting to pass through the passed through devices?  What I don't understand is why don't you remove unRAID and just run the VM's on VMware.  There are no NAS features in use that I could see, no hard drives at all, not even cache.  To this eye (not the most experienced with VM's), it looks like you are trying to run VM's on top of unRAID, on top of VMware, without any other use of unRAID?

 

There's one Intel NIC port passed through, but doesn't work very well.  Although you did get an eth0, it's broken.  You have bonding, bridging, and DHCP turned on.  Try turning off bonding, that may be confusing it (or the fact it's passed through?)  And using a static IP can help.  Not sure if turning off bridging would help or hurt.

 

The SAS controller was passed up to unRAID, and partly was set up successfully, but then failed, not sure why, but can't help wondering if it would work better bare metal.  If there are drives attached, it didn't get far enough in the initialization to find them.

 

Edit: One difference I've noticed between unRAID 6.2 and 6.1, the kernel 4.4 assigns mpt3sas, whereas 4.1 assigned mpt2sas, for cards like that.

Edit2: Sorry EGOvoruhk, I see elsewhere implied that you do have drives attached, and normal NAS usage.  Please ignore those comments.

I have a question for Tom or other parity experts, knowledgeable in the new Q parity.  The P parity we're used to was a simple sum (or in our case the equivalent XOR) of the stream of bits at a specific disk offset.  As such, it didn't matter what order the bits were in, which meant that the disks could be freely rearranged without any change to parity.  This alternative way of calculating the Q parity has to use the same bits, but apply a different algorithm, and it seems likely to me that the bit order matters.  And if it does, then array drives cannot be freely rearranged without invalidating the second parity drive.

 

So there's the question, can we still swap drives around, change their array assignments, without having to redo the Q parity?  I'm asking because I'm updating the FAQ for v6, about rearranging drives within the array.

 

My apologies for never taking the time to study how the new parity drive is calculated!