January 29, 20233 yr Hello, I have read a few other posts about using the “new config” tool to do what i think I need. However, I have enough uncertainty that I wanted to reach out and get confirmation of the proper procedure to avoid data loss. A shorted rail on my PSU killed both of my SSDs. I’ve replaced the PSU and put new SSDs into the array, and recreated my dockers/VMs already. However, the disks show as wrong/disabled for the cache since they’re different than the previously assigned drives. As I understand it, I should be able to use the “New Config” tool and preserve the current configuration to make Unraid accept the current configuration as “correct” and not “wrong”? Do I need to stop the array before this? Could this cause any data loss?
January 29, 20233 yr Community Expert 13 minutes ago, internetbummer said: put new SSDs into the array, and recreated my dockers/VMs already. However, the disks show as wrong/disabled for the cache since they’re different than the previously assigned drives. Can't make much sense of this part. Attach diagnostics to your NEXT post in this thread.
January 29, 20233 yr Author Quote put new SSDs into the array, and recreated my dockers/VMs already. However, the disks show as wrong/disabled for the cache since they’re different than the previously assigned drives. I removed the dead SSDs and put alternate SSDs in after identifying the problem with my power supply. Before starting up the array, I put the new SSDs into the slots in the configuration, reformatted them, restored appdata from backups, and recreated my VMs. My system is in a "good state" now, except for the drives appearing on the Main tab with red X's next to them that says "Device is disabled, contents emulated". As far as I can tell, it's saying that because the disk identifiers are different now. I believe I just need to tell Unraid that those are now the "correct" drives to be in those slots. I just want to confirm the proper procedure to avoid needing to go through the backup/restore procedures for the cache drives again. Diagnostics are attached now. (edit: removed after receiving solution) Edited January 29, 20233 yr by internetbummer Removing diagnostics
January 29, 20233 yr Community Expert Solution 6 hours ago, internetbummer said: put new SSDs into the array pools are not "in the array" 15 minutes ago, internetbummer said: except for the drives appearing on the Main tab with red X's next to them that says "Device is disabled, contents emulated". Not sure I've seen that before on pool disks, they really can't be "emulated" since they are outside the parity array. Post a screenshot. 6 hours ago, internetbummer said: use the “New Config” tool and preserve the current configuration to make Unraid accept the current configuration as “correct” I guess you could New Config/Trust Parity. https://wiki.unraid.net/Manual/Tools#New_Config Your appdata and system shares have files on disk5. You will have to set to cache:prefer, disable Docker and VM Manager then run Mover. If they are duplicates you will have to clean up manually. You can see how much of each disk is used by each user share by clicking Compute... for the share on the User Shares page, or the Compute All button
January 29, 20233 yr Author Success! For anyone doing this in the future, the process I followed was: - Stop docker and VMs (I could have just stopped the array, but I had other clean-up to do based on trurl's noticing I had content on disk5) - Stop the array from the "Main" tab - Use the new config tool, preserving the array positions with the dropdown - Go to main tab and assign my cache drives again - Start array - At this point I could enable docker again, but I have the mover running now to bring content from disk5 back to the cache pool. Thank you trurl!
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.