melloa
Wizard
- Joined
- May 22, 2016
- Messages
- 1,749
I've a friend that one of the HDs on the pool started failing, so brought it off line and replaced with a new WD Red. After the pool resilvered I've noticed errors saying that the GPT table was corrupt or invalid..
Oct 29 13:06:28 bennas GEOM: ada0: the primary GPT table is corrupt or invalid.
Oct 29 13:06:28 bennas GEOM: ada0: using the secondary instead -- recovery strongly advised.
Oct 29 13:06:29 bennas notifier: dd: /dev/ada0: short write on character device
Oct 29 13:06:29 bennas notifier: dd: /dev/ada0: end of device
After little research I think that's because the HD had a previous linux partition in it (Please let me know if that's not the case).
So ... planning of taking that HD off line, doing a gpart delete to blank it, re-add to the pool, and let it resilver. 'course I did a back-up earlier.
Is this Ok or it is so bad that I should be @#$%&? Any other suggestions?
Oct 29 13:06:28 bennas GEOM: ada0: the primary GPT table is corrupt or invalid.
Oct 29 13:06:28 bennas GEOM: ada0: using the secondary instead -- recovery strongly advised.
Oct 29 13:06:29 bennas notifier: dd: /dev/ada0: short write on character device
Oct 29 13:06:29 bennas notifier: dd: /dev/ada0: end of device
After little research I think that's because the HD had a previous linux partition in it (Please let me know if that's not the case).
So ... planning of taking that HD off line, doing a gpart delete to blank it, re-add to the pool, and let it resilver. 'course I did a back-up earlier.
Is this Ok or it is so bad that I should be @#$%&? Any other suggestions?
