Do2a-2d

March 22, 2020

Thank you.

I have updated to 6.8.3 as per above. I copied over the config folder except for the network.cfg file. This resolved the DNS issue. However the hang on reboot persists. Also, I was using the Nvidia version of Unraid and I did re-install Nvidia 6.8.3 after upgrading.

Happy to upload any logs to resolve the reboot issue. This is a major problem for me as I am self-hosting Nextcloud and need system to come up by itself if I am not home.

March 22, 2020

39 minutes ago, Squid said:

That's your browser running on whatever system its on reaching GitHub. unRaid (or specifically in this case, CA cannot)

Yes. Understand that. Just saying that DNS is being resolved outside of Unraid.

41 minutes ago, Squid said:

The obvious question is have you instead set a DNS to something other than pfsense? IIRC, there was another user who had pfsense wind up blocking unRaid's needs

No. DNS is set to PfSense as has been for the past 3 years. No changes there and was resolving just fine till a few days ago. This instance of Pfsense is running PfBlockerNG.

Also Pfsense is resolving DNS just fine for the backup unraid server as CA is able to reach out.

Have also tried swapping the main Pfsense box with an older Pfsense box that I used till a few months ago. Same problem on the old PfSense. Old PfSense not running PFBlockerNG so the problem is with the instance of Unraid on the main server. Something that has developed over the last week.

46 minutes ago, Squid said:

I would download the unRaid zip file from Limetech's website, then replace all of the bz* files on the flash drive with the ones contained in the zip.

Are there any differences in the *bz files in the current version 6.8.3 to the version I am running - 6.8.0?

Also if I were to do a fresh install on a new usb, what files/folders do I need to copy from old flash to new flash to maintain drive and docker settings. Drives are encrypted and have a lot of personal data that I do not want to loose.

Thanks.

March 22, 2020

I can reach the Github page if I click on the "here" hyperlink

March 22, 2020

On 3/19/2020 at 3:06 PM, johnnie.black said:

Reboot and boot using the GUI mode, then reconfig your lan, you can type "reboot" on the console to do a clean shutdown.

Thank you for your reply. I have done this but seems my server has other issues. Don't know whether this forum is the appropriate section or my question needs to be moved to some other forum. Server is running 6.8.0

Issues:

Main unraid server not able to reach DNS server (PfblockerNG on Pfsense) even though all other clients on various Vlans and backup Unraid server getting DNS.
Main server no longer re-booting. Have to do a hard restart after any change - gets stuck at "Loading /bzroot...ok" Then nothing (see attached)

Please advise.

Thank you.

March 19, 2020

Hi all

I need instructions on how to reassign eth0 to a different port from the command line. I have a 2 port Mellanox 10gb card + 2 nic ports on the motherboard. The Mellanox port assigned to eth0 has failed - no connectivity. NO GUI so I cannot get into Unraid to change the default eth0 port from network settings.

Please advise how I can re-assign from the command line.

ALSO

How to bond one of the other ports to eth0 so that there is redundancy in case one fails.

Thanks in advance.

January 21, 2019

On ‎11‎/‎9‎/‎2018 at 12:33 AM, Mlatx said:

Well it's always good to resolve your own problems. When I installed pfSense, I changed my private IP scheme to 10.10 from 192.168 and one of the files in nextcloud was configured with the old IP. So now it's working. In case anyone is having difficulty with ssl connections on hosts/apps within unraid, I put the following info into dns resolver at the bottom for adding a host override. I'm connecting via SSL to unraid.

host - long chain of characters before unraid.net in your address bar
parent domain - unraid.net
IP - unraid IP address

I have the same issue and tried your solution. However I get a long series of errors from pfSense. Could you kindly share a screenshot or the syntax you used to get this working. The errors I get are:

