> I'm sorry I believe I'm unable to help with deeper
> troubleshooting of this, because I managed to make it
> work by doing another 94->95 upgrade using the help
> for making a 86-> upgrade like described at
> 
> http://opensolaris.org/os/project/indiana/resources/rn
> 3/image-update/
> 
> and that did work. Why, I haven't got the faintest
> idea. I had tried the 94->95 upgrade (simply with pkg
> image-update) two times already with similar results
> (no menu, just grub).
> 
> I still have the 94 snapshot on my Virtualbox but
> being a newbie with it I don't know how to boot the
> old snapshot without destroying newer snapshots
> (including my new 95 system).
When I installed it the first time, make sure ther is eneough  partition under 
NTFS , Solaris2 (fidsk) , then when you get to the divvy of (format) for the 
slice panel, I created the following slices equal sizes using (ufs filesytems):
/ (root) s0 8001
swap     s1 8001
(leave alone s2 (complete drive c:)
(leave blank) s3 8001
/export s4 8001
(leave blank reserve for zfs) s5 leftover-65 cyl
(leave blank reserve for SVM mdb) s6 30 cyl
(leave blank reserve for SVM mdb) s7 30 cyl
Please note there is still issues when there are neg rounding errors # on cyl 
count total. leave at a positive single intiger value) with 0 left over, if yuu 
can not get with 0 cyl and 0 rounding error, most drive geomitries do not allow 
this, that is why Windws leaves a small amount of space free when you do Vista 
or XP defaults.
then I can do a lucreate -c os1 -m/:c0d0s3:ufs -n newos assuming I instaled the 
on slice s0 also , in a reload situaltion you can then not over write the s0 
with the old OS and run a preserve existing partitions and install on s3 and 
then when you boot up after the install is complete, you can as root mount 
/dev/dsk/c0d0s0 /mnt to get at your old root volume.
 

 If it's possible I can
> try to find out the devid, or anything else, once
> someone tells me how.
--
This message posted from opensolaris.org

Reply via email to