Config Issue

[jelter]

I have another FreeNAS7 server that i am trying to create a new server for. The(9.1)new server boots to flash has a RAID5 software array. I am able to configure the server with out issue however as soon as i power the server down or reboot the entire configuration is lost and i have to start from the beginning again and have done so now three times. I seem to be missing something over the old version 7. Any assistance directly related to the issue is appreciated. Thank you!

[jelter]

I am using the LiveUSB version should i be using the embedded?

[jelter]

Changes are not saved. Answered my own question.

[armandh]

there are numerous ways to save the config file or the embedded OS

live CD and USB flash or floppy config
a small Hdd to spin down after 5 minutes for the embedded and config
industrial IDE flash drives for embedded and config http://www.logicsupply.com/categories/f ... sh_modules

my favorite are small Hdd or industrial flash

if the hardware will boot USB that will work too

[jelter]

armandh thanks for the info. I really would like to buy one of those industrial flash hdds. However for now i will be booting it to a standard kingston traveler flash drive. I would like to know how i should or what i should use to back up the system on that flash drive. Perhaps another flash drive drive but what do i use to image it to the other?

[raulfg3]

For Kingston use embeded install, and save config in your desktop PC

[jelter]

How do i save those config files from the flash drive to my local computer and maintain recoverable. How to?

[raulfg3]

In N4F webgui, select save config

http://wiki.nas4free.org/doku.php?id=do ... up_restore

[armandh]

the config file is VERY small about 20 Kb

simply retain the CD or file you used to load the OS to the flash drive
and when the flash drives goes bad install to a new one then boot it
set the NIC and IP address and from the client GUI restore the config
you will find it in the down load file [or where ever you previously saved it]
if it was a larger [non drive] hardware failure and it is all new hardware
add a final step of resetting the NIC and IP to the new hardware and existing drives.

N4F is easily relocated to other hardware in an emergency
ZFS is tenacious keeping the data secure

I once stuck a small Hdd I had used as a ZFS mirror test into a test N4F expecting to use it as a boot drive
only to find the data was still there in the degraded pool. I had to reformat it EXT4 and delete partition to erase the data.
only to find it has a bad MBR sector and was unusable as a boot device.