parity rebuild, no files

[andribolla]

 

Drive 3 failed. When I finished rebuilding, all the files were missing on the disk

[Squid]

By failed what do you mean exactly

And please list the steps you followed to rebuild the drive

Sent from my LG-D852 using Tapatalk

[trurl]

Tools - Diagnostics. Post complete zip. The speed probably means there are a lot of errors in syslog.

 

Did you rebuild to the same drive or did you replace it? Most likely a connection issue with the new drive or you knocked the connection of another drive when you did the replacement.

 

How did you decide what to do? "Failed" has many possible meanings as Squid noted. Connection issues are much more common that actual disk failures.

[andribolla]

I was having trouble connecting to my array. So I restarted. When it was restarted, disk 3 was not formatted. So I tried to rebuild with the same disk

vulcan-diagnostics-20170806-1219.zip

[Squid]

4 minutes ago, andribolla said:

When it was restarted, disk 3 was not formatted

Did you hit the "format" button that appeared at anytime?

[andribolla]

yes, i probably hit the format button be for i started to rebuild  

[Squid]

That's the problem.

 

If a disk comes up as unmountable, it has some corruption on it (probably as @trurl said due to cabling issue, etc)

 

By hitting format, you've wiped the contents of the drive (format in unRaid is the exact same as any other OS).  If at the time the drive was enabled, then you've formatted the physical drive (and updated parity info to reflect this).  If at the time the drive was disabled, you've formatted the emulated drive - Subsequently rebuilding onto the same drive has then rebuilt the drive from the parity information - So it's now wiped clean.

 

Unfortunately right now, because you've done one of the two above scenarios, and rebuilt onto the existing drive, basically you've lost the file(s) that were present on the drive.

 

[andribolla]

Okay.

Thanks for the quick response