GUI hanging, Unassigned Devices not showing

[sonofdbn]

Just over the last few days the GUI has hung and on the Main page instead of showing the single Unassigned Device that I have, in the UD section there is an animated unRAID logo. At first, I can still access a few things, including files on the UD, and most (but not all) docker containers and my Win10 VM still seem to be running. But gradually the whole system seems to hang. When I restart, everything seems fine (although I end up with an unclean shutdown - but that's another issue I think), but then after a while - some hours or a day or so - it happens again.

 

I'm on 6.11.5.

 

I've attached diagnostics and a syslog file. Hope someone can help.

syslog-192.168.1.14.log tower-diagnostics-20230227-2214.zip

[sonofdbn]

Unfortunately It's happened again. GUI is getting unresponsive. Main tab shows up with the Unassigned Devices showing only the unRAID logo. (Pic is attached.) Can't get into other tabs, like Dashboard or Docker. VM is still OK, but looks like containers aren't running, or at least can't be accessed. Can't get to Plex, qBittorrent or Audiobookshelf from local network, for example.

 

I've uploaded the current syslog. Can't get to the GUI page for getting diagnostics. Parity check is running because of previous unclean shutdown.

syslog_2.log

[dlandon]

Can you remove the UD SSD and see if you have the same issue?

[sonofdbn]

Do you mean physically or virtually? (It's just that doing it physically means digging around in my very untidy case and possibly knocking wires loose.)

[sonofdbn]

Just to add: perhaps I didn't check properly earlier, but Plex is definitely working now. But I can't get to qbittorrent, or Audiobookshelf. VM is still OK after many hours.

[sonofdbn]

On 2/28/2023 at 10:20 AM, dlandon said:

Can you remove the UD SSD and see if you have the same issue?

 

OK, I've removed the UD SSD (virtually) so that it's now under Historical Devices. Everything seems to be OK now! So it looks like it's quite possibly a UD issue.

[Arbadacarba]

I've had similar problems, but it turned out I was causing them by removing Drives physically without dismounting them first.

[sonofdbn]

Problem solved here:

 

 

Essentially the problem is an issue with libtorrent 2.x, which is used by qbittorrent, which I was running. Solution was to roll back to an earlier version of qbittorrent. See details in the quoted thread.