03fc35ss Posted January 29, 2022 Share Posted January 29, 2022 Hi all, When building my array, I accidentally included a small 256G SSD as part of the array. Wanting to use it as a cache drive instead, I took the array off-line, unassigned the drive (Disk 6) and assigned the drive to be the cache device. I then went to tools, new config and preserved the current assignments. I then started the array again and ran a 'check'. As can be seen below, I am still seeing the missing drive in the array and there appears to be no way that I can find to remove it. I am still very new to unRAID so any pointers in how to fix this would be much appreciated. I'm running version 6.9.2. Thanks! Quote Link to comment
Solution JorgeB Posted January 29, 2022 Solution Share Posted January 29, 2022 That means the new config wasn't properly done, repeat the procedure. Quote Link to comment
itimpi Posted January 29, 2022 Share Posted January 29, 2022 5 hours ago, 03fc35ss said: Hi all, When building my array, I accidentally included a small 256G SSD as part of the array. Wanting to use it as a cache drive instead, I took the array off-line, unassigned the drive (Disk 6) and assigned the drive to be the cache device. I then went to tools, new config and preserved the current assignments. I then started the array again and ran a 'check'. As can be seen below, I am still seeing the missing drive in the array and there appears to be no way that I can find to remove it. I am still very new to unRAID so any pointers in how to fix this would be much appreciated. I'm running version 6.9.2. Thanks! When you ran the New Config tool did you make sure that you no longer had the SSD assigned to the array before you tried to start the array (committing the assignments). Quote Link to comment
03fc35ss Posted January 29, 2022 Author Share Posted January 29, 2022 Unfortunately, I attempted this a couple of weeks back so I don't recall the exact process I followed. I'm pretty sure the disk (Disk 6 as per the above screenshot) was in the state it is now, 'unassigned'. Any ideas on what I could try next? Quote Link to comment
ChatNoir Posted January 29, 2022 Share Posted January 29, 2022 6 hours ago, JorgeB said: That means the new config wasn't properly done, repeat the procedure. Quote Link to comment
itimpi Posted January 29, 2022 Share Posted January 29, 2022 3 hours ago, 03fc35ss said: I'm pretty sure the disk (Disk 6 as per the above screenshot) was in the state it is now, 'unassigned'. According to the screenshot the SSD WAS left as assigned so Unraid now thinks it is missing. 1 Quote Link to comment
03fc35ss Posted January 30, 2022 Author Share Posted January 30, 2022 15 hours ago, itimpi said: According to the screenshot the SSD WAS left as assigned so Unraid now thinks it is missing. Okay. So it sounds like I did the wrong thing then. So how can I remove it from there now? Quote Link to comment
JorgeB Posted January 30, 2022 Share Posted January 30, 2022 58 minutes ago, 03fc35ss said: So how can I remove it from there now? On 1/29/2022 at 7:50 AM, JorgeB said: new config wasn't properly done, repeat the procedure. 2 Quote Link to comment
03fc35ss Posted January 30, 2022 Author Share Posted January 30, 2022 3 hours ago, JorgeB said: new config wasn't properly done, repeat the procedure. Okay, so I did the following: Set all shares to use only Disks 1-5 (note 6 is not an option) Screenshot of drive assignments Take array offline Tools -> New config Preserve current assignments -> All -> Yes I want to do this -> Apply Confirmed that drive assignments are still correct Confirmed that array devices is no longer listing disk 6 as 'missing' Started the array This appears to have resolved my issue and the offending drive is no longer showing. I think I did not set all shares to use specific disks previously when attempting this. The array is now re-building parity: Thank you! Quote Link to comment
itimpi Posted January 30, 2022 Share Posted January 30, 2022 I am virtually certain that the step you missed the first time around was to make sure that disk6 was not assigned after New Config was run as restricting which disks a share can use should have no effect. Regardless at least it appears you are now in the state you want 1 Quote Link to comment
03fc35ss Posted January 30, 2022 Author Share Posted January 30, 2022 I suspect you are quite right @itimpi thanks for your assistance! Quote Link to comment
Recommended Posts
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.