Yes thanks that help point it to the right repo, it still has not finished installing yet.
Ok, why does the 2010.02 dev ai build point to /release? Should it not point to /dev and it's particular build by default, since thats what it is for? Sent from my iPod On 31 Aug 2009, at 03:20, Jack Schwartz <Jack.A.Schwartz at Sun.COM> wrote: > Hi John-Paul. > > I'm wondering if the instructions you followed were for 2009.06. > Unless you changed things, 2009.06 would have installed 111b because > the repo is set by default to pkg.opensolaris.org/release. The > latest release would be at pkg.opensolaris.org/dev. Check your > ai_pkg_repo_default_authority in the AI manifest, that it points to > the .../dev repo. Here are some references: > > http://dlc.sun.com/osol/docs/content/dev/AIinstall/manifest.html > http://dlc.sun.com/osol/docs/content/dev/AIinstall/associate.html > http://dlc.sun.com/osol/docs/content/dev/AIinstall/faq.html#modifymanifest > > I hope that helps, > Jack > > > > John-Paul Drawneek wrote: >> ok trying to get opensolaris to work since sxce is now going to >> become dead. >> >> Not having much luck. >> >> final managed to get ai to install with out it timing out with b121. >> >> But it now boots with the worrying message of: >> >>> Boot device: /pci at 7c0/pci at 0/pci at 8/scsi at 2/disk at 0,0:a File >>> and args: >>> SunOS Release 5.11 Version snv_111b 64-bit >>> >> >> I didn't install that? >> >> >>> NOTICE: zfs_parse_bootfs: error 48 >>> Cannot mount root on rpool/51 fstype zfs >>> >>> panic[cpu0]/thread=180e000: vfs_mountroot: cannot mount root >>> >>> 000000000180b950 genunix:vfs_mountroot+320 (200, 18acc00, 18da400, 1909400 >>> , 1261538, 18acc00) >>> %l0-3: 0000000000000000 0000000000000000 0000000000000000 >>> 00000000018accc0 >>> %l4-7: 0000000001261400 0000000000000600 0000000000000200 0000000000000800 >>> 000000000180ba10 genunix:main+c4 (182b400, 180bec0, 182b7c0, >>> 185eec0, 1, 1860558) >>> %l0-3: 0000000000000000 0000000000000000 0000000000000000\ >>> >> >> so what went wrong? did i miss the notice that ai is broke in b121? >> Why is b111b installed when it should have been b121? >> >> I did read the instructions, i did follow them - so how did i end >> up in this mess? >> >
