Small world... Never seen this problem before your post, and hit it now myself
;)
We had an outage on an SXCE snv_117 server today with a data pool taking
unknown time to import, so we decided to "zpool import -F" it. But the feature
is lacking in build 117, so we imported the pool into an Open
Sorry, I guess I'm running out of reasonable ideas then.
One that you can try (or already did) is installing Solaris not by JumpStart or
WANBoot but from original media (DVD or Network Install) to see if the problem
pertains. Maybe your flash image lacks some controller drivers, etc? (I am not
Hello Jim,
Thanks for the reply following is my o/p before setting bootfs parameter
# zpool get all rpool
NAME PROPERTY VALUE SOURCE
rpool size 68G -
rpool capacity 5%-
rpool altroot-
Hello again.
As I kind of explained earlier, and as your screenshots display, your actual
root filesystem dataset is named "rpool/ROOT/zfsBE_patched". However either the
boot loader (eeprom parameters on SPARC) or much more likely the "rpool"
ZFS-pool level attribute "bootfs" contains a differe
Hi Ketan,
What steps lead up to this problem?
I believe the boot failure messages below are related to a mismatch
between the pool version and the installed OS version.
If you're using the JumpStart installation method, then the root pool is
re-created each time, I believe. Does it also instal
So y my system is not coming up .. i jumpstarted the system again ... but it
panics like earlier .. so how should i recover it .. and get it up ?
System was booted from network into single user mode and then rpool imported
and following is the listing
# zpool list
NAMESIZE ALLOC FREE
Technically "bootfs ID" is a string which names the root dataset, typically
"rpool/ROOT/solarisReleaseNameCode". This string can be passed to Solaris
kernel as a parameter manually or by bootloader, otherwise a default current
"bootfs" is read from the root pool's attributes (not dataset attribu
