X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77724.714BB493@onstor-exch02.onstor.net>; Wed, 4 Apr 2007 18:48:00 -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: New BC filers
Date: Wed, 4 Apr 2007 18:48:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E031DF6A5@onstor-exch02.onstor.net>
In-Reply-To: <20070404175650.3ffc829d@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New BC filers
Thread-Index: Acd3HUuRs24wpLNHTWC7NZRE2aqvvgABxHvw
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

Nope its not. Its 512MB.=20

This flash is supported by us. Looks like a bug in copy init.

Will file one.

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, April 04, 2007 5:57 PM
To: Raj Kumar
Cc: Larry Scheer; Brian DeForest
Subject: Re: New BC filers

It definitely does not like the flash card.  One clue:

"Disk size 2673901568 bytes is not supported"

Would seem to indicate that this is a 2.49 GB flash card, but I bet
it's not.

Cheers,

a

On Wed, 4 Apr 2007 15:46:10 -0700 "Raj Kumar" <raj.kumar@onstor.com>
wrote:

> System copy init (runnig R1.3.3.1-103106)  fails. Any clues? The
> secondary flash  is 512MB.
>=20
> _____________________________________________
> From: John Rogers=20
> Sent: Wednesday, April 04, 2007 3:26 PM
> To: Raj Kumar; Sandrine Boulanger; Elab
> Subject: RE: New BC filers
>=20
> System copy is broken? Unsupported flash card?
>=20
> _____________________________________________
> From: Raj Kumar=20
> Sent: Wednesday, April 04, 2007 3:25 PM
> To: Sandrine Boulanger; John Rogers; Elab
> Subject: RE: New BC filers
>=20
> System copy init is failing. Any clues?
>=20
>=20
> g4r8 diag> system copy init=20
> Disk size 2673901568 bytes is not supported
> % Command failure.
>=20
>=20
> wd1 at wdc1 channel 0 drive 0: <CF u1rMB ` ` ` ` ` ` ` ` ` ` ` ` ` ` `
> `>
> wd1: can use 16-bit, PIO mode 0
> wd1: 65-sector PIO, LBA, 2550MB, 1020 cyl, 80 head, 127 sec, 5222464
> sectors
> Apr  4 15:22:15 g4r8 : 0:0:auth_agent:INFO:
> authAgent_checkForReqTimeouts: 5737: Timedifference is c
> omputed to be greater than 1 sec: 3=20
> Apr  4 15:22:18 g4r8 : 0:0:nfxsh:NOTICE: cmd[0]: system version  :
> status[0]
> Apr  4 15:22:24 g4r8 : 0:0:nfxsh:NOTICE: cmd[1]: system show
> chassis  : status[0]
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0)
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0)
> wd1: dos partition I/O error
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0)
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0), retrying
> wd1c:  aborted command, id not found reading fsbn 0 (wd1 bn 0; cn 0
> tn 0 sn 0)
> wd1: dos partition I/O error
> Apr  4 15:23:05 g4r8 : 0:0:nfxsh:NOTICE: cmd[1]: system copy init  :
> status[11]
>=20
> _____________________________________________
> From: Sandrine Boulanger=20
> Sent: Wednesday, April 04, 2007 3:24 PM
> To: John Rogers; Raj Kumar; Elab
> Subject: RE: New BC filers
>=20
> This is a cheetah. Autoreboot is "on" on Toshiba:
> RCON-SSC_MGMT:1 > env view
>=20
> Current Environment Settings:
>         autoload         =3D on         ( off on )
>         autoreboot       =3D on         ( off on )
>         load_src         =3D disk       ( disk network )
>         load_opts        =3D mAt        ( m/s|A/a|d|t )
>         boot_dev         =3D wd0a       ( wd0a wd1a sc1 )
>         upgrade_prom     =3D yes        ( no yes )
>         env_reset        =3D no         ( no yes )
>         autolinkenable   =3D on         ( off on )
>         hw_qt            =3D off        ( off on )
>         hw_ft            =3D off        ( off on )
>         hw_diag          =3D off        ( off on )
>=20
> RCON-SSC_MGMT:2 >
>=20
> _____________________________________________
> From: John Rogers=20
> Sent: Wednesday, April 04, 2007 3:09 PM
> To: Raj Kumar; Elab
> Cc: Sandrine Boulanger
> Subject: RE: New BC filers
>=20
> G4r8 is racked, its in the start script, remember to p4 sync. IP is
> 10.2.8.4
>=20
> John
>=20
> _____________________________________________
> From: Raj Kumar=20
> Sent: Monday, April 02, 2007 5:58 PM
> To: Elab
> Cc: Sandrine Boulanger
> Subject: New BC filers
>=20
> John,
>=20
> Whenever you install/rack a new BC filer  in the lab can you notify
> us? We need to check some PROM settings on those.
>=20
> Thanks.
>=20
> PS: We will start with S-soak BC.
