Unraid version: 6.12.14

Have a drive that threw a bad sector, but needed to upgrade Parity drive as it is small and new drives I have are all larger. Followed the manual https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/ exactly. It would not start parity swap. here are the syslog errors.

error: pswap_dsbl_copy, 6786: No such file or directory (2): open: /dev/sdd1

Right now I'm stuck with it unable to start at all, a data disk with bad sector, and 3 drives that i cant add till parity is upgrades. Not sure if drive with bad sector will survive rebuild. Array wont start as too many disks wrong

Rysz found another person with issue, not sure if this is an OS issue, or hardware. but if it is no longer an option, might want to note in the manual.

 

Edited December 15, 20241 yr by ZarZ
speeling

Please post the diagnostics.
 

I'll try to get them, wont help me at this point sadly. If i can save other people from losing data, that will be good, but i am looking at options to never be in this spot again.

Since I needed to get access to my data, the discord helpers recommended to just do new config, then regular parity sync on new drive, and hope the failing drive stays working until parity is done, which it is currently trying to finish but going VERY slowly. 

23 hours ago, ZarZ said:

No such file or directory (2): open: /dev/sdd1

Would need the diags to confirm, but this error suggests parity was not added as a new drive, but added with the "parity is already valid" option and then synced, doing this won't create the partition for parity, and hence fail during parity swap.

I followed the above instructions and did nothing otherwise untill after the issue. then I has left trying to find out how to possibly save my data. But when i get the diagnostics i will put them up. Sadly i  have not got the backup server going yet as both chassis are 45 and 60bay and unraid array does not support them. and don't want to build it out with unraid only to have to find a solution for support of all bays

1 hour ago, ZarZ said:

I followed the above instructions and did nothing otherwise untill after the issue.

If it's what I think, the problem was created when the array (or parity) was first added, not now.

ok that infact is what i did, I had all new disks, and clicked parity as valid when first building the server a year ago, as there was no data. 

Is there some way to fix this without starting fresh?

Edited December 16, 20241 yr by ZarZ

12 minutes ago, ZarZ said:

Is there some way to fix this without starting fresh?

You can try manually creating a partition, but please note that it's something I've never tested before, though it should work and keep parity valid:

 

sgdisk -o -a 8 -n 1:32K:0 /dev/sdX

 

Then you would need to retry the parity swap.

Odd question, since i did new config, added new parity, did NOT check parity is valid, will the parity it is currently building fix this issue?

29 minutes ago, ZarZ said:

will the parity it is currently building fix this issue?

That will also work, and long as the array is healthy for parity to be rebuilt correctly

Nice, ya the bad drive is still hanging in there, hasnt gave out yet, so just needs like 12 more hours to finish and hopefully my next parity swap will work

On 12/16/2024 at 1:09 PM, JorgeB said:

If it's what I think, the problem was created when the array (or parity) was first added, not now.

 

On 12/16/2024 at 1:32 PM, JorgeB said:

You can try manually creating a partition, but please note that it's something I've never tested before, though it should work and keep parity valid:

 

sgdisk -o -a 8 -n 1:32K:0 /dev/sdX

 

Then you would need to retry the parity swap.

Folow up, Last Time I tried Parity Swap as we discussed it didnt work, and you were 100%. I once again am upgrading disk sizes from 24TB to 28TB, and because I did a fresh build of parity it made that partition that i accidentally skipped on initial build. It is now properly copying Parity for swap. Thanks for the help and wanted to confirm your suspicions were correct.

Lesson for me and anyone else, even if starting with all fresh disks, do NOT shortcut and click "Parity is valid", let it build so there is a partition created.

Edited January 22, 20251 yr by ZarZ

On 12/16/2024 at 1:18 PM, ZarZ said:

I had all new disks, and clicked parity as valid when first building the server a year ago, as there was no data.

Unless all the disks had been precleared, parity was not valid anyway even if they had no "data".

 

15 minutes ago, ZarZ said:

even if starting with all fresh disks, do NOT shortcut and click "Parity is valid"

 

50 minutes ago, trurl said:

Unless all the disks had been precleared, parity was not valid anyway even if they had no "data".

 

 

Sadly when i first set it up I was dumb and assumed if all is zeroed, all is valid. Live and learn. Glad it was a me dumb moment and not actual unraid problem