August 7, 201411 yr I currently running ESXi with unraid and a windows 8 VM for Argus TV, MySQL, and XBMC library sync. My question is now that unraid supports dockers will I be able to use unraid v6 with dockers within ESXi? I will not be able to move away from ESXi completely until there is a tv tuner software comparable to Argus TV, MySQL, and XBMC are all available in dockers. Right now my ESXi setup works great and I don't know if I even want to use dockers but it would be great to know if I can use dockers on my unraid VM.
August 7, 201411 yr My understanding is that Docker does not use virtualization at all, so I see no reason it would not work. And StevenD appears to be doing it successfully. Sounds promising for you!
August 14, 201411 yr Hijacking this thread, as it seems like the original question was answered. This question is directed at StevenD and whoever else has unRAID6b6 running as a VM in ESXi. I currently have unRAID 5 running fine from a hybrid VMDK(with unRAID5 files on it)/USB boot configuration on a VM in ESXI. I wanted to check out unRAID6b6 and docker, but I keep PSOD ESXi when I try to boot unRAID6b6. I've troubleshooted numerous things, and since everything is passed through and configured fine on the current unRAID 5 VM I think it is how I built/repackaged the vmdk for unraid. I've tried opening my current unRAID5 vmdk and copying over the files for the new unRAID6. I've tried making a blank vmdk in esxi, opening it via a windows vm, formatting and running syslinux.exe on the partition and then adding in unRAID6 files. I've tried winimage and copied the image from the usb drive. I've even tried plop on a vmdk. Every single time it begins to boot, I watch the console of unraid, it appears to go through loading, it sees all my drives, gives no error about finding the usb 'UNRAID' , then it just freezes at a random point as ESXi PSOD. The VM for this is the exact same settings as my current unRAID5 VM. The only difference is the USB with unRAID6 and the vmdk with unRAID6. So it has to be one of those. Any ideas or help would be much appreciated. I can provide logs and screenshots if someone thinks those would help. Thanks!
August 14, 201411 yr Hijacking this thread, as it seems like the original question was answered. This question is directed at StevenD and whoever else has unRAID6b6 running as a VM in ESXi. I currently have unRAID 5 running fine from a hybrid VMDK(with unRAID5 files on it)/USB boot configuration on a VM in ESXI. I wanted to check out unRAID6b6 and docker, but I keep PSOD ESXi when I try to boot unRAID6b6. I've troubleshooted numerous things, and since everything is passed through and configured fine on the current unRAID 5 VM I think it is how I built/repackaged the vmdk for unraid. I've tried opening my current unRAID5 vmdk and copying over the files for the new unRAID6. I've tried making a blank vmdk in esxi, opening it via a windows vm, formatting and running syslinux.exe on the partition and then adding in unRAID6 files. I've tried winimage and copied the image from the usb drive. I've even tried plop on a vmdk. Every single time it begins to boot, I watch the console of unraid, it appears to go through loading, it sees all my drives, gives no error about finding the usb 'UNRAID' , then it just freezes at a random point as ESXi PSOD. The VM for this is the exact same settings as my current unRAID5 VM. The only difference is the USB with unRAID6 and the vmdk with unRAID6. So it has to be one of those. Any ideas or help would be much appreciated. I can provide logs and screenshots if someone thinks those would help. Thanks! So, your whole ESXi host PSOD's when you try to boot an unRAID 6 VM?
August 15, 201411 yr So, your whole ESXi host PSOD's when you try to boot an unRAID 6 VM? Yup. Entire ESXi PSOD. I'm at work Right now, but I've downloaded and have been looking through some of the esxi kernel dump logs that it has generated over all my crashes. I think I may have figured it out, but not sure. Will go home and test tonight; My current UNRAID5 usb drive is connected internally on the mobo. When I've been testing the UNRAID6 usb, I've been plugging it into the external port on my Norco case. I have a feeling from the logs that something may be up with that and will try internal tonight. <EDIT AS I TYPE> I just remembered I loaded on unraid5 onto the same usb device (to rule out the new usb drive being bad)and plugged it in externally and it booted fine. so crap. now I don't know again.<END EDIT> So much for that. I've linked to 2 of thee ESXi logs here if you know much about it and are able to browse through it. (txt size was too large to attach) The recurring theme that set me on the internal/external idea above were these similar type of usb lines repeated throughout each crash: log1: 2014-08-14T03:23:51.485Z cpu0:4543)<6>usb 1-1.6: USB disconnect, address 6 2014-08-14T03:23:51.485Z cpu0:4543)<6>usb 1-1.6: usbfs: unregistered usb0106 2014-08-14T03:28:38.203Z cpu0:4543)<6>usb 1-1.6: new high speed USB device using ehci_hcd and address 7 2014-08-14T03:28:38.322Z cpu0:4543)<6>usb 1-1.6: New USB device found, idVendor=0781, idProduct=5571 2014-08-14T03:28:38.322Z cpu0:4543)<6>usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2014-08-14T03:28:38.322Z cpu0:4543)<6>usb 1-1.6: Product: Cruzer Fit 2014-08-14T03:28:38.322Z cpu0:4543)<6>usb 1-1.6: Manufacturer: SanDisk 2014-08-14T03:28:38.322Z cpu0:4543)<6>usb 1-1.6: SerialNumber: 4C530005870704117312 2014-08-14T03:28:38.322Z cpu1:4543)<6>usb 1-1.6: Vendor: 0x0781, Product: 0x5571, Revision: 0x0127 2014-08-14T03:28:38.322Z cpu1:4543)<6>usb 1-1.6: Interface Subclass: 0x06, Protocol: 0x50 [7m2014-08-14T03:28:38.323Z cpu1:4543)WARNING: LinScsiLLD: scsi_add_host:601:vmkAdapter (usb-storage) sgMaxEntries rounded to 255. Reported size was 255[0m 2014-08-14T03:28:38.323Z cpu1:4543)DMA: 609: DMA Engine 'vmhba41' created using mapper 'DMANull'. 2014-08-14T03:28:38.323Z cpu1:4543)<6>usb-storage 1-1.6:1.0: interface is claimed by usb-storage 2014-08-14T03:28:38.323Z cpu1:4543)<6>usb 1-1.6: device is not available for passthrough 2014-08-14T03:28:38.323Z cpu1:4543)<6>usb 1-1.6: usbfs: registered usb0107 ... 2014-08-14T03:37:22.040Z cpu3:7004)<6>usb 1-1.6: device is available for passthrough 2014-08-14T03:37:22.124Z cpu0:7004)<6>usb 1-1.6: reset high speed USB device using ehci_hcd and address 7 2014-08-14T03:37:22.242Z cpu0:7004)<6>usb 1-1.6: Device is allocated for USB passthrough use; not available for VMkernel use 2014-08-14T03:37:22.458Z cpu0:7004)<6>usb 1-1.6: reset high speed USB device using ehci_hcd and address 7 2014-08-14T03:37:22.739Z cpu0:6996)<6>usb 1-1.6: device is available for passthrough [7m2014-08-14T03:37:52.455Z cpu1:4097)WARNING: Heartbeat: 645: PCPU 0 didn't have a heartbeat for 8 seconds; *may* be locked up.[0m https://www.dropbox.com/s/2pyljtnwymnrosm/vmkernel-log1.txt Log2: 2014-08-13T23:58:44.137Z cpu0:42693)<6>usb 2-1.6: Device is allocated for USB passthrough use; not available for VMkernel use 2014-08-13T23:58:44.370Z cpu0:42693)<6>usb 2-1.6: reset high speed USB device using ehci_hcd and address 3 https://www.dropbox.com/s/suwox3ww89565q0/vmkernel-log2.txt ESXi PSOD official error for why it crashed is the 'WARNING: Heartbeat' fail. But I think why the heartbeat check failed is because of the lines above it in the logs about the USB devices.
August 15, 201411 yr I assume you are running the most recent updates on your ESXi host? https://www.vmware.com/patchmgr/findPatch.portal
August 15, 201411 yr I assume you are running the most recent updates on your ESXi host? https://www.vmware.com/patchmgr/findPatch.portal No. I've been on a stable 5.1.0 early build. I've decided not to update in the past, as I saw no reason at the time, and heard 5.5 is not good for the free version to use with unRAID. I suppose at this time I could apply patches. However, I don't see that as really being the issue. Were you able to identify anything in those logs by chance?
August 15, 201411 yr There is a specific patch for this error, but it should have been fixed in 5.1. [7m2014-08-14T03:37:52.455Z cpu1:4097)WARNING: Heartbeat: 645: PCPU 0 didn't have a heartbeat for 8 seconds; *may* be locked up.[0m http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000091
August 17, 201411 yr So after updating ESXi to the latest 5.1.0 build, and still had the issues. I continued to experiment with different ways and I eventually figured it out. I was the stupid one. I use the MV8 cards, and I failed to add the hack for them into the new .vmx file. Simple mistake and one I won't overlook again. So many hours wasted. lol. Thanks again for your help.
Archived
This topic is now archived and is closed to further replies.