AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080331150305.13302c98@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<manohar.divate@onstor.com>,<john.keiffer@onstor.com>,<larry.scheer@onstor.com>,<vikas.saini@onstor.com>,<dl-cougar>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E050CFA06@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 31 Mar 2008 15:03:13 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Manohar Divate" <manohar.divate@onstor.com>
Cc: "John Keiffer" <john.keiffer@onstor.com>, "Larry Scheer"
 <larry.scheer@onstor.com>, "Vikas Saini" <vikas.saini@onstor.com>,
 <dl-cougar>
Subject: Re: upgrade
Message-ID: <20080331150313.2f96450c@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E050CFA06@onstor-exch02.onstor.net>
References: <20080331132943.612271c1@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E050CFA06@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It looks like the PROM is trying to load Linux, but the flash install
was done for a bobcat/opt build.

On Mon, 31 Mar 2008 14:51:04 -0700 "Manohar Divate"
<manohar.divate@onstor.com> wrote:

> Larry
>=20
> I did a init and flash install  on a secondary flash=20
> But secondary flash fails to boot with error that directory not found
> in submittal #15. The workflow was ok with FTI branch build.
>=20
> #system copy init
>=20
> #mount -r
> 10.0.0.236:/nx-d_buildup/build-trees/R4.0.0.0/R4.0.0.0-032808/nfx-tree/B
> uild/bc/opt/Release /mnt
>=20
> cd /mnt/etc
> #/.flash_install /mnt 1
>=20
> #System rebot -s=20
>=20
>=20
> Error Not able to load.
>=20
> nitializing Autoloader, hit control-E to bypass
> ........................................................................
> ........
>=20
> Type ctrl-e to stop autoload.
> Waiting for SSC to enter autoload init state...done.
>  ext2_load_file /dev/sdb1/boot/vmlinux.bin at location
> ffffffff82000000 disk model: CF 1GB                                  =01
> disk geometry: cylinders=3D2044 heads=3D16 sectors=3D63
>  Error in directory or file name or not found /boot/vmlinux.bin
> SSC-PROM>
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Monday, March 31, 2008 12:30 PM
> To: John Keiffer
> Cc: Vikas Saini; dl-cougar
> Subject: Re: upgrade
>=20
> On Mon, 31 Mar 2008 11:38:39 -0700 "John Keiffer"
> <john.keiffer@onstor.com> wrote:
>=20
> > Andy,
> >=20
> > =20
> >=20
> > I spoke with Vikas about the concerns you mentioned between system
> > upgrade and flash_install upgrade. He says that we will continue to
> > use system upgrade unless we can actually say that there is
> > something wrong with the current system upgrade procedure that
> > needs to be fixed.=20
>=20
> Vikas is, of course, wrong ~:^) Just trying to check if you're out
> there, Vikas.  Something everyone needs to try to keep in mind is that
> this issue is about Linux, and is not relevant to OpenBSD.  This is
> not an upgrade issue since there is no previous Linux release to
> upgrade from, and upgrade is purposely not designed to upgrade from
> submittal to submittal.  Since the Linux side of things are still a
> WIP, things may change that have to be addressed by doing a flash
> install, or perhaps some manual steps, that won't ever be handled by
> upgrade.
>=20
> To reiterate:
>=20
> Because the Linux part of our distribution is a WIP at the moment, it
> is best to do "flash_install upgrades" rather than the traditional
> system upgrade.  This is because changes from a previous submittal
> often require changes to config file formats or other things that
> cannot be addressed by system upgrade.  A "flash_install upgrade" is
> where you create a flash with the flash_install.sh command, and then
> tell it to copy the config files from the primary flash, and then boot
> the new flash.  Sometimes even this isn't sufficient and a manual
> process may also be involved.  Hopefully in those cases someone will
> remember to send out a specific email detailing that process.  And by
> someone, I mean me, because most other folks seem to remember handily.
>=20
> Cheers,
>=20
> a
