Upgrading from 8.3 to 9.1 zfs pool can't attach

Wed May 22 18:07:00 UTC 2013


2013-05-22 19:54, Freddie Cash skrev:
> On Wed, May 22, 2013 at 10:45 AM, Leslie Jensen <leslie at eskk.nu
> <mailto:leslie at eskk.nu>> wrote:
>
>     zpool import in single user mode gives:
>
>     zfs filesystem version 5
>     zfs storage pool version 28
>     ZFS WARNING: Unable to attach to ada0.
>     ZFS WARNING: Unable to attach to ada1.
>     ZFS WARNING: Unable to attach to ada4.
>     ZFS WARNING: Unable to attach to ada5.
>
>
>
>     grep ada /var/log/messages
>     ------------------------------__--------------
>
>     May 22 19:34:03 bagnerbsd kernel: ada0 at siisch0 bus 0 scbus0
>     target 0 lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada0: <ST3320620AS 3.AAE> ATA-7
>     SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada0: 150.000MB/s transfers (SATA
>     1.x, UDMA6, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada0: Command Queueing enabled
>     May 22 19:34:03 bagnerbsd kernel: ada0: 305245MB (625142448 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada0: Previously was known as ad4
>     May 22 19:34:03 bagnerbsd kernel: ada1 at siisch1 bus 0 scbus1
>     target 0 lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada1: <ST3320620AS 3.AAE> ATA-7
>     SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada1: 150.000MB/s transfers (SATA
>     1.x, UDMA6, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada1: Command Queueing enabled
>     May 22 19:34:03 bagnerbsd kernel: ada1: 305245MB (625142448 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada1: Previously was known as ad6
>     May 22 19:34:03 bagnerbsd kernel: ada2 at ata0 bus 0 scbus2 target 0
>     lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada2: <WDC WD360GD-00FNA0
>     35.06K35> ATA-6 SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada2: 150.000MB/s transfers (SATA
>     1.x, UDMA5, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada2: 35304MB (72303840 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada2: Previously was known as ad0
>     May 22 19:34:03 bagnerbsd kernel: ada3 at ata0 bus 0 scbus2 target 1
>     lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada3: <WDC WD360GD-00FNA0
>     35.06K35> ATA-6 SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada3: 150.000MB/s transfers (SATA
>     1.x, UDMA5, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada3: 35304MB (72303840 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada3: Previously was known as ad1
>     May 22 19:34:03 bagnerbsd kernel: ada4 at ata1 bus 0 scbus3 target 0
>     lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada4: <ST3320620AS 3.AAE> ATA-7
>     SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada4: 150.000MB/s transfers (SATA
>     1.x, UDMA5, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada4: 305245MB (625142448 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada4: Previously was known as ad2
>     May 22 19:34:03 bagnerbsd kernel: ada5 at ata1 bus 0 scbus3 target 1
>     lun 0
>     May 22 19:34:03 bagnerbsd kernel: ada5: <ST3320620AS 3.AAE> ATA-7
>     SATA 1.x device
>     May 22 19:34:03 bagnerbsd kernel: ada5: 150.000MB/s transfers (SATA
>     1.x, UDMA5, PIO 8192bytes)
>     May 22 19:34:03 bagnerbsd kernel: ada5: 305245MB (625142448 512 byte
>     sectors: 16H 63S/T 16383C)
>     May 22 19:34:03 bagnerbsd kernel: ada5: Previously was known as ad3
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-841a1a00: Disk
>     ada2 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-841a1a00: Subdisk
>     Volume0:0-ada2 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-841a1a00: Disk
>     ada3 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-841a1a00: Subdisk
>     Volume0:1-ada3 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Disk
>     ada0 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Subdisk
>     Volume0:1-ada0 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Disk
>     ada1 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Subdisk
>     Volume0:3-ada1 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Disk
>     ada4 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330:
>     Subdisk SiI Raid5 Set:0-ada4 state changed from NONE to STALE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Disk
>     ada5 state changed from NONE to ACTIVE.
>     May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330:
>     Subdisk SiI Raid5 Set:1-ada5 state changed from NONE to STALE.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada0.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada1.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada4.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada5.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada0.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada1.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada4.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada5.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada0.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada1.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada4.
>     May 22 19:34:03 bagnerbsd kernel: ZFS WARNING: Unable to attach to ada5
>     ------------------------------__----------------
>
>     I'm using whole disks. The pool was created back in 2010 and I have
>     forgot the details on how I did but I think I just created the out
>     of the four disks.
>
>     The disks might have been renumbered I'm not sure. It would be
>     logical because the disks ada2 and ada3 had to bee changed in fstab
>     as I wrote before.
>
>     Thanks
>
>
> What happens if you rename /boot/zfs/zpool.cache, and run "zpool import
> -d /dev <poolname>"?
>
> --
> Freddie Cash
> fjwcash at gmail.com <mailto:fjwcash at gmail.com>


This is what happens

zpool import -d /dev storage
cannot import 'storage': a pool with that name is already created/imported,
and no additional pools with that name were found


/Leslie