"no pools available" after kernel panic

This forum is to find answers to problems you may be having with ZEVO Community Edition.

Moderators: jhartley, MSR734, nola

"no pools available" after kernel panic

Post by erico » Sun Nov 25, 2012 10:50 pm

Hello,
I've just started using zevo, and had a kernel panic when copying files to an external sata array. When I rebooted, the pool did not mount, and when I go to the command line and issue "zpool list" I receive a "no pools available". I can see the disk via a diskutil list....but is there a way to get ZEVO to recover the pool list?

Thank you,

Eric
erico Offline


 
Posts: 10
Joined: Sun Nov 25, 2012 6:31 pm

Re: "no pools available" after kernel panic

Post by grahamperrin » Mon Nov 26, 2012 5:38 am

Welcome!

Outputs please from twelve commands:

Code: Select all
sw_vers
kextstat | grep zfs
ls -l /Volumes
ls -l /dev/dsk
ls -l /var/zfs/dsk
diskutil list
diskutil coreStorage list
zpool upgrade
zfs upgrade
sudo zpool import
sudo zpool status -vx -T d
sudo zpool status -v


Hints: when replying, use the full editor to format as code; and maybe present each of the twelve outputs as a separate block of code.

Hopefully the outputs will help to describe the configuration of the pool.

If you can, please also paste the content of the panic report.

Maybe not immediately relevant, but of interest: what type of Mac, and how much memory? What make and model is the drive enclosure? Makes and models of the drives?

Thanks.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: "no pools available" after kernel panic

Post by erico » Thu Nov 29, 2012 3:45 pm

Thank you for taking a look at this. Any help on interpreting this would be helpful. I can see that the system still has some sort of diskid related to the volume. Is there a way to force that to mount? Yes, the machine is running snow leopard....I haven't seen anywhere that would suggest that is the problem, but I could install mountain lion if that would make a difference....Thank you for the help!

erico

sw_vers
Code: Select all
ProductName:   Mac OS X
ProductVersion:   10.6.8
BuildVersion:   10K549

kextstat | grep zfs
Code: Select all
  124    0 0xffffff7f81358000 0x140000   0x140000   com.getgreenbytes.filesystem.zfs (2012.09.23) <12 7 5 4 3 1>

ls -l /Volumes
Code: Select all
drwxrwxr-x  17 eric  staff   646 Nov 25 16:48 2tb
lrwxr-xr-x   1 root  admin     1 Nov 25 21:00 4gb -> /
drwxrwxr-x  52 root  admin  1836 Nov 25 19:05 4gb-ext
drwxr-xr-x@  9 eric  staff   374 Oct 18 14:42 OmniFocus
drwxr-xr-x  42 root  wheel  1496 Nov 25 19:28 boot
drwxrwxr-x  32 eric  staff  1156 Nov 26 09:22 int-onepointfive
drwxrwxr-x  23 eric  staff   850 Nov 25 15:30 long term storage

ls -l /dev/dsk
Code: Select all
lrwxr-xr-x  1 root  wheel  0 Nov 25 20:59 /dev/dsk -> /var/zfs/dsk
ls -l /var/zfs/dsk
Code: Select all
lrwxr-xr-x  1 root  wheel  12 Nov 25 21:01 GPTE_585A9D18-B3FD-4281-A65D-82AE5E3C5602 -> /dev/disk5s2

diskutil list
Code: Select all
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                 Apple_RAID                         2.0 TB     disk0s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                 Apple_RAID                         2.0 TB     disk1s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.5 TB     disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:                  Apple_HFS boot                    1.5 TB     disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.5 TB     disk3
   1:                        EFI                         209.7 MB   disk3s1
   2:                 Apple_RAID                         1.5 TB     disk3s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk3s3
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS 4gb                    *4.0 TB     disk4
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk5
   1:                        EFI                         209.7 MB   disk5s1
   2:                        ZFS                         2.0 TB     disk5s2
/dev/disk6
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk6
   1:                        EFI                         209.7 MB   disk6s1
   2:                 Apple_RAID                         2.0 TB     disk6s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk6s3
/dev/disk7
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk7
   1:                        EFI                         209.7 MB   disk7s1
   2:                 Apple_RAID                         2.0 TB     disk7s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk7s3
