Steviewunda

Fixed by disabling the unused ethernet adapters

Hi all - my boot process stops for about 2 minutes with the following lines: "Starting haveged entropy daemon: /sbin/haveged br0: failed to request information" Can anyone advise how to deal with this? Diagnostics attached Cheers, Steve tower-diagnostics-20200712-0135.zip

Thanks itimpi

Hi - I received this error message during yesterday's monthly parity check - 'udma crc error count is 1' But at the end of the parity check I got the following - 'Parity check finished (0 errors)' Do I need to worry about this? Cheers Steve

6.8.0 to 6.8.2 and no probs - thanks!

Thanks very much Johnnie - I have upgraded my BIOS and cpu and added a video card and new fans (see signature) and will see how the Win10 VM runs soon.

Sorry - I meant to post the new diags with my last post - here they are tower-diagnostics-20200103-0048.zip

Thanks Johnnie - after a reboot, and parity check, everything seems fine. I ran the extended 'Fix common problems' which only found the 40 re-allocated sectors which appeared 6 months ago. I have attached the current diagnostics logs and would be very grateful if you could check them for errors. Should I re-enable the WIN10 VM and run the diagnostics again, as that is what was running when the problems appeared. Can you see anything about my setup that would cause the VM to be problematic?

I am having problems with disk errors after installing a WIN10 VM per SpaceinvaderOne's video tutorials. The VM became unresponsive so I force stopped it, at which point I began to get disk error messages. I don't want to attempt a reboot until I hear from someone regarding the best course of action. Diagnostics attached - thanks in advance tower-diagnostics-20191231-0944.zip

I am following Spaceinvader's video guide to install a WIN10 VM on unRaid 6.8.0 'A media driver your computer needs is missing' appears early in the installation, and when I try to install from the 'virtio-win-0.1.160-1.iso', I am told that 'No new device drivers have been found'. Here are a couple of screenshots of my VM settings. Any suggestions gratefully received Solved - I redownloaded the WIN10 iso and installation is proceeding now. The first must have been corrupted.

As I said, I did several things at the same time, so I'm not sure what provided the fix. I would assume that deleting the docker image, the docker templates, the network and networkrules cfg files - and reinstalling the dockers from scratch - would be the most likely contenders. But remember that I also upgraded unRaid 6.6.7 to 6.7.0, upgraded the motherboard BIOS, and installed an Intel i350 T4 NIC. I think I also had to change the MAC address for eth0 in Interface rules under Network Settings. I also found that my switch was misconfigured with the wrong gateway (192.168.1.254 instead of 192.168.1.1), but it had been like that when Sonarr, Radarr, etc were working ok. Sorry I haven't been more methodical....I'm afraid my troubleshooting skills are fairly limited, but the shotgun approach seems to have done the trick 😉

No the tests were failing as well. I have just completed an upgrade to 6.7.0, installed an i350 Intel NIC, reset my network settings, and setup my dockers from scratch (Sabnzbd, Sonarr, Radarr, Deluge,Krusader, Firefox).........and everything is working again. It's been a bit of a mission - the problems began 2 weeks ago with a failing psu which presumably caused corruption from unclean reboots. After replacing the psu, and adding 2 10GB WD Ultrastar SATA drives (which my system wouldn't recognise until I powered them via molex to SATA adapters to workaround the 'power disable' function of these enterprise drives), I found that Sonarr and Radarr wouldn't connect to the indexers or Sabnzbd. Several days of troubleshooting later, I have a working system again. I won't pretend that the lack of response hasn't been frustrating, but I do understand that life gets in the way at times And the silver lining is, of course, that I have learnt way more than I would have by following someone's instructions. Cheers, Steve

I'm closing this request for help due to lack of response. Somewhat disappointing given the community welcome page's claim: "Our Welcoming Community - Our community is comprised of the most open, informative, and helpful people you’re likely to run across. Feel free to jump in and get acquainted on the forum."

Anyone?

Is anyone able to help with this? Even advice about whether to try to fix this, or to try a fresh install would be appreciated - cheers

Thanks for your efforts binhex. I had a thread in the General forum regarding a reboot problem that turned out to be a faulty PSU. I have replaced it and performed a correcting parity check. My current problem (which only started after the unclean shutdowns) is that Radarr and Sonarr will not connect. I followed trurl's instructions to rebuild the docker image and reinstall my previous dockers, and Radarr, Sonarr and SABNZBD will all start, but Radarr and Sonarr won't connect. (SABNZB test connects successfully) Any help appreciated - logs attached Log for binhex-radarr.txt Log for binhex-sabnzbd.txt Log for binhex-sonarr.txt tower-diagnostics-20190509-1614.zip

I will mark this thread solved, as the original problem (unclean shutdowns) was resolved with a new power supply. I will start a new thread in the SABNZBD forum (Sonarr and Radarr cannot connect). Thanks for everyone's help

I have followed trurl's instructions and can run binhex_sabnzbd, radarr and sonarr, but I'm having connection problems (logs attached) Log for binhex-radarr.txt Log for binhex-sabnzbd.txt Log for binhex-sonarr.txt tower-diagnostics-20190508-1307.zip

Ok - I rebuilt docker.img and reinstalled my dockers, which now start up. binhex_sabnzbd seems ok, but sonarr and radarr have connection errors. I have attached their logs, if someone could have a look I would be grateful. Edit - sorry I posted this before seeing Trurl's reply - I will follow your advice. Log for binhex-radarr.txt Log for binhex-sonarr.txt

Parity check completed with new PSU and corrected 27 errors. Only problem now is that binhex_Sabnzbd and binhex_sonarr will not start (binhex_radarr starts up ok) - logs attached tower-diagnostics-20190507-1815.zip

No problems with memtest...replaced psu and I'm currently halfway thru parity check with no reboots or errors Looking good so far, I'll hopefully be marking this solved before long

I'll need to buy one tomorrow in order to test - it won't hurt to have a spare on hand ;-). And I'll run memtest+ for a day.

Unraid server is still rebooting as soon as I start a parity check - any other suggestions?

I stopped the parity check, shut down cleanly, and booted up cleanly (as far as I can tell .... logs attached) tower-diagnostics-20190505-1304.zip

The unclean shutdown happens soon after starting the parity check. Disk 1 shows 40 reallocated sectors - is that significant?