wgstarks

Post the contents of settings>SMB>SMB extras

Start a post in general support and pm me a link.

They work just fine for me. Haven’t seen any problems with TM in any of the RC’s.

Whenever the unraid os is updated I get a couple of emails I think from this plugin. First is to wait while the nvidia driver updates. Second is the "all done". Third has a subject line "output from your job 3". I'm not sure if this is associated with the driver update or not? If it is would it be possible to not send this notification? I doubt it really matters but seems like a waste.

Updated from rc5 without issue. Like the new highlighting.👍

https://forums.unraid.net/forum/53-feature-requests/

Actually I was talking about the nordvpn server that you are connecting to.

Getting macOS to work well with SMB can be a bit of a challenge. There is a fair amount of discussion on this forum in various threads regarding the best SMB settings (settings>SMB>SMB extras). Here is what is working well for me- #macOS config start server multi channel support = no [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [Media] path = /mnt/user/Media veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes [mini_SMB] path = /mnt/user/mini_SMB veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes #macOS config end [global] is applied to all shares. [Media] and [mini_SMB] are shares on my server that I have applied the associated settings to. Edit the names in the square brackets to match your shares. You can also apply those settings in [global] if you want to use them everywhere. I haven’t tested that though so no idea what unintended consequences might come up. If you are running unRAID 6.10 rc5 or later you don’t need server multi channel support = no. That’s already the default. Edit: You also need to adjust the path in per-share settings to match yours.

I would probably try switching the vpn server that your connecting to. I’ve never used nordvpn but I know PIA sometimes has similar issues and switching to another endpoint will usually correct it.

What about perms.txt and nzbdrone.pid? I see that both those files are also currently owned by root.

I posted regarding this issue on the Sonarr forum and got a reply back that the Sonarr app was not able to write to logs.db. I changed the permissions for this file and it fixed the issue. The original permissions were owner:read/write group:read only others:read only. New permissions owner:read/write group:read/write and others:read/write. I noticed that logs.db has root as the owner while most of the other files are owned by nobody. This doesn’t seem correct to me and I suspect that that is the real problem since Sonarr is running as nobody. Shouldn't the owner for logs.db be nobody as well? This is a little outside my experience since I usually avoid making changes to permissions and owners.

Thanks. I’ll give this a try.

I'm at a loss for this. I don't understand how the sonarr db could be readonly in one version and readwrite in another??? I've checked all the db's in my appdata folder using dynamix file manager and they all show "Owner: Read/Write". I re-applied the setting just to be sure. Didn't make any difference though. Maybe I'm misunderstanding the error? Tried google but couldn't find any info about this error. I did see a similar issue that was corrected by cd to the folder containing the db and then running .recover but that just results in command not found.

Not sure what version you are running but I'm on 4.4.2 and not having any issues with my custom "incomplete" file path. The qbit forum would probably be the best place for an answer to your question though. They'll have much more knowledge regarding app development and current issues.

You can do that with most of the dockers on unRAID. Just go to the dockerhub page and grab the tag for the version you want. Enter the tag number after the name in the repository field separated by a colon.

Enter this in the repository field for the docker- binhex/arch-prowlarr:0.2.0.1678-1-01

Google search shows that xmrig is a cryptominer possibly installed as part of one of your plugins. Possibly delete your plugins and re-install one-at-a-time. A google search for xmrig will give lots of hits.

