Hi everyone,

I've successfully completed my first parity-check but after stopping the array and rebooting one of my array drives appeared as unmountable because of a missing file system.

I've attached my diagnostics, maybe someone can help me with this issue. 

 

thanks in advance  

tower-diagnostics-20190815-2028.zip

system/vars in diagnostics shows all disks mounted. All user shares show data only on cache or disk1. I think syslog is indicating disk2 hadn't been formatted or was just formatted. Is this a new array?

 

Post a complete screenshot of Main - Array Devices.

49 minutes ago, trurl said:

system/vars in diagnostics shows all disks mounted. All user shares show data only on cache or disk1. I think syslog is indicating disk2 hadn't been formatted or was just formatted. Is this a new array?

 

Post a complete screenshot of Main - Array Devices.

At first thank you for your answer  

 

You're right this is a new array, but I've included the disk in the array before I first started it up yesterday and the first parity-check/ build of the array completed without any issues. 

I've attached the screen you've been asking for.

 

Thanks

Edited August 15, 20196 yr by peezy45

The screenshot agrees that all disks are mounted. Don't know what you had before but it looks normal to me. Do you have any reason to think there was data on disks 2,3?

1 hour ago, peezy45 said:

You're right this is a new array, but I've included the disk in the array before I first started it up yesterday and the first parity-check/ build of the array completed without any issues. 

Did you by any chance do a new config and add the extra array drives and check the box saying parity was already valid?

2 hours ago, jonathanm said:

Did you by any chance do a new config and add the extra array drives and check the box saying parity was already valid?

Either that or parity had never been built to begin with judging by the large number of sync errors.

 

Is there anything else you can tell us about how you got to this point? It really seems like you haven't told us everything you did.

20 hours ago, trurl said:

Either that or parity had never been built to begin with judging by the large number of sync errors.

 

Is there anything else you can tell us about how you got to this point? It really seems like you haven't told us everything you did.

Hey, 

 

at first thanks for your advice.

I was able to resolve the issue by simply running another parity-check. I rebooted and everything is just fine.

I don't know why it didn't work at the first run but now it does.

I think you're right , the parity has never been build correctly within the first run. 

Anyway thank you very much !! 

 

greetins