At shut-down, my NAS warns I have no volume, but I do

I've run into a situation that's just odd.  Although my data volume is completely accessible in read/write mode, one of my NAS complains when I shut it down that my configuration changes will not be saved without a volume.  Since there is always a pop-up when you shut down and my data and configurations are being saved, it's not a really big deal.  But it annoys me and I'm not fully confident it won't cause a problem in the future.

Here is some history:  The NAS in question is a two-bay one with a not vertically expanded XRAID RAID1 dedicated to running OwnCloud (though that last part probably doesn't matter).  One of the drives failed.  Before I swapped out the drive, I decided the NAS needed a good cleaning with compressed air, so I also removed the other drive and did that cleaning.  I then put just the good drive in and booted so I could insert the replacement for the other with power on.  But the NAS came up and started the wizard, claiming I had no volume, and I exited the wizard.  The Volumes screen then showed an inactive volume, as has affected many here. 

From SSH, I did a btrfs check of the volume and it reported as fine, so I manually mounted it and then the GUI showed my volume as active.  I inserted the new drive and it completed RAID sync.  When that was completed, I went to re-boot and the NAS gave me that warning.  But I figured that was because I manually mounted the volume after it booted and either all would be well after re-boot or it still wouldn't boot with the volume mounted and I'd need to start from scratch and backup.

After that re-boot, the NAS recognized the volume and all looked fine.  I did a couple more re-boots, and it always gives that warning but does mount the volume on boot.  It doesn't invoke the wizard, either.  I did some pretty intensive testing reading, writing, creating a new share, and changing a user password, and everything is being properly performed as best I can tell.

I'm thinking that my aborting the wizard when I did is the cause and some flag in the OS is set wrong, but I cannot figure out how to fix it.

Has anyone done enough digging around in the OS that they have a suggestion for what I can do?