MrDatum

Awesome, thanks!

Would using BTRFS in single profile allow me to expand the cache easily by adding another drive?

I'm using BTRFS in Single profile.

Thanks for the help, it is working and I have that warm fuzzy feeling from being fully backed-up In the future if I need more space in the pool can I just expand it by shutting down the array, adding another dive and then assigning that drive to the existing pool?

I'm about to setup my new pool but wanted to confirm that a single large multi-TB file can span across more than one of the drives in the pool so that I don't run into the issue of my backups failing because there isn't enough space. For example, if I have a 3TB and another 3TB drive, and my backup file is 4TB, setting up a pool and selecting the Single profile will allow the 4TB file to span across both drives?

Thanks, I'll give this a shot.

I want to backup a number of my home computers to my Unraid server. Some of the backup files are multi-terrabytes. I have been using a share with a couple of drives on the array, but I'm running into an issue where the backup fails as their isn't enough room, although I have TB's of space available. However, that space is spread over a couple of drives and I don't have the size needed on any one of those drives for the large multi-TB backup file. 1. Is it possible to create a JBOD pool where all of the drives are combined into one large drive such that a single large multi-TB file can span across more than one of the drives? 2. If so, can the drives be of different sizes? Would this be the best way to accomplish what I am trying to do with my backups?

That makes sense, I'll give that a shot.

I think I have the docker issue sorted. I ended up reverting to V2.0 versions of both and that seemed to fix the issue as they both now load. Still not sure what is going on with the appdata folder being on both the cache and the array. I did stop the docker service before running mover but that did not seem to fix the issue.

Any thoughts on this?

I had an issue with my Unraid server a few weeks ago where my boot drive failed and my cache pool drives were showing up in Unassigned devices. I made a new boot drive and was able to recreate the cache pool. However, two of my dockers (Radarr and Sonarr) would not load while my Plex and NZBget dockers loaded fine. The logs for both says the database is corrupt: "EPIC FAIL! NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/sonarr.db is corrupt, restore from backup if available." Something else I’ve noticed is that my appdata folder is, for some reason, present on both my cache pool as well as on one of my drives in the array. The appdata share setting had Use Cache Pool set to “Only” so I don’t know how it wound up being also on one of my array drives. I stopped Docker, set the share settings for appdata to “prefer” for the cache pool and ran the mover. However, I am still seeing appdata on one of my array drives. What I’ve tried to get Sonarr and Radarr running: 1. In Settings/Docker I ran a scrub with “correct file system errors” 2. I forced an update of both Dockers so the Docker would be recreated 3. I removed the Dockers and added them back with “Add Container” and selected the appropriate template 4. I stopped the Docker service and deleted the vdisk file, restarted Docker and reinstalled all of my Dockers using the templates. Again, Sonarr and Radarr will not load (same corrupt database error in the log) while NZBget and Plex do load fine. So I’m not sure what the next step is. If I can’t get Sonarr/Radarr to run by deleting the Docker image and reinstalling, what else can I try? tower-diagnostics-20230618-1509.zip

Would I just copy the old appdata folder over top of the existing and then delete the docker and then recreate the docker using the template?

No, I haven't done that yet. I do have a few points in time of the CA backups, is there now way to use those to rebuild the Docker without losing data/settings?

I think I did that. From my previous post: I stopped Sonarr, deleted the docker image and then recreated the Sonarr docker image using the Sonarr template, then started the docker and I still get the same 'Epic Fail" error message. So I'm really not sure what I can do to get those two dockers back up and running so any suggestions would be appreciated.

Attached is my diagnostic file tower-diagnostics-20230528-0915.zip

I'm almost there (I hope). I created a new pool and assigned my cache drives to the proper drive slots and my VM's all came up after enabling the VM's. However, after enabling my Dockers some of the them booted fine but both Sonarr and Radarr will not start. Looking at the logs for Sonarr there is an "EPIC FAIL!" error message: [Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.10.1567 [Info] AppFolderInfo: Data directory is being overridden to [/config] [Info] Router: Application mode: Interactive [Info] MigrationLogger: *** Checking database for required migrations data source=/config/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 *** [Fatal] ConsoleApp: EPIC FAIL! [v3.0.10.1567] NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/sonarr.db is corrupt, restore from backup if available. See: https://wiki.servarr.com/sonarr/faq#i-am-getting-an-error-database-disk-image-is-malformed ---> System.Data.SQLite.SQLiteException: database disk image is malformed malformed database schema (10087) 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) [0x003d3] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.BuildNextCommand () [0x000f6] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.GetStatement (System.Int32 index) [0x00008] in <cf516e4846354910b3d60749c894b1bf>:0 at (wrapper remoting-invoke-with-check) System.Data.SQLite.SQLiteCommand.GetStatement(int) at System.Data.SQLite.SQLiteDataReader.NextResult () [0x00124] 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 System.Data.SQLite.SQLiteConnection.Open () [0x00a13] in <cf516e4846354910b3d60749c894b1bf>:0 at FluentMigrator.Runner.Processors.GenericProcessorBase.EnsureConnectionIsOpen () [0x00014] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Exists (System.String template, System.Object[] args) [0x00000] in <137fb96feee44f379d6a8fba4e172d1c>:0 at NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSqliteProcessor.TableExists (System.String schemaName, System.String tableName) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\Migration\Framework\NzbDroneSqliteProcessor.cs:28 at FluentMigrator.Runner.VersionLoader.get_AlreadyCreatedVersionTable () [0x0001c] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.VersionLoader.LoadVersionInfo () [0x00028] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.VersionLoader..ctor (FluentMigrator.Runner.IMigrationRunner runner, FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.IMigrationConventions conventions) [0x00077] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner..ctor (FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00175] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner..ctor (System.Reflection.Assembly assembly, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00007] in <137fb96feee44f379d6a8fba4e172d1c>:0 at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.Migrate (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x000c0] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:60 at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x0000b] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:117 --- End of inner exception stack trace --- at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00045] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:128 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00027] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:82 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationType migrationType) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:70 at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (NzbDrone.Common.Composition.IContainer container) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:48 at NzbDrone.Host.NzbDroneServiceFactory.Start () [0x00037] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\ApplicationServer.cs:60 at NzbDrone.Host.Router.Route (NzbDrone.Host.ApplicationModes applicationModes) [0x0007f] in C:\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 C:\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 C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\Bootstrap.cs:41 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00030] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Console\ConsoleApp.cs:42 EPIC FAIL! NzbDrone.Core.Datastore.CorruptDatabaseException: Database file: /config/sonarr.db is corrupt, restore from backup if available. See: https://wiki.servarr.com/sonarr/faq#i-am-getting-an-error-database-disk-image-is-malformed ---> System.Data.SQLite.SQLiteException: database disk image is malformed malformed database schema (10087) 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) [0x003d3] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.BuildNextCommand () [0x000f6] in <cf516e4846354910b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.GetStatement (System.Int32 index) [0x00008] in <cf516e4846354910b3d60749c894b1bf>:0 at (wrapper remoting-invoke-with-check) System.Data.SQLite.SQLiteCommand.GetStatement(int) at System.Data.SQLite.SQLiteDataReader.NextResult () [0x00124] 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 System.Data.SQLite.SQLiteConnection.Open () [0x00a13] in <cf516e4846354910b3d60749c894b1bf>:0 at FluentMigrator.Runner.Processors.GenericProcessorBase.EnsureConnectionIsOpen () [0x00014] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.Processors.SQLite.SQLiteProcessor.Exists (System.String template, System.Object[] args) [0x00000] in <137fb96feee44f379d6a8fba4e172d1c>:0 at NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSqliteProcessor.TableExists (System.String schemaName, System.String tableName) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\Migration\Framework\NzbDroneSqliteProcessor.cs:28 at FluentMigrator.Runner.VersionLoader.get_AlreadyCreatedVersionTable () [0x0001c] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.VersionLoader.LoadVersionInfo () [0x00028] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.VersionLoader..ctor (FluentMigrator.Runner.IMigrationRunner runner, FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.IMigrationConventions conventions) [0x00077] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner..ctor (FluentMigrator.Infrastructure.IAssemblyCollection assemblies, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00175] in <137fb96feee44f379d6a8fba4e172d1c>:0 at FluentMigrator.Runner.MigrationRunner..ctor (System.Reflection.Assembly assembly, FluentMigrator.Runner.Initialization.IRunnerContext runnerContext, FluentMigrator.IMigrationProcessor processor) [0x00007] in <137fb96feee44f379d6a8fba4e172d1c>:0 at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.Migrate (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x000c0] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:60 at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x0000b] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:117 --- End of inner exception stack trace --- at NzbDrone.Core.Datastore.DbFactory.CreateMain (System.String connectionString, NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00045] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:128 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationContext migrationContext) [0x00027] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:82 at NzbDrone.Core.Datastore.DbFactory.Create (NzbDrone.Core.Datastore.Migration.Framework.MigrationType migrationType) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:70 at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (NzbDrone.Common.Composition.IContainer container) [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Datastore\DbFactory.cs:48 at NzbDrone.Host.NzbDroneServiceFactory.Start () [0x00037] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\ApplicationServer.cs:60 at NzbDrone.Host.Router.Route (NzbDrone.Host.ApplicationModes applicationModes) [0x0007f] in C:\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 C:\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 C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Host\Bootstrap.cs:41 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00030] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Console\ConsoleApp.cs:42 Press enter to exit... [Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version 3.0.10.1567 The link in the error message says to upgrade Sonarr to 3.0.10 to resolve the issue. I am already running that version so it does not help. I stopped Sonarr, deleted the docker image and then recreated the Sonarr docker image using the Sonarr template, then started the docker and I still get the same 'Epic Fail" error message. So I'm not sure how to proceed. What would be the next troubleshooting step?

