import pool failed, what are my options?

[Ustak]

When trying to import one of my pools, I get the following error:

Code:

[root@freenas ~]# zpool import
pool: weihan
id: 9310776408472677972
state: FAULTED
status: The pool metadata is corrupted.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported using
the '-f' flag.
see: http://illumos.org/msg/ZFS-8000-72
config:

weihan FAULTED corrupted data
gptid/3fe3f5cc-72ae-11e3-9a48-001a4d467f02 ONLINE

[root@freenas ~]# zpool import weihan
cannot import 'weihan': I/O error
Destroy and re-create the pool from
a backup source. 

Do I have any other options other than "zpool import -f weihan" and hoping for the best? I unfortunately don't have any back ups of this pool, but it's nothing critical.

 

[SweetAndLow]

Read the rules, hardware spec and freenas version if expect help.

 

[Ustak]

Sorry about that.

Motherboard: asrock c2550d4i
CPU: Intel® Quad-Core Avoton C2550
Ram: crucial 16 gb ECC CT2KIT102472BD160B
Freenas Version: FreeNAS-9.3-STABLE-201602031011
Disks: Hitachi deskstar 250GB (HDT722525DLA380) <-- problem drive
3x3TB WD Red

 

[SweetAndLow]

Did you have multiple drives fail? This error shouldn't really happen with a well maintained pool. I have a feeling you are out of luck, maybe stick around to see if someone else chimes in.

 

[Ustak]

I believe multiple drives failed in another pool on my old system, but this disk was in a pool by itself.

 

[Fuganater]

I believe multiple drives failed in another pool on my old system, but this disk was in a pool by itself.

Looks like that single disk is bad. I have to ask... why create a pool with 1 drive?

 

[Ustak]

My old system was made a long time ago, and I just used whatever disks I had lying around, and I got that 1 disk after I created my main pool, so I just added the 1 disk by itself.

 

[DrKK]

Well sir, I'm afraid it's lights out. Whatever pool that single disk vdev was attached to would now appear to be toast.

 

[Ustak]

I guess it wouldn't hurt to go for broke and try to force mount it then right? In my mind the data is already gone anyway.

 

[DrKK]

I guess...

 

[anodos]

I guess it wouldn't hurt to go for broke and try to force mount it then right? In my mind the data is already gone anyway.

Not everything is lost. You can always turn the hard drive into a snazzy clock.

 

[Mirfster]

Please take some time to familiarize yourself with FreeNas. I would highly recommend the "Slideshow explaining VDev, zpool, ZIL and L2ARC for noobs!"; which is linked in my sig.

 

[DrKK]

Not everything is lost. You can always turn the hard drive into a snazzy clock.

View attachment 10604

I wouldn't actually use a Seagate even as a chassis for a snazzy clock. I might use one to shim an out-of-square door frame, but that's about it.

Edit: I'm confusing this thread with another never-say-die thread where the guy has Seagates. Ignore me.

 

[Ustak]

Not everything is lost. You can always turn the hard drive into a snazzy clock.

Heh, I've got plenty of drives to make clocks out of since my last pool failed.

Please take some time to familiarize yourself with FreeNas. I would highly recommend the "Slideshow explaining VDev, zpool, ZIL and L2ARC for noobs!"; which is linked in my sig.

I've read it, I made that pool a long time ago when I didn't know better (I still don't). My current pool is 3x3TB WD Red in RAID-Z.

I tried force mounting the pool, no luck unfortunately. Thanks for the help everyone.

 

[danb35]

Keep in mind, there are two "force" options to 'zpool import'. -f will import the otherwise-healthy pool if it appears it was last in use on another system. -F (capital F) will attempt to roll back the last n transactions (where n is a constant whose value I don't know) to try to bring the pool to a mountable state. You can combine -F with -n to do a "dry run" of the force import--it will tell you if it could import your pool that way, but won't actually import it. That command would look like 'zpool import -F -n weihan'.