Hi,

Today I noticed my server had an unclean restart this morning and the array couldn't start due to missing assignments.

Initially I thought the unclean restart may have caused file corruption on the boot usb, however, the files don't seem corrupted, they just seem reset. Here is an example from my system pool config (before -> after):

• diskFsType: "xfs" → "auto"

• diskUUID: "<uuid>" → ""

• diskAutotrim: "on" → ""

• diskCompression: "off" → ""

• diskFsWidth: "1" → ""

• diskFsGroups: "1" → ""

• diskId: "Samsung_SSD_860_QVO_1TB_<id>" → ""

• diskSize: "976761560" → "0"

Not only that, but it seems like the USB backup made to unraid connect contained this reset config before the unclean restart happened (about 5 hours before). Which implies this problem existed before the unclean restart, and the restart only revealed the fact the config had been messed up.

Oddly, it doesn't seem like the other drives in my data array were affected, just system pool/acceleration array.

I'm missing any logs/insight into what could have reset my configs this way. Does anyone have any tips for how I can troubleshoot this issue more?

You can just reimport the pool(s)

on main, create a new pool with the same name and number of slots

assign the pool device(s), leave the filesystem set to auto

start the array to import the pool

If you need help with the array assignments, i.e., you don't know which drive is parity, see here:

https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device/#recovering-from-a-failed-boot-device-without-a-backup

Thanks @JorgeB .

Thankfully I had backups so reconfiguring the array wasn't difficult. I'm more worried about the fact I lost the config in the first place.

I'd like to rectify whatever caused it if possible.

That's typically a flash drive issue, but it could be filesystem related, not necessarily a bad flash drive.

Filesystem of what? The array?

I'll guess if it was usb related, I wouldn't have clean config files (maybe something malformed/corrupted). Array filesystem problems does make sense, but I'm not sure how to troubleshoot it.

One semi-related issue I have is I can't find any syslogs from before the unclean restart, so it's difficult to follow if something odd did happen. I have the option to write syslogs to usb before restart enabled, but it didn't seem to work. I guess it doesn't happen on an unclean restart?

12 hours ago, rbhalla said:

Filesystem of what? The array?

The flash drive.