After upgrade to 10.3.0.3, embedded drive 'changed'

[Prufrock]

I've just upgraded from 10.2 to the latest, 10.3.0.3, using the .img.xz method and all seemed to go smoothly. However, when I checked the Disk Management menu, there was this warning in red at the top:

The device(s) in config are different to actual device(s). Please remove the device(s) and re-add it or use 'Clear config and Import disks'.

The offending disk was shown as:
da0 Verbatim STORE N GO PMAP 7386MB 097A01B24050 umass-sim0 XHCI (generic) USB 3.0 controller Always On UFS CHANGED (Device Serial : '097A01B24050' to '070B45F7CBA99A12')

This USB drive is, of course, where the system is installed - and it wasn't changed or even removed. Does the disk have more than one serial number?

I'm reluctant to 'remove the device(s) and re-add it or use 'Clear config and Import disks' as I'm not sure what will happen if I do. The other disks seem OK and the system seems to be working fine - I can access my data over the network, for example - but I assume I need to act on this warning, or clear it somehow.

Any advice?

Thanks!

x64-embedded on AMD Sempron(tm) 3850 APU with Radeon(tm) R3, ASRock AM1B-ITX

[Prufrock]

Well, I guess I should have searched harder. Having found another post with a similar problem (though in that case the user had changed the USB drive), I learnt that it should be safe to do as advised and 'Clear config and Import disks'. So I did, and clicked apply (without removing the USB drive). After a short while, the disk management list showed all was fine.

Needed to log out and in again: I did discover that I needed to do one other thing, however. After this process, when I attempted to log in as a user through the file system on my Linux desktop, I found that instead of accessing my storage files I appeared to be browsing the root system of the embedded system on the USB drive. Trying to unmount didn't clear this. So I logged out completely as a user on my desktop client and then logged in again. Now I can access the files stored on the NAS. It's now happily (I hope) copying several hundred GB of images.

So, fairly quickly solved - but one small question remains: should this error message have been generated in the first place?

Thanks for the (now working) system!

[crowi]

It is always a good idea to read the README file before the upgrade:

"...Don't forget to backup the current system configuration of NAS4Free before upgrading! 1. System|Backup/Restore Restore your config. 2. Disks|Management click on Clear config and Import disks to update configuration. 3. Disks|Management|Disk Edit After step 2, you will need to re-activate S.M.A.R.T. monitoring for every device...."

[Prufrock]

Hi: thanks for the quick feedback. Of course, I should have looked at the Readme. What puzzled me at the time was that it was only the USB drive that showed an error after the upgrade. Anyway, all's well now and 300GB have already been copied.