The generated config file cannot be parsed by unbound. Please correct the following errors:
    /var/unbound/test/unbound.conf:114: error: unknown keyword 'host'
    /var/unbound/test/unbound.conf:114: error: stray ':'
    /var/unbound/test/unbound.conf:114: error: stray '"'
    /var/unbound/test/unbound.conf:114: error: unknown keyword 'https'
    /var/unbound/test/unbound.conf:114: error: stray ':'
    /var/unbound/test/unbound.conf:114: error: unknown keyword '//402xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
    /var/unbound/test/unbound.conf:114: error: stray '"'
    /var/unbound/test/unbound.conf:115: error: unknown keyword 'parent'
    /var/unbound/test/unbound.conf:115: error: unknown keyword 'domain'
    /var/unbound/test/unbound.conf:115: error: stray ':'
    /var/unbound/test/unbound.conf:115: error: stray '"'
    /var/unbound/test/unbound.conf:115: error: unknown keyword 'unraid.net'
    /var/unbound/test/unbound.conf:115: error: stray '"'
    /var/unbound/test/unbound.conf:116: error: unknown keyword 'IP'
    /var/unbound/test/unbound.conf:116: error: stray ':'
    /var/unbound/test/unbound.conf:116: error: stray '"'
    /var/unbound/test/unbound.conf:116: error: unknown keyword '192.xxx.xx.xx'
    /var/unbound/test/unbound.conf:116: error: stray '"'
    read /var/unbound/test/unbound.conf failed: 18 errors in configuration file

Thanks for your help

September 20, 2018

On ‎9‎/‎19‎/‎2018 at 11:53 AM, CHBMB said:

All of those containers affected use SQLite, my guess is you've got the /config mount as /mnt/user/appdata/.....

On ‎9‎/‎19‎/‎2018 at 11:53 AM, CHBMB said:

This can break SQLite. Change the appdata to /mnt/cache/appdata

Ha ha. Now I see this. Eventually this is what I ended up doing. See my post in binhex

On ‎9‎/‎19‎/‎2018 at 11:53 AM, CHBMB said:

As an aside, not sure why you've posted in our support thread. Seems that you're a binhex container user and just used our containers to rule out a container issue and confirm it's an issue on your machine. 🙄

Very true. When I saw "corrupt database" errors in the log, I decided to use a different repository to see if it was local to my machine or to what the docker was pulling. Tested it on two different machines and got the same errors in the log for both repositories - panicked and posted to your support also.

Thanks a lot for your help.

September 20, 2018

5 hours ago, binhex said:

ahh a good point YES fuse i forgot about that old chestnut, hmm i wish the default host path wasnt /mnt/user for docker on unraid, ho hum, thanks for the heads up, lets hope its just that.

I am sorry but I do not know what that means.

This is what I did do last night...

On all the dockers I changed the path for the config file to /mnt/cache/appdata/xyz_container. This brought up the web UI for

Binhex-radarr

Binhex-plexpass

Binhex-lidarr

Though as mentioned by Binhex above, everything has reverted to "factory settings"

This did NOT bring up the web UI for Binhex-sonarr. I thought my pfSense was blocking something so fiddled with that side. In the end I assigned a static IP to the binhex-sonarr docker from within the docker settings and the web UI does come up on the new IP address.

I don't know it sonarr will now have issues talking to the other dockers that use the host IP. Am happy to try anything that will recreate the original settings so that I don't have to go through the setup process again.

Thank you all for all your help.

September 20, 2018

7 minutes ago, CHBMB said:

I think you should try my suggestion first.

Sent from my Mi A1 using Tapatalk

Which was? Sorry don't follow.

September 20, 2018

5 hours ago, CHBMB said:

He's crossposted in our thread and I wonder if it's an issue with sqlite and the FUSE fs. Hasn't responded yet to my post.

@CHBMB I have not received any post from you.

I did see something about SQLite in the error logs but did not save those logs. I don't know any Linux and am new to Unraid so don't know what that means. But see my response to binhex below regarding path for config files.

Thanks for all your support.

September 20, 2018

5 hours ago, binhex said:

