Here's another bit that may or may not help understanding the problem: upon reboot the system tries to remount BE roots, but it doesn't always work, i.e.:
# init 6 propagating updated GRUB menu Saving existing file </boot/grub/menu.lst> in top level dataset for BE <snv_93> as <mount-point>//boot/grub/menu.lst.prev. Saving existing file </boot/grub/menu.lst> in top level dataset for BE <snv_93.tmp> as <mount-point>//boot/grub/menu.lst.prev. File </boot/grub/menu.lst> propagation successful ERROR: cannot unmount '/': Device busy ERROR: cannot set mount mount point </.alt.snv_93> on dataset <rootpool/rootfs_snv93> ERROR: cannot mount root device <rootpool/rootfs_snv93> to mount point </.alt.snv_93> for boot environment <snv_93> ERROR: cannot mount boot environment by name <snv_93> ERROR: Failed to mount BE <snv_93>. ERROR: Failed to mount BE <snv_93>. Cannot propagate file </etc/lu/GRUB_backup_menu> to BE File propagation was incomplete bootadm: error propagating backup GRUB menu: /etc/lu/GRUB_backup_menu Then again, it is probably due to the methid I used to "create" this current BE (snv_93) by copying files from snv_77, since lucreate failed... I'll see what's wrong in /etc/lu files. This should not however permit GRUB to not parsing the ZFS pool sometimes, should it? This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
