I had 2 server crashed yesterday. I rebooted the server today into XEN but w/o any VMs. Docker is not shut down. No plugins installed other that those which came with stock unRAID.

 

I started a reiserfsck --fix-fixable /dev/mdx for all drives 1-7 (md1 & md5 still running). Everything seems to be fine. However I have the system console full of these messages: Tower kernel: vif vif-3-0 vif3.0: draining TX queue

 

Can you provide a few more details?  What was running and what were you doing ar the time of the crashes? Did the server literally freeze? I'd suggest taking a photo of the console (if it contains other hints) after the crash to give LimeTech a little more to go on.

There was nothing specific and no heavy lifting like large file transfer etc, just the two VM's started (arch with mySQL and AirVideo server / debian with ownCloud).

unRAID was only streaming one movie, so only mySQL was actively doing something.

 

The server was entirely frozen, neither accessible via web gui nor via SSH. Unfortunately the console is just showing endless lines of: Tower kernel: vif vif-3-0 vif3.0: draining TX queue. A photo will not provide any additional information - unfortunately.

 

Btw. reiserfsck --fix-fixable /dev/md1 & md5 finished w/o errors. Filesystem is ok. So that's good news.

Were the VMs Xen or KVM?

 

I had crashes with a Xen VM with beta 5a that was fixed by pinning a core (I actually did 2 = 1 full CPU) to don0.

That's actually an interesting theory.  We haven't been pinning any CPUs to dom0 in our testing, but that doesn't necessarily mean that we shouldn't be.  Another good thing to test for those that are having problems.

 

Sent from my Nexus 5 using Tapatalk

 

 

Another crash after having started a parity check but I took a picture this time. I might need to Run a memcheck.

Read through some of your syslog.  The syslog-20140619-233302.txt file in your ZIP specifically is the biggest one and I noticed lots of this:

 