Getting an epic fail with latest sonarr image (3.0.8.1507-1-01)- at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, NzbDrone.Host.IUserAlert userAlert, System.Action`1[T] startCallback) [0x0007f] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\Bootstrap.cs:41 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00030] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Console\ConsoleApp.cs:42 2022-05-01 14:45:02,874 DEBG 'sonarr' stdout output: EPIC FAIL! System.Exception: attempt to write a readonly database attempt to write a readonly database While Processing: "INSERT INTO "VersionInfo" ("Version", "AppliedOn", "Description") VALUES (168, '2022-05-01T18:45:02', 'add_additional_info_to_pending_releases')" ---> System.Data.SQLite.SQLiteException: attempt to write a readonly database attempt to write a readonly database at System.Data.SQLite.SQLite3.Reset (System.Data.SQLite.SQLiteStatement stmt) [0x00088] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLite3.Step (System.Data.SQLite.SQLiteStatement stmt) [0x0006e] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteDataReader.NextResult () [0x00174] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteDataReader..ctor (System.Data.SQLite.SQLiteCommand cmd, System.Data.CommandBehavior behave) [0x0008e] in <cf516e4846354910b3d60749c894b1bf>: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 <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery (System.Data.CommandBehavior behavior) [0x00006] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery () [0x00006] in <cf516e4846354910b3d60749c894b1bf>:0 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.ExecuteNonQuery (System.String sql) [0x00013] in <137fb96feee44f379d6a8fba4e172d1c>:0 --- End of inner exception stack trace --- at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.ExecuteNonQuery (System.String sql) [0x0003e] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Process (System.String sql) [0x0003f] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.Processors.ProcessorBase.Process (FluentMigrator.Expressions.InsertDataExpression expression) [0x0000d] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Expressions.InsertDataExpression.ExecuteWith (FluentMigrator.IMigrationProcessor processor) [0x00000] in <c16130ff2bfb4746b4fb36de17115e3e>:0 at FluentMigrator.Runner.VersionLoader.UpdateVersionInfo (System.Int64 version, System.String description) [0x00040] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner.ApplyMigrationUp (FluentMigrator.Infrastructure.IMigrationInfo migrationInfo, System.Boolean useTransaction) [0x0010f] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner.MigrateUp (System.Boolean useAutomaticTransactionManagement) [0x000af] in <137fb96feee44f379d6a8fba4e172d1c>:0 at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.Migrate (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x000a2] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:51 at NzbDrone.Core.Datastore.DbFactory.CreateLog (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00000] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:136 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00047] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:89 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationType migrationType) [0x00000] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:70 at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (NzbDrone.Common.Composition.IContainer container) [0x00019] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:52 at NzbDrone.Host.NzbDroneServiceFactory.Start () [0x00037] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\ApplicationServer.cs:60 at NzbDrone.Host.Router.Route (NzbDrone.Host.ApplicationModes applicationModes) [0x0007f] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\Router.cs:56 at NzbDrone.Host.Bootstrap.Start (NzbDrone.Host.ApplicationModes applicationModes, NzbDrone.Common.EnvironmentInfo.StartupContext startupContext) [0x0003d] in M:\BuildAgent\work\63739567f01dbcc2\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) [0x0007f] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\Bootstrap.cs:41 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00030] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Console\ConsoleApp.cs:42 2022-05-01 14:45:02,891 DEBG 'sonarr' stdout output: Press enter to exit... Reverting to 3.0.7.1477-1-01 corrects the problem. Docker run- root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-sonarr' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Brunnhilde" -e HOST_CONTAINERNAME="binhex-sonarr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sonarr-icon.png' -p '8989:8989/tcp' -p '9897:9897/tcp' -v '/mnt/user/qbit/':'/data':'rw' -v '/mnt/user/Media/XBMC/TVTorrents/':'/media':'rw' -v '/mnt/user/Media/XBMC/TVTorrents/.RecycleBin':'/Recycle_Bin':'rw' -v '/mnt/user/appdata/binhex-sonarr-v3':'/config':'rw' 'binhex/arch-sonarr:latest' a8757f4762952c381937aae30f3b4fa3ecd0debb93e4de312606409d1aad69bf

The command finished successfully! brunnhilde-diagnostics-20220501-1452.zip

Same for me. It’s as if there isn’t any link there. @SimonF I do see all the readings in tools>ipmi.

IF I am understanding the vfs_fruit options correctly all those per share options can also be used globally. I haven’t tested that though. I imagine it might have some unwanted effect on connections from windows machines or even macs running different versions of the OS since apple likes to change things.

At the top of the docker configuration you should see this- As it says, for nvidia GPU switch to advanced view and add the proper command in the extra parameters. Looks to me like that is what the error you posted is complaining about. Also, don’t forget to add the UUID.

If it's only happening with one torrent I don't really think its a problem with the Deluge app. Sounds like the seeders are breaking the connection. I'm guessing its only one or two. You might try waiting a few more days and see if you can download more of it.

Do any of those seeders show as 100%? If everyone is seeding a torrent that they only have 94% of then that's all you'll get. Its possible that you have all the files complete but one is missing from what the original torrent had.

You may need to use other settings as well. Here is my settings from SMB configurations extras- #macOS config start [Global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [Media] path = /mnt/user/Media veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes [Media] is the name of the share these settings are being applied to. You will need to change this to fit your needs.

Multi Channel support was disabled because having it enabled was causing poor performance when connecting from a Mac via SMB. You’ll probably want to leave it off.