Re: [j-nsp] Software Upgrade failures on EX4200

[Chuck Anderson]

Personally I would stick with 12.3.  They came out with another service 
release, 12.3R12-S6.

On Thu, Sep 28, 2017 at 03:26:36AM +1000, Kamal Dissanayaka wrote:
> Hi Jason,
> 
> Thanks for the response,
> This happened to us irrespective of version, some switches were from
> 12.3.r9 to 15.1.r2.9 and some were from 15.1.r2.9 to 15.1.R6s2.1  as far as
> I remember.
> 
> 
> Same thing here with the JTAC support, they say go to the site and upgrade
> using USB if the device fails during upgrade. They don't understand
> practical difficulties when you have frequent failures.
> 
> Best Regards
> 
> Kamal
> 
> 
> 
> 
> On Wed, Sep 27, 2017 at 11:58 PM, Jason Healy  wrote:
> 
> > On Sep 27, 2017, at 1:56 AM, Kamal Dissanayaka 
> > wrote:
> > >
> > > The issue with this is remote upgrades. Remote upgrades fails randomly
> > and
> > > some has to visit the sit to fix it. Is there any way fix it ?
> >
> > What version were you running previously?  We bumped all of our 4200s from
> > 12.x to 15.x and got badly burned with switches that didn't come up.
> >
> > JTAC told us (after the fact) that we needed to be on the VERY LATEST 12
> > series before making the upgrade or else there might be 'issues'.  Ended up
> > having to do a format reinstall from USB on about a third of the switches.
> >
> > Jason
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Software Upgrade failures on EX4200

[Kamal Dissanayaka]

Hi Jason,

Thanks for the response,
This happened to us irrespective of version, some switches were from
12.3.r9 to 15.1.r2.9 and some were from 15.1.r2.9 to 15.1.R6s2.1  as far as
I remember.


Same thing here with the JTAC support, they say go to the site and upgrade
using USB if the device fails during upgrade. They don't understand
practical difficulties when you have frequent failures.

Best Regards

Kamal




On Wed, Sep 27, 2017 at 11:58 PM, Jason Healy  wrote:

> On Sep 27, 2017, at 1:56 AM, Kamal Dissanayaka 
> wrote:
> >
> > The issue with this is remote upgrades. Remote upgrades fails randomly
> and
> > some has to visit the sit to fix it. Is there any way fix it ?
>
> What version were you running previously?  We bumped all of our 4200s from
> 12.x to 15.x and got badly burned with switches that didn't come up.
>
> JTAC told us (after the fact) that we needed to be on the VERY LATEST 12
> series before making the upgrade or else there might be 'issues'.  Ended up
> having to do a format reinstall from USB on about a third of the switches.
>
> Jason
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Software Upgrade failures on EX4200

[Jason Healy]

On Sep 27, 2017, at 1:56 AM, Kamal Dissanayaka  wrote:
> 
> The issue with this is remote upgrades. Remote upgrades fails randomly and
> some has to visit the sit to fix it. Is there any way fix it ?

What version were you running previously?  We bumped all of our 4200s from 12.x 
to 15.x and got badly burned with switches that didn't come up.

JTAC told us (after the fact) that we needed to be on the VERY LATEST 12 series 
before making the upgrade or else there might be 'issues'.  Ended up having to 
do a format reinstall from USB on about a third of the switches.

Jason
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Software Upgrade failures on EX4200

[Kamal Dissanayaka]

Hi Nicholas,

Thanks for the reply,

Yes, MD5 check sum all correct.

I believe this some thing related to corruption in the partition however
switch does show any errors with fsck and nand-mediack on storage.

 I want to check any one in the list had same problem and anyway to process
remote upgrade on those devices.


Thank you

Kamal

On Wed, Sep 27, 2017 at 9:27 PM, Nicholas Oas 
wrote:

