Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Your boot drive is corrupted or offline. Post your diagnostics in the forum for help

Featured Replies

Hey all,

I recently had a USB boot drive become corrupt and so I used a recovery tool to download the config folder off of it and copied it to a new usb drive. However, when rebooting unraid with the new USB drive, I get an error message "Your boot drive is corrupted or offline. Post your diagnostics in the forum for help" and my Main tab is blank (image below). I assume the previous usb drive corruption occured in the config folder, but I am not sure how to find it / fix it. Attached is my diagnostics zip.

Where should I look to fix this? How do I prevent this from happening again? Should I switch over to SSD boot? I am currently running Unraid 7.3.2.

Thank you all in advance!

Screenshot 2026-10-08 100208.png

tower-diagnostics-20261008-0958.zip

Solved by JorgeB

  • Community Expert

Your diagnostics show that config/flash.cfg contains only zero bytes. This is consistent with a damaged file carried over during recovery.

The replacement USB is mounted, and your array is running despite the blank Main tab. This warning does not, by itself, mean the replacement USB has failed.

First, save a copy of the current config folder to another computer. Keep the original recovered files too.

If you have a backup from before the corruption, restore config/flash.cfg from it. Otherwise, use the Unraid terminal to preserve the damaged file under another name:

mv -n /boot/config/flash.cfg /boot/config/flash.cfg.bad

Then reboot cleanly and check the Main tab. If the command reports an error, stop and post the error.

Fix Common Problems also flags a share configuration file as corrupt. Please attach fresh diagnostics after the reboot so we can check for remaining damage.

SSD boot is optional, but repair the configuration first. Migration copies the existing configuration, so it would carry damaged files across too.

Once recovery is complete, keep an off-server boot backup and use clean shutdowns. Unraid Connect’s automated flash backup can help with future recovery.

  • Author

Thank you for the prompt response! I followed your instructions and changed the name of the flash.cfg file, rebooted cleanly. At startup, I saw the main tab populate with all of my disks, but then a few seconds later the main tab reverted back to the blank page I showed before. Attached is an updated diagnostics.

However, I am no longer getting an error banner stating that the USB drive is corrupted.

I will take better care to backup my config next time. I'll look into Unraid Connect for that purpose!

tower-diagnostics-20261008-1114.zip

  • Community Expert
  • Solution

The banner is gone, so flash.cfg is sorted.

The blank Main tab is a different file damaged in the same recovery: config/parity-checks.log (your parity check history). It doesn't contain valid text, and the Main page crashes when it tries to read the last entry. That's why the disks appear for a moment and then disappear. It's a known WebGUI bug that will be fixed in a future release. Your array and data are fine.

The share config that Fix Common Problems flags is also damaged; it contains binary data rather than settings.

In the terminal, set both aside the same way as before:

mv -n /boot/config/parity-checks.log /boot/config/parity-checks.log.bad

Do the same for the share file Fix Common Problems names: mv -n /boot/config/shares/<name>.cfg /boot/config/shares/<name>.cfg.bad

You'll lose the parity check history, but it was already unreadable. The share will come back with default settings, so check and re-apply its settings (primary/secondary storage, export, etc.) in the Shares tab before running the mover. The data in the share isn't affected.

Since several files were damaged, check for others before rebooting:

grep -rlPa '\x00' /boot/config --include='*.cfg' --include='*.log' --include='*.conf'

This lists any config files containing zero bytes. If anything other than the two files above shows up, post the list. Then reboot and check the Main tab. If anything is still wrong, post new diagnostics.

  • Author

Thank you for the help! My Main tab now shows up with the parity check log remade.

I found a few other config files that were corrupt and replaced those too. Now everything seems to be stable and I have off server backups. Thanks again!

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.