itimpi Posted January 28, 2020 Share Posted January 28, 2020 Reboots are normally hardware related in some way. Do you have a UPS? If not then a short power cut could cause that to happen. Quote Link to comment
johnsanc Posted January 28, 2020 Share Posted January 28, 2020 Yes I do have a UPS. None of the clocks in my house are reset so I don't think it was power related. I'll keep an eye on the logs to see if anything else weird happens. Is this user script the best way to capture logs leading up to a crash? #!/bin/bash mkdir -p /boot/logs FILENAME="/boot/logs/syslog-$(date +%s)" tail -f /var/log/syslog > $FILENAME Quote Link to comment
itimpi Posted January 28, 2020 Share Posted January 28, 2020 20 minutes ago, johnsanc said: Yes I do have a UPS. None of the clocks in my house are reset so I don't think it was power related. I'll keep an eye on the logs to see if anything else weird happens. Is this user script the best way to capture logs leading up to a crash? #!/bin/bash mkdir -p /boot/logs FILENAME="/boot/logs/syslog-$(date +%s)" tail -f /var/log/syslog > $FILENAME Probably better is this option that is available in current Unraid releases. Quote Link to comment
Frank1940 Posted January 28, 2020 Share Posted January 28, 2020 1 hour ago, itimpi said: Probably better is this option that is available in current Unraid releases. Here is a link to using the Syslog Server that might be a bit easier to understand: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 Quote Link to comment
wirenut Posted January 28, 2020 Share Posted January 28, 2020 remotely connected using wireguard, from my phone upgraded 6.8.1 to 6.8.2 without error. thank you unraid team! 2 1 Quote Link to comment
johnsanc Posted January 28, 2020 Share Posted January 28, 2020 Thanks all, yeah needing to put in the local IP for the unraid server was not intuitive for the Syslog Server, the help content should be updated for that. Will report back with proper logging if any other crashes occur. Quote Link to comment
testdasi Posted January 28, 2020 Share Posted January 28, 2020 Uneventful update from 6.8.1. 1 Quote Link to comment
Interstellar Posted January 28, 2020 Share Posted January 28, 2020 All OK here from 6.8.1 too. 1 Quote Link to comment
Srengr Posted January 28, 2020 Share Posted January 28, 2020 2 servers 6.8.1 —> 6.8.2. Smooth sailing. 1 Quote Link to comment
Struck Posted January 28, 2020 Share Posted January 28, 2020 Updated from 6.7.2 to 6.8.2 without any problems so far. Dockers stated normally, VMs all good. 1 Quote Link to comment
zoggy Posted January 29, 2020 Share Posted January 29, 2020 (edited) updated from 6.7.2 to 6.8.2, unable to start array. array tab just shows reboot or shutdown, looking at logs: Jan 28 18:24:02 husky emhttpd: error: mdcmd, 2721: Device or resource busy (16): write Jan 28 18:24:02 husky kernel: mdcmd (47): stop Jan 28 18:24:02 husky kernel: md: 1 devices still in use. husky-diagnostics-20200128-1832.zip thinking it may be the recent security change... removing this line from my go file and rebooting: cp /boot/custom/docker-shell /usr/local/bin looks like that was the culprit... went and and just deleted this script since it's not really needed (was checking it out from a spaceinvader video) I know in the 6.8 notes it mentioned about the go entries no longer having the +x bit and you'd have to copy the files off.. but why did this kill the array from being able to boot? or was it just some fluke (I do not have array auto start enabled) Edited January 29, 2020 by zoggy Quote Link to comment
jbartlett Posted January 29, 2020 Share Posted January 29, 2020 I updated two of my three servers. On one, the VM Manager was set to disabled after the reboot. No apparent loss after re-enabling which is fortunate because I have ten custom tweaked VM's that I would find unpleasant to redo that work. On the other machine, a VM that had vanished sometime in the past was now available after the reboot. So, what's the best way to back up the VM settings? Stopping the array and backing up /mnt/user/system/libvirt/libvirt.img ? Quote Link to comment
limetech Posted January 29, 2020 Author Share Posted January 29, 2020 49 minutes ago, jbartlett said: So, what's the best way to back up the VM settings? Stopping the array and backing up /mnt/user/system/libvirt/libvirt.img ? Yes 1 Quote Link to comment
cobhc Posted January 29, 2020 Share Posted January 29, 2020 6 hours ago, jbartlett said: So, what's the best way to back up the VM settings? Stopping the array and backing up /mnt/user/system/libvirt/libvirt.img ? Can be done automatically using this plug-in. 1 Quote Link to comment
scorcho99 Posted January 29, 2020 Share Posted January 29, 2020 7 hours ago, jbartlett said: I updated two of my three servers. On one, the VM Manager was set to disabled after the reboot. No apparent loss after re-enabling which is fortunate because I have ten custom tweaked VM's that I would find unpleasant to redo that work. On the other machine, a VM that had vanished sometime in the past was now available after the reboot. So, what's the best way to back up the VM settings? Stopping the array and backing up /mnt/user/system/libvirt/libvirt.img ? I've had this problem with earlier releases when changing other configuration options. Never really did figure it out, but it never seemed to happen when I wasn't messing with things so I wasn't to worried about it. In my case I never seemed to lose anything, just an annoyance since I had to reboot after re-enabling. Quote Link to comment
SpecFroce Posted January 29, 2020 Share Posted January 29, 2020 My W10 VM refuses to boot. It freezes during startup. This was not a issue in the previous version. Quote Link to comment
JorgeB Posted January 29, 2020 Share Posted January 29, 2020 16 minutes ago, SpecFroce said: My W10 VM refuses to boot. It freezes during startup. This was not a issue in the previous version. Please create a bug report for this. Quote Link to comment
jbartlett Posted January 29, 2020 Share Posted January 29, 2020 2 hours ago, SpecFroce said: My W10 VM refuses to boot. It freezes during startup. This was not a issue in the previous version. I haven't had this particular issue but one of my first troubleshooting steps is to create another VM using the same settings. Sometimes, something gets funged up in the XML that isn't visible in the GUI and it isn't obvious if you aren't intimately familiar with every part of the XML. Quote Link to comment
scubieman Posted January 29, 2020 Share Posted January 29, 2020 (edited) Does this support 9th gen igpu? 9700k ? It appears this uses 4.19.98 and i need 4.20. This correct? Edited January 29, 2020 by scubieman Quote Link to comment
_0m0t3ur Posted January 29, 2020 Share Posted January 29, 2020 Updated from 6.8.1 to 6.8.2. No issues. Thank you for another hassle free unRAID experience. 1 Quote Link to comment
dgreig Posted January 29, 2020 Share Posted January 29, 2020 Can anyone clarify.... rc.docker: include missing changes to suppoort new setting "Host access to custom networks" I can't find this setting anywhere. Quote Link to comment
Ryoko Posted January 30, 2020 Share Posted January 30, 2020 Updated from 6.7.2 to 6.8.2 on 2 servers and seem to have no issues. Dockers are up and running and VMs with passthrough all seem good too. *cheers* 1 Quote Link to comment
falconexe Posted January 30, 2020 Share Posted January 30, 2020 All good here too! 6.81 > 6.82 😉 1 Quote Link to comment
gvers Posted January 30, 2020 Share Posted January 30, 2020 Upgraded 6.7.2 - 6.8.2 no issues all VM's start fine 1 Quote Link to comment
dianasta Posted January 30, 2020 Share Posted January 30, 2020 (edited) Upgraded from 6.7.2 to 6.8.2, and no issues as far as I can see so far. Thanks for the hard work team! Edited January 30, 2020 by dianasta 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.