June 23, 201610 yr So here is a topic to discuss * in case this happens*. unRAID boots off a USB drive and contains all of the OS data on it. Including the purchased key and the array configuration. How what do we do if the USB fails and a new one is replaced? Well I put that to a test today... I got a brand new flash usb drive and booted off it... Unfortunately none of the drive assignment was automatically picked up, which leads me to believe there is no meta data at play here which would mark each drive as being used in an array and in particular order... Question to experienced community: 1) Should the USB Flash Drive be occasionally backed up? dd'ed? 2) Anything in particular should be backed up from the USB Flash Drive? 3) Maintenance? Cheers.
June 23, 201610 yr Author Didn't help. I did use search. "USB Recovery" didn't provide significant search results.
June 23, 201610 yr Author https://lime-technology.com/wiki/index.php/Files_on_the_unRAID_flash_drive " Backing up the unRAID flash drive[edit] It is recommended to always keep your unRAID flash drive backed up. Once in awhile, you should make a copy of all files and folders to an external drive. For daily backups, just copy the /config folder, with its files and folders. The /config folder contains all of your settings and unRAID configuration. Ideally this backup should be made with the array stopped. " That's that was needed. Thanks.
June 23, 201610 yr Community Expert Just a couple of things to add about the super.dat file. You should never restore a backup of super.dat that doesn't contain your current array configuration. There has been more than one case of a user using an old super.dat where that file had the wrong drive configured as parity. They had a data drive in their array that had once been a parity drive, and when they used the old super.dat it showed that the drive they now had data on was the parity drive and it began to overwrite the data with parity. Also, you can make a copy of the boot drive over the network. It appears as the share named flash. In addition to the drive assignments, super.dat also stores the started/stopped status of the array. If you boot from a copy of super.dat that shows the array was started, unRAID will begin an automatic correcting parity check due to an unclean shutdown. The flash share can still be accessed over the network even with the array stopped, so if you stop the array before making the copy then you will have a super.dat backup that shows the array was stopped and you won't get the parity check when you boot.
June 23, 201610 yr Community Expert Picking the right search words can make a huge difference in the results, and it is not always obvious what should be tried. Searching for "backup flash" gets a lot more relevant results, including some of my own posts with some of the things I have repeated here.
Archived
This topic is now archived and is closed to further replies.