I am unable to connect to the Web UI, but other aspects of the server (Docker, shares) seem to be functioning, at least partially.  I saw a message on the Web UI about problems with the flash drive, but I reloaded the page and lost connection.

 

I have access to the command line and tried a few commands to fix or identify the issue (attached image).  The diagnostics command is not found.  The /boot folder appears to be empty.

 

What is my next step?  I've picked up a new flash drive to use if needed.

 

 

Edited April 28, 20251 yr by fritzdis

Since I now have a new flash drive on hand, and I have a flash backup through Unraid Connect, I could just try to safely shut down the server and replace the flash device.  But I'd like to know if there is any info I should try to capture before doing that just in case something else is at fault.

Edited April 28, 20251 yr by fritzdis

See if you can get the diagnostics.

Command was unavailable.

 

Unfortunately, I lost command line access overnight.  Just see a couple repeated lines on the attached monitor, and login doesn't work.  No SSH access either.

 

Seems like I'll have to do a hard shutdown now.

Did the hard shutdown.  Replaced the flash drive.  Ready to start the array.

 

Since I did a hard shutdown, are there any special steps I should take to try to make sure the filesystems on the array disks/pools are OK?  The array disks are ZFS, and I have a BTRFS cache pool (SSDs, mirror) and a ZFS pool (HDDs, raidz1).

 

Post-reboot diagnostics attached in case it matters.

sf-unraid-diagnostics-20250428-0847.zip

You should just start normally, any issues post new diags.

Thanks!

 

Logs look good so far from what I can tell.  Docker apps and shares appear fine.  Scrubbed the BTRFS pool and scrubbing the ZFS pool now.  Will do the array drives too.

 

Seems like it was just a hardware issue with the flash drive, and replacing it was the solution.  I should have initiated a clean shutdown while I had the chance.  My best guess for why I lost command line access was that the failed flash drive created those (frequent) repeated messages, which filled up the log, causing memory issues.