February 4, 20251 yr Hi, so I had the bad luck that a power outage today broke my USB stick. Although I don't know how it happened, it is completely bricked. I managed to create a new USB and transferred my key onto that. The precrash system ran version 6.12.15 but when I created the new USB I thought I could upgrade to version 7.0.0 while I'm at it. I have installed every plugin that the precrash system had, and tried out of my own memory to recreate the disk array as I remember it was (see screenshot). My precrash system was running a lot of docker containers and one VM running Home Assistant which is very important for me to get back. I haven't dared to start the array yet. So, I have a few questions: Is this the right way to go about it? I see that All existing data on this device will be OVERWRITTEN when array is Started which somewhat scares me. Does the Disk order matter in case I didn't get it in the right order compared to previously? Anything else I should consider? From now on, I will backup my USB stick regularly, that you can count on. Any input is appreciated. Best regards, Nony.
February 4, 20251 yr Community Expert Did you not have a current flash backup? Your configuration (everything set in the webUI) is completely contained in the config folder on flash or your flash backup. That config folder is all you need to get going again with your configuration exactly as it was on a new install.
February 4, 20251 yr Community Expert 3 minutes ago, nony said: Does the Disk order matter in case I didn't get it in the right order compared to previously? If you assigned a data disk to a parity slot it will be overwritten with parity so its data would be lost.
February 4, 20251 yr Community Expert 10 minutes ago, nony said: I have installed every plugin that the precrash system had, and tried out of my own memory to recreate the disk array as I remember it was (see screenshot). My precrash system was running a lot of docker containers and one VM running Home Assistant which is very important for me to get back. All of that was part of your configuration. If you don't have that there will be a lot of work to do to get back to where you were. VMs and dockers will still exist, but you won't be able to manage them from the webUI since it doesn't remember their configurations, so they will have to be setup again. User Shares will still exist, since they are simply the combined top level folders on array and pools. But without your configuration, they will have default settings. Other things will also have to be setup again. ALL settings from the webUI are gone without your config folder.
February 4, 20251 yr Author 6 minutes ago, trurl said: Did you not have a current flash backup? Your configuration (everything set in the webUI) is completely contained in the config folder on flash or your flash backup. That config folder is all you need to get going again with your configuration exactly as it was on a new install. Sadly, no, well, it's a half truth. I have one backup from a crash I had in 2023 or something, but that time, the USB stick did not die completely as it did now, but my disk.cfg does not have the names on the disks somehow. # Generated settings: startArray="yes" spindownDelay="0" queueDepth="auto" spinupGroups="no" defaultFsType="xfs" shutdownTimeout="90" luksKeyfile="/root/keyfile" poll_attributes="30" nr_requests="Auto" md_scheduler="auto" md_num_stripes="1280" md_queue_limit="80" md_sync_limit="5" md_write_method="auto" diskIdSlot.0="-" diskSpindownDelay.0="-1" diskSpinupGroup.0="" diskIdSlot.1="-" diskSpindownDelay.1="-1" diskSpinupGroup.1="" diskFsType.1="xfs" diskFsProfile.1="" diskFsWidth.1="0" diskFsGroups.1="0" diskNumMissing.1="0" diskAutotrim.1="off" diskCompression.1="off" diskComment.1="" diskWarning.1="" diskCritical.1="" diskExport.1="-" diskCaseSensitive.1="auto" diskSecurity.1="public" diskReadList.1="" diskWriteList.1="" diskVolsizelimit.1="" diskExportNFS.1="-" diskExportNFSFsid.1="0" diskSecurityNFS.1="public" diskHostListNFS.1="" diskIdSlot.2="-" diskSpindownDelay.2="-1" diskSpinupGroup.2="" diskFsType.2="xfs" diskFsProfile.2="" diskFsWidth.2="0" diskFsGroups.2="0" diskNumMissing.2="0" diskAutotrim.2="off" diskCompression.2="off" diskComment.2="" diskWarning.2="" diskCritical.2="" diskExport.2="-" diskCaseSensitive.2="auto" diskSecurity.2="public" diskReadList.2="" diskWriteList.2="" diskVolsizelimit.2="" diskExportNFS.2="-" diskExportNFSFsid.2="0" diskSecurityNFS.2="public" diskHostListNFS.2="" diskIdSlot.3="-" diskSpindownDelay.3="-1" diskSpinupGroup.3="" diskFsType.3="xfs" diskFsProfile.3="" diskFsWidth.3="0" diskFsGroups.3="0" diskNumMissing.3="0" diskAutotrim.3="off" diskCompression.3="off" diskComment.3="" diskWarning.3="" diskCritical.3="" diskExport.3="-" diskCaseSensitive.3="auto" diskSecurity.3="public" diskReadList.3="" diskWriteList.3="" diskVolsizelimit.3="" diskExportNFS.3="-" diskExportNFSFsid.3="0" diskSecurityNFS.3="public" diskHostListNFS.3="" diskIdSlot.4="-" diskSpindownDelay.4="-1" diskSpinupGroup.4="" diskFsType.4="xfs" diskFsProfile.4="" diskFsWidth.4="0" diskFsGroups.4="0" diskNumMissing.4="0" diskAutotrim.4="off" diskCompression.4="off" diskComment.4="" diskWarning.4="" diskCritical.4="" diskExport.4="-" diskCaseSensitive.4="auto" diskSecurity.4="public" diskReadList.4="" diskWriteList.4="" diskVolsizelimit.4="" diskExportNFS.4="-" diskExportNFSFsid.4="0" diskSecurityNFS.4="public" diskHostListNFS.4="" diskIdSlot.29="-" diskSpindownDelay.29="-1" diskSpinupGroup.29="" But there are new unraid versions and other changes on the system since that time, so that backup wouldn't be valid anyway I guess. 10 minutes ago, trurl said: If you assigned a data disk to a parity slot it will be overwritten with parity so its data would be lost. I'm 100% sure that the 10TB drive is the parity one since it is larger than the rest as well.
February 4, 20251 yr Community Expert Solution 5 minutes ago, nony said: that backup wouldn't be valid anyway I guess If you didn't change any disk assignments since that backup then I would consider reusing it, except maybe the .plg files in config/plugins since they were probably way out-of-date. And if you are unsure if any disk assignments were changed, you could just delete config/super.dat and it will make you assign array disks again. That might give you a head start. config has your share settings in config/shares, it has your docker templates in config/plugins/dockerMan/templates-user. Almost all files in config are text, you can examine them. and maybe figure out how they correspond to webUI settings. And decide what you want to transfer from the backup to your new flash. For future reference, you can always download a zipped copy of flash from Main - Boot Device - Flash - Flash Backup. Also, Unraid Connect plugin will keep a backup of your flash in Unraid Cloud. You must always have a current backup of flash. When you make any settings in the webUI, they will be lost unless they are backed up.
February 4, 20251 yr Community Expert 33 minutes ago, nony said: I see that All existing data on this device will be OVERWRITTEN when array is Started which somewhat scares me. That is referring to your parity disk. If you think your disk assignments are correct, you can check the Parity valid box and it won't even overwrite parity. Probably a good idea to at least do a parity check after starting the array.
February 4, 20251 yr Community Expert And for single parity, disk order isn't important as long as parity is assigned correctly.
February 4, 20251 yr Author I started the array with the parity is valid box checked, and everything spun up as it should. Docker containers and VM started as it should, however, it is as you said. I can't manage them from the GUI any longer. And my docker-compose stuff was removed as well. But I should be able to mostly restore all that using my old backup. Shares are there, but users are gone, but that's an easy fix. Most importantly, my Home Assistant is up and running again, so that I can control my lights and stuff again I am backing up my Flash drive to Unraid cloud from now on. Running a parity check now 13 hours left. Thanks for the quick replies and good support @trurl. You are awesome.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.