so whats causing this, well as you have already done a wipe of the docker image file and re formatted your cache drive, the only other possibility that could be causing corruption is RAM, have you tried running memtest on your system recently?, if not then i would def give this a go, its part of unraid and can be accessed at boot time via the unraid boot menu, let it run for at least 2 full cycles.

Ok. Can try. However everything else running on both servers is super stable. When building the machine I ran memtest for a solid 24 hours - no errors.

September 20, 2018

20 hours ago, trurl said:

Please don't post to multiple threads for the same problem. That is known as crossposting, and it has been considered a bad thing on messaging boards since before the World Wide Web.

One reason it isn't a good thing to do is because there is no way to coordinate the responses in the multiple threads. So you could have some people, sometimes going to a lot of trouble to diagnose or research your problem, responding on one thread, completely unaware that someone else has already duplicated their effort on the other thread.

Right. Sorry about that. Since the repositories have separate support pages I did not know whether the support requests are cross referenced. Because I use the binhex containers, and upon trying the Linuxserver.io docker encountered the same error, I thought I should let them know also about a possible file corruption issue.

Didn't know. My bad!

September 19, 2018

4 minutes ago, binhex said:

i would say you have some corruption of the lidarr database, and seeing that your problems seem to be affecting more than one container, i would guess that you may have corruption of the docker image file (loopback mounted image) or maybe even possibly corruption of your entire cache drive.

As I have listed above, the steps I have taken so far to mitigate the possibility of a faulty array:

Deleted the docker image file - multiple times
Deleted the appdata folder - multiple times
Removed the two new nvme M.2 drives, swapped slots, reformatted the cache - 2 times
The identical problem persists on more than 1 physical machine. Please see original post - the same error on a second machine that is solely used as a NAS and never had any other docker installed except Krusader.

As of yesterday, I am getting the same result on Linuxserver.io containers for Radarr and Sonarr which leads me to believe that either some file that the docker image is pulling is corrupted or there are corrupted files on the flash drive that persist after docker image and appdata are deleted. Not sure if I remember whether or not the appdata and the docker config data reside in the same directory for your dockers. Is that a possible scenario?

Thanks.

September 19, 2018

Unraid problem or Docker Repository Issue - Don't know. Need help! -

This was originally posted in Binhex-Lidarr support page but the problem persists with Linuxserver.io docker containers also. -

Background:

Last Saturday I decided to swap the 250gb nvme in my main rig for 2 500gb nvme drives in raid 0. Followed instructions found here https://www.youtube.com/watch?v=ij8AOEF1pTU from Spaceinvader One. After restoring libvert and disk image from backup, Win10 VM fired up without issues.

Restored appdata using community applications backup and restore app and reinstalled docker images from history. While the dockers install without error and startup, I am unable to reach the web UI for any of the affected dockers. (Log for Lidarr posted in images attached).

Jumped through hoops.

Deleted docker image file multiple times,

un-installed / re-installed nvme drives and re-formatted.

Did NOT restore appdata and tried to re-install binhex dockers listed from scratch and still the same results.

To test if the flash drive for the Main Rig was corrupted, tried to install Binhex-Lidarr on my NAS box (Usually Krusader is the only docker that runs on the NAS). Same resuts.

As a test, installed Unraid 6.6.0 -rc4 on the NAS box last night and tried to install Binhex-Lidarr again. Same results.

Essentially the error message in the logs for Radarr, Sonarr and Lidarr seems to be the same:

at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x0000b] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:122 is corrupt, restore from backup if available. See: https://github.com/Lidarr/Lidarr/wiki/FAQ#i-am-getting-an-error-database-disk-image-is-malformed

Docker containers affected:

Binhex-Radarr

Binhex-Sonarr

Binhex-Lidarr

Binhex-Plexpass

Linuxserver.io-Sonarr

Linuxserver.io-Radarr

Docker containers NOT affected:

Binhex-SABNZBD

Binhex-Deluge

