gnollo Posted December 21, 2018 Share Posted December 21, 2018 clear browser cacheDone that. On three different browsers, no change.Sent from my SM-A520F using Tapatalk Quote Link to comment
trurl Posted December 21, 2018 Share Posted December 21, 2018 14 minutes ago, gnollo said: Done that. On three different browsers, no change. Sent from my SM-A520F using Tapatalk Perhaps there is something wrong with your flash. Put the boot flash in your PC and make a backup of the config folder. Prepare flash as a new install. Copy config backup to flash, Boot Quote Link to comment
Squid Posted December 21, 2018 Share Posted December 21, 2018 1 hour ago, gnollo said: Copied the bz* files across: bzfirmware bzimage bzmodules bzroot bzroot-gui Rebooted Now all I have is the top banner, with an indication of the % disk used. Any suggestions? On the flash drive, see if there is /config/dynamix.plg Delete it, and you're probably good to go after a reboot 1 Quote Link to comment
gnollo Posted December 21, 2018 Share Posted December 21, 2018 4 hours ago, Squid said: On the flash drive, see if there is /config/dynamix.plg Delete it, and you're probably good to go after a reboot Well spotted Squid. There was a dynamix.plg inside the plugins folder within Config. Deleted, rebooted, back in business. Upon reboot I received the following message: udma crc error count is 4, for drive 6. Diagnostics attached tower-diagnostics-20181221-0644.zip Quote Link to comment
JorgeB Posted December 21, 2018 Share Posted December 21, 2018 42 minutes ago, gnollo said: Upon reboot I received the following message: udma crc error count is 4, for drive 6. That attribute wasn't monitored by the older release you were using, just acknowledge it, you only need to worry about it if it keeps increasing. 1 Quote Link to comment
vurt Posted December 21, 2018 Share Posted December 21, 2018 I just noticed at the bottom of the unRAID WebUI (the "ticker), it still says "Array Started. Starting services..." after my unRAID has been up for 14 days. Quote Link to comment
spencers Posted December 24, 2018 Share Posted December 24, 2018 Just updated to this version from 6.4.1 and everything went smoothly except DNS is no longer resolving. Is there any known issues or a quick fix? Quote Link to comment
trurl Posted December 24, 2018 Share Posted December 24, 2018 Just now, spencers said: quick fix Have you tried 8.8.8.8? Quote Link to comment
spencers Posted December 24, 2018 Share Posted December 24, 2018 (edited) 19 minutes ago, trurl said: Have you tried 8.8.8.8? Yes I've tried changing it to 8.8.8.8, and when I ping anything from command line I get: PING google.com (216.58.217.206) 56(84) bytes of data. From 169.254.160.146 icmp_seq=1 Destination Host Unreachable EDIT: Deleted network.cfg from flash and rebooted. Works now. Edited December 24, 2018 by spencers Quote Link to comment
Zonediver Posted December 24, 2018 Share Posted December 24, 2018 11 hours ago, spencers said: Yes I've tried changing it to 8.8.8.8, and when I ping anything from command line I get: PING google.com (216.58.217.206) 56(84) bytes of data. From 169.254.160.146 icmp_seq=1 Destination Host Unreachable EDIT: Deleted network.cfg from flash and rebooted. Works now. ..thats an APIPA Adress (Automatic Private IP Adressing) Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 (edited) Hi all, I updated from 6.5 to 666. I'm now getting random lockups. Any help pointing me in the right direction would be much appreciated. tower-syslog-20190101-1403.zip Edited January 1, 2019 by bel_din Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 2 hours ago, bel_din said: Hi all, I updated from 6.5 to 666. I'm now getting random lockups. Any help pointing me in the right direction would be much appreciated. tower-syslog-20190101-1403.zip Go to Tools - Diagnostics and attach the complete zip file to your next post. Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 Thanks in advance tower-diagnostics-20190101-1637.zip Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 39 minutes ago, bel_din said: Thanks in advance tower-diagnostics-20190101-1637.zip Nothing obvious. You might try Troubleshooting Mode in Fix Common Problems to capture logs closer to the crash. Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 This May help, the last time it locked up. I had a monitor plugged in and it showed something about an irq I'm guessing its not in logs because of the hard resets needed. Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 Its in troubleshooting mode now. Thanks. Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 4 minutes ago, bel_din said: This May help, the last time it locked up. I had a monitor plugged in and it showed something about an irq I'm guessing its not in logs because of the hard resets needed. A photo from the monitor might also help when it happens again. Yes, diagnostics aren't saved except in Troubleshooting mode, and all logs etc are lost on reboot since all the OS files are in RAM. Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 Will do that. Did you happen to see anything in the logs about plex? It fails to start during boot. Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 1 minute ago, bel_din said: Will do that. Did you happen to see anything in the logs about plex? It fails to start during boot. Not really. Did notice some wrong csrf tokens in the syslog. This typically means you left a browser open somewhere when you rebooted. Doesn't look like you have cache. Is this true? Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 Correct no cache drive or parity yet. this has been kind of a long term test project. Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 Since you don't have cache, where is your system share? Go to Shares page and click Compute... Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 (edited) New Bitmap Image.bmp Looks Like Disk 1 Edited January 1, 2019 by bel_din Quote Link to comment
trurl Posted January 1, 2019 Share Posted January 1, 2019 Well I haven't seen anything suspicious in anything you have given us so far. As for plex, you might try this: Quote Link to comment
bel_din Posted January 1, 2019 Share Posted January 1, 2019 Thanks for your help. If it stays running overnight Ill probably just reinstall the plex docker. If it crashes overnight I have a monitor and will snap a pic and post the troubleshooting mode logs. Thanks again Rob Quote Link to comment
dirtysanchez Posted January 3, 2019 Share Posted January 3, 2019 Hello all, Updated to 6.6.6 from 6.6.5. I am now unable to stop dockers. Most containers are linuxserver.io. Have also tried to stop from cmd line and it does not stop. Also rolled back to 6.6.5 and no change. It is possible this started before the upgrade and I just haven't had to manually stop a docker in a month or two. Did some searching and didn't find much. Not sure this is related to the unRAID version or some other issue. Diags attached. Many thanks for any assistance. landfill-diagnostics-20190102-1851.zip 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.