FalconX

Can confirm - had this happened to me today. Clicked the "Update All" button, it updated the containers and got stuck in a loop where it would keep trying every single one again. Refreshing didn't solve it either, as the logs still kept telling me containers were getting updated. Had to do a complete restart of the server. I'm on Version: 6.11.1

I use the SSD Plex (metadeta, config etc), nzbget unpacking and I have one VM disk on there which is not currently being utilized.

As requested. Thanks!

Every since a few updates ago, I've been getting the following errors in my logs every now and then regarding my UD ssd. The SSD is about 2 years old with a lot of writes but I don't see any other issues with it, SMART reports are all ok. Should I look at replacing it? Thoughts?

Is there an option within UD to keep the drives spinning 100% of the time? I have a few drives that I write to periodically and they spin down after a period of time, and when my application goes to write to it, it gets a write error because the drive takes a bit to spin up.

I have not experienced any SQlite DB corruptions running on Version 6.7.2 since its release. Currently running Radarr, Sonarr, Plex, Emby etc. All of my appdata resides on the cache, with Plex and Emby being the exception. Plex and Emby are currently on an Unassigned device SSD (/mnt/disks/samsungssd/plex/ - /mnt/disks/samsungssd/emby/) mounted as RW/Slave.

Did you ever end up solving this? I am having the same issue.

Also getting the same error at usually the same time. No idea what GSCP is.

Hi all, Recently I started getting the following errors, I would appreciate any and all help I can get with this. If someone can look over my network settings that would be wonderful. I have two NICs. I decided to keep eth0 and br0 to unRaid and Dockers, whilst having eth1 being assigned to VM's using VLANS. I keep getting these errors. I'm not sure if I have my network settings correct, or if I am doing VLAN's correctly. Every 12 hours which is my USG router dhcp lease time, it gets a fail to rebind message and shortly after I get the following: I would also like to mention, I have a pihole container set on Custom br0: 192.168.1.5. Everytime I reboot unraid, the container fails to start. I have to turn dockers off and on again to get Custom br0 to show up again as a network interface and then start the container. Network settings: Docker settings: USG: Thank you in advance!

I'm also experiecing this same issue with piHole which is using Custom br0 with an IP address I defined. After every reboot, I need to disable docker and enable docker to get Custom br0 to show up again.

Upon further research, as long as I backup the config/super.dat file, unraid should recognize the XFS encryption and ask for a passphrase...someone correct me if I am wrong?

I've read this https://wiki.unraid.net/index.php/Files_on_v6_boot_drive#Starting_Over and understand how to back up the drive configuration but does having an encrypted xfs drive configuration with an encryption key file change the process any way? How do I make sure I don't lose any data when I re-install unraid and backup the drive configuration, should I delete the encryption keyfile before hand? The goal is to keep the encrypted data on the array but restart unraid from scratch. Thanks for the help.

My issue was resolved in the VM section I was not getting any luck here.

Well either, or both of those solutions appears to have fixed my issue. Much appreciated @AnnabellaRenee87 @1812 !

I've added append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot to my syslinux.cfg Unfortunately my diagnostics do not say anything since unraid crashes and won't dump a diagnostics file. The last thing that shows up on the log is this: php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it Plex,Sonarr,Radarr,LetsEncrypt,Organizr,Nextcloud,Pihole,rtorrentvpn,tautulli,unifi,unms,ddclient,jackett,mariadb,netdata are all running on the server. System usually sits at 10% cpu load and memory at 24% I've enabled MSI interrupts (it was off) Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ I will let it run overnight again and try shutting down tomorrow. Thanks for the suggestions!