X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87D6A.8087C982@onstor-exch02.onstor.net>; Mon, 3 Mar 2008 13:09:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Check out this wild boot sequence when using rev 1.0.4 proms
Date: Mon, 3 Mar 2008 13:09:34 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E089F242F@onstor-exch02.onstor.net>
In-Reply-To: <20080303115942.5bc59f80@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Check out this wild boot sequence when using rev 1.0.4 proms
Thread-Index: Ach9aR7Qg7HurxibTKOUHyyjXvFc9wAAIGBQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E08627CCF@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E056C93C3@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E08627F06@onstor-exch02.onstor.net> <20080303115942.5bc59f80@ripper.onstor.net>
From: "Warren Gale" <warren.gale@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Depends on which prom you are booting from.
  "prom view"  will tell you which prom you are booting from.
  " Rec  or Standard"  wil be printed it the 1st few lines..
If Rec then use sibyte_cb.bin
Else  use sibfimg_cg.bin

Since you are only upgrading the SSC PROM:
  "prom upgrade [ip-address] [file-name]"
Ie  "prom upgrade 10.1.1.189 sibfig_cg.bin"

[ip-address] =3D tftpboot server
It will look for the file in /tftpboot  dir


Warren


-----Original Message-----
From: Andy Sharp=20
Sent: Monday, March 03, 2008 12:00 PM
To: Warren Gale
Subject: Re: Check out this wild boot sequence when using rev 1.0.4
proms

On Tue, 19 Feb 2008 18:14:42 -0800 "Warren Gale"
<warren.gale@onstor.com> wrote:

> Yup.. I screwed that one up :-(.  Well it did seem to work though. I
> got some responses :-)
> You are absolutely correct.
>=20
> =20
>=20
> I now have new images for you, and Andy.
>=20
> Please find @ "/n/users/warreng/cg_proms/Larry104/ver-02-19"
>    new files that have all of what Andy was looking for in his last
> e-mail,
> including the default   just "g" command. (Nice way to slip that 1 in
> there)

which file should I use?  there is a sibfimg_cg.bin and a sibyte_cg.bin

And where did I put those damn prom upgrade instructions again....some
wiki page somewhere....

> So Please let me know if there are any problems with these.
>=20
> I have done some testing, but as you can see I didn't catch my errors
> in the last e-mail..
>=20
> =20
>=20
> Thanks,
>=20
> Warren
>=20
> =20
>=20
> =20
>=20
> ________________________________
>=20
> From: Larry Scheer=20
> Sent: Tuesday, February 19, 2008 5:55 PM
> To: Warren Gale; Andy Sharp; Brian Stark
> Cc: Tim Gardner
> Subject: RE: Check out this wild boot sequence when using rev 1.0.4
> proms
>=20
> =20
>=20
> Warren,
>=20
>   Andy already answered this email. But I just want to point out that
> your matrix is pretty messed up which leads to much confusion. The
> second compact flash root is /dev/sdb1 not /dev/sdb2 and the env
> Boot_dev should be sdb1 not sda2 .The boot devices are sda1 and sdb1
> not sda1 and sda2.
>=20
> =20
>=20
> Larry
>=20
> =20
>=20
> ________________________________
>=20
> From: Warren Gale=20
> Sent: Tuesday, February 19, 2008 1:54 PM
> To: Andy Sharp; Brian Stark
> Cc: Larry Scheer; Tim Gardner
> Subject: RE: Check out this wild boot sequence when using rev 1.0.4
> proms
>=20
> =20
>=20
> Ok, let me see, I believe this is what everyone wants:
>=20
> =20
>=20
> Boot from
>=20
> Environments
>=20
> PROM passes in
>=20
> Net
>=20
> Load_src =3D network
>=20
> Boot_dev =3D   don't care
>=20
>   Arg [0] =3D bsd
>=20
>   Arg [1] =3D root=3D/dev/nfs
>=20
>   Arg [2] =3D ip=3Ddhcp
>=20
> Sda1   CF present in other slot
>=20
> Load_src =3D disk
>=20
> Boot_dev =3D sda1
>=20
>   Arg [0] =3D g
>=20
>   Arg [1] =3D root=3D/dev/sda1
>=20
>   Arg [2] =3D ip=3Dnone
>=20
>   Arg [3] =3D rootdelay=3D1
>=20
> Sda2   CF present in other slot
>=20
> =20
>=20
> Load_src =3D disk
>=20
> Boot_dev =3D sda2
>=20
>   Arg [0] =3D g
>=20
>   Arg [1] =3D root=3D/dev/sdb2
>=20
>   Arg [2] =3D ip=3Dnone
>=20
>   Arg [3] =3D rootdelay=3D1
>=20
> Sda1   no CF in other slot
>=20
> =20
>=20
> Load_src =3D disk
>=20
> Boot_dev =3D sda1
>=20
>   Arg [0] =3D g
>=20
>   Arg [1] =3D root=3D/dev/sda1
>=20
>   Arg [2] =3D ip=3Dnone
>=20
>   Arg [3] =3D rootdelay=3D1
>=20
> Sda2   no CF in other slot
>=20
> =20
>=20
> Load_src =3D disk
>=20
> Boot_dev =3D sda2
>=20
>   Arg [0] =3D g
>=20
>   Arg [1] =3D root=3D/dev/sda1
>=20
>   Arg [2] =3D ip=3Dnone
>=20
>   Arg [3] =3D rootdelay=3D1
>=20
> =20
>=20
> Is this correct?
>=20
> =20
>=20
> Thanks,
>=20
> Warren
>=20
> =20
>=20
> =20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, February 19, 2008 11:47 AM
> To: Brian Stark
> Cc: Larry Scheer; Warren Gale; Tim Gardner
> Subject: Re: Check out this wild boot sequence when using rev 1.0.4
> proms
>=20
> =20
>=20
> On Tue, 19 Feb 2008 10:52:22 -0800 "Brian Stark"
>=20
> <brian.stark@onstor.com> wrote:
>=20
> =20
>=20
> > Larry,
>=20
> >=20
>=20
> > Excellent, thanks to both you and Warren for jumping on this.  We
> > will
>=20
> > make this fix part of 1.0.5.
>=20
> >=20
>=20
> >=20
>=20
> > Andy,
>=20
> >=20
>=20
> > Let us know how you'd like to proceed with ip=3Ddhcp and any other
>=20
> > command line args.
>=20
> =20
>=20
> The prom should not pass in ip=3Ddhcp.  If boot_dev is CF, then it
>=20
> should pass in ip=3Dnone and rootdelay=3D1 in addition to the
> root=3Dboot_dev
>=20
> argument.   It appeared to be doing that in the trace Larry sent,
>=20
> except that it got the boot_dev wrong.
>=20
> =20
>=20
> Cheers,
>=20
> =20
>=20
> a
>=20
> =20
>=20
> =20
>=20
