Upgrading from 8.3 to 9.1 zfs pool can't attach
Leslie Jensen
leslie at eskk.nu
Wed May 22 17:45:24 UTC 2013
2013-05-22 17:33, Freddie Cash skrev:
> What's the output of "zpool import" in single-user mode?
>
> What are the names of your disk devices? "grep ad /var/log/messages"
> for example.
>
> Are you using whole disks, disk partitions, labels, etc to access your
> disks? Are you sure your disks haven't been renumbered at all?
>
>
> On Wed, May 22, 2013 at 3:53 AM, Leslie Jensen <leslie at eskk.nu
> <mailto:leslie at eskk.nu>> wrote:
>
>
> I've upgraded a machine with freebsd-update from 8.3 to 9.1.
>
> After the first restart I edited /etc/fstab in single user mode
> because the names on the disks had changed. But the zfs pool I have
> seem to have a problem and I'm sure on how to recover it.
>
>
> May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada0.
> May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada1.
> May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada4.
> May 22 12:00:40 kernel: ZFS WARNING: Unable to attach to ada5.
>
>
> camcontrol devlist
> <ST3320620AS 3.AAE> at scbus0 target 0 lun 0 (ada0,pass0)
> <ST3320620AS 3.AAE> at scbus1 target 0 lun 0 (ada1,pass1)
> <WDC WD360GD-00FNA0 35.06K35> at scbus2 target 0 lun 0 (ada2,pass2)
> <WDC WD360GD-00FNA0 35.06K35> at scbus2 target 1 lun 0 (ada3,pass3)
> <ST3320620AS 3.AAE> at scbus3 target 0 lun 0 (ada4,pass4)
> <ST3320620AS 3.AAE> at scbus3 target 1 lun 0 (ada5,pass5)
>
> ada2 and ada3 are configured as raid/r0 holding the system.
>
> ada0, ada1, ada4 and ada5 should be a zfs pool with /home
>
>
> cat /etc/fstab
>
> # Device Mountpoint FStype Options Dump Pass#
> /dev/raid/r0s1b none swap sw 0 0
> /dev/raid/r0s1a / ufs rw 1 1
> /dev/raid/r0s1e /tmp ufs rw 2 2
> /dev/raid/r0s1f /usr ufs rw 2 2
> /dev/raid/r0s1d /var ufs rw 2 2
>
>
> I'm not sure but shouldn't the mount point for /home also appear in
> fstab?
>
> Maybe I messed up during the manual editing of files during the
> update process?
>
>
> Can I recover or shall I destroy the pool and rebuild it?
>
> Thanks
>
> /Leslie
>
>
>
> _________________________________________________
> freebsd-fs at freebsd.org <mailto:freebsd-fs at freebsd.org> mailing list
> http://lists.freebsd.org/__mailman/listinfo/freebsd-fs
> <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>
> To unsubscribe, send any mail to
> "freebsd-fs-unsubscribe at __freebsd.org
> <mailto:freebsd-fs-unsubscribe at freebsd.org>"
>
>
>
>
> --
> Freddie Cash
> fjwcash at gmail.com <mailto:fjwcash at gmail.com>
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
/Leslie
More information about the freebsd-fs
mailing list