zpool status unknown

[Wade]

May 31, 940pm.... 22 hours later..... still in the boot process trying to import tank...

any words of encouragement?

 

[SweetAndLow]

I didn't have high hopes for it to work.

 

[Wade]

anything else i can try before throwing in the towel?

 

[Robert Trevellyan]

anything else i can try before throwing in the towel?

More RAM? But I'm also pessimistic.

 

[titan_rw]

In my experience really long pool import times is usually caused by a pool with large dedupe tables that needs to be imported 'dirty', ie the server wasn't shutdown cleanly last time.

Any chance that dedupe was enabled at all on this pool?

If it was, more memory is likely the only solution.

 

[cyberjock]

Well, if you've done a large dataset delete or other things, those transactions must be completed before the import will complete. I've personally seen people have to wait more than 5 days after doing very large delete operations, so 22 hours seems fast in comparison. The amount of system RAM will *significantly* affect how fast a system will complete a delete operation (the transactions like deletions are heavy on ARC usage). Frankly, I'd leave it alone for a couple of days (if your data is worth the wait) and see what happens. As long as the disks look like they are being accessed and *something* is going on, I'd ride out the wait.

Likewise enabling dedup is a major problem, but if you enabled that and didn't read the warning in the WebGUI, you only have yourself to blame. :P

 

[Wade]

Well, if you've done a large dataset delete or other things, those transactions must be completed before the import will complete. I've personally seen people have to wait more than 5 days after doing very large delete operations, so 22 hours seems fast in comparison. The amount of system RAM will *significantly* affect how fast a system will complete a delete operation (the transactions like deletions are heavy on ARC usage). Frankly, I'd leave it alone for a couple of days (if your data is worth the wait) and see what happens. As long as the disks look like they are being accessed and *something* is going on, I'd ride out the wait.

Likewise enabling dedup is a major problem, but if you enabled that and didn't read the warning in the WebGUI, you only have yourself to blame. :p

thank you for the heads up, the longest i've let it sit has been about a day and a half. the thing is it stops during boot after importing tank, it will read 8 or 9 lines then stop, so i have no indication that *something* is going on, its still booting so theres no gui or command line, the curser is there and may be usable but even if it was usable i dont know the inputs to make it do

how can i tell the discs are being accessed? do you mean by touch?

i dont know what dedup is so im sure it hasnt been activated

 

[titan_rw]

I would create new freenas boot media and boot off that. That will get the system booted without the pool imported.

Then you can run things like gstat to see disk activity. You could then try importing the pool in the GUI, or via the command line. Either would probably be fine for testing.

Keep and eye on gstat to see if the disks are active. If the disks are continuously busy during import I'd say leave it go. It's doing something.

 

[Wade]

I would create new freenas boot media and boot off that. That will get the system booted without the pool imported.

Then you can run things like gstat to see disk activity. You could then try importing the pool in the GUI, or via the command line. Either would probably be fine for testing.

Keep and eye on gstat to see if the disks are active. If the disks are continuously busy during import I'd say leave it go. It's doing something.

thanks titan excellent idea

i made a new boot media, got me in the system with all six drives, when i ssh into the box and try zpool import tank it tells me to use -f so i try zpool import tank -f and it gives me the same error

Code:

[root@freenas] ~# zpool import tank
cannot import 'tank': pool may be in use from other system, it was last accessed by  (hostid: 0x659d91db) on Wed Jun  1 20:24:05 2016
use '-f' to import anyway
[root@freenas] ~# zpool import tank -f
cannot import 'tank': pool may be in use from other system, it was last accessed by  (hostid: 0x659d91db) on Wed Jun  1 20:24:05 2016
use '-f' to import anyway
[root@freenas] ~#

 

[Wade]

does this help any?

Code:

[root@freenas] ~# zpool import
   pool: tank
     id: 5610617844076698952
  state: DEGRADED
status: One or more devices were being resilvered.
action: The pool can be imported despite missing or damaged devices.  The
        fault tolerance of the pool may be compromised if imported.
config:

        tank                                              DEGRADED
          raidz2-0                                        DEGRADED
            gptid/7ea641e5-2398-11e4-b424-10c37b949d82    ONLINE
            gptid/7f0871b3-2398-11e4-b424-10c37b949d82    ONLINE
            replacing-2                                   DEGRADED
              5791587837835604627                         OFFLINE
              gptid/f1571c81-249b-11e6-904c-a0369f3fbb75  ONLINE
            gptid/7fcfaad8-2398-11e4-b424-10c37b949d82    ONLINE
            gptid/80883a33-2398-11e4-b424-10c37b949d82    ONLINE
            gptid/814b9861-2398-11e4-b424-10c37b949d82    ONLINE
[root@freenas] ~#

 

[Robert Trevellyan]

zpool import tank -f

The correct syntax is zpool import -f tank.

 

[Wade]

The correct syntax is zpool import -f tank.

thanks rob, i used the correct syntax this time and the gui says loading but gstat shows all the drives at 0% busy

 

[Robert Trevellyan]

gstat shows all the drives at 0% busy

:(