Hi Rainer,
I haven't seen this in a while but I wonder if you just need to set the
bootfs property on your new root pool and/or reapplying the bootblocks.
Can you import this pool booting from a LiveCD and to review the
bootfs property value? I would also install the boot blocks on the
rpool2 disk.
I would also check the grub entries in /rpool2/boot/grub/menu.lst.
Thanks,
Cidny
On 11/11/10 14:15, Rainer Orth wrote:
I'm still trying to find a fix/workaround for the problem described in
Unable to mount root pool dataset
http://opensolaris.org/jive/thread.jspa?messageID=492460
Since the Blade 1500's rpool is mirrored, I've decided to detach the
second half of the mirror, relabel the disk, create an alternative rpool
(rpool2) there, copy the current BE (snv_134) using beadm create -p
rpool2 snv_be-pkg143, activate the new BE and boot from the second disk.
Unfortunately, this doesn't work: the kernel panics with
Can not read the pool label from <device>
spa_import_rootpool: Error 5
I've booted under kmdb, set a breakpoint in zfs`zfs_mountroot, and found
that this happens because
zfs_devid = spa_get_bootprop("diskdevid");
returns NULL. I've no idea how/why this can happen, and found no code
in the OpenSolaris sources that sets diskdevid for SPARC, so I must
assume that this is directly from OBP (there's only some code in Grub,
which of course is irrelevant here).
Any suggestions what can cause this or what I'm doing wrong?
There's a second machine suffering from the same problem (a Sun Fire
V880 serving as fileserver for the GCC-on-Solaris project), so it would
be extremely valuable to get this fixed/worked around.
Thanks.
Rainer
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
