lost array, started with metadata issues #18642
Anaxagoras-bc
started this conversation in
General
Replies: 1 comment
|
IIRC one of the reason to suspend the pool can be a write error. Clearing the errors is not a way out. I don't remember if it tries to replay the errored write, but if not, it is a request for troubles. You may try to import the pool as read-only at some older TXG, hoping it might be some more complete, but at that point it already becomes a data recovery project. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I moved my DAS from a proxmox host with an lsi 9200 HBA to a truenas host with a dell 355e HBA. The array was clean when unplugged from proxmox. upon plugging it into truenas it had a bunch of checksum errors, i assumed due to lose cable, so i shut everything down and reseated everything, the pool was suspended, so i ran a zpool clear on it to reset the error counters. after running the clear i ran a zpool scrub just to make sure nothing was corrupt.
this is the first error i saw
while trying to figure out what the error was the system locked up, so i rebooted it. I can no longer import the pool. All the disks are present an online.
zpool import shows the array and all 12 drives are online.
when trying to import the pool i either get
"cannot import 'Archive': insufficient replicas Destroy and re-create the pool from a backup source."
OR
"cannot import 'Archive': one or more devices is currently unavailable"
Unfortunatly i don't have backups of about 15% of the data on the pool that is irreplaceable.
All reactions