AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080918160025.0aaa98b0@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<joachim.thiessen@onstor.com>,<larry.scheer@onstor.com>,<dl-cstech@onstor.com>
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	BB375AF679D4A34E9CA8DFA650E2B04E08B3E4E3@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 18 Sep 2008 16:02:15 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Joachim Thiessen" <joachim.thiessen@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>, "dl-cstech"
 <dl-cstech@onstor.com>
Subject: Re: 3.3.0.0 upgrade secondary CF card...
Message-ID: <20080918160215.79eb4d5e@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08B3E4E3@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E08B3E4E3@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=US-ASCII
Content-Transfer-Encoding: 7bit

It really helps us en-gin-ears when you can be a little more precise
with the terminology.  Otherwise we get hopelessly confused.  If I
understand, you did not do "an upgrade of the secondary slot".  You did
a rough equivalent of a _system copy all -i_.

If that's what you did, and it succeeded, and the original 3.3 flash
was not bogus for some reason, then the new one should have
the /etc/mdrive_fstab file on it.  If it doesn't, then that's a bug.
We'll find out when Larry finished reproducing this workflow.

Cheers,

a

On Thu, 18 Sep 2008 15:46:01 -0700 "Joachim Thiessen"
<joachim.thiessen@onstor.com> wrote:

> I think figured out what went wrong. 
> 
> I replaced the CF card in slot 0 with a 3.3.0.0 card. Did the upgrade
> of the secondary card. Rebooted the filer and replaced the 3.3.0.0
> card with the 3.1.0.17 card. CF slot 0 had 3.1.0.17 and slot 1 had
> 3.3.0.0. Executed "system copy init" on CF card in slot 1. BSD Unix
> of CF card in slot 1 doesn't have a /etc/mdrive file. Therefore it
> cannot copy the file over.
> 
> ...Joachim
> 
> 
> ----- Original Message -----
> From: Larry Scheer
> To: Joachim Thiessen; dl-cstech
> Sent: Thu Sep 18 15:06:29 2008
> Subject: RE: 3.3.0.0 upgrade secondary CF card...
> 
> I am attempting to recreate your workflow in the development lab.
> So far I have not had a problem using the current release so I am
> downgrading a bobcat to 3.1.0.17.
> 
> If I understand your problem correctly the file /etc/mdrive_fstab
> goes MIA somewhere in the copy/cloning process that you are doing.
> 
> Correct me if I am wrong here, but you are not actually using system
> upgrade in this workflow. You are just using master 3.3.0.0 flashes
> and systems with 3.1.0.17. BTW: If the version of 3.3.0.0 you are
> using is not the GA version I will need to know precisely what
> version it is. (output of system show version or chassis view version)
> 
> Larry
> 
> -----Original Message-----
> From: Joachim Thiessen 
> Sent: Thursday, September 18, 2008 2:02 PM
> To: Larry Scheer; dl-cstech
> Subject: Re: 3.3.0.0 upgrade secondary CF card...
> 
> - I'm installing five brand new systems. 
> - All five system came with 3.1.0.17.
> - I have three new CF cards with 3.3.0.0 
> - replaced 3.1.0.17 CF card with 3.3.0.0 card
> - configure the system on the 3.3.0.0 card
> - upgrade secondary CF card (3.1.0.17).
> - reboot the system with "system reboot -s"
> - remove the "real" 3.3.0.0 CF card while the system is powered off
> - insert the original 3.1.0.17 CF card
> - upgrade the card from the CF card that was previously a 3.1.0.17
> card, but is now a 3.3.0.0 card.
> 
> That fails. I can send you the error message later. I have three more
> systems to install.
> 
> Cheers...
> 
> ...Joachim
> 
> 
> ----- Original Message -----
> From: Larry Scheer
> To: Joachim Thiessen
> Sent: Thu Sep 18 13:45:20 2008
> Subject: RE: 3.3.0.0 upgrade secondary CF card...
> 
> What are the missing files? What release is on the primary flash that
> is running the system copy all?
> 
> I am having difficulty parsing this statement:
> ..from a CF card that was 3.1.0.x before.
> 
> Do you mean?
> ..to a CF card that was 3.1.0.x before.
> 
> If your primary flash is running 3.1.0.x you are copying 3.1.0.x to
> the standby flash. You do know this correct?
> 
> -----Original Message-----
> From: Joachim Thiessen 
> Sent: Thursday, September 18, 2008 1:36 PM
> To: dl-cstech
> Subject: Re: 3.3.0.0 upgrade secondary CF card...
> 
> I figure it out...
> 
> You need an "original" 3.3.0.0 CF card directly from Abdalla. If you
> do a:
> 
> system copy init
> system copy all
> 
> ..from a CF card that was 3.1.0.x before. The "system copy init" will
> complain about two missing files, and the "system copy all" will fail.
> 
> Regards...
> 
> ...Joachim
> 
> 
> ----- Original Message -----
> From: Joachim Thiessen
> To: dl-cstech
> Sent: Thu Sep 18 13:18:12 2008
> Subject: Re: 3.3.0.0 upgrade secondary CF card...
> 
> I forgot to include the elog entry...
> 
> Sep 18 13:00:02 pufs101 newsyslog[32229]: logfile turned over
> Sep 18 13:02:52 pufs101 : 0:0:nfxsh:NOTICE: command[4]: system copy
> all : status[11]
> 
> No more information. Elog level is info.
> 
> Command:
> 
> system vers -s
> Failed to get a valid version
> 
> 
> 
> ----- Original Message -----
> From: Joachim Thiessen
> To: dl-cstech
> Sent: Thu Sep 18 13:03:56 2008
> Subject: 3.3.0.0 upgrade secondary CF card...
> 
> Hi,
> 
> I'm trying to upgrade the secondary CF card from the primary card on
> a system running 3.3.0.0.
> 
> system upgrade -s
> 
> ...doesn't work as it needs a ftp and/or url. 
> 
> system copy init
> system copy all
> 
> ...takes forever and at the end fails. Is there a workaround or is
> this a feature? :-/
> 
> Thanks...
> 
> ...Joachim
