snowboardjoe

I just installed 2024.03.06c on unRAID 6.12.8. The plugin is stable and working. All dashboards are loading normally. Thanks!

Ouch, that was painful. Got to the point I could not load anything from the UI unless I knew what the exact URL was. I saw in the release notes that the multi minute delay was possible. IMHO, if there would be that much of an impact, it should not have been released that way. This was very disruptive. I've removed the plugin for now until it's stable again.

This tripped me up today as it rendered several containers as orphans. When trying to fix the problem, I kept getting errors where certain null values would render the container as an orphan rather than just erroring out and returning me back to the configuration screen. I'm now aware of this patch after more research and some feedback. Fortunately I was able to fix the problem with new templates for my containers. I know this is not an unraid bug, but if there are changes that can break things (and we've been relying on them a long time), this needs to be called out in the upgrade notes.

When it crashes, is it just automatically rebooting or stuck waiting for user intervention? If stuck, anything on the console?

Each cable is its on unique link between two points. Your diagnostic shows your server is linked at 1000, but it appears there is another link between your server and router that is not. Are you able to verify each link has a 1000Mbps connection? How many links are there to get to your router?

Running 6.12.6 here. A few weeks ago when I ran into a btrfs emergency I was using the restore command to copy the contents of that to an externally attached SSD (Samsung T7 and formatted as hfsplus). I was able to copy the contents of that restore there for safe keeping while I did my btrfs repairs. A week later I realized my external drive was not attached to my personal system (mac mini). I went to plug it in and it would not mount. It had power, but nothing could see it. I used Samsung Magician would could see it, but said there were no mountable systems. It knew there was data there, but could not do anything with it. I was rather stunned by this and thought maybe the drive died. On a hunch, I took the drive and plugged it back into unraid and mounted it. All data was there (old and new data). Uh, ok, this is odd. It looks perfectly fine. Detached it from unraid and back into Mac mini and it mounted immediately as if nothing ever happened. All data was present as expected. Any thoughts on what might have happened here? Happy my data is fine, but very strange behavior. It's as if the first mount on unraid left the filesystem in some bad state, but repeating the operation set things straight again.

Ended up using a backup from 2-3 months ago. Restored that and seem to be stable now. Just had to re-add some shows to monitor that I added since then. Watching logs for a week and will then try to upgrade to v4.

Still not working very well. Jumped to a backup from almost a month ago and still showing database errors. Sonarr is running, but constant database error events.

Yeah, going to dig back to older backups too and see if I can get past the corruption. Check your event log and make sure there are no new errors involving the database. I wish I had know there was a problem much earlier.

Found the resources on how to restore and did that from backup on 27 Dec. Had to roll back to earlier version to match that backup. WebUI is restored and performing updates, but still seems like there is corruption in the database. 23:11 HousekeepingService Error running housekeeping task: CleanupCommandQueue: database disk image is malformed database disk image is malformed 23:11 CommandExecutor Error occurred while executing task MessagingCleanup: database disk image is malformed database disk image is malformed 23:10 EventAggregator CommandQueueManager failed while processing [ApplicationStartedEvent]: database disk image is malformed database disk image is malformed