I had an issue where when I restarted my Unraid server it wouldn't start as the boot drive was trashed. I created a new boot drive from a backup but my two SSD's in a cache pool are now showing in unassigned devices. I saw this question asked before and I want to follow the procedure @JorgeB outlined to get the cache drives back in the pool without losing data but I have a couple of questions. The steps and questions are: 1. Stop the array 2. If Docker/MV services are using the cache pool disable them - does this mean to go into settings and for both Docker and VM Manager to set the "Enable Docker" and Enable VM's" to 'NO'? 3. Unassign all cache devices - I'm not currently showing any cache drives as they are both now in unassigned devices. So I think I don't need to do anything here, correct? 4. Start array to make Unraid "forget" current cache config 5. Stop array 6. Reassign all cache devices - at this point would I click on the "Add Pool" button to assign the cache drives? I thought I would see a section with a "Cache" header with a dropdown to assign drives but I don't see a "Cache" header on the page, just the "Add Pool" under a 'Pool Devices' header. 7. Re-enable Docker/VM's if needed - is this the reverse of step 2 where I would go into the settings for Dockers and VM's and enable them? 8. Start array

Thanks for help, I'm getting there! I created a new boot drive and after booting and assigning the drives to the correct drive slots I was able to find a backup of my USB boot drive that was only a couple of days old. I copied over that config folder to the new boot drive and transferred the key to the new drive and the server is back up. However, there are some issues that I still need to sort out. 1. I have two SSD cache drives but they are now showing as unassigned devices. 2. None of my VM's are showing. The VM tab isn't present in the UI. 3. None of my dockers (plex, sonarr, radarr, nzbget) are working. They all show as running but when I open the webUI it gives an error message of, "This site can't be reached". Checking the logs show "fatal error" for all of the dockers: Sonarr: GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [Info] Bootstrap: Starting Sonarr - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.5338 [Info] AppFolderInfo: Data directory is being overridden to [/config] w32error-unix.c: unknown error (123) "No medium found" [Trace] DiskProviderBase: Directory '/config' isn't writable. Win32 IO returned 50. Path: /config/sonarr_write_test.txt [Debug] X509CertificateValidationPolicy: Certificate validation for https://sentry.sonarr.tv/api/8/store/ failed. RemoteCertificateChainErrors [Fatal] ConsoleApp: EPIC FAIL! [v2.0.0.5338] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: AppFolder /config is not writable at NzbDrone.Common.EnvironmentInfo.AppFolderFactory.Register () [0x0007c] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\EnvironmentInfo\AppFolderFactory.cs:50 at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, NzbDrone.Host.IUserAlert userAlert, System.Action`1[T] startCallback) [0x00050] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Host\Bootstrap.cs:36 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00029] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Console\ConsoleApp.cs:37 Press enter to exit... Non-recoverable failure, waiting for user intervention... [Info] Bootstrap: Starting Sonarr - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.5338 [Info] AppFolderInfo: Data directory is being overridden to [/config] w32error-unix.c: unknown error (123) "No medium found" [Trace] DiskProviderBase: Directory '/config' isn't writable. Win32 IO returned 50. Path: /config/sonarr_write_test.txt [Debug] X509CertificateValidationPolicy: Certificate validation for https://sentry.sonarr.tv/api/8/store/ failed. RemoteCertificateChainErrors [Fatal] ConsoleApp: EPIC FAIL! [v2.0.0.5338] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: AppFolder /config is not writable at NzbDrone.Common.EnvironmentInfo.AppFolderFactory.Register () [0x0007c] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\EnvironmentInfo\AppFolderFactory.cs:50 at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, NzbDrone.Host.IUserAlert userAlert, System.Action`1[T] startCallback) [0x00050] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Host\Bootstrap.cs:36 at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00029] in M:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Console\ConsoleApp.cs:37 Press enter to exit... Non-recoverable failure, waiting for user intervention... Plex: PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... Is there something I overlooked that might be causing these issues?

I have a screenshot showing my drive assignments but I just want to make sure that if I boot using a newly created Unraid boot drive that none of the existing data will be corrupted during the first boot. Will the array be offline when I first boot, allowing me to assign the data and parity drives before I then bring the array online? Does my idea make sense of booting into the server with a new boot drive so that I can find my USB backup that I believe to be saved to the array, and then copy that config folder over to the boot drive? Assuming my backup is recent, would that get my Unraid server back to what it was? Also, does it matter if I create the new boot drive with a more recent version of Unraid than what my server is currently configured with?

Yeah, that's a bummer. I'm pretty sure that I have a recent USB backup on the array. Should I make a new Unraid USB boot drive and then bring up the array and see if I can then copy the config folder from the backup over to the USB drive? My server is running Unraid 6.8.2, does it matter what version I install on the USB drive? I don't see that version as available using the Unraid USB creator. When I boot the first time after creating the Unraid USB boot drive, will Unraid know what drive is my parity drive and what are my data drives and unassigned drives? Is there a guide I can follow to get everything back up and running?

BTW, I tried to see if I could grab the config folder off of the USB drive but the drive doesn't show up on my Windows or Linux desktops when I plug it in.

I wanted to add a bigger parity drive to my server so I first upgraded my Unraid license to the Pro version as I was at my drive limit, stopped the array and entered the license key, and added a new drive. After bringing up the array I started a preclear on the new drive. I noticed that during the preclear the Docker tab was no longer visible and there was an error message on the main page. I didn't write down the exact error message but I believe it had something to do with the dockers. I figured I would wait until the preclear was done and then reboot the server to see if that fixed the error message and the disappearing Docker tab. (As a separate issue that I won't try and address just yet, in addition to that error messages some of my shares got messed up. I had a couple of shares that were only allowed to use a specific drive but now those two shares were using all array drives. This issue I will deal with after I get the server up and running). After the preclear was finished I tried stopping the array but would get the message to, "retry unmounting disk share(s)". I left it for a good 30 minutes and the array still wasn't stopped. Checking the logs and it looked like Disk 1 was "busy" and couldn't be unmounted: May 22 10:21:05 Tower emhttpd: shcmd (844908): umount /mnt/disk1 May 22 10:21:05 Tower root: umount: /mnt/disk1: target is busy. May 22 10:21:05 Tower emhttpd: shcmd (844908): exit status: 32 May 22 10:21:05 Tower emhttpd: Retry unmounting disk share(s)... I ended up shutting the server down with a "powerdown" command. However, the server will now not boot. Connecting a monitor to the server and during boot I get an error message of: Media test failure, check cable I tried moving the usb key to another usb port. I also looked in the BIOS to disable secure/fast boot but couldn't find either option in my Supermicro BIOS. I believe I have a backup of the USB key, but of course, it's on the array which I don't have access to Is my only option to make a new USB boot drive? Will I have to redo all my settings (shares, VM's, dockers, etc...)?

I ended up deleting the vdisk, rebooting the VM, shut it down and then re-added the vdisk and now it seems to work. Don't know what the issue was but at least it's sorted

I have two unassigned devices that I use for Blue Iris storage in a Windows 10 VM by editing the XML and adding them as vdisks. I went to add a new drive to the array but I removed the wrong drive caddy and accidentally pulled one of the unassigned devices drives. I popped it back in but the Windows VM can no longer see that drive. I've tried restarting the VM to no avail. I do have the unassigned devices plugin with destructive mode enabled. I tried deleting the partition and then formatting the drive but the drive still isn't showing up in the VM. Any thoughts on why the drive no longer shows up in Windows 10 VM?

Thanks, that did it