Pool is in a DEGRADED state (GPT Table corrupt)

mainstream

Dabbler
Joined
Jan 7, 2022
Messages
18
Hello everyone,

I have a question regarding my drives. A couple days ago my PSU short-circuited, after replacement my "HDD" pool was degraded. I did a couple scrubs and cleared the errors.

The drives are back online without errors, also the S.M.A.R.T. test (long) are SUCCESS, but when i run fdisk -l:
1692343634962.png


How can i fix this gpt table?

Best regards
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
There are a few ways to address it.

If that disk is in a pool with sufficient redundancy, you can offline the disk, wipe it and replace it with itself.

If it's the only disk in the pool, then you may need to copy over the partition table from another similar disk or recreate the table in-place... I advise looking up the detailed steps as that can go badly wrong if you don't do it right.
 

mainstream

Dabbler
Joined
Jan 7, 2022
Messages
18
It's has redundancy (raidz2). So you mean to disconnect it, hook it up to another computer and completely wipe it and resilver it?
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
If it's the only disk in the pool, then you may need to copy over the partition table from another similar disk or recreate the table in-place... I advise looking up the detailed steps as that can go badly wrong if you don't do it right.
FreeBSD's gpart has got an easy to use recover command to fix corrupt GPT tables. Isn't there an equivalent on Debian?
 

mainstream

Dabbler
Joined
Jan 7, 2022
Messages
18
I guess gdisk?

1692349287937.png


Strange that it mentions a valid GPT, while fdisk outputs an error.

Edit: Ah, i see that the main GPT table is valid, but the backup GPT table is corrupt. Recovery (R) would try to recover from the backup.
 
Last edited:
Top