Good Afternoon. I updated to 6.12.13 last night and noticed, (This could have been there before and I never noticed) a red star on the button bar. I tried to hover over it but nothing happened, I was on Chrome. I then opened Firefox and tried there and it said incorrect autostart order. I then looked up what that was and tried to move things around as suggested in a post I read. That didn't work.

Then I noticed that I had a few docker apps with broken links. I remember on 6.11.* there was an issue and you needed to install Docker Patch, but that was just for 6.11.*. So I started to read more threads and before I started trying what I was reading I wanted to just come and ask for help before I started doing anything. 

By the way, while creating the diagnostic log, I just saw that there is a nvme error. Is it possible to explain that error to me, as I have no idea what it means. I appreciate any and all help. 

tsunade-diagnostics-20240826-1411.zip

Only issue I so so far is this:

 

Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme2n1p2): error count since last fsck: 11
Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme2n1p2): initial error at time 1693713601: ext4_validate_block_bitmap:420
Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme2n1p2): last error at time 1723348801: ext4_validate_block_bitmap:420
Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme3n1p2): error count since last fsck: 4
Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme3n1p2): initial error at time 1684036801: ext4_validate_block_bitmap:390
Aug 26 13:58:24 Tsunade kernel: EXT4-fs (nvme3n1p2): last error at time 1716696002: ext4_validate_block_bitmap:420

 

Check file system on these unassigned devices.

Thank you for the response, I ran the command from the log file (e2fsck) and cleared those errors. Or at least they aren't showing up in the disk log, but I am seeing this though:

 

Aug 26 16:25:28 Tsunade unassigned.devices: Mount of 'nvme2n1p3' failed: 'mount: /mnt/disks/S467NX0M705964T-part3: unknown filesystem type 'LVM2_member'.        dmesg(1) may have more information after failed mount system call.'

 

Also, would you have an idea of how I could fix the 'not available' in the prowlarr app in Docker? Thank you so much.

So I figured it out thanks to a post by @hathi_ndg Fix for Hotio Containers with not available  Thanks so much for all the help I hope this helps other people.