ZFS - RAIDZ1 Recovery (Evgeny Sam)

[Evgeny Sam]

The Command "zpool import -fFn 2918670121059000644 zh_vol_old" does not
show anything.

The failed drive is(has always been) 'ada3' - currently showing bad bloks.
The disk FreeNas sent me an alert that the drive has failed and I verified
that.

[root at juicy] ~# zpool status
no pools available
[root at juicy] ~# zpool import
   pool: zh_vol
     id: 2918670121059000644
  state: FAULTED
 status: One or more devices are missing from the system.
 action: The pool cannot be imported. Attach the missing
    devices and try again.
    The pool may be active on another system, but can be imported using
    the '-f' flag.
   see: http://illumos.org/msg/ZFS-8000-3C
 config:

    zh_vol                                          FAULTED  corrupted data
      raidz1-0                                      DEGRADED
        17624020450804741401                        UNAVAIL  cannot open
        gptid/2b70d9c0-8e40-11e3-aa1c-d43d7ed5b587  ONLINE
        gptid/5dacd737-18ac-11e6-9c25-001b7859b93e  ONLINE
[root at juicy] ~# zdb
zh_vol:
    version: 5000
    name: 'zh_vol'
    state: 0
    txg: 1491
    pool_guid: 10149654347507244742
    hostid: 1802987710
    hostname: 'juicy.zhelana.local'
    vdev_children: 2
    vdev_tree:
        type: 'root'
        id: 0
        guid: 10149654347507244742
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 5892508334691495384
            path: '/dev/ada0s2'
            whole_disk: 1
            metaslab_array: 33
            metaslab_shift: 23
            ashift: 12
            asize: 983564288
            is_log: 0
            create_txg: 4
        children[1]:
            type: 'disk'
            id: 1
            guid: 296669430778697937
            path: '/dev/ada2p2'
            whole_disk: 1
            metaslab_array: 37
            metaslab_shift: 34
            ashift: 12
            asize: 2997366816768
            is_log: 0
            create_txg: 1489
    features_for_read:
[root at juicy] ~# zdb -e

SHOWS ONLY HELP INFO

[root at juicy] ~# dmesg | grep ada
ada0 at ahcich2 bus 0 scbus0 target 0 lun 0
ada0: <Patriot Pyro SE 332ABBF0> ATA-8 SATA 3.x device
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 57241MB (117231408 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ahcich3 bus 0 scbus1 target 0 lun 0
ada1: <ST3000DM001-1ER166 CC25> ATA-9 SATA 3.x device
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6
ada2 at ahcich4 bus 0 scbus2 target 0 lun 0
ada2: <ST3000DM001-1ER166 CC25> ATA-9 SATA 3.x device
ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad8
ada3 at ahcich5 bus 0 scbus3 target 0 lun 0
ada3: <ST3000DM001-9YN166 CC4H> ATA-8 SATA 3.x device
ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada3: quirks=0x1<4K>
ada3: Previously was known as ad10
GEOM_ELI: Device ada1p1.eli created.
GEOM_ELI: Device ada2p1.eli created.


On Sat, May 28, 2016 at 5:03 PM, BlackCat <blackcatzilla at gmail.com> wrote:

> 2016-05-29 2:07 GMT+03:00 Evgeny Sam <esamorokov at gmail.com>:
> > I ran the command "zpool import -fFn 2918670121059000644 zh_vol_old"
> > amd it did not work.
> >
> > [root at juicy] ~# zpool import -fFn 2918670121059000644 zh_vol_old
> > [root at juicy] ~# zpool status
> > no pools available
> >
> Does 'zpool import' print something?
>
> >  I think it did not work, because I am running it on the clonned drives,
> > which have different GPID's, please correct me if I am wrong. I can
> switch
> > it to the original drives, if you suggest so.
> >
> No, please do not connect original drives until you get your data back.
>
> Ok, let's start info collection from beginning. Could you describe
> which exactly disk is fail (e.g. /dev/ada????)? Since I still can not
> realize this. Please describe, what happened to the disk (e.g. a lot
> of bad blocks or disk controller start to fail).
>
> Could you show output of these commands:
> zpool status
> zpool import
> zdb
> zdb -e
>
> And if your disk has bad blocks then please show or post to pastebin
> output of (where ??? is failed disk)
> dmesg | grep 'ada???'
>
> --
> BR BC
>