-
Persistent 'not installed' disk after disk failure and rebuild of array
Thank you @trurl and @itimpi . Your help and patience are much appreciated. I have everything up and running again and my set-up is much improved. I have followed your advice and am using only HDDs for the array and leaving the SSDs for pool jobs. 🙏
-
Persistent 'not installed' disk after disk failure and rebuild of array
OK. I have reached the point of trying to reassign Disk 2 as Disk 1. In New Config I don't seem to have anything that says 'Trust Parity' as per your suggestion. How do I achieve the disk reassignment, and will all the Shares then point to the correct places on the new disk?
-
Persistent 'not installed' disk after disk failure and rebuild of array
Oh, and I also apologised for keeping on coming back with queries. I really want to complete the process you have suggested so that I can mark this thread as 'solved'.
-
Persistent 'not installed' disk after disk failure and rebuild of array
thinkcentre-diagnostics-20260828-0836.zipThis seems to have lost the text I had composed to go with it! Basically, I have been following your advice, but the process has been a lengthy one. I have copied the data from the emulated disk (Disk 1) to a new disk (Disk 2). However, the process never seems to complete. The bottom of the Main screen on the UI tells me: Array Started Completed: 99%, Speed: 1.82MB/s, ETA: 33:41:21. I don't know what this means, and I am hesitant to stop the array in case it fouls up the copying process which has already taken something like 36 hours! I need to stop the array to follow the next bit of your advice about reassigning Disk 2 and Disk 1.
-
Persistent 'not installed' disk after disk failure and rebuild of array
No, I didn't see any checkbox. Would it be in the same area or would it be further down the page under array management?
-
Persistent 'not installed' disk after disk failure and rebuild of array
Still not working! Now it says 'missing disk' for Parity 2 and will not allow the array to re-start. How do I tell it that I no longer want a Parity 2 drive?
-
Persistent 'not installed' disk after disk failure and rebuild of array
I think I have sorted it out. I needed to select 'no device' for Parity 2, which freed up the drive to be allocated to Data 1. Thanks for your patience.
-
Persistent 'not installed' disk after disk failure and rebuild of array
I think this is where I went wrong the first time. I have stopped the array. The system does not seem to give me any options regarding the array. The dropdown menu for Parity 2 allows me to choose 'no device'. The dropdown menu for Disk 1 doesn't give any options. I can't see anything which allows me to add to, remove from or modify the array. How do I "Add it as an additional data disk."? Am I working with the wrong part of the UI? The next section down, Pool Devices, allows 'Add pool' but there is nothing like this under Array. Sorry to be so slow on this.
-
Persistent 'not installed' disk after disk failure and rebuild of array
Your reply re the SSDs, HHDs and parity are much appreciated. I do remember seeing a reference to that in the documentation, but it had slipped my mind. Your question about the lack of a disk to be assigned as Disk 1: what is now the second Parity disk was supposed to do that. I think I now need to stop the array, remove that second parity disk, re-format it, and then reinstall it as a new data disk. Is that correct? Should I copy the emulated disk files onto a separate drive first, or can I copy after the drive is re-formatted and reinstalled?
-
Persistent 'not installed' disk after disk failure and rebuild of array
How can I copy data from Disk 1 if it’s an emulation and it’s not mounted? Sorry, have just discovered the copy function.
-
Persistent 'not installed' disk after disk failure and rebuild of array
A question: does a basic array consist of a data disk plus a parity disk? I think I have become confused about the difference between an array and parity.
-
Persistent 'not installed' disk after disk failure and rebuild of array
I am sorry, I’m used to dealing with disks on a Linux system, but I feel somewhat out of my depth dealing with Parity disks, arrays and the like. To try to answer your questions, one of the parity disks is SSD and the other is a regular disk. The failed disk was originally ntfs, but I thought it had been reformatted. Maybe when I first set it up, this disk was just a data disk and the SSD was the parity disk. I can connect another drive and copy the data from Disk1to it. I’m not sure exactly how to do this, but I can figure it out. Then I can rebuild the array, as you suggest. Maybe I should use the hard disk for the array and use the SSD as a data disk? Your help is very much appreciated.
-
Persistent 'not installed' disk after disk failure and rebuild of array
I am puzzled by the 'ntfs' as I said in my post. I thought the parity drives had their own formatting standard? Anyway, here is the diagnostics file. thinkcentre-diagnostics-20260824-1436.zip
-
Persistent 'not installed' disk after disk failure and rebuild of array
My setup has two 2Tb parity drives. One of them failed, and I was left with a single parity drive and an emulated drive, 'Disk 1'. I installed a new replacement drive, following the advice in https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/. However, I encountered a problem where in the advice it says "If you started in Maintenance Mode, go to the Main tab and manually click Sync to start the data rebuild." I couldn't find anything at all that said 'Sync' in the Main tab under Maintenance Mode. I clicked on something which seemed similar and the parity process started. It took about 24 hours to complete. Then I rebooted, everything came up correctly, but Disk 1 is still there with its little X next to it. According to the Shares tab my data is still there (and it also shows up with the little blue box icon before Disk 1). It is listed as being held in 'Array'. Has it transferred to the two Parity disks or is it still being held in the 'emulation' in Disk 1? I also can't understand why Disk 1 shows the FS as being ntfs. I have a suspicion that all is not well and that my data is at risk. How do I make sure the data is being held properly on the two Parity disks and how do I then get rid of 'Disk 1'? There is probably an answer to this, but I have done a lot of searching and nothing promising has shown up. I may be using the wrong terminology. Anyway, any help is much appreciated.
stokeymj
Members
-
Joined
-
Last visited