IcarusFountain

As soon as I reverted it to a 580.x.x driver, everything worked perfectly. Thank you for pointing that out!

I'm having a very similar issue to griffinpuc in that I was having system issues, so I built a new 7.2.3 drive on a brand new flash drive (Samsung Bar 128GB); the old flash drive was an old SanDisk Cruzer 16GB that I'd been using for like 6-8 years until some recent issues prompted me to try multiple things to get Unraid back up and running. Used the Unraid creation tool to create the drive, copied over files for some of my Docker containers like Plex, and once the system was running, I went to update my containers. Updates went fine except for Plex, which said it couldn't complete with the --runtime=nvidia argument, indicating to me that there was an issue with the nvidia tool/driver. I removed the driver and tool, rebooted, re-installed the tool, re-installed the driver, was prompted to stop and restart Docker, so I did that. Nvidia tool said "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running". Did a full reboot, still no joy. Checked Tools -> System Devices and saw both my P2000 and GeForce GT 1030. When checking Tools -> System Drivers, the only thing that shows up related to Nvidia is the blacklisted limetech nouveau driver that's disabled. When I was having issues with the old flash drive and the kernel wasn't loading on bootup, I ran a full hardware diagnostic from my server's lifecycle controller, and all hardware passed (2 CPUs, 48 cores, 320GB RAM, 10 HDDs all passed), so I don't have reason to suspect failing RAM like they mentioned. Although being an old Dell R720xd with DDR3 memory, it's not like I'm not using aging parts that could be failing; I just figure the diagnostic would catch problems. Unraid Diagnostics attached. unraid-diagnostics-20260107-2242.zip

I'm still getting the sqlite error, espite having upated Sonarr (and I'm running Unraid 6.8.2). Just in the last week, I've noticed that shows aren't correctly updating to reflect whether I have episodes, and similarly I can't add new series to monitor. 2020-02-27 22:13:50,270 DEBG 'sonarr' stdout output: [Error] TaskExtensions: Task Error [v2.0.0.5338] System.Data.SQLite.SQLiteException (0x80004005): database disk image is malformed database disk image is malformed at System.Data.SQLite.SQLite3.Reset (System.Data.SQLite.SQLiteStatement stmt) [0x00083] in <61a20cde294d4a3eb43b9d9f6284613b>:0 at System.Data.SQLite.SQLite3.Step (System.Data.SQLite.SQLiteStatement stmt) [0x0003c] in <61a20cde294d4a3eb43b9d9f6284613b>:0 at System.Data.SQLite.SQLiteDataReader.NextResult () [0x0016b] 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.ExecuteScalar (System.Data.CommandBehavior behavior) [0x00006] in <61a20cde294d4a3eb43b9d9f6284613b>:0 at System.Data.SQLite.SQLiteCommand.ExecuteScalar () [0x00006] in <61a20cde294d4a3eb43b9d9f6284613b>:0 at Marr.Data.QGen.InsertQueryBuilder`1[T].Execute () [0x00046] in M:\BuildAgent\work\5d7581516c0ee5b3\src\Marr.Data\QGen\InsertQueryBuilder.cs:140 at Marr.Data.DataMapper.Insert[T] (T entity) [0x0005d] in M:\BuildAgent\work\5d7581516c0ee5b3\src\Marr.Data\DataMapper.cs:728 at NzbDrone.Core.Datastore.BasicRepository`1[TModel].Insert (TModel model) [0x0002d] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Datastore\BasicRepository.cs:111 at NzbDrone.Core.Messaging.Commands.CommandQueueManager.Push[TCommand] (TCommand command, NzbDrone.Core.Messaging.Commands.CommandPriority priority, NzbDrone.Core.Messaging.Commands.CommandTrigger trigger) [0x0013d] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Messaging\Commands\CommandQueueManager.cs:82 at NzbDrone.Core.Messaging.Commands.CommandQueueManager.Push (System.String commandName, System.Nullable`1[T] lastExecutionTime, NzbDrone.Core.Messaging.Commands.CommandPriority priority, NzbDrone.Core.Messaging.Commands.CommandTrigger trigger) [0x000b7] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Messaging\Commands\CommandQueueManager.cs:95 at NzbDrone.Core.Jobs.Scheduler.ExecuteCommands () [0x00043] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Jobs\Scheduler.cs:42 at System.Threading.Tasks.Task.InnerInvoke () [0x0000f] in /build/mono/src/mono/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:2476 at System.Threading.Tasks.Task.Execute () [0x00000] in /build/mono/src/mono/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:2319 I even tried removing the docker and re-adding it, although now that I think about it I didn't think to clear the appdata.