Finished building parity. Everything was good so figured I would update from 6.6.0 to 6.6.6. Rebooted and was greeted by this.

 

I assume I could just rebuild the parity but something is definitely not right.

 

Edited December 21, 20187 yr by bnevets27

Do you have a recent backup of flash?

Not since changing the parity and doing a parity build. The backup is a week old and has a different disk config.

 

I had a 8tb Parity and a 4tb Parity 2. Changed out the 4tb Parity 2 for a 8tb.

Built parity, everything looked good. Upgraded the OS, and rebooted. And this is what I was presented with.

 

My backup is from before the parity 2 upgrade.

 

I'm ok with doing another Parity build, though not happy about it. But I don't want this to happen again and seems like a bug or corruption of some sort.

 

 

 

 

Well you could always just do a New Config and tell it to trust parity.

True. Well I did a new config and trust parity so I'm back up. Would like to know what happen to have caused that but oh well. 

 

Corrupt super.dat? 

18 minutes ago, bnevets27 said:

True. Well I did a new config and trust parity so I'm back up. Would like to know what happen to have caused that but oh well. 

 

Corrupt super.dat? 

That would make sense but can't say for sure.

 

Be sure to get a new backup of flash. You can download at Main - Boot Device - Flash - Flash Backup

1 hour ago, bnevets27 said:

Corrupt super.dat? 

I think it's likely. The trouble is that it isn't a human-readable file. If you try to view it in a text editor you'll see your disk serial numbers embedded in it but it's essentially a binary file with no easy means of interpreting its contents. Maybe the system ought to keep a second copy on the flash device.

^ That is definitely true as I had tried to view it and that's what I saw. A backup/copy could be a good idea.

 

Backups in general are a good idea but I had made a change from my last backup and therefore the backup wasn't useful.