April 11Apr 11 Community Expert Good morning, all!I ran into an odd one this morning when attempting to update a couple of community-installed applications, Plex and FileBrowser in this case. The update process was taking far longer than at any point previously. After 5+ minutes, I decided to simply close the browser tab and log back in to the GUI.That worked without issue, but then I was presented with the following screen:I was able to recover the"Key File URL" and paste it in the requisite field, but nothing happened when I clicked "Install Key".Any thoughts on how to remedy this issue? I'm hesitant to reboot as my Docker applications are currently functioning as expected.Thanks in advance!
April 11Apr 11 Community Expert post up the diagnostics file in a new post in this thread. (Using a new post indicates that you have provided the requested information. Editing an existing post does not do that!)
April 11Apr 11 Author Community Expert 1 hour ago, Frank1940 said:post up the diagnostics file in a new post in this thread. (Using a new post indicates that you have provided the requested information. Editing an existing post does not do that!)Doesn't look like I can pull them via the typical methods.
April 11Apr 11 Community Expert See if you can connect a keyboard and monitor to the system and if you can log into the shell, you should be able to type in diagnostics and it will run it and save to flash drive.I suspect the flash drive may be dying. If you cant access the shell via the local monitor/keyboard method, I would pull the flash drive and see if it can be read by your PC and maybe even run a fsck from windows on it.
April 11Apr 11 Author Community Expert Solution 36 minutes ago, MowMdown said:See if you can connect a keyboard and monitor to the system and if you can log into the shell, you should be able to type in diagnostics and it will run it and save to flash drive.I suspect the flash drive may be dying. If you cant access the shell via the local monitor/keyboard method, I would pull the flash drive and see if it can be read by your PC and maybe even run a fsck from windows on it.Well, now I'm even more confused. I pulled the boot drive, and this was the result from the validation test under Windows:Put it back in, rebooted, and everything is back to normal. I've also pulled the logs, which are now attached to this post. Do you think it's worth migrating to the recently released internal boot, or is it still a bit early to jump ship, given potential bugs, etc.? I already have a pool of drives set up in anticipation of such a move.tower-diagnostics-20260411-1137.zip
April 11Apr 11 Community Expert 2 hours ago, Aimzor said:Well, now I'm even more confused. I pulled the boot drive, and this was the result from the validation test under Windows:Put it back in, rebooted, and everything is back to normal. I've also pulled the logs, which are now attached to this post. Do you think it's worth migrating to the recently released internal boot, or is it still a bit early to jump ship, given potential bugs, etc.? I already have a pool of drives set up in anticipation of such a move.tower-diagnostics-20260411-1137.zipThis use to be a bigger problem about eight to ten years (as I remember...). It was often 'solved' by using a UBS 2.0 port rather than a USB 3.0 port. I thought that these issues had finally been addressed at the hardware level. BUT...
April 12Apr 12 Community Expert 10 hours ago, Aimzor said:Do you think it's worth migrating to the recently released internal boot, or is it still a bit early to jump ship, given potential bugs, etc.? I already have a pool of drives set up in anticipation of such a move.The drive is clean and the symptoms were most likely a temporary system state issue.That said, the drive has been in service since July 2017 -- nearly 9 years. At 32GB it's almost certainly planar TLC which is adequate but not the most reliable option long term. Worth running ChipGenius to confirm what's inside. Depending on what you find, sourcing a verified quality legacy MLC drive as a replacement might be the simpler and more reliable path compared to migrating to internal boot -- the USB Flash section guide and MLC companion thread cover exactly what to look for and list specific verified options currently available on eBay.On internal boot -- beta.2 just dropped and the bug backlog is still being worked through. Your pool drives will still be there when stable releases. No need to rush the migration.
April 12Apr 12 Author Community Expert 1 minute ago, Lolight said:The drive is clean and the symptoms were most likely a temporary system state issue.That said, the drive has been in service since July 2017 -- nearly 9 years.At 32GB it's almost certainly planar TLC which is adequate but not the most reliable option long term. Worth running ChipGenius to confirm what's inside.Depending on what you find, sourcing a verified quality legacy MLC drive as a replacement might be the simpler and more reliable path compared to migrating to internal boot -- the USB Flash section guide and MLC companion thread cover exactly what to look for and list specific verified options currently available on eBay.On internal boot -- beta.2 just dropped and the bug backlog is still being worked through.Your pool drives will still be there when stable releases. No need to rush the migration.<3 Thank you.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.