Volume degraded but no disk failure

[Coronel]

After a power failure my volume got degraded. Everything is working as normal (I can access the volume through explorer and open files), but when i view de volumes it says that it is degraded, but when i look at the disks, no errors or warning can be seen. Is there a way to recheck the volume to see if is really degraded or can i force freenas to get the volume undegraded. Most similar cases, people do have a faulty disk, but i can't find one without faulty disk.

Some info
ZFS 6-disk raidz
Freenas on separate usb-device
FreeBSD 8.2-RELEASE-p1

 

[paleoN]

What VERSION of FreeNAS are you running?

From an SSH session, as root, what is the output of:

Code:

zpool status -v

camcontrol devlist

gpart show

Do me a favor and throw [code] [/code] tags around the output. It will keep the formatting.

 

[Coronel]

Oke, i added the version to my original post. But for some reason i cannot login with SSH, but i already had connected a monitor and keyboard. So i immediately saw that ada3 was unavailable and on the location where gpt/ada3 should have stood, there was a long number (16384637795044098828). And it is saying unavailble. So clearly this disk is het problem.

In the camcontrol-list i'm missing one device, but the failing disk is on the list. I can see 5 times my WD20EARS (ada0 till ada4), also a small back-up drive ST9120823AS (ada5) and my USB-device at da0. Mayby the 6th disk is missing because it is used for the checksum.

So is it normal that the gui isn't showing any informaton about a faulty disk? And what is the easiest solution the find the disk. Because there al the same, and there are no number on the mainboard.

 

[paleoN]

Oke, i added the version to my original post.

Wrong version. That's the FreeBSD version not the FreeNAS one. See this image where it says Build:

But for some reason i cannot login with SSH, but i already had connected a monitor and keyboard.

I'd feel more comfortable with you pasting the output from SSH. You may not have enabled it is all. Here's the documentation. Working from SSH is easiest, but you could take pictures of the screen as well I guess.

So i immediately saw that ada3 was unavailable and on the location where gpt/ada3 should have stood, there was a long number (16384637795044098828). And it is saying unavailble. So clearly this disk is het problem.

In the camcontrol-list i'm missing one device, but the failing disk is on the list. I can see 5 times my WD20EARS (ada0 till ada4), also a small back-up drive ST9120823AS (ada5) and my USB-device at da0. Mayby the 6th disk is missing because it is used for the checksum.

Or ada4, ada5 & ada6 became ada3, ada4 & ada5 when the original ada3 died or whatever.

So is it normal that the gui isn't showing any informaton about a faulty disk?

Sounds like a possible bug.

And what is the easiest solution the find the disk. Because there al the same, and there are no number on the mainboard.

To write the serial number on a sticker for each disk, put sticker on each disk, look at the serial of the failed disk and compare it to the serial on the sticker you made, pull that disk! Shh, don't tell anyone, but I haven't done this myself yet.

Write down the serial number and compare to each disk one by one. I would take the opportunity to record the serials on the other disks as well since you will have to look at about half of them unless you get lucky.

 

[z4sleep]

I have a similar problem a few days ago degrade an array of 4 disks RAIDZ

FreeNAS Build FreeNAS-8.0.2-RELEASE-amd64 (8288)
Platform Intel(R) Core(TM)2 Duo CPU E7300 @ 2.66GHz
Memory 4080MB

Code:

[root@freenas] ~# zpool import
  pool: vol01
    id: 2093742675861619639
 state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:

        vol01       ONLINE
          raidz1    ONLINE
            ada1p2  ONLINE
            ada2p2  ONLINE
            ada3p2  ONLINE
            ada4p2  ONLINE
[root@freenas] ~# zpool import vol01
cannot import 'vol01': one or more devices is currently unavailable

Indicates that all disks are operational, but for some reason there is no import array

Code:

[root@freenas] ~# zpool status -v
no pools available
[root@freenas] ~# camcontrol devlist
<ST3160023A 8.01>                  at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD1001FALS-00J7B0 05.00K05>   at scbus1 target 1 lun 0 (pass1,ada1)
<ST31000333AS SD15>                at scbus2 target 1 lun 0 (pass2,ada2)
<WDC WD10EALX-009BA0 15.01H15>     at scbus3 target 0 lun 0 (pass3,ada3)
<ST31000333AS SD15>                at scbus4 target 0 lun 0 (pass4,ada4)
[root@freenas] ~# gpart show
=>       63  312579603  ada0  MBR  (149G)
         63    1930257     1  freebsd  (943M)
    1930320         63        - free -  (32K)
    1930383    1930257     2  freebsd  [active]  (943M)
    3860640       3024     3  freebsd  (1.5M)
    3863664      41328     4  freebsd  (20M)
    3904992  308674674        - free -  (147G)

=>        34  1953522988  ada1  GPT  (932G)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1949328590     2  freebsd-zfs  (930G)

=>        34  1953525101  ada2  GPT  (932G)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1949330703     2  freebsd-zfs  (930G)

=>        34  1953522988  ada3  GPT  (932G)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1949328590     2  freebsd-zfs  (930G)

=>      0  1930257  ada0s1  BSD  (943M)
        0       16          - free -  (8.0K)
       16  1930241       1  !0  (943M)

=>      0  1930257  ada0s2  BSD  (943M)
        0       16          - free -  (8.0K)
       16  1930241       1  !0  (943M)

=>        34  1953522988  ada4  GPT  (932G)
          34          94        - free -  (47K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  1949328590     2  freebsd-zfs  (930G)