Upgrading from 8.3 to 9.1 zfs pool can't attach

[Andriy Gapon]

on 22/05/2013 20:45 Leslie Jensen said the following:
> 
> 
> 2013-05-22 17:33, Freddie Cash skrev:
[snip]
>> On Wed, May 22, 2013 at 3:53 AM, Leslie Jensen <leslie at eskk.nu
>> <mailto:leslie at eskk.nu>> wrote:
[snip]
>>     ada2 and ada3 are configured as raid/r0 holding the system.
>>
>>     ada0, ada1, ada4 and ada5 should be a zfs pool with  /home

If you look at the messages below you can see that  ada0, ada1, ada4 and ada5 are
also claimed by the raid driver.


> 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.

Apparently they used to be in raid configurations and the metadata was never
properly cleared.

-- 
Andriy Gapon