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
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
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,
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
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
David Finberg [EMAIL PROTECTED] writes:
JN I had a similar problem: After installing and booting Opensolaris
JN 2008.05, I succeded to lock myself out through some passwd/shadow
JN inconsistency (totally my own fault). Not a problem, I thought -- I
JN booted from the install disk, imported
Hello David,
Tuesday, September 30, 2008, 10:57:45 PM, you wrote:
DF On Tue, 30 Sep 2008, Robert Milkowski wrote:
Hello Juergen,
Tuesday, September 30, 2008, 5:43:56 PM, you wrote:
JN Stephen Quintero [EMAIL PROTECTED] writes:
I am running OpenSolaris 2008.05 as a PV guest under Xen. If
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
Stephen Quintero [EMAIL PROTECTED] writes:
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.
I had a similar problem: After installing and booting Opensolaris
2008.05, I succeded
Hello Juergen,
Tuesday, September 30, 2008, 5:43:56 PM, you wrote:
JN Stephen Quintero [EMAIL PROTECTED] writes:
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.
JN I had a
On Tue, 30 Sep 2008, Robert Milkowski wrote:
Hello Juergen,
Tuesday, September 30, 2008, 5:43:56 PM, you wrote:
JN Stephen Quintero [EMAIL PROTECTED] writes:
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
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
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.
13 matches
Mail list logo