Krusader

Calibre

Cops

Lazylibrarian

Any help/input/work around will be greatly appreciated. Want to avoid having to use some docker from a different repository and go through setting up each from scratch. Especially Plex.

Main Rig - Media Server

UNRAID 6.5.0

Intel Core i9-7900x

Gigabyte Aorus x299 Gaming 9

64gbs Corsair Vengence DDR4 3000

Samsung PM961 M.2 512gbs x 2 - cache in raid 0

8 port HDD controller

iStarUSA 3.5" x 5 bay hotswap disk cage

EVGA 850W P2 power supply

Seagate Enterprise level 8TB HDD - parity drive

WD Red 8TB HDD - parity drive x 2

Misc HDDs for a total of 20TB storage space

Backup Rig - NAS

UNRAID 6.6.0 - rc4

Intel Core i7-4790k

Asus z97 pro gamer

32gbs (gotta check) DDR3

Samsung PM961 M.2 125gbs - cache

Marvel 8 port HDD controller

Silverstone CS380 hotswap case

EVGA 650W P2 power supply

Seagate 2TB HDD - parity drive

Seagate 2TB HDD - parity drive x 2

Misc HDDs for a total of 6TB storage space

2018-09-17 19:34:02.985572 [info] System information Linux 0e75fe0edf53 4.18.8-unRAID #1 SMP Sat Sep 15 09:15:50 PDT 2018 x86_64 GNU/Linux

2018-09-17 19:34:03.003646 [info] PUID defined as '99'

2018-09-17 19:34:03.052851 [info] PGID defined as '100'

2018-09-17 19:34:03.103273 [info] UMASK defined as '000'

2018-09-17 19:34:03.120460 [info] Permissions already set for volume mappings

2018-09-17 19:34:03.139694 [info] Starting Supervisor...

2018-09-17 19:34:03,372 INFO Included extra file "/etc/supervisor/conf.d/lidarr.conf" during parsing

2018-09-17 19:34:03,372 INFO Set uid to user 0 succeeded

2018-09-17 19:34:03,373 INFO supervisord started with pid 8

2018-09-17 19:34:04,375 INFO spawned: 'lidarr' with pid 48

2018-09-17 19:34:04,375 INFO reaped unknown pid 9

2018-09-17 19:34:04,577 DEBG 'lidarr' stdout output:

[Info] Bootstrap: Starting Lidarr - /usr/lib/lidarr/Lidarr.exe - Version 0.3.1.471

2018-09-17 19:34:04,884 DEBG 'lidarr' stdout output:

[Info] AppFolderInfo: Data directory is being overridden to [/config]

2018-09-17 19:34:04,947 DEBG 'lidarr' stdout output:

[Info] Router: Application mode: Interactive

2018-09-17 19:34:05,059 DEBG 'lidarr' stdout output:

[Info] MigrationLogger: *** Migrating data source=/config/lidarr.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***

2018-09-17 19:34:05,113 DEBG 'lidarr' stdout output:

2018-09-17 19:34:05,427 DEBG 'lidarr' stdout output:

[Fatal] ConsoleApp: EPIC FAIL!

[v0.3.1.471] NzbDrone.Core.Datastore.CorruptDatabaseException: Lidarr failed to start: Database file: System.Data.SQLite.SQLiteException (0x80004005): disk I/O error

disk I/O error

at System.Data.SQLite.SQLite3.Prepare (System.Data.SQLite.SQLiteConnection cnn, System.String strSql, System.Data.SQLite.SQLiteStatement previous, System.UInt32 timeoutMS, System.String& strRemain) [0x0033c] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteCommand.BuildNextCommand () [0x000f6] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteCommand.GetStatement (System.Int32 index) [0x00008] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at (wrapper remoting-invoke-with-check) System.Data.SQLite.SQLiteCommand.GetStatement(int)

