Hey all. Looking for some tips here. hoping I haven't been hacked.

I run regular updates, and am on the current version of unRAID. However 3 days ago, I was unable to log in. The GUI was completely unresponsive. Couldn't SSH in either - kept getting connection refused.

Had to hard power the server down :-( Came up fine though, and everything seemed good.

Today, 2 days later, GUI was not working properly. Basically hardly anything being displayed on screen. Again, couldn't SSH in. Accessed terminal from connected keyboard and monitor, logged in and entered "reboot" on cli.
Saw an error in /etc/initscript: line 22 /etc/rc.d/rc.6: input/output error.

Hard to force power off again for second time in 3 days.

unRAID rebooted, I logged in, figured I would check SSH is enabled (it was). Cancelled the Parity Check (as that would take days and had just completed 4 or 5 days ago. Saw there was a plugin update for Tailscale, started it, then saw an error the update was unavailable. Clicked Docker to check for updates, then got thrown out to a First-Time-Boot type of screen.

I've been running unRAID Plus for years, and mostly just do updates. But something seems to have gone haywire.

Every time I hit "Skip Setup" it just returned to this screen. After 5 minutes, I just tried it again, and the GUI is no longer accessible.

[OK - figured out it was using https which is no longer valid, so can see the login screen at http://IP address. BUT, I cannot log in as root, just clears my password and returns to login screen]

However I have now been successfully able to SSH in.

I've suddenly got lots of questions! What is going wrong and where do I begin to diagnose / fix it?

My first concern would be data preservation.

• How do I stop the array cleanly from an SSH connection?

• How can I restart the GUI?

• How can I diagnose what problems there are (e.g. is it my USB flash drive going bad, memory errors)?

• Has all my config totally disappeared?

Extra information - my shares are currently inaccessible.

I have a flash drive backup that is approximately 2 months old (from version 7.2.4) although unRAID had been updated to 7.3.1 (if that's what current is).

Any help with next steps would be greatly appreciated!

Thanks.

Edited Monday at 06:59 PM3 days by MediaMaan
Extra detail added

Attach Diagnostics ZIP to your NEXT post in this thread.

42 minutes ago, MediaMaan said:

flash drive backup that is approximately 2 months old (from version 7.2.4) although unRAID had been updated

Have you made any significant changes since then? Most importantly, any changes to drive assignments?

12 minutes ago, trurl said:

Attach Diagnostics ZIP to your NEXT post in this thread.

Says it created a diagnostic file, but it isn't visible.

I have found 3 diagnostic directories created in the root directory. Under /unraid-diagnostics-20260706-1343

I see 7 subfolders and 1 unraid-7.3.1.txt file. Not sure how to turn that into a ZIP file and move it from unRAID to my linux desktop here.

No significant changes made at all. No new containers / plugins etc.

Edited Monday at 07:46 PM3 days by MediaMaan

10 minutes ago, MediaMaan said:

I see 7 subfolders and 1 unraid-7.3.1.txt file. Not sure how to turn that into a ZIP file and move it from unRAID to my linux desktop here.

No significant changes made at all. No new containers / plugins etc.

OK, used Mint GUI to connect via SSH and ZIP the directory. Looks like most things are blank to me (e.g. no shares etc).

unraid-diagnostics-20260706-1253.zip

Further to my last, I performed a reboot via SSH.
unRAID then proceeded to boot normally, permit me to login, and is showing my drives and shares as usual.

This time I used the GUI to create a diagnostic zip file, that looks quite different to the last.

See attached.

I'm really confused as to what is going on right now.

unraid-diagnostics-20260706-1359.zip

Jul 6 18:25:49 unraid kernel: fat__get_entry: 891 callbacks suppressed

Jul 6 18:25:49 unraid kernel: FAT-fs (sdf1): Directory bread(block 32316) failed

Jul 6 18:25:49 unraid kernel: FAT-fs (sdf1): Directory bread(block 32317) failed

Jul 6 18:25:49 unraid kernel: FAT-fs (sdf1): Directory bread(block 32318) failed

Jul 6 18:25:49 unraid kernel: FAT-fs (sdf1): Directory bread(block 32319) failed

Jul 6 18:25:49 unraid kernel: FAT-fs (sdf1): Directory bread(block 32320) failed

Flash drive problem: you can try backup and recreate first; if the issues persist, replace it.

On 7/7/2026 at 12:39 AM, JorgeB said:

Flash drive problem: you can try backup and recreate first; if the issues persist, replace it.

Thanks for this.

I made a fresh backup, let windows fix the errors on the drive, and reinstalled the flash drive. Back up and running. Hopefully problem solved.

I may pick up a new USB drive just in case. I'm wondering if these USB drives are susceptible to RF transmissions nearby. The server is located next to walkie talkies running 5W of power, and several 50W radios dumping into a termination load. That load should arrest most of the RF, but perhaps having the transmitters a few feet away is causing an issue.