Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

zfs pool unmountable after a restart of the array

Featured Replies

I setup unraid a few days ago and successfully "imported" and existing zfs pool. (raidz1, 2vdevs of 2 devices). Last night I stopped the Array in order to try and use the unassigned disk plugin to mount a disk before adding to array. when I restarted the Array, my pool status showed up as "Unmountable: wrong or no file system". I've removed the pool and tried to import again (after a start without the pool), but I continue to get the same status.

Are there other commands I should try or guidance on recovering my pool?

I tried a manual import from the cli. All of the commands return "cannot import 'media-pool': no such pool available"

zpool import -a

zpool import -f media-pool

zpool import -F media-pool

zpool import -FX media-pool

zpool import -fD

zpool import -d /dev/

zpool import -d /dev/disks/by-id/

zpool import -d /dev/disk/by-uuid/ -a

The zfs labels are intact on all disks

  • zdb -l /dev/sdc1

------------------------------------
LABEL 0
------------------------------------
    version: 5000
    name: 'media-pool'
    state: 1
    txg: 6706079
    pool_guid: 2272386273227785721
    errata: 0
    hostname: 'batcomputer'
    top_guid: 436500489736789877
    guid: 4226078641111056155
    vdev_children: 2
    vdev_tree:
        type: 'mirror'
        id: 0
        guid: 436500489736789877
        metaslab_array: 146
        metaslab_shift: 34
        ashift: 12
        asize: 12000123420672
        is_log: 0
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 4226078641111056155
            path: '/dev/sdc1'
            devid: 'ata-HUH721212ALE601_8DKDG99H-part1'
            phys_path: '/dev/disk/by-uuid/2272386273227785721'
            whole_disk: 1
            DTL: 10111
            create_txg: 4
        children[1]:
            type: 'disk'
            id: 1
            guid: 17759701068753237779
            path: '/dev/sdd1'
            devid: 'ata-HUH721212ALE601_8DJN3ZYH-part1'
            phys_path: '/dev/disk/by-uuid/2272386273227785721'
            whole_disk: 1
            DTL: 10110
            create_txg: 4
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data
        com.klarasystems:vdev_zaps_v2
    labels = 0 1 2 3
  • zdb -l /dev/sdd1

------------------------------------
LABEL 0
------------------------------------
    version: 5000
    name: 'media-pool'
    state: 1
    txg: 6706079
    pool_guid: 2272386273227785721
...
  • zdb -l /dev/sde1

------------------------------------
LABEL 0
------------------------------------
    version: 5000
    name: 'media-pool'
    state: 1
    txg: 6706079
    pool_guid: 2272386273227785721
...
  • zdb -l /dev/sdf1

------------------------------------
LABEL 0
------------------------------------
    version: 5000
    name: 'media-pool'
    state: 1
    txg: 6706079
    pool_guid: 2272386273227785721
...
  • Author

So these labels are on the partition and not the raw disk. zpool also can't read labels 1,2,3.

I attempted to repair the label and got following. trying to figure out what this means

> zhack label repair /dev/sdc1
Calculated filesize to be 12000128139264
error: label 0: UB TXG of 0 expected, but got 6706048
It would appear the device was not properly removed.
error: label 1: UB TXG of 0 expected, but got 6706048
It would appear the device was not properly removed.
error: label 2: UB TXG of 0 expected, but got 6706048
It would appear the device was not properly removed.
error: label 3: UB TXG of 0 expected, but got 6706048
It would appear the device was not properly removed.
label 0: uberblock: skipped checksum: skipped
label 1: uberblock: skipped checksum: skipped
label 2: uberblock: skipped checksum: skipped
label 3: uberblock: skipped checksum: skipped
  • Community Expert

Is the above the full output from zdb -l? Also, please post the diagnostics.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.