I'm not sure what was causing the "configuration exists" error -- perhaps it was due to attempting to write configuration through a telnet connection, or something else. I usually run the system headless.
In any case, I completely shut down the server, created several new NanoNAS diskettes (for backup/emergency use), booted with one of the brand new NanoNAS diskettes, re-entered all the license information with a local keyboard, and was able to save configuration to the other diskettes using the local interface. So I guess the particular issue is closed. However, it would be nice to know why the "configuration exists" message was occuring. (Is it an "error," or something else? When I successfully saved, I only got a "DONE" message.)
In future versions, it would be nice if there was an option to input license and unlock codes during the initial floppy configuration, or at least allow both license and unlock codes to be entered from NanoNAS without a reboot.
|