jguest

So I had a folder under config called super.dat, but no file name super.dat. I'm not sure why, I've never messed with it intentionally. I let windows repair the drive, deleted the super.dat folder and restored using a backup. It now just booted with the correct configuration. Thanks for your guidance.

I just confirmed the disk was labeled UNRAID

Would it hurt to delete the folder super.dat on the drive? Maybe clearing these entries will allow it to write next time? Thankfully all my disks are good right now so I shouldn't lose any data.

Just tried to stop the array and I'm getting: Array Stopping•Retry unmounting disk share(s)... And it just hangs. I backed up my usb in order to relabel. Not sure if I'm just going to have to force shut since it's stuck hanging.

Odd, it never has been. I'll work on that now.

I haven't touched the flash in about a year. This issue only started last week. It is on a USB2 port. The flash doesn't have a write-protection switch. I see that super.da.CA_BACKUP is there. I also see there are many files that were last modified today and yesterday, so that should rule out write-protection. There is a super.dat folder last modified 6-23 Thanks for your help.

Thanks for the reply. Here is the attached zip. tower-diagnostics-20200702-1847.zip

In the past week each time I've rebooted my server it has completely lost the config. I have to reassign each drive and recreate parity. I thankfully don't lose any data or drives. I can't think of anything major that has changed. Only recent change I can think of is setting up CA Backup / Restore Appdata. I'm not even sure how to run a report. I just enabled syslog logging now to the cache drive to be able to catch it next time. I did some digging on google but didn't find anything related to my issue.