Suddenly, everything's horrible

CRAZY thing just happened.

Set up UnRaid over the weekend, everything is running awesome. Things are building up, but suddenly:

[Fatal] ConsoleApp: EPIC FAIL!

[v4.0.17.2952] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: AppFolder /config is not writable

at NzbDrone.Common.EnvironmentInfo.AppFolderFactory.Register() in ./Sonarr.Common/EnvironmentInfo/AppFolderFactory.cs:line 56

at NzbDrone.Host.Startup.Configure(IApplicationBuilder app, IContainer container, IStartupContext startupContext, Lazy\1 mainDatabaseFactory, Laz1 logDatabaseFactory, DatabaseTarget dbTarget, ISingleInstancePolicy singleInstancePolicy, InitializeLogger initializeLogger, ReconfigureLogging reconfigureLogging, IAppFolderFactory appFolderFactory, IProvidePidFile pidFileProvider, IConfigFileProvider configFileProvider, IRuntimeInfo runtimeInfo, IFirewallAdapter firewallAdapter, IEventAggregator eventAggregator, SonarrErrorPipeline errorHandler) in ./Sonarr.Host/Startup.cs:line 219

at System.RuntimeMethodHandle.InvokeMethod(Object target, Span\1& arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)`

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)

at Microsoft.AspNetCore.Hosting.ConfigureBuilder.<>c__DisplayClass4_0.<Build>b__0(IApplicationBuilder builder)

at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass15_0.<UseStartup>b__1(IApplicationBuilder app)

at Microsoft.AspNetCore.Mvc.Filters.MiddlewareFilterBuilderStartupFilter.<>c__DisplayClass0_0.<Configure>g__MiddlewareFilterBuilder|0(IApplicationBuilder builder)

at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)

at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)

at NzbDrone.Host.Bootstrap.Start(String[] args, Action\1 trayCallback) in ./Sonarr.Host/Bootstrap.cs:line 80`

at NzbDrone.Console.ConsoleApp.Main(String[] args) in ./Sonarr.Console/ConsoleApp.cs:line 45

Press enter to exit...

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

Okay, wth? I tried everything I could think of and then restarted the container. Nothing. Tried removing it and reinstalling it. Nothing. Same result. Radarr? Same

The ONLY think I can think is that the mover is running ATM. Could that possible be the issue?

Best bet is to look for the support thread for that container:

Figured out why it wouldn't load. Somehow the database was full and after deleting everything in Logs, it's working again.

ACTUAL solution for those looking in the future:

I was downloading my entire (50-70 TB) library and it was all going to Cache (1 TB drive). Mover couldn't keep up. So the cache was filling and since I have Sonarr running on the cache.....

Solution was to set mover to move ever hour (say 12pm) and pause all transfers (12pm) then start new transfers every half hour (12:30). The end result is that the cache would fill 30-40% in 30 minutes, mover would run and when the transfers started again, the cache was mostly empty.

Created 2 scripts for this and then just run them on a schedule. Using Mover Tuner with Turbowrite enabled and scheduling there. Transfer will take longer, but it'll actually finish.

Actual solutions would be, when moving large amounts of data to a share on HDD array, is to disable cache for the share for the duration of your transfer. There is no positive benefit for using cache during the transfer. No time is saved, it puts unneeded wear on your cache drive and server, and you have experienced what happens to your dockers when the drive holding your system and appdata shares in nearly full.

Edited April 24Apr 24 by ConnerVT

If you do not want to disable the cache as @door-to-door-oddball3058 recommended, then at least make sure that you have a sensible value set for the Minimum Free Space for the 'cache' pool to stop it filling up too far. When the free space falls below this value then Unraid will start bypassing the cache for new files and instead write them directly to the array.

16 hours ago, door-to-door-oddball3058 said:

Mover couldn't keep up

Of course not. It is impossible to move to slow array as fast as you can write to fast cache. Mover is intended for idle time.

17 hours ago, door-to-door-oddball3058 said:

So the cache was filling and since I have Sonarr running on the cache.....

The above, and also make sure to set min free space on each share correctly so that media shares consider the cache full before appdata/system/anything other that'd be critical for apps working.