Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

Hello Jürgen, Monday, October 6, 2008, 6:27:54 PM, you wrote: Cannot mount root on /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],2/[EMAIL PROTECTED],0:a fstype zfs JK Is that physical device path correct for your new system? JK Or is this the physical device path (stored on-disk in the

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

Again, what I'm trying to do is to boot the same OS from physical drive - once natively on my notebook, the other time from withing Virtualbox. There are two problems, at least. First is the bootpath as in VB it emulates the disk as IDE while booting natively it is sata. When I started

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

Thanks for all of your input. I intalled 2008.11 build 98 as an HVM guest under Xen: If you make a block-level copy of the boot pool and attach it as a disk on the original VM, zpool import does not recognize it. If you attach a non-root pool as a disk, zpool import does recognize it. So,

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

I've upgraded to b98, checked if zpool.cache is not being added to boot archive and tried to boot from VB by presenting a prtition to it. It didn't. I got it working by installing a new build of OpenSolaris 2008.11 from scratch rather than upgrading, but deleting zpool.cache, deleting both

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

Cannot mount root on /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],2/[EMAIL PROTECTED],0:a fstype zfs Is that physical device path correct for your new system? Or is this the physical device path (stored on-disk in the zpool label) from some other system? In this case you may be able to

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

I came across this bug in a similar way myself. The explanation given by Stephen Hahn is this: -- For a while, the boot-archive on 2008.nn systems included a copy of zpool.cache. Recent versions do not make this mistake. Delete and regenerate your boot archive, and you should be able

Re: [zfs-discuss] zpool import of bootable root pool renders it unbootable

I have not tried importing bootable root pools onto other VMs, but there have been recent ZFS bug fixes in the area of importing and exporting bootable root pools - the panic might not occur on Solaris Nevada releases after approximately 97. There are still issues with renaming of bootable

[zfs-discuss] zpool import of bootable root pool renders it unbootable

I am running OpenSolaris 2008.05 as a PV guest under Xen. If you import the bootable root pool of a VM into another Solaris VM, the root pool is no longer bootable. It is related to the device associated to the pool, which is originally c4d0s0, but on import (-f) becomes c0d2s0 in this case.