Help with failed disk and web UI down

[dtemp]

Just got the "Critical Alerts" email. This isn't my first drive replacement (I originally had 6 mis-matched old disks that I replaced one-by-one with 3TB Reds as they failed), but things are a bit different this time. When I go to log in via the web, I get "ERR_CONNECTION_REFUSED" from Chrome. I get a error from Safari as well.

I log in via terminal, run "zpool status", and see the failed disk ("too many errors"). Given this is a degraded system, I want to use soft hands here and not just restart the OS via terminal. Any tips for getting the web UI back up?

I'm pretty sure I have 9.2.1.9 but I'm not certain; how would I check in terminal? All of the other specs in my signature I'm sure of.

 

[SweetAndLow]

'uname -a' should give you a version number.

 

[dtemp]

result of uname -a:

FreeBSD FreeNAS.local 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

This looks like the kernel info and not the FreeNAS distro version.

 

[DifferentStrokes]

Is the pool that is degraded the boot device or a data pool?

 

[dtemp]

Is the pool that is degraded the boot device or a data pool?

The pool has faulted. I'd like to hope the boot device didn't.

Code:

[root@FreeNAS] ~# zpool status
  pool: MyPool
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
    Sufficient replicas exist for the pool to continue functioning in a
    degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
    repaired.
  scan: scrub repaired 0 in 5h9m with 0 errors on Wed Apr 15 09:09:13 2015
config:

    NAME                                            STATE     READ WRITE CKSUM
    MyPool                                        DEGRADED     0     0     0
      raidz2-0                                      DEGRADED     0     0     0
        gptid/1f0e92f0-1eb1-11e4-88f8-00505609949f  ONLINE       0     0     0
        gptid/9e3f2257-2ff3-11e4-b409-00505609949f  FAULTED      1   180     0  too many errors
        gptid/720cc782-ecb7-11e3-9ba2-00505609949f  ONLINE       0     0     0
        gptid/93769577-e6b7-11e3-892a-00505609949f  ONLINE       0     0     0
        gptid/f07b9f42-235c-11e4-baf4-00505609949f  ONLINE       0     0     0
        gptid/fc6d5fdc-d8c3-11e3-b29c-00505609949f  ONLINE       0     0     0

 

[gpsguy]

For those of you who can't see the OP's signature, he's running it virtualized under ESXi 5.5u1.

ESXi 5.5U1, FreeNAS 9.2.1.9, SM X10SL7-F, E3-1230v3, 4x 8GB Samsung ECC, Intel DC S3500 120GB 2.5", 6x WD-Red 3TB in RAIDZ2, Enermax ERX430AWT, FD Define Mini, UPS. LSI IT flashed & VT-d'ed, 12GB RAM (reserved), 2x vCPUs.

 

[dtemp]

For those of you who can't see the OP's signature, he's running it virtualized under ESXi 5.5u1.

ESXi 5.5U1, FreeNAS 9.2.1.9, SM X10SL7-F, E3-1230v3, 4x 8GB Samsung ECC, Intel DC S3500 120GB 2.5", 6x WD-Red 3TB in RAIDZ2, Enermax ERX430AWT, FD Define Mini, UPS. LSI IT flashed & VT-d'ed, 12GB RAM (reserved), 2x vCPUs.

Yep that's true, the right way too, using VT-D for the controller.

Anyone have a suggestion on restarting the web UI?

 

[cyberjock]

The pool has faulted. I'd like to hope the boot device didn't.

One device faulted, NOT the pool.

 

[dtemp]

One device faulted, NOT the pool.

Yep, and hallelujah at that.