at System.Data.SQLite.SQLiteDataReader.NextResult () [0x0011e] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteDataReader..ctor (System.Data.SQLite.SQLiteCommand cmd, System.Data.CommandBehavior behave) [0x00090] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at (wrapper remoting-invoke-with-check) System.Data.SQLite.SQLiteDataReader..ctor(System.Data.SQLite.SQLiteCommand,System.Data.CommandBehavior)

at System.Data.SQLite.SQLiteCommand.ExecuteReader (System.Data.CommandBehavior behavior) [0x0000c] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery (System.Data.CommandBehavior behavior) [0x00006] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery () [0x00006] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at System.Data.SQLite.SQLiteConnection.Open () [0x00959] in <61a20cde294d4a3eb43b9d9f6284613b>:0

at FluentMigrator.Runner.Processors.GenericProcessorBase.EnsureConnectionIsOpen () [0x0000e] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\Processors\GenericProcessorBase.cs:54

at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Exists (System.String template, System.Object[] args) [0x00000] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\Processors\SQLite\SQLiteProcessor.cs:78

at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.TableExists (System.String schemaName, System.String tableName) [0x00000] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\Processors\SQLite\SQLiteProcessor.cs:47

at FluentMigrator.Runner.VersionLoader.get_AlreadyCreatedVersionTable () [0x00000] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:124

at FluentMigrator.Runner.VersionLoader.LoadVersionInfo () [0x00028] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:160

at FluentMigrator.Runner.VersionLoader..ctor (FluentMigrator.Runner.IMigrationRunner runner, FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.IMigrationConventions conventions) [0x00077] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:50

at FluentMigrator.Runner.MigrationRunner..ctor (FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00167] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\MigrationRunner.cs:102

at FluentMigrator.Runner.MigrationRunner..ctor (System.Reflection.Assembly assembly, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00000] in C:\Users\Mark\Source\Repos\fluentmigrator\src\FluentMigrator.Runner\MigrationRunner.cs:72

at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.Migrate (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x000b5] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:58

at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x0000b] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:122 is corrupt, restore from backup if available. See: https://github.com/Lidarr/Lidarr/wiki/FAQ#i-am-getting-an-error-database-disk-image-is-malformed

at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00045] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:133

at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00027] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:81

at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationType migrationType) [0x00000] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:69

at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (NzbDrone.Common.Composition.IContainer container) [0x00000] in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:47

at NzbDrone.Host.NzbDroneServiceFactory.Start () [0x00037] in C:\projects\lidarr\src\NzbDrone.Host\ApplicationServer.cs:60

at NzbDrone.Host.Router.Route (NzbDrone.Host.ApplicationModes applicationModes) [0x0007f] in C:\projects\lidarr\src\NzbDrone.Host\Router.cs:55

at NzbDrone.Host.Bootstrap.Start (NzbDrone.Host.ApplicationModes applicationModes, NzbDrone.Common.EnvironmentInfo.StartupContext startupContext) [0x0003d] in C:\projects\lidarr\src\NzbDrone.Host\Bootstrap.cs:78

at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, NzbDrone.Host.IUserAlert userAlert, System.Action`1[T] startCallback) [0x00075] in C:\projects\lidarr\src\NzbDrone.Host\Bootstrap.cs:41

at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00029] in C:\projects\lidarr\src\NzbDrone.Console\ConsoleApp.cs:38

2018-09-17 19:34:05,427 INFO success: lidarr entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2018-09-17 19:34:05,436 DEBG 'lidarr' stdout output:

Press enter to exit...

2018-09-17 19:34:06,436 DEBG 'lidarr' stdout output:

Non-recoverable failure, waiting for user intervention...

From <https://ba38b4426689c3df9029cd275e6e37518af21f76.unraid.net/plugins/dynamix.docker.manager/include/Events.php?action=log&container=0e75fe0edf53&title=Log%20for:%20binhex-lidarr>

September 18, 2018

Unraid problem or Binhex Docker Repository Issue - Don't know. Need help!