> it seems i have the same problem after zfs boot
> installation (following this setup on a snv_69 release
> http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ ).
Hmm, in step 4., wouldn't it be better to use ufsdump / ufsrestore
instead of find / cpio to clone the ufs root into the zfs root pool?
cd /zfsroot
ufsdump 0f - / | ufsrestore -xf -
Advantages:
- it copies the mountpoint for the /etc/dfs/dfstab filesystem
(and all the other mountpoints, like /tmp, /proc, /etc/mnttab, ...)
- it does not mess up the /lib/libc.so.1 shared library
I think the procedure at the above url could copy the wrong
version of the shared libc.so.1 into the zfsroot /lib/libc.so.1;
this might explain bugs like 6423745,
Synopsis: zfs root pool created while booted 64 bit can not be booted 32 bit
- the files hidden by the /devices mount are copied,too
> The outputs from the requested command
> are similar to the outputs posted by dev2006.
>
> Reading this page, i found no solution concerning the
> /dev/random problem. Is there somewhere a procedure
> to repair my install ?
AFAICT, there's nothing you can do to avoid the
"WARNING: No randomness provider enabled for /dev/random."
message with zfs root at this time. It seems that zfs mountroot
needs some random numbers for mounting the zfs root filesystem,
and at that point early during the bootstrap there isn't a fully initialized
random device available. This fact is remembered by the random
device and is reported later on, when the system is fully booted.
I think when the system is fully booted from zfs root, the random
device should work just fine.
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
