August 30, 20241 yr Community Expert Follow these instructions very carefully. If something doesn't seem to work as described, or if you have other questions, ask. Tools - New Config - Keep all assignments. Before starting the array, make any needed assignment changes. In your situation, leave all assignments alone except for reassigning parity to the original 20TB. Before starting the array, check both the Parity Valid and Maintenance Mode boxes. Start the array. Stop the array. Unassign disk1. Start the array. This will disable and emulate disk1 again. Then post new Diagnostics so we can see if disk1 emulation is working, and decide how to proceed from there.
August 31, 20241 yr 5 hours ago, Scuba_Steve said: With the New Config, I need to connect my 20TB hdd back into my array? 22 hours ago, trurl said: leave all assignments alone except for reassigning parity to the original 20TB
August 31, 20241 yr Author Are these the proper settings after installing the 20TB hdd for parity? I selected All for Preserve current assignments.
August 31, 20241 yr Author I thought from what Trural posted I should put my original 20TB hdd back as parity. I am starting to get confused. Should I put my 18TB drive back in the Parity slot?
September 1, 20241 yr Community Expert That screenshot suggests you did not complete New Config correctly! Did you remember to click Apply after selecting which assignments to keep? If you simply clicked Done then that acts like a Cancel in other OS.
September 1, 20241 yr Author I proceeded with New Config and then selected the 20TB hdd for parity. Started the array in maintenance mode with parity is already valid options. Do I need to start the parity check with or without "Write corrections to parity"? uss-enterprise-diagnostics-20240901-1557.zip Edited September 1, 20241 yr by Scuba_Steve
September 1, 20241 yr Author I am not sure if I did it properly. I have posted my diags and some screenshots. uss-enterprise-diagnostics-20240901-1618.zip
September 4, 20241 yr Community Expert Looks like you followed the instructions correctly but the emulated disk1 didn't mount, and the disk got disabled again after the attempted rebuild. Unassign disk1, start the array and post the output from: xfs_repair -v /dev/md1p1
September 4, 20241 yr Author I have unassigned disk 1 started the array and posting output. Executed: xfs_repair -v /dev/md1p1 Not sure what is going on, but I just lost another drive. uss-enterprise-diagnostics-20240904-1847.zip Edited September 4, 20241 yr by Scuba_Steve
September 5, 20241 yr Community Expert Emulated disk1 cannot be repaired, but disk6 was already missing when you did the new config above, if there was supposed to be a disk6, the emulated disk would never work without it.
September 5, 20241 yr Community Expert You can check/replace cables for disk6 to see if it comes back online, and if it does, try the new config procedure once more. If disk6 is dead not much else you can do other than recover the data from the remaining drives.
September 5, 20241 yr Author If I can not get Disk 6 mounted, how do I proceed to start moving my data from each drive?
September 6, 20241 yr Community Expert You don't need to move the data, you can do a new config with the remaining good disks, which should be all except disks 1 and 6.
September 7, 20241 yr Author I fixed Disk 6, the sata connector broke. I created a new config and still Disk 1 is not mountable. Do I need to format Disk 1? uss-enterprise-diagnostics-20240906-2034.zip Edited September 7, 20241 yr by Scuba_Steve
September 7, 20241 yr Community Expert You didn't do the procedure correctly this time, you didn't unassign disk1, try now but it would have been better without starting the array first. Stop the array, unassing disk1, start the array, post new diags.
September 7, 20241 yr Author I stopped the array, unassigned disk 1 started the array and I posting my new diags. uss-enterprise-diagnostics-20240907-1256.zip
September 8, 20241 yr Community Expert You did another new config without disk1, that was not what I asked you to do, I'm starting to think you are trolling us. Repeat the new config procedure with all disks, including 1 and 6, as described here: https://forums.unraid.net/topic/172556-array-wont-stop-of-shutdown/?do=findComment&comment=1459519
September 8, 20241 yr Author My apologies, as I mentioned I am a noob to this and never had an issue in the past. I have not had to troubleshoot this type of situation. I just want to get my array resolved. I am not trolling I created a new config with disk 1 and disk 6 assigned. Now it is showing all existing data will be overwritten. Is this correct before I proceed? I ran it in maintenance mode with parity valid checked. I started the array and disk 1 is still not mountable. uss-enterprise-diagnostics-20240908-1555.zip Why is my system in paused mode? uss-enterprise-diagnostics-20240908-1611.zip Edited September 8, 20241 yr by Scuba_Steve
September 8, 20241 yr Community Expert On 8/30/2024 at 2:01 PM, trurl said: Tools - New Config - Keep all assignments. Before starting the array, make any needed assignment changes. In your situation, leave all assignments alone except for reassigning parity to the original 20TB. Before starting the array, check both the Parity Valid and Maintenance Mode boxes. Start the array. Stop the array. Unassign disk1. Start the array. This will disable and emulate disk1 again. Then post new Diagnostics so we can see if disk1 emulation is working, and decide how to proceed from there.
September 8, 20241 yr Author 21 minutes ago, JorgeB said: Before starting the array, check both the Parity Valid and Maintenance Mode boxes. Here is my diag from the instructions provided. Disk 1 has my system files on it too. uss-enterprise-diagnostics-20240908-1744.zip
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.