/dev/disk8
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *1.5 TB     disk8
   1:        Apple_partition_map                         32.3 KB    disk8s1
   2:             Apple_Driver43                         28.7 KB    disk8s2
   3:             Apple_Driver43                         28.7 KB    disk8s3
   4:           Apple_Driver_ATA                         28.7 KB    disk8s4
   5:           Apple_Driver_ATA                         28.7 KB    disk8s5
   6:             Apple_FWDriver                         262.1 KB   disk8s6
   7:         Apple_Driver_IOKit                         262.1 KB   disk8s7
   8:              Apple_Patches                         262.1 KB   disk8s8
   9:                  Apple_HFS long term storage       1.5 TB     disk8s10
/dev/disk10
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS int-onepointfive       *1.5 TB     disk10
/dev/disk11
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk11
   1:                        EFI                         209.7 MB   disk11s1
   2:                  Apple_HFS 2tb                     2.0 TB     disk11s2
/dev/disk12
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS 4gb-ext                *4.0 TB     disk12
/dev/disk13
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            OmniFocus              *104.9 MB   disk13

diskutil coreStorage list
Code: Select all
diskutil: did not recognize verb "coreStorage"; type "diskutil" for a list

zpool upgrade
Code: Select all
This system is currently running ZFS pool version 28.

All pools are formatted using this version.

zfs upgrade
Code: Select all
This system is currently running ZFS filesystem version 5.

All filesystems are formatted with the current version.

sudo zpool import
Code: Select all
  pool: test
    id: 18049541239639813165
 state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though
   some features will not be available without an explicit 'zpool upgrade'.
config:

   test                                         ONLINE
     GPTE_585A9D18-B3FD-4281-A65D-82AE5E3C5602  ONLINE

sudo zpool status -vx -T d
Code: Select all
Thu Nov 29 13:42:15 2012
no pools available

sudo zpool status -v
Code: Select all
no pools available
erico Offline


 
Posts: 10
Joined: Sun Nov 25, 2012 6:31 pm

Re: "no pools available" after kernel panic

Post by erico » Thu Nov 29, 2012 4:20 pm

Addendum: It did occur to me that I could force the pool import. So I did that.... First I received this result:

octo:~ eric$ sudo zpool import -f 18049541239639813165
cannot import 'test': invalid vdev configuration

I issued the same command again and it mounted, but now everything i do with the disk gives me checksum errors (Error 92). Is this normal? I don't quite understand what the role of the virtual device is, or whether the checksum errors refer to the earlier failed file copy or something else. This is a brand new HDD, by the way.

Thanks!
Eric
erico Offline


 
Posts: 10
Joined: Sun Nov 25, 2012 6:31 pm

Virtual Devices (vdevs)

Post by grahamperrin » Thu Nov 29, 2012 5:09 pm

From the man page for zpool(8):

Virtual Devices (vdevs)
       A "virtual device" describes a single device or a collection of devices
       organized according to certain performance and fault characteristics. …
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: "no pools available" after kernel panic

Post by grahamperrin » Thu Nov 29, 2012 5:27 pm

If the history for the pool will be of interest, and if cautiously you wish to read only (not write to) the file system at the root of the pool, then maybe:

  • restart the computer, export the pool (assuming it imports dynamically), import the pool with readonly=on for the file system.

For the import try first without force –

Code: Select all
sudo zpool import -o readonly=on 18049541239639813165


– if that fails, then:

Code: Select all
sudo zpool import -f -o readonly=on 18049541239639813165


For the most verbose history of your pool named test:

Code: Select all
sudo zdb -hvvvvv test


Thoughts

The result of a complete scrub will be of interest but first, maybe the history. Although the hard disk drive is new, wonder whether there's a problem with hardware.

If you can, please let us have the make and model of the drive, Mac etc.. Thanks.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: "no pools available" after kernel panic

Post by grahamperrin » Fri Dec 07, 2012 10:14 pm

Here with Mountain Lion:

Code: Select all
macbookpro08-centrim:~ gjp22$ kextstat | grep zfs
   99    1 0xffffff7f80799000 0x19b000   0x19b000   com.getgreenbytes.filesystem.zfs (2012.09.23) <13 7 5 4 3 1>
  100    0 0xffffff7f80936000 0x6000     0x6000     com.getgreenbytes.driver.zfs (2012.09.14) <99 13 7 5 4 3 1>


erico, would you like to re-run the command on your Snow Leopard system?

The absence of com.getgreenbytes.driver.zfs is puzzling.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom


Return to Troubleshooting

Who is online

Users browsing this forum: bileyqrkq, ilovezfs and 0 guests

cron