Sorry you are having trouble. Just a couple probing questions to open up everyones mind. Before I forget, make sure you have burned a OS b134 live cd and a OI b147 live dvd before you do anything.
The first thing I would try is booting into your b134 BE. Then export all the pools besides rpool. zpool export tank zpool export dataen Then try the OI b147 boot environment again. Does it boot now?? If boot = yes, try: zpool import (you have to run this first) zpool import tank zpool import daten Do you get a kernel panic upon one of the imports?? <<there is your problem Or another kernel panic upon OI b147 boot with data pools exported? Maybe the rpool version is too old for OI b147 to work with?? The next thing I would try: I would leave the data pools exported until you get everything sorted out with the boot issues. Boot into your b134 boot environment. Run: zpool get version rpool and zfs get version rpool/ROOT It's possible that you might need to update your rpool to a certain pool version in order to boot OI properly. I imagine that you have been running this machine for a while, and probably did not start out with b134. FWIW, all of the (mostly test) machines that I have upgraded from OS b134 running zpool version 22 zfs version 4 to OI b147 have all booted up fine the first time after the operating system upgrade. If you are running a really old pool version on your rpool, say 14 or something like that, you might try booting into your b134 boot environment and upgrading it to the highest pool version b134 can use, pool version 22, zfs version 4. zpool upgrade -V 22 rpool zfs upgrade -V 4 rpool/ROOT zfs upgrade -V 4 rpool/opensolaris basically anything in the rpool Running the commands above will make boot environments before 134 obsolete, so a warning is in order. Seeing as that you are trying to move forward, rather than keep compatibility with older BE's it's worth a shot to make sure your rpool is running something that OI can see. -Chris On Wed, Sep 29, 2010 at 2:40 AM, <thorsten.h...@vkb.de> wrote: > Hi, > > by following the instructions on the wiki I just upgraded from OpenSolaris > b134 to OpenIndiana. Unfortunately booting into the new BE results in a > kernel panic: > > ... > NOTICE: zfs_parse_bootfs: error 22 > Cannot mount root on rpool/101 fstype zfs > > panic[cpu0]/thread=fffffffffbc2f260: vs_mountroot: cannot mount root > > Warning - stack not written to the dump buffer > fffffffffbc718e0 genunix:vfs_mountroot+33e () > fffffffffbc71910 genunix:main+136 () > fffffffffbc71920 unix:_locore_start+90 () > > panic: entering debugger (no dump device, continue to reboot) > > Welcome to kmdb > Loaded modules: [ scsi_vhci mac uppc sd unix zfs krtld apix genunix specfs > pcplusmp cpu.generic ] > [0]> > > > My machine is a HP ProLiant ML350 G5 with 2 quad-core Xeons, 32GB RAM and > a HP SmartArray E200i RAID controller with 3x160 and 3x500GB SATA discs > connected to it. Two of the 160GB discs build the mirrored root pool > (rpool), the third serves as a temporary data pool called "tank", and the > three 500G discs form a RAIDZ1 pool called "daten". > > What is causing this kernel panic? > I tried to recreate/upgrade the boot archive for the OpenIndiana BE, but > that didn't help... > > > Regards > > Thorsten > > _______________________________________________ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
