zpool import unavail cannot open

Status
Not open for further replies.

Tristan

Cadet
Joined
Jan 29, 2015
Messages
1
Hi all,

I've had a crash on my NAS and since then one of my drives will not import. They are all single drive ZFS pools at this point so structurally more simple than any RAID configs.

Attempting an import from the command line returns UNAVAIL cannot open but gpart shows the drive and its partitions appear intact. zdb -l /dev/ada0 shows label 0 cannot be unpacked but the other three are fine.

Is there any hope in resolving or is this looking a little bleak ?

Output from zpool import, gpart and zdb -l follow.

Tristan.

------------
pool: Storage

id: 1260348755058239175

state: UNAVAIL

status: One or more devices are missing from the system.

action: The pool cannot be imported. Attach the missing

devices and try again.

see: http://illumos.org/msg/ZFS-8000-3C

config:


Storage UNAVAIL insufficient replicas

13158554300718352359 UNAVAIL cannot open
----------------------

gpart list

Geom name: ada0

modified: false

state: OK

fwheads: 16

fwsectors: 63

last: 7814037134

first: 34

entries: 128

scheme: GPT

Providers:

1. Name: ada0p1

Mediasize: 2147483648 (2.0G)

Sectorsize: 512

Stripesize: 4096

Stripeoffset: 0

Mode: r1w1e1

rawuuid: 696f0415-7b5d-11e4-bdbc-b499bab536ea

rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b

label: (null)

length: 2147483648

offset: 65536

type: freebsd-swap

index: 1

end: 4194431

start: 128

2. Name: ada0p2

Mediasize: 3998639460352 (3.7T)

Sectorsize: 512

Stripesize: 4096

Stripeoffset: 0

Mode: r0w0e0

rawuuid: 698342f7-7b5d-11e4-bdbc-b499bab536ea

rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b

label: (null)

length: 3998639460352

offset: 2147549184

type: freebsd-zfs

index: 2

end: 7814037127

start: 4194432

Consumers:

1. Name: ada0

Mediasize: 4000787030016 (3.7T)

Sectorsize: 512

Stripesize: 4096

Stripeoffset: 0

Mode: r1w1e2
---------------
zdb -l /dev/ada0

--------------------------------------------

LABEL 0

--------------------------------------------

failed to unpack label 0

--------------------------------------------

LABEL 1

--------------------------------------------

version: 5000

name: 'Storage'

state: 0

txg: 2785329

pool_guid: 1260348755058239175

hostid: 4266313884

hostname: 'freenas.graham.uk.com'

top_guid: 13158554300718352359

guid: 13158554300718352359

vdev_children: 1

vdev_tree:

type: 'disk'

id: 0

guid: 13158554300718352359

path: '/dev/ada0'

whole_disk: 1

metaslab_array: 34

metaslab_shift: 35

ashift: 12

asize: 4000782221312

is_log: 0

DTL: 85

create_txg: 4

features_for_read:

com.delphix:hole_birth

--------------------------------------------

LABEL 2

--------------------------------------------

version: 5000

name: 'Storage'

state: 0

txg: 2785329

pool_guid: 1260348755058239175

hostid: 4266313884

hostname: 'freenas.graham.uk.com'

top_guid: 13158554300718352359

guid: 13158554300718352359

vdev_children: 1

vdev_tree:

type: 'disk'

id: 0

guid: 13158554300718352359

path: '/dev/ada0'

whole_disk: 1

metaslab_array: 34

metaslab_shift: 35

ashift: 12

asize: 4000782221312

is_log: 0

DTL: 85

create_txg: 4

features_for_read:

com.delphix:hole_birth

--------------------------------------------

LABEL 3

--------------------------------------------

version: 5000

name: 'Storage'

state: 0

txg: 2785329

pool_guid: 1260348755058239175

hostid: 4266313884

hostname: 'freenas.graham.uk.com'

top_guid: 13158554300718352359

guid: 13158554300718352359

vdev_children: 1

vdev_tree:

type: 'disk'

id: 0

guid: 13158554300718352359

path: '/dev/ada0'

whole_disk: 1

metaslab_array: 34

metaslab_shift: 35

ashift: 12

asize: 4000782221312

is_log: 0

DTL: 85

create_txg: 4

features_for_read:

com.delphix:hole_birth
 
D

dlavigne

Guest
While it's hard to tell from the output (these need to be pasted into code tags!) it looks like you have a stripe of 4 drives. Since there is no redundancy, a failed drive == no more data.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Looks like you are down for the count. :(

This is why striping is so incredibly dangerous. I hope you have backups.
 
Status
Not open for further replies.
Top