Gristev
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Gristev
-
-
I should have sorted out that issue of the unassigned drive earlier.. Didn't think it would a problem. Learned this the hard way 😉
Thanks again for helping out.
Let's say I could do some kind of recovery to a new drive (don't think it will work). Should I then assign the new drive to Disk 1?
-
Aii, that doesnt look to good then.. thanks for helping out! It's not that disk I'm worried about because it was empty. It's the failed disk 1.
Maybe another approach could help me out to recover disk 1?
-
On 4/3/2022 at 2:27 PM, itimpi said:
That screenshot shows 2 drives missing or failed but only single parity so Unraid cannot do the parity swap.
Disk 3 is unassigned, not missing, right? I accidentally assigned a drive but unassigned it, so it hasn't failed..
Or am I fried because of this? Hope there is a solution without data loss..
-
2 hours ago, JorgeB said:
Please post the diagnostics and a screenshot of the main GUI page.
Not sure what is needed in diagnostics, so posted the entire zip and a screenhot of the main GUI page. Disk 1 is the failed drive. The unassigned drives are a new data and parity drive that I wish to use.
-
1 hour ago, itimpi said:
Not clear exactly what you have done. Since you have a failed drive then you effectively start at step 9.
Yes, I did that. Unassign the old parity drive, assign the new parity drive as the parity drive and assign the old parity drive as new data drive.
The manual says there should be a "Copy button, with a statement indicating "Copy will copy the parity information to the new parity disk"."
But there is no "Copy" button..
-
Recently one of my data drives has failed. Since then I cannot start the array because of error: Too many wrong and/or missing disks!
I have a bigger replacement drive available, even bigger than parity drive. So I want to do the parity swap procedure. https://wiki.unraid.net/The_parity_swap_procedure
In step 3 of the procedure: Start the array (put a check in the Yes I want to do this checkbox if it appears (older versions: Yes, I'm sure))
Yes, you need to do this. Your data drive should be showing as Not installed.
But I cannot start my array as mentioned before. So the failed drive is showing as Missing, not as Not Installed.
If I skip step 3 in de procedure, there's a problem with step 13:
Go to the Main -> Array Operation section
You should now have a Copy button, with a statement indicating "Copy will copy the parity information to the new parity disk".
There is no Copy button.
I'm a bit lost. Hope someone can put me in the right direction.
-
Thanks for all the advice. Midnight commander works like a charm. Copying data now on the Unraid server. I have multiple disks to copy, so this is perfect. Will check out Krusader on a later moment.
-
I'm a total noob to Unraid. Just started with a clean setup with 3x 10TB disks. Everything is fine, building an arry with 1x 10TB parity disk and 2x array disks. But I want to copy files from several NTFS disks to my array, but don't seem to find a way to copy these files. I installed the Unassigned Devices plugin, but don't see a way how to copy the files to my arrary. I have several disks NTFS disks with data which I want to copy to the array.
Cannot start array or do parity swap after failed data drive
in General Support
Posted
Thanks again. You were very helpful!
After tingling around for hours I managed to get Drive 1 to work again, I had to connect the disk upside down and with some duck tape to connect the power connector. It's not stupid if it works right? 😏 (The entire plastic casing around the power connector is gone because I dropped it long time ago while connected.. Not recommended)
I started a new config as you advised, with the 'old' data drive connected and the bigger (18TB) as parity drive. After about 32 hours it completed!
It was a hard lesson to learn not to have unnassigned drives in my setup and to solve this in the setup before other problems arise. I never thought this would be a problem with only 1 parity drive. Now I now better.