Stuck on Auto Import Volume

[Bogd]

I'm running FreeNAS 9.2.1.1 on an HP server, with an HP P800 RAID controller and a 9TB RAID volume presented to FreeNAS (yes, yes, I know, not the best design possible, but please bear with me :) )

After a series of problems with the HDDs/RAID controller, I had to detach the volume. Now I'm trying to reimport it, but FreeNAS simply gets stuck on "auto import volume", step 2.

Here's what I tried so far:

1. Auto-import volume from the GUI. I can see the volume in the dropdown box, but the process seems to hang on step 2 of 2 (I get the box with the animated blue bar, and nothing happens). Right now, it's been like that for more than 2 hours, with no result visible.
2. Import from the command line. At the end of this message, you can see the output from zpool status and zpool import. You can see the existing volume (BOX1) showing up just fine on "zpool import". However, if I try to actually import it ("zpool import BOX1"), it's the same - nothing happens for a very long time. What's worse, during this time the system stops responding to both SSH and HTTP.

Can anyone tell me what I am doing wrong? What would be the proper way to proceed in order to reimport the volume?

Thank you!

[root@freenas] ~# zpool status
pool: BOX2_C6
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Sun Oct 19 00:00:01 2014
config:

NAME STATE READ WRITE CKSUM
BOX2_C6 ONLINE 0 0 0
gptid/605969d8-b5f5-11e3-95b0-001b214dcbfb ONLINE 0 0 0

errors: No known data errors

pool: BOX2_C7
state: ONLINE
scan: scrub repaired 0 in 4h29m with 0 errors on Sun Oct 19 04:29:57 2014
config:

NAME STATE READ WRITE CKSUM
BOX2_C7 ONLINE 0 0 0
gptid/73d3d9df-b5f5-11e3-95b0-001b214dcbfb ONLINE 0 0 0

errors: No known data errors
[root@freenas] ~# zpool import
pool: BOX1
id: 17621609228464062134
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:

BOX1 ONLINE
gptid/e4d3b039-b527-11e3-9e9f-001b214dcbfb ONLINE

 

[dlavigne]

How much RAM?

 

[Bogd]

32GB RAM

 

[cyberjock]

I'd say you just found out what it's like to lose your pool because you used a hardware RAID controller with ZFS.

The system's behavior that you explained is classic signs of a corrupted pool.

 

[solarisguy]

I'd say you just found out what it's like to lose your pool because you used a hardware RAID controller with ZFS.

The system's behavior that you explained is classic signs of a corrupted pool.

@Bogd, and what does your hardware RAID controller say when you enter it during a boot up sequence?

 

[Bogd]

@solarisguy: The problems I mentioned earlier were caused by a dual HDD failure, which took the volume (a RAID6) offline. After replacing the failed HDDs, the volume is now online, and repairing.