Jun 19 16:02:37 Tower root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/31/0
Jun 19 16:02:37 Tower kernel: device vif31.0 entered promiscuous mode
Jun 19 16:02:37 Tower root: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif31.0, bridge br0.
Jun 19 16:02:37 Tower root: /etc/xen/scripts/vif-bridge: Writing backend/vif/31/0/hotplug-status connected to xenstore.
Jun 19 16:02:37 Tower root: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/31/0
Jun 19 16:02:37 Tower root: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif31.0-emu, bridge br0.
Jun 19 16:02:37 Tower kernel: device vif31.0-emu entered promiscuous mode
Jun 19 16:02:37 Tower kernel: br0: port 6(vif31.0-emu) entered forwarding state
Jun 19 16:02:37 Tower kernel: br0: port 6(vif31.0-emu) entered forwarding state
Jun 19 16:02:42 Tower avahi-daemon[6571]: Withdrawing workstation service for vif31.0-emu.
Jun 19 16:02:42 Tower kernel: br0: port 6(vif31.0-emu) entered disabled state
Jun 19 16:02:42 Tower kernel: device vif31.0-emu left promiscuous mode
Jun 19 16:02:42 Tower kernel: br0: port 6(vif31.0-emu) entered disabled state
Jun 19 16:02:46 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:02:46 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.000E/input/input17
Jun 19 16:02:46 Tower kernel: hid-generic 0003:0D8C:013C.000E: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:02:46 Tower kernel: br0: port 5(vif31.0) entered forwarding state
Jun 19 16:02:46 Tower kernel: br0: port 5(vif31.0) entered forwarding state
Jun 19 16:02:47 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:02:47 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.000F/input/input18
Jun 19 16:02:47 Tower kernel: hid-generic 0003:0D8C:013C.000F: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:02:47 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:02:47 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.0010/input/input19
Jun 19 16:02:47 Tower kernel: hid-generic 0003:0D8C:013C.0010: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:03:01 Tower avahi-daemon[6571]: Withdrawing workstation service for vif31.0.
Jun 19 16:03:01 Tower kernel: br0: port 5(vif31.0) entered disabled state
Jun 19 16:03:01 Tower kernel: br0: port 5(vif31.0) entered disabled state
Jun 19 16:03:01 Tower kernel: device vif31.0 left promiscuous mode
Jun 19 16:03:01 Tower kernel: br0: port 5(vif31.0) entered disabled state
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/31/0
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif31.0 failed
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: ifconfig vif31.0 down failed
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif31.0, bridge br0.
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: remove type_if=tap XENBUS_PATH=backend/vif/31/0
Jun 19 16:03:01 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge remove for vif31.0-emu, bridge br0.
Jun 19 16:03:05 Tower logger: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/32/0
Jun 19 16:03:06 Tower kernel: device vif32.0 entered promiscuous mode
Jun 19 16:03:06 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif32.0, bridge br0.
Jun 19 16:03:06 Tower logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/32/0/hotplug-status connected to xenstore.
Jun 19 16:03:06 Tower logger: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/32/0
Jun 19 16:03:06 Tower kernel: device vif32.0-emu entered promiscuous mode
Jun 19 16:03:06 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif32.0-emu, bridge br0.
Jun 19 16:03:06 Tower kernel: br0: port 6(vif32.0-emu) entered forwarding state
Jun 19 16:03:06 Tower kernel: br0: port 6(vif32.0-emu) entered forwarding state
Jun 19 16:03:11 Tower avahi-daemon[6571]: Withdrawing workstation service for vif32.0-emu.
Jun 19 16:03:11 Tower kernel: br0: port 6(vif32.0-emu) entered disabled state
Jun 19 16:03:11 Tower kernel: device vif32.0-emu left promiscuous mode
Jun 19 16:03:11 Tower kernel: br0: port 6(vif32.0-emu) entered disabled state
Jun 19 16:03:14 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:03:15 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.0011/input/input20
Jun 19 16:03:15 Tower kernel: hid-generic 0003:0D8C:013C.0011: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:03:15 Tower kernel: br0: port 5(vif32.0) entered forwarding state
Jun 19 16:03:15 Tower kernel: br0: port 5(vif32.0) entered forwarding state
Jun 19 16:03:15 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:03:15 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.0012/input/input21
Jun 19 16:03:15 Tower kernel: hid-generic 0003:0D8C:013C.0012: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:03:15 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci
Jun 19 16:03:16 Tower kernel: input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:0D8C:013C.0013/input/input22
Jun 19 16:03:16 Tower kernel: hid-generic 0003:0D8C:013C.0013: input,hidraw2: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.0-1.2/input3
Jun 19 16:03:30 Tower kernel: br0: port 5(vif32.0) entered forwarding state
Jun 19 16:07:50 Tower kernel: mdcmd (73): spindown 2
Jun 19 16:08:31 Tower kernel: mdcmd (74): spindown 4
Jun 19 16:08:32 Tower kernel: mdcmd (75): spindown 6
Jun 19 16:08:32 Tower kernel: mdcmd (76): spindown 7
Jun 19 16:10:21 Tower avahi-daemon[6571]: Withdrawing workstation service for vif32.0.
Jun 19 16:10:21 Tower kernel: br0: port 5(vif32.0) entered disabled state
Jun 19 16:10:21 Tower kernel: br0: port 5(vif32.0) entered disabled state
Jun 19 16:10:21 Tower kernel: device vif32.0 left promiscuous mode
Jun 19 16:10:21 Tower kernel: br0: port 5(vif32.0) entered disabled state
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/32/0
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: brctl delif br0 vif32.0 failed
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: ifconfig vif32.0 down failed
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif32.0, bridge br0.
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: remove type_if=tap XENBUS_PATH=backend/vif/32/0
Jun 19 16:10:22 Tower root: /etc/xen/scripts/vif-bridge: Successful vif-bridge remove for vif32.0-emu, bridge br0.
Jun 19 16:10:30 Tower root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/33/0
Jun 19 16:10:30 Tower kernel: device vif33.0 entered promiscuous mode

 

Over and over again, VIFs fail, create a new one, remove the old one, rinse repeat.  This is a Xen bug for sure.  What is the network card on your motherboard? 

 Tower kernel: vif vif-3-0 vif3.0: draining TX queue. 

Edgar i had the same issue when i upgraded to beta6, going back to beta4 fixed my stuff =)

 

::using the supermicro h8dme-2 mobo btw i dunno if your using the same mobo.

@Jon, I do not have anything specific....a normal Supermicro board (pls.  see my signature). This board has the following LAN ports:

2x Gigabit Ethernet LAN ports: Intel® 82579LM and Intel® 82574L

1x RJ45 Dedicated IPMI LAN port

 

@Pyrater, thanks for your confirmation. Beta5a was rock solid for me as well.

 

The memcheck was running 3 times and didn't reported any errors. That means that HW and the file system is in good shape. As jonp said, it must be a XEN issue.

Moving back to Beta 5a as there are many who are reporting the same or similar issues. I have unfortunately overlooked the "unRAID 6 Beta 6: Xen-Specific Issues Thread" ... maybe the moderator can move this all to this thread?