> Does the version you are upgrading FROM seem to matter? Also is the md5sum
> on your jinstall .tgz correct?
>
> On Sep 27, 2017 1:57 AM, "Kamal Dissanayaka"  wrote:
>
>> Hi Experts
>>
>>
>> Has anyone experience if error "*g_vfs_done():da1[READ(offset=4194304,
>> length=16384)]error = 6" *when upgrading EX4200 switches? The switch will
>> not boot after reboot though it suggest to reboot. We can manually boot it
>> through console and the see the partition that was backup before upgrade
>> is
>> corrupted.
>>
>> The issue with this is remote upgrades. Remote upgrades fails randomly and
>> some has to visit the sit to fix it. Is there any way fix it ?
>>
>>
>> 1.  Upgrade
>>
>> root> request system software add
>> /var/tmp/jinstall-ex-4200-15.1R2.9-domestic-signed.tgz
>>
>> umass1: at uhub0 port 1 (addr 3) disconnected
>>
>> (da1:umass-sim1:1:0:0): lost device
>>
>> umass1: detached
>>
>>
>>
>> Checking pending install on fpc0
>>
>>
>>
>> Validating on fpc0
>>
>> Done with validate of
>>  on VC members
>>
>>
>>
>> fpc0:
>>
>> Verify the signature of the new package
>>
>> *g_vfs_done():da1[READ(offset=4194304, length=16384)]error = 6*
>>
>>
>> Verified jinstall-ex-4200-15.1R2.9-domestic.tgz signed by
>> PackageProductionRSA_2015 method RSA2048+SHA1
>>
>> WARNING: A reboot is required to install the software
>>
>> WARNING: Use the 'request system reboot' command immediately
>>
>>
>>
>> {master:0}
>>
>>
>>
>> 2. Upgrade finally fail and stop at
>>
>>
>>
>> * FILE SYSTEM MARKED CLEAN *
>>
>> tunefs: soft updates remains unchanged as enabled
>>
>> [: -eq: unexpected operator
>>
>> Installing disk0s3d:/jinstall-ex-4200-15.1R2.9-domestic-signed.tgz
>>
>>
>>
>> gzip: stdin: invalid compressed data--format violated
>>
>> tar: Unexpected EOF in archive
>>
>> tar: Unexpected EOF in archive
>>
>> tar: Error is not recoverable: exiting now
>>
>> *** The installer exited with status 2 ***
>>
>> *** The installation is unsuccessful!!! ***
>>
>> A shell has been started. type exit to reboot:
>>
>> #
>>
>>
>> 3. when you exit it will boot with old image, and
>>
>>
>> > show system storage partitions
>>
>> fpc0:
>>
>> 
>> --
>>
>> Boot Media: internal (da0)
>>
>> Active Partition: da0s2a
>>
>> Backup Partition: da0s1a
>>
>> Currently booted from: active (da0s2a)
>>
>>
>>
>> Partitions information:
>>
>>   Partition  Size   Mountpoint
>>
>>   s1a183M   altroot
>>
>>   s2a184M   /
>>
>>   s3d369M   /var/tmp
>>
>>   s3e123M   /var
>>
>>   s4d62M/config
>>
>>
>>
>> {master:0}
>>
>> root>
>>
>>
>>
>> {master:0}
>>
>> root> show system snapshot media internal
>>
>> fpc0:
>>
>> 
>> --
>>
>> error: /dev/da0s1a is not a JUNOS snapshot
>>
>>
>>
>> {master:0}
>>
>> root> show system snapshot
>>
>> fpc0:
>>
>> 
>> --
>>
>> error: external media missing or invalid
>>
>>
>>
>>
>> Thank you
>>
>>
>> Kamal
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Software Upgrade failures on EX4200

[Kamal Dissanayaka]

Hi Experts


Has anyone experience if error "*g_vfs_done():da1[READ(offset=4194304,
length=16384)]error = 6" *when upgrading EX4200 switches? The switch will
not boot after reboot though it suggest to reboot. We can manually boot it
through console and the see the partition that was backup before upgrade is
corrupted.

The issue with this is remote upgrades. Remote upgrades fails randomly and
some has to visit the sit to fix it. Is there any way fix it ?


1.  Upgrade

root> request system software add
/var/tmp/jinstall-ex-4200-15.1R2.9-domestic-signed.tgz

umass1: at uhub0 port 1 (addr 3) disconnected

(da1:umass-sim1:1:0:0): lost device

umass1: detached



Checking pending install on fpc0



Validating on fpc0

Done with validate of
 on VC members



fpc0:

Verify the signature of the new package

*g_vfs_done():da1[READ(offset=4194304, length=16384)]error = 6*

Verified jinstall-ex-4200-15.1R2.9-domestic.tgz signed by
PackageProductionRSA_2015 method RSA2048+SHA1

WARNING: A reboot is required to install the software

WARNING: Use the 'request system reboot' command immediately



{master:0}



2. Upgrade finally fail and stop at



* FILE SYSTEM MARKED CLEAN *

tunefs: soft updates remains unchanged as enabled

[: -eq: unexpected operator

Installing disk0s3d:/jinstall-ex-4200-15.1R2.9-domestic-signed.tgz



gzip: stdin: invalid compressed data--format violated

tar: Unexpected EOF in archive

tar: Unexpected EOF in archive

tar: Error is not recoverable: exiting now

*** The installer exited with status 2 ***

*** The installation is unsuccessful!!! ***

A shell has been started. type exit to reboot:

#


3. when you exit it will boot with old image, and


> show system storage partitions

fpc0:

--

Boot Media: internal (da0)

Active Partition: da0s2a

Backup Partition: da0s1a

Currently booted from: active (da0s2a)



Partitions information:

  Partition  Size   Mountpoint

  s1a183M   altroot

  s2a184M   /

  s3d369M   /var/tmp

  s3e123M   /var

  s4d62M/config



{master:0}

root>



{master:0}

root> show system snapshot media internal

fpc0:

--

error: /dev/da0s1a is not a JUNOS snapshot



{master:0}

root> show system snapshot

fpc0:

--

error: external media missing or invalid




Thank you


Kamal
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp