I don't want to rebuild parity

[Walter Smith]

Disk 1 has failed, and with unBalance I have transfered all the data off the emulated disk. Now I don't want to rebuild parity. How do i do that?

 

[JorgeB]

5 minutes ago, Walter Smith said:

Now I don't want to rebuild parity.

If you want to remove disk1 from the array you need to do a new config and rebuild parity, or it won't be in sync.

[trurl]

And while you are doing New Config you can reassign disks, such as assigning parity2 to the parity slot, and reassigning your last data disk as disk1, or however you want.

[trurl]

Of course, another possibility, and very likely, is that there is nothing actually wrong with disk1, and you can just reassign it and rebuild.

 

Attach diagnostics to your NEXT post in this thread.

[Walter Smith]

Ok I see you need more context. I want to shrink array because i now have four WD6TB  disks fail after 2 years. I have old green wd disks no problems. But new purple and reds are a disaster. I RMA disks back and fourth few times, and I get stuck with them not working. Last time was like this:

 

I go new config but it says "Too many wrong and/or missing disks!"

diskstation-diagnostics-20220504-1542.zip

[JorgeB]

13 minutes ago, Walter Smith said:

I go new config but it says "Too many wrong and/or missing disks!"

That error can only appear if the "new config" wasn't correctly done, try again.

[trurl]

2 minutes ago, Walter Smith said:

I go new config but it says "Too many wrong and/or missing disks!"

That does not compute.

 

Reviewing your syslog, I suspect you may not know what we mean by New Config (Tools - New Config).

 

New Config makes it forget any assignments, lets you assign any disks however you want, and rebuilds parity on any disk assigned to any parity slot.

 

Since those diagnostics were without the array started, and after rebooting and other things were done trying to change disk assignments, I can't actually tell if emulated disk1 mounts, or indeed which disk was originally disk1, or if it is still attached.

 

But most of the things I see in syslog are about nvidia, and about your disk controller.

 

At this point I doubt you have an actual disk problem. Is original disk1 still attached? If so, what are the last 4 characters of its serial number?

[Walter Smith]

Thank you, we solved it. I check marked "Preserve current assignments: Pool slots." I mixed what it means pool slots with array slots. I thought it would preserve only cache pools.

[trurl]

2 minutes ago, Walter Smith said:

solved it

So are you rebuilding parity(2?) without disk1 now?

[Walter Smith]

Actually three disks, then two. First run to see shares without parity. All There. Then with parity disk in slot parity 1, not 2 . Disk 2 was empty, so now it will be backup. I will run preclear on it later, not to bottleneck rebuild. Thank you again.

[trurl]

3 minutes ago, Walter Smith said:

Disk 2 was empty, so now it will be backup. I will run preclear on it later

Your screenshot shows it 92% full, and of course, you can't preclear a disk while it's in the array.

[Walter Smith]

It isn't in the array, it is in unassigned devices (previous disk 2). It is Dev 1, and Dev 2 is faulty disk that would not rebuild parity. Both out of the array.