Sonarr container is offline. Getting some ugly database errors on startup. Pasting the main bits here and attaching the full log. While Processing: "INSERT INTO "Commands_temp" ("Id", "Name", "Body", "Priority", "Status", "QueuedAt", "StartedAt", "EndedAt", "Duration", "Exception", "Trigger", "Result") SELECT "Id", "Name", "Body", "Priority", "Status", "QueuedAt", "StartedAt", "EndedAt", "Duration", "Exception", "Trigger", "Result" FROM "Commands"" ---> code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed NOT NULL constraint failed: Commands_temp.Body [Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Rolling back transaction [Fatal] ConsoleApp: EPIC FAIL! [v4.0.0.748] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: Error creating main database ---> System.Exception: constraint failed NOT NULL constraint failed: Commands_temp.Body While Processing: "INSERT INTO "Commands_temp" ("Id", "Name", "Body", "Priority", "Status", "QueuedAt", "StartedAt", "EndedAt", "Duration", "Exception", "Trigger", "Result") SELECT "Id", "Name", "Body", "Priority", "Status", "QueuedAt", "StartedAt", "EndedAt", "Duration", "Exception", "Trigger", "Result" FROM "Commands"" ---> code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed NOT NULL constraint failed: Commands_temp.Body Press enter to exit... Non-recoverable failure, waiting for user intervention... Any ideas what may be happening here? Seems it started a few days ago when I did an update this past weekend and did not realize it was down. More data I found in the logs when the database problem started: 2023-12-28 06:19:11.1|Info|ExistingOtherExtraImporter|Found 0 existing other extra files 2023-12-28 06:19:11.1|Info|ExistingExtraFileService|Found 0 possible extra files, imported 0 files. 2023-12-28 06:20:50.7|Error|CommandExecutor|Error occurred while executing task MessagingCleanup [v3.0.10.1567] code = Corrupt (11), message = System.Data.SQLite.SQLiteException (0x800007EF): database disk image is ma lformed database disk image is malformed at System.Data.SQLite.SQLite3.Reset (System.Data.SQLite.SQLiteStatement stmt) [0x00088] in <cf516e4846354910b3d60749c8 94b1bf>:0 at System.Data.SQLite.SQLite3.Step (System.Data.SQLite.SQLiteStatement stmt) [0x0006e] in <cf516e4846354910b3d60749c89 4b1bf>: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,Sys tem.Data.CommandBehavior) at System.Data.SQLite.SQLiteCommand.ExecuteReader (System.Data.CommandBehavior behavior) [0x0000c] in <cf516e484635491 0b3d60749c894b1bf>:0 at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery (System.Data.CommandBehavior behavior) [0x00006] in <cf516e4846354 910b3d60749c894b1bf>:0 sonarr_database_error.txt

All good here. Deleted the container, reinstalled it and it fired right up.

Need help troubleshooting install that is no longer working. I had a BTRFS issue earlier that needed repair and this one app (out of about 15) did not come back. When I try to start it it shutdown within 1 second. Nothing in the logs other than declaring the service is starting. What's the best way to debug this?

Went through several other steps, but did not make any progress. Ran restore to an external drive and that seemed to grab everything just fine. Then as a last ditch effort I ran the repair command: root@laffy:/etc# btrfs check --repair --force /dev/sdg1 enabling repair mode Opening filesystem to check... WARNING: filesystem mounted, continuing because of --force Checking filesystem on /dev/sdg1 UUID: 8bdd3d07-cbb0-4d53-a9f2-da67099186ea [1/7] checking root items Fixed 0 roots. [2/7] checking extents parent transid verify failed on 2151677952 wanted 14578466 found 14578474 parent transid verify failed on 2151677952 wanted 14578466 found 14578474 parent transid verify failed on 2151677952 wanted 14578466 found 14578474 Ignoring transid failure super bytes used 258022117376 mismatches actual used 258022100992 parent transid verify failed on 2151677952 wanted 14578466 found 14578474 Ignoring transid failure No device size related problem found [3/7] checking free space tree [4/7] checking fs roots parent transid verify failed on 2151677952 wanted 14578466 found 14578474 Ignoring transid failure ...identical reponses delted for bervity... [5/7] checking only csums items (without verifying data) parent transid verify failed on 2151677952 wanted 14578466 found 14578474 Ignoring transid failure [6/7] checking root refs Recowing metadata block 2151677952 parent transid verify failed on 2151677952 wanted 14578466 found 14578474 Ignoring transid failure [7/7] checking quota groups skipped (not enabled on this FS) found 516044218368 bytes used, no error found total csum bytes: 415007296 total tree bytes: 1490927616 total fs tree bytes: 743276544 total extent tree bytes: 180305920 btree space waste bytes: 374203586 file data blocks allocated: 943655108608 referenced 490961231872 Ran check one more time and it came back clean. Remounted filesystem as RW and remained stable (normally it would go RO in about 30 seconds). Did a full reboot and all services are back online including all containers. Watching for stability at this point.

Making a copy of all data that I can to a separate disk. Turns out I do not have full backups of everything as I thought. Then I'm going to take a look at this item I found and see if there is a way to recover to an older metablock (usebackuproot). https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org/index.php/FAQ.html#How_do_I_recover_from_a_.22parent_transid_verify_failed.22_error.3F I fear this entire filesystem may be unrecoverable, but still fighting a little more.