![]() ![]() MigrationLogger: *** Migrating data source=/config/lidarr.db cache size=-10485760 datetimekind=Utc journal mode=Wal pooling=True version=3 *** AppFolderInfo: Data directory is being overridden to Bootstrap: Starting Lidarr - /usr/lib/lidarr/Lidarr.exe - Version 0.3.1.471 19:34:03,373 INFO supervisord started with pid 8 19:34:03,372 INFO Set uid to user 0 succeeded 19:34:03,372 INFO Included extra file "/etc/supervisor/conf.d/nf" during parsing 19:34:03.120460 Permissions already set for volume mappings Misc HDDs for a total of 6TB storage space Misc HDDs for a total of 20TB storage space Seagate Enterprise level 8TB HDD - parity drive Samsung PM961 M.2 512gbs x 2 - cache in raid 0 Want to avoid having to use some docker from a different repository and go through setting up each from scratch. See: Īny help/input/work around will be greatly appreciated. Same results.Įssentially the error message in the logs for Radarr, Sonarr and Lidarr seems to be the same:Īt .CreateMain (System.String connectionString, .Framework.MigrationContext migrationContext) in C:\projects\lidarr\src\NzbDrone.Core\Datastore\DbFactory.cs:122 is corrupt, restore from backup if available. Same resuts.Īs a test, installed Unraid 6.6.0 -rc4 on the NAS box last night and tried to install Binhex-Lidarr again. 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). Un-installed / re-installed nvme drives and re-formatted.ĭid NOT restore appdata and tried to re-install binhex dockers listed from scratch and still the same results. (Log for Lidarr posted in images attached).ĭeleted docker image file multiple times, While the dockers install without error and startup, I am unable to reach the web UI for any of the affected dockers. Restored appdata using community applications backup and restore app and reinstalled docker images from history. After restoring libvert and disk image from backup, Win10 VM fired up without issues. Followed instructions found here from Spaceinvader One. Last Saturday I decided to swap the 250gb nvme in my main rig for 2 500gb nvme drives in raid 0. This was originally posted in Binhex-Lidarr support page but the problem persists with Linuxserver.io docker containers also. Unraid problem or Docker Repository Issue - Don't know. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |