Lost power briefly this morning and noticed a little while later that my NAS was off. I turned it back on and check to make sure everything was okay. It booted fine and let me login. The disks, arrays, and configs seemed to all be fine, except it said the license key file was corrupted. I was able to successfully recover the key, but it failed to write the recovered key to the disk.

This showed up in the system logs when I got the error:

Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422240) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422241) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422242) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422243) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422244) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422245) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422246) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422247) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422248) failed
Jun 11 12:23:01 NAS kernel: FAT-fs (sda1): Directory bread(block 3422249) failed
Jun 11 12:23:27 NAS kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 54756145)

Looks like there's some level of file system corruption on the stick. Not enough to prevent booting or lose the configs, but at least enough to prevent me from restoring the license key file.

I'm not entirely sure what to do from here. Is there any way to backup the configs and re-image the USB Stick? Or maybe I could migrate things over to a new USB Stick?

Edited June 11Jun 11 by CivBase

First step try recreating the flash drive, first backup the current one, then recreate it using the USB tool, then restore only the /config folder from the backup overwriting any existing files.

If the issues persist after that, bette to repalce it.

When I click the "Flash Backup" button I get a 404 response. If I click it again within the minute, I get a 403. I'm accessing the NAS directly on my local network, not through a reverse proxy.

The server has stopped working. I was able to pull all the files off the USB's file system, including the config dir. Is that sufficient for a backup before I try the USB tool?

Edited June 11Jun 11 by CivBase

I re-imaged the USB stick and copied over all the config files. Upon boot I see many things carried over.

My users are there, my configs are there, and all my disks were picked up. However...

1. My shares are gone.

2. My parity disk is no longer assigned. It is marked as "missing". I have the "Unassigned Devices" plugin and it appears there, but is not available as an option for the parity disk.

3. I no longer see an interface to manually browse files on the disks.

Is there a way to recover my shares without having to set everything back up manually? I still have the config files for all of them.

I have not started the array.

I grabbed the latest version of UNRAID, but maybe that's my problem. My old server was on an older version.

Would the server version be logged anywhere in the old USB files?

8 hours ago, CivBase said:

1. My shares are gone.

2. My parity disk is no longer assigned. It is marked as "missing". I have the "Unassigned Devices" plugin and it appears there, but is not available as an option for the parity disk.

That's suggests all the config files were not copied, or they are corrupt.

AFAICT the share configs seem to all be fine. I have /config/share.cfg, /config/shares/system.cfg, and another /config/shares/*.cfg for each share (attached). So I find it strange that it's not showing the shares.

Based on the changes.txt file from my backup, I was on version 6.12.10. I don't suppose there was a change to how those configs are stored in version 7?

Or are there other relevant config files besides those?

config.zip

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

I've attached my diagnostics and syslog.

natasha-diagnostics-20260613-1627.zip natasha-syslog-20260613-1627.txt

Jun 13 16:28:11 NAtaSha kernel: device offline error, dev sda, sector 8799 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607)

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 38223365)

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607)

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): FAT read failed (blocknr 607)

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 38223365)

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30176) failed

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30177) failed

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30178) failed

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30179) failed

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30180) failed

Jun 13 16:28:11 NAtaSha kernel: FAT-fs (sda1): Directory bread(block 30181) failed

Syslog shows flash drive problems, try recreating it, if they persist, use a new one

I took out each of my disks and manually made an extra backup of all the files I cared about. It doesn't look like there was any missing data.

Then I installed the exact version I had previously to a new USB stick and copied the configs I backed up onto that. This time it picked up all the disks correctly. There were no issues with the parity disk. I transferred the license key to the new stick, double-checked my configs, and then started the array. Looks like it picked up all the shares.

It's still doing a parity check, but I don't see any indication of data loss so I expect that to be alright. Once that's done, I really need to update. And it looks like version 7 lets me migrate my boot device to an internal drive, so I'll probably take advantage of that while I'm at it.

Thanks for the help!