November 4, 201411 yr Author Server just crashed again. I'll try again when it boots up again. it's not booting. I have to stop the server with the power button, then pull the flash drive, then repair it, then boot again. Why is it 'breaking' the flash drive when this happens?
November 4, 201411 yr Since you have an ASRock board, you may want to add this fix for booting (specifically rebooting). This wouldn't have anything to do with your locking up, but may help with other issues relating to rebooting. http://lime-technology.com/forum/index.php?topic=35739.msg335373#msg335373
November 4, 201411 yr Author Since you have an ASRock board, you may want to add this fix for booting (specifically rebooting). This wouldn't have anything to do with your locking up, but may help with other issues relating to rebooting. http://lime-technology.com/forum/index.php?topic=35739.msg335373#msg335373 Thanks. I had to read thru most of that thread to find the actual solution. (FYI, this is the specific post with the solution; for anyone following along at home ... http://lime-technology.com/forum/index.php?topic=35739.msg335033#msg335033) I'll do that as soon as my server crashes again, since this issue has also been bothering me a bunch lately. I think it was a type-o the "/" before the cat and it is rsyslogd.pid. Try: kill -1 `cat /var/run/rsyslogd.pid` Thanks, but it's still not working. On a fresh reboot. I... deleted the entire /mnt/cache/logs folder ran mkdir -p /mnt/cache/logs ran touch /mnt/cache/logs/syslog ran kill -1 `cat /var/run/rsyslogd.pid` ran logger -ttest test message checked the syslog file; nothing/blank ran logger -test test message (because I'm not sure if ttest is a typo or not) checked syslog file; nothing/blank ran root@media:~# pgrep rsyslog 1263 root@media:~# ps -fp 1263 UID PID PPID C STIME TTY TIME CMD root 1263 1 0 16:33 ? 00:00:00 /usr/sbin/rsyslogd -i /var/run/rsyslogd.pid root@media:~# kill -1 1263 root@media:~# logger -ttest test message root@media:~# logger -test test message checked syslog; nothing/blank I'm not sure where I'm going wrong here. Family is really starting to give me grief that the server 'never works' anymore. I'm at my wits end with this never-ending string of problems with my server. I'm literally willing to do just about anything to get this goddam thing working once and for all. Any other ideas I can try?
November 4, 201411 yr What entry are you putting in the /etc/rsyslog.conf file? You would need that to produce another error log. Are you still running Xen, or did you switch back to non-Xen?
November 4, 201411 yr Author ARRGGGHHHHH I neglected/forgot to add those lines last time. However, I did just notice something weird. just after I manually instigated shutdown, I looked at the console screen and saw this message... error: Failed to get option 'network': Option arument is empty modprobe: WARNING: Module tun is in use. the server shutdown, i pulled the thumb and made the changes from this post to fix the server's inability to reboot (which seems to have worked!!). When the server booted back up, I didn't do anything, and I got that same message on the console again. I'm not sure where it's coming from, but I was not seeing that message prior to trying to get this extra logging setup, so I assume it's related; somehow. I'm going to try setting up the extra logging one more time right now.
November 4, 201411 yr Author okay, still doesn't write to the cache/logs/syslog file, but does write to the regular syslog file... Nov 4 17:16:25 media rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="1274" x-info="http://www.rsyslog.com"] rsyslogd was HUPed Nov 4 17:16:35 media test: test message Nov 4 17:17:08 media est: test message Nov 4 17:18:04 media rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="1274" x-info="http://www.rsyslog.com"] rsyslogd was HUPed Nov 4 17:18:49 media test: test message Nov 4 17:19:10 media est: test message I'm going to try changing everything to put it on the thumb drive, and see if that works. Nope - that didn't work either. I did root@media:/mnt/cache# mkdir -p /boot/logs root@media:/mnt/cache# touch /boot/logs/syslog root@media:/mnt/cache# kill -1 `cat /var/run/rsyslogd.pid` root@media:/mnt/cache# logger -ttest test message nothing in /boot/logs/syslog then I thought I'd remove the second line from rsyslog (*.debug /dev/tty12 ) and see if that helped. root@media:/mnt/cache# nano /etc/rsyslog.conf root@media:/mnt/cache# kill -1 `cat /var/run/rsyslogd.pid` root@media:/mnt/cache# logger -ttest test message it didn't. I'm still not getting any logging other than in the normal syslog. When I was doing the 'fix' for the thumb drive, I realized that I had made a couple changes to folders on that thumb shortly before the crashes returned. I'm inclined to think they are related. I had a folder called "extra" which has to files in it 1) screen-4.0.3-x86_64-4.txz 2) utempter-1.1.5-x86_64-1.txz I had these in there to allow me to run screen while preclearing some disks a couple weeks ago. When the crashing was happening all the time I renamed the folder from "extra" to "OLDextra" I had another folder called "scripts" which had several files in it 1) diskspeed.html 2) diskspeed.sh 3) dupes.sh 4) preclear_disk.sh 5) tunables_tester.sh 6) unRAIDFindDuplicates.sh I have all these in this folder just to keep them off the root of the drive. When the crashes were happening all the time I renamed it from "scripts" to "OLDscripts". After renaming these two folders, and removing 2 plugins (Apcupsd-x86_64.plg & powerdown-x86_64.plg), the crashing stopped for several days. During that time I got my windows VM running, and the server ran for a few days without any problems. Then I changed the names of the folders back (removed the OLD from the names), then yesterday it crashed again. I'm not sure why having folders with these names would cause issues, but it seems to be a problem. Maybe it's not the folder names, maybe it's one of the 2 files in the extras folder; I'm not sure. Anyway, I've put the OLD back into the folder names, and have not had any issues for the last 45 minutes or so. I'm going to start the Windows VM and see if it crashes. if it does, I don't think I've got any external logging working, so I sill won't have any 'evidence' to provide, but I'm not sure what else to do at this point.
November 4, 201411 yr I don't think the kill -1 is working, I just tested it on my machine. Try adding the following into the rsyslog.conf file: *.debug -/mnt/user/Movies/syslog The last is the file destination where you want the log, so customize it based on your shares. The run: /etc/rc.d/rc.rsyslogd restart You should then see the new syslog at the destination you specified in the rsyslog.conf file.
November 5, 201411 yr /etc/rc.d/rc.rsyslogd restart use the restart line. I don't have unRAID 6 so I couldn't tell what was there. However the hup (-1) should work as well. I just tested rsyslog on my CentOS system. hup works, the issue is rsyslog does not duplicate destinations like syslog or syslog-ng. So temporarily, you can just change the /var/log/syslog destination to be on your cache, flash or somewhere else on your array. I would suggest removing the - in front of the file too. That will remove buffering. While it will eat some resources, you do not want to loose messages. mkdir -p /mnt/cache/logs touch /mnt/cache/logs/syslog Change the destination file in /etc/rsyslog.conf to be on your cache drive (remove the - in front of the file) *.debug /mnt/cache/logs/syslog /etc/rc.d/rc.rsyslogd restart There's a way to have duplicate output but that requires a number of other lines that I cannot test right now.
November 5, 201411 yr Author Thanks again for the help. So, it turns out that the problem I'm having must be related to this... When I was doing the 'fix' for the thumb drive, I realized that I had made a couple changes to folders on that thumb shortly before the crashes returned. I'm inclined to think they are related. I had a folder called "extra" which has two files in it 1) screen-4.0.3-x86_64-4.txz 2) utempter-1.1.5-x86_64-1.txz I had these in there to allow me to run screen while preclearing some disks a couple weeks ago. When the crashing was happening all the time I renamed the folder from "extra" to "OLDextra" I had another folder called "scripts" which had several files in it 1) diskspeed.html 2) diskspeed.sh 3) dupes.sh 4) preclear_disk.sh 5) tunables_tester.sh 6) unRAIDFindDuplicates.sh I have all these in this folder just to keep them off the root of the drive. When the crashes were happening all the time I renamed it from "scripts" to "OLDscripts". After renaming these two folders, and removing 2 plugins (Apcupsd-x86_64.plg & powerdown-x86_64.plg), the crashing stopped for several days. During that time I got my windows VM running, and the server ran for a few days without any problems. Then I changed the names of the folders back (removed the OLD from the names), then yesterday it crashed again. I'm not sure why having folders with these names would cause issues, but it seems to be a problem. Maybe it's not the folder names, maybe it's one of the 2 files in the extras folder; I'm not sure. Anyway, I've put the OLD back into the folder names, and have not had any issues for the last 45 minutes or so. Since renaming these folders, I've opened the VM in VNC, repaired the install, updated a couple of things, rebooted a few times, then rebooted the server. Then I ran the VM with passthru, and it's been fine since then. It's been running all night, and this morning I've played several videos, and it's been very solid. There must be something with either the names of the folders, or, I strongly suspect, one/both of the files in the extras folder causing my issues.
November 7, 201411 yr Author woke up today to a crashed server again. I'll try to implement the steps for logging and report back.
November 8, 201411 yr Author I've come to the conclusion that my crashes might not actually be crashes, but instead, the network getting hoses, so that I can't access unRAID, which feels like it's crashed, even though it may not have. I tested this earlier by unplugging both ethernet cables, waiting about a minute, then plugging in again, and I could access the server again. So, at least one of my crashes wasn't a crash. Who knows how many more were like this. I have since disabled one of the onboard NIC's in BIOS, and am currently using only one NIC. I tried to install/create a new Windows 8 VM, and it hung at 'expanding files' at 2%. I left it for about a half hour, but it was frozen. I think tried to stop the VM from vmMan plugin, but that froze the whole GUI of unRAID. I did still have putty access, so it wasn't a complete crash. Here is what I could grab from the log; not sure if it's helpful at all... root@media:/boot# tail -f /var/log/syslog Nov 7 23:20:16 media kernel: [<ffffffff81124ae5>] do_io_submit+0x225/0x2dc Nov 7 23:20:16 media kernel: [<ffffffff81124ba7>] SyS_io_submit+0xb/0xd Nov 7 23:20:16 media kernel: [<ffffffff815df469>] system_call_fastpath+0x16/0x1b Nov 7 23:20:16 media kernel: NOHZ: local_softirq_pending 2ca Nov 7 23:26:06 media kernel: e1000e: eth0 NIC Link is Down Nov 7 23:26:06 media kernel: br0: port 1(eth0) entered disabled state Nov 7 23:26:16 media kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 7 23:26:16 media kernel: br0: port 1(eth0) entered forwarding state Nov 7 23:26:16 media kernel: br0: port 1(eth0) entered forwarding state Nov 7 23:26:31 media kernel: br0: port 1(eth0) entered forwarding state The eth0 disable and entered are from when I unplugged the cable, before trying putty.
November 9, 201411 yr Author So, things have been pretty good lately. I got a windows 8 VM up and running, and the GPU passthru survives a reboot even. It's all updated, and I've been able to play video on it for most of the day. I've been getting occasional 'micro-stutters' for the last hour or so. usually just a half or one second very fast repeating stutter of the audio, which clears up quickly and video continues along. Not enjoyable, but way better than crashing. Then, about 5 minutes ago, video froze, on both the server/windows 8 VM, and on my laptop playing a different video from the server. The VM had shutdown, and when I looked at the browser to see if the GUI had frozen, I saw that it was running, but there was now a parity check in progress. This means the server just rebooted itself; for no apparent reason. So, still problems, but seemingly different ones now it seems unRAID hates me.
November 9, 201411 yr So, things have been pretty good lately. I got a windows 8 VM up and running, and the GPU passthru survives a reboot even. It's all updated, and I've been able to play video on it for most of the day. I've been getting occasional 'micro-stutters' for the last hour or so. usually just a half or one second very fast repeating stutter of the audio, which clears up quickly and video continues along. Not enjoyable, but way better than crashing. Then, about 5 minutes ago, video froze, on both the server/windows 8 VM, and on my laptop playing a different video from the server. The VM had shutdown, and when I looked at the browser to see if the GUI had frozen, I saw that it was running, but there was now a parity check in progress. This means the server just rebooted itself; for no apparent reason. So, still problems, but seemingly different ones now it seems unRAID hates me. Wait, so you have your gtx 550 working after you reboot the VM?
November 9, 201411 yr Author Wait, so you have your gtx 550 working after you reboot the VM? Yeah, with Windows 8, yes; with Windows 7, no. I rebooted it 3 or 4 times since getting the install finished, all rebooted I'm fine. I guess I need to purchase a windows 8 license now.
November 10, 201411 yr OK, so if you power off the VM and turn it back on, does video still work in that scenario or only reboots?
November 10, 201411 yr Author I installed the OS as much as I could, including updates on a VM with VNC, including reboots. Then I added the GPU passthru, and installed the nvidia driver, and the TV tuner driver. then just used 'restart' from the windows install. it restarted fine. i installed some more windows update, restarted again, just fine. I've since restarted twice more, all without issue. Something a few hours ago caused the whole server to reboot unexpectedly, and when I started the VM again, it started fine again. it's been running fine since then. In other words, I've not rebooted the server on purpose since getting the windows 8 VM running.
November 10, 201411 yr This may sound dumb, but I have to ask, do you have a UPS? Also, with that memory, It looks to be high end fast ram, have you tried dialing back/relaxing some of the timings(settings) for the ram?
November 10, 201411 yr Author I do have a UPS, but I don't have the apcupsd plugin installed, since it seems it might be part of my issues. I have not tried dialing back the memory, nor have I tried to overclock anything. I may look into that next. I've setup the logging to write to my cache drive, but it's run without crashing since then, so I've got new clues to what's going on yet. The next time it crashes I'll hopefully have some logging to point to some issue, and if it points to memory, or to nothing, that seems a good next step.
November 11, 201411 yr Author I thought I had this situation resolved, as it's been stable for a couple of days. I decided to 'tweak' by XML for my Windows8 VM, to make sure I'm getting the 'right' amount of cores and memory to the VM, and in the right way. Based on feedback from jonp, I made some small changes and restarted the VM, but passthru wasn't working. So I stopped it with the vmMan plugin, and lost all access to my server I rebooted the server, but still had no access. I rebooted again, and still have no access. I rebooted my router, and still have no access. I rebooted the server into safe mode, and now have access again. Here is the end of the syslog, which does seem to have been writing to the cache drive. Nov 11 12:29:32 media kernel: device vnet0 entered promiscuous mode Nov 11 12:29:32 media kernel: br0: port 2(vnet0) entered forwarding state Nov 11 12:29:32 media kernel: br0: port 2(vnet0) entered forwarding state Nov 11 12:29:46 media kernel: vfio-pci 0000:07:00.0: enabling device (0400 -> 0402) Nov 11 12:29:47 media kernel: br0: port 2(vnet0) entered forwarding state Nov 11 12:29:51 media kernel: vfio-pci 0000:01:00.0: Invalid ROM contents Nov 11 12:29:51 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:51 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:51 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:52 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609a20 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609ae0 Nov 11 12:29:52 media kernel: usb 3-12.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:52 media kernel: usb 3-12.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:52 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:52 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:52 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609780 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609720 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609600 Nov 11 12:29:52 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:52 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:52 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:52 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3200 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3290 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3248 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767588 Nov 11 12:29:52 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767540 Nov 11 12:29:53 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:53 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:53 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:53 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:53 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3200 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3290 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3248 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767588 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767540 Nov 11 12:29:53 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:53 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:53 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:53 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:53 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609780 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609720 Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609600 Nov 11 12:29:53 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:53 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:53 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:54 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:54 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:54 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:54 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:54 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609a20 Nov 11 12:29:54 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609ae0 Nov 11 12:29:54 media kernel: usb 3-12.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:54 media kernel: usb 3-12.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:54 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:54 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:54 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:54 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:54 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:54 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:55 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609a20 Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609ae0 Nov 11 12:29:55 media kernel: usb 3-12.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:55 media kernel: usb 3-12.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:55 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:55 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:55 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:55 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:55 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609780 Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609720 Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609600 Nov 11 12:29:55 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:55 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:55 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:55 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Nov 11 12:29:55 media kernel: usb 3-12.2: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.2: reset low-speed USB device number 5 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609a20 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609ae0 Nov 11 12:29:56 media kernel: usb 3-12.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:56 media kernel: usb 3-12.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:56 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:56 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3200 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3290 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3248 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767588 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767540 Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:56 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Nov 11 12:29:56 media kernel: usb 3-12.4: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.4: reset full-speed USB device number 7 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3200 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3290 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800adce3248 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767588 Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224767540 Nov 11 12:29:56 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:56 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:56 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:56 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Nov 11 12:29:56 media kernel: usb 3-12.3: hub failed to enable device, error -22 Nov 11 12:29:57 media kernel: usb 3-12.3: reset full-speed USB device number 6 using xhci_hcd Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609780 Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609720 Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880224609600 Nov 11 12:29:57 media kernel: usb 3-12.1: reset full-speed USB device number 4 using xhci_hcd Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4. Nov 11 12:29:57 media kernel: usb 3-12.1: hub failed to enable device, error -22 Nov 11 12:29:57 media kernel: usb 3-12.1: reset full-speed USB device number 4 using xhci_hcd Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4. Nov 11 12:29:57 media kernel: usb 3-12.1: hub failed to enable device, error -22 Nov 11 12:29:57 media kernel: usb 3-12.1: reset full-speed USB device number 4 using xhci_hcd Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022187b9c0 Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022187ba08 Nov 11 12:29:57 media kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802246096c0 Nov 11 12:29:57 media kernel: usb 3-12.1: ep 0x83 - rounding interval to 64 microframes, ep desc says 80 microframes Full log is attached. I've confirmed that one and only one NIC is enabled in my BIOS, and that that NIC can get to the internet, by trying to do a network update of the BIOS, and it connected and came back to confirm that my BIOS is up to date, so the NIC is working. I'll reboot again, into 'normal' mode to see where I stand right now. FYI, apparently safe mode still enables dockers to run. Not sure why, but okay. syslog.zip
November 15, 201411 yr Author My server just rebooted again for no reason. I'm going to change the logging again to try to figure out why. As much for myself in the future as anything else, here are the steps for making this change... mkdir -p /mnt/cache/logs touch /mnt/cache/logs/syslog nano /etc/rsyslog.conf Change *.debug -/var/log/syslog to *.debug /mnt/cache/logs/syslog save changes /etc/rc.d/rc.rsyslogd restart logger -ttest test message verify it's writing to syslog on cache Hopefully persistent logging gets added to unRAID soon.
December 10, 201411 yr My server just rebooted again for no reason. I'm going to change the logging again to try to figure out why. As much for myself in the future as anything else, here are the steps for making this change... mkdir -p /mnt/cache/logs touch /mnt/cache/logs/syslog nano /etc/rsyslog.conf Change *.debug -/var/log/syslog to *.debug /mnt/cache/logs/syslog save changes /etc/rc.d/rc.rsyslogd restart logger -ttest test message verify it's writing to syslog on cache Hopefully persistent logging gets added to unRAID soon. Well, actually you can persist your /etc/rsyslog.conf if you copy it to /boot/config/rsyslog.conf I built and pushed for the upgrade to rsyslog because there's a few really neat things we can do with it over the original syslog shipped with slackware. More to come down the road with this after 6.0 is out the door. For now that little gem will persist your rsyslod across reboots (and capture the entire log starting from system boot to output to your intended target log location). The check for (and copy of) /boot/config/rsyslog.conf to /etc/rsyslog.conf happens right before the rsyslogd service is started up during the boot process.
December 11, 201411 yr Justin, Since you've acquired new hardware, have your crashing issues persisted? If not, please update this thread as solved (or I can do that too). Thanks!!
December 11, 201411 yr Author Yeah, it seems to be resolved now. I didn't want to mark it solved until I'd given it a good amount of time, but after about 2 weeks, my VM has only rebooted once, for no apparent reason. That happened after i replaced the virtio driver location in my windows VM XML. After replacing with the .94 version, then starting the VM, the whole server became unresponsive. I hard booted, then removed the virtio driver location entirely from the XML, since the drivers are already installed, and working fine. It was probably just a coincidence. Anyway, it seems a new motherboard, SATA card, CPU fan and 2 new case fans (after previously replacing the power supply, 3 hard drives, and several SATA cables) has gotten this under control. Knock on wood, my windows 8 VM has been running great lately. Thanks again for all your help.
December 11, 201411 yr Yeah, it seems to be resolved now. I didn't want to mark it solved until I'd given it a good amount of time, but after about 2 weeks, my VM has only rebooted once, for no apparent reason. That happened after i replaced the virtio driver location in my windows VM XML. After replacing with the .94 version, then starting the VM, the whole server became unresponsive. I hard booted, then removed the virtio driver location entirely from the XML, since the drivers are already installed, and working fine. It was probably just a coincidence. Anyway, it seems a new motherboard, SATA card, CPU fan and 2 new case fans (after previously replacing the power supply, 3 hard drives, and several SATA cables) has gotten this under control. Knock on wood, my windows 8 VM has been running great lately. Thanks again for all your help. I'm THRILLED to hear this. Glad your system issues are all resolved.
December 11, 201411 yr Author I'm THRILLED to hear this. Glad your system issues are all resolved. You and me both!! I hope all the random weirdness is behind me for good now.
Archived
This topic is now archived and is closed to further replies.