[SOLVED!} - zpool import: cannot import 'x': one or more devices is currently unavailable

[Martin Bauer]

Hello All, and thanks in advance for any help you might be able to give:


Hardware:

Unfortunately I don't have all the details right now -
RAM = 5GB
Zpool made from 3 drives @750GB ( showing to be on a 'blacklist' below ? )
For the most part I did use what was available ( INTEL Mobo & CPU ? I5 ? ) but I will need to go onsite to get the detailed info -
\ I know this all sounds 'hokey' but it's been running pretty well after I set it up in a crunch last year
​

Background:

Running for over a year with nary a hiccup
Cause of Failure: Power Outage / Corrupt USB /
Looks like the '3 drive' Zpool lost 1 drive awhile back and the email never got handled - oh my.
Last week I built a new USB boot drive with the latest release and got her back up
AutoImport worked well and the data was accessible as in the past - despite the missing HDD
I was in proccess of ordering new parts and copied 1/4 of the data off the zPool
This past monday - USB key went on the fritz again, upon rebuild I can no longer auto-import the pool
​

Status:

I'm looking to recover the data / move it to another unit for backup / then fix ALL the issues ( memcheck / different drives ) then rock on with Freenas - I love it
​

Code:

[root@CAVO-FN001] ~# uname -a
FreeBSD CAVO-FN001.CAVO-NET 9.2-RELEASE-p12 FreeBSD 9.2-RELEASE-p12 #0 r262572+b043649: Sun Sep 28 23:03:31 PDT 2014     root@build3.ixsystems.com:/tank/home/jkh/build/921/freenas/os-base/amd64/fusion/jkh/921/freenas/FreeBSD/src/sys/FREENAS.amd64  amd64

Code:

[root@CAVO-FN001] ~# camcontrol devlist
<ST3750330AS SD15>                 at scbus5 target 0 lun 0 (pass0,ada0)
<ST3750330AS SD15>                 at scbus6 target 0 lun 0 (pass1,ada1)
<SanDisk Cruzer 8.01>              at scbus9 target 0 lun 0 (pass2,da0)

Code:

[root@CAVO-FN001] ~# gpart show
=>        34  1465149101  ada0  GPT  (698G)
          34          94        - free -  (47k)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1460954703     2  freebsd-zfs  (696G)

=>        34  1465149101  ada1  GPT  (698G)
          34          94        - free -  (47k)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1460954703     2  freebsd-zfs  (696G)

=>      63  15731648  da0  MBR  (7.5G)
        63   1930257    1  freebsd  [active]  (942M)
   1930320        63       - free -  (31k)
   1930383   1930257    2  freebsd  (942M)
   3860640      3024    3  freebsd  (1.5M)
   3863664     41328    4  freebsd  (20M)
   3904992  11826719       - free -  (5.7G)

=>      0  1930257  da0s1  BSD  (942M)
        0       16         - free -  (8.0k)
       16  1930241      1  !0  (942M)

Code:

[root@CAVO-FN001] ~# glabel status
                                      Name  Status  Components
gptid/dcdec164-505f-11e3-a2fd-0019d1050453     N/A  ada0p2
gptid/ded485e4-505f-11e3-a2fd-0019d1050453     N/A  ada1p2
                             ufs/FreeNASs3     N/A  da0s3
                             ufs/FreeNASs4     N/A  da0s4
                            ufs/FreeNASs1a     N/A  da0s1a

dmesg output
smart - ada0
smart - ada1

 

[rs225]

I assume this was a RAIDZ1 that lost the 3rd member a while ago?

My recommendation is ddrescue to be run on both drives to make new images, possibly using another computer.

Once that is done, use the new copies to attempt to regain access to your pool.

Wildcard: Firmware version SD15 has a major bug that disables access to the drive after enough power cycles. Once you are out of this jam, either toss those drives or firmware update them. If either one of them seems to be totally failed, Seagate might still be offering recovery for them because of the SD15 problem.

 

[Ericloewe]

5GB of RAM is 3GB less than the minimum requirement.

 

[Martin Bauer]

5GB of RAM is 3GB less than the minimum requirement.

Yes you are indeed correct Ericloewe - I cheated on the RAM - I did the install / setup a year ago and never looked back - Now that she's down I'm going to correct that !

 

[Martin Bauer]

I assume this was a RAIDZ1 that lost the 3rd member a while ago?

My recommendation is ddrescue to be run on both drives to make new images, possibly using another computer.

Once that is done, use the new copies to attempt to regain access to your pool.

Wildcard: Firmware version SD15 has a major bug that disables access to the drive after enough power cycles. Once you are out of this jam, either toss those drives or firmware update them. If either one of them seems to be totally failed, Seagate might still be offering recovery for them because of the SD15 problem.

rs225 - you are also correct - I saw that info awhile after the initial setup - everything was up and the SMART data seems to indicate it 'might' be an issue -
Since all was well, I just 'kept on trucking' - doh ! I am also going to correct that now as well on the rebuild / retrofit

thanks !

 

[Martin Bauer]

UPDATE : SOLVED !!
Well I lucked out people !!!!
After putting the FN server on the bench and letting it sit awhile I got prepared to run the ddrescue and tough it out through recovery -
I plugged in a 2T spare drive and booted her up -
Just for fun I tried the auto-import again and guess what !!!! IT WORKED !
Scramble Scramble Scramble - Copy - offload - etc...

PROBLEM SOLVED !!

Thanks to all who helped ! much obliged - now it's time to rebuild and reinforce -

I am going to post a couple of other questions now that I have tried to use ddrescue - If you have time rs225 I could use a little hand holding :)

please look for the new posts presently -