Hi All,

 

i have make a mistake to swap 1 of my data disk with my parity disk, i notice the mistake and stop the array immediately.

but the data drive has been corrupted as cannot be detected, but my parity disk i believe still intact.

 

is there anyway i can rebuild back my data drive using the parity drive?

i have click the new config, i have add back all the drive to the correct location (except corrupted Data disk i did not add in yet)

i start the array with parity is valid option and did not add the corrupted data disk and start array.

but all my folder in the corrupted data disk still missing.

is there anyway for me to emulate the corrupted disk?

since actually all my data still consider there, i just have to use the parity and my other data drive to rebuild back my corrupted disk.

oh ya this happen because my boot drive die, i have to start the array in new config.

which is y i added in the disk :(

very worry now, all my critical data was on that disk.

i have my party drive assign correctly now, all my data drive assign correctly also.

 

i need a solution to rebuild the corrupted data drive back from the parity and my other data drive.

 

i still in panic mode now :(

Hi,

 

If you have all but one disk and the parity is good, the array should be recoverable.

 

Best advice, leave it well alone until one of the experts drops in with some guidance or you are very likely to lose some data.

It can take a day or so to get support depending on time zones etc.

Good luck. 

1 hour ago, Decto said:

leave it well alone

Might even be a good idea to shutdown until further advice arrives.

 

I have some ideas but would rather wait on @JorgeB

 

1 hour ago, trurl said:

Might even be a good idea to shutdown until further advice arrives.

 

I have some ideas but would rather wait on @JorgeB

the server is now up but array not started. so all HDD is 'not in use' per say

2 hours ago, Decto said:

Hi,

 

If you have all but one disk and the parity is good, the array should be recoverable.

 

Best advice, leave it well alone until one of the experts drops in with some guidance or you are very likely to lose some data.

It can take a day or so to get support depending on time zones etc.

Good luck. 

yea something like that, if can recover 95% i will be happy already.

You can try the invalid slot command, but since it looks like you started the array twice with a different config parity won't be 100% in sync, so some corruption is expected, if you're using xfs it should be recoverable with small to none data loss, before posting the instructions I need to know what Unraid release you're using, also confirm that you only have one parity disk and the number of the disk you want to rebuild.

6 hours ago, JorgeB said:

You can try the invalid slot command, but since it looks like you started the array twice with a different config parity won't be 100% in sync, so some corruption is expected, if you're using xfs it should be recoverable with small to none data loss, before posting the instructions I need to know what Unraid release you're using, also confirm that you only have one parity disk and the number of the disk you want to rebuild.

yes im using default xfs,

using latest stable 6.8.3 version.

and is single parity array, with 6 ( 5 ok + 1 corrupted drive)

and only 1 data drive needed to be rebuild.

 

this should be the correct order of the HDD, the corrupted drive should be in slot 1 which i have not assign in yet.

 

do let me know the step by step that i need to bring up the corrupted drive.

Edited September 14, 20205 yr by Ong Hui Hoong

Follow the instructions below carefully and ask if there's any doubt.

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, like old disk1
-Important - After checking the assignments leave the browser on that page, the "Main" page.

-Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters):

mdcmd set invalidslot 1 29

-Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk1 will start rebuilding, disk should mount immediately (probably not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

5 minutes ago, JorgeB said:

Follow the instructions below carefully and ask if there's any doubt.

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, like old disk1
-Important - After checking the assignments leave the browser on that page, the "Main" page.

-Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters):

mdcmd set invalidslot 1 29

-Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk1 will start rebuilding, disk should mount immediately (probably not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

understand very clearly on the instruction, i will do it now, wish me luck #FingerCross ...

9 minutes ago, JorgeB said:

Follow the instructions below carefully and ask if there's any doubt.

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, like old disk1
-Important - After checking the assignments leave the browser on that page, the "Main" page.

-Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters):

mdcmd set invalidslot 1 29

-Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk1 will start rebuilding, disk should mount immediately (probably not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

anyway, before i start, 1 question, can i start the array without the disk1?

can i emulate the disk1 to confirm the data is there? then 2nd round only i add in the corrupted disk1 for rebuild?

2 minutes ago, Ong Hui Hoong said:

anyway, before i start, 1 question, can i start the array without the disk1?

No, but you can use a spare disk if available, same size or larger.

2 minutes ago, JorgeB said:

No, but you can use a spare disk if available, same size or larger.

ah, too bad then, let me follow ur instruction and start the array now ...

i started the array follow the instruction, but my folder still missing, is that normal?

Like mentioned disk1 will likely be unmountable because you mounted the array without all devices, you can cancel the rebuild and run xfs_repair to see if it's fixable, if yes then start rebuilding again:

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

 

1 minute ago, JorgeB said:

Like mentioned disk1 will likely be unmountable because you mounted the array without all devices, you can cancel the rebuild and run xfs_repair to see if it's fixable, if yes then start rebuilding again:

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

 

should i stop now?

 

i start to panic already :(

 

You can do it now, since not much point rebuilding if the filesystem can't be fixed, to use the GUI check you need to set the filesystem on that disk to xfs, you can do that by clicking on it.

4 minutes ago, JorgeB said:

You can do it now, since not much point rebuilding if the filesystem can't be fixed, to use the GUI check you need to set the filesystem on that disk to xfs, you can do that by clicking on it.

i have stop the array and change the files system to sfx. but it still show as unmounted, should i follow the xfs_repair repair 1st?

 

1 minute ago, Ong Hui Hoong said:

i have stop the array and change the files system to sfx. but it still show as unmounted

Yes, that's expected, you have to run xfs_repair, using the GUI or the console.

2 minutes ago, JorgeB said:

Yes, that's expected, you have to run xfs_repair, using the GUI or the console.

ok i will do the repair now, i will update again.

8 minutes ago, Ong Hui Hoong said:

ok i will do the repair now, i will update again.

using GUI,

i have run the check with -n, then without any option. and now running with -L

2 minutes ago, Ong Hui Hoong said:

 

using GUI,

i have run the check with -n, then without any option. and now running with -L

afrer with -L, still same, and there is some read write on the parity, did i screw up? :(

 

 

 

or should i just format the disk?

 

Don't format, post the output of xfs_repair -vL

7 minutes ago, JorgeB said:

Don't format, post the output of xfs_repair -vL

should i do it with the parity disk in? it look like writing some data in to parity :(