AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<mtracy@css.glasshouse.com>,<dl-cstech@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	4BC43E8D.2000307@css.glasshouse.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 13 Apr 2010 08:08:46 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: Michael Tracy <mtracy@css.glasshouse.com>
Cc: DL-ONStor-cstech <dl-cstech@lsi.com>
Subject: Re: How to pro-actively tell if a CF is bad
Message-ID: <20100413080846.24f457ef@ripper.onstor.net>
In-Reply-To: <4BC43E8D.2000307@css.glasshouse.com>
References: <4BC43E8D.2000307@css.glasshouse.com>
Organization: LSI
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

On Tue, 13 Apr 2010 03:51:09 -0600 Michael Tracy
<mtracy@css.glasshouse.com> wrote:

> Hey all
> Customer tried to run an upgrade and found the secondary CF was bad.
> After we replaced the CF, the upgrade went well. Customer's question
> now is if there is any way to tell if a CF is bad pro-actively? To
> quote the reseller: ==============
> They would like to know whether any error logs come out when system
> cannot able to recognize CF card.  The reason is they would like to
> avoid to see the problem right before upgrade the EverON.
> 
> Are there any logs that I would watch out for?  Or are there any
> better way to monitor the CF card? ==============
> 
> I can't think anything other than run a periodic "system copy all -i"
> Any better way of doing this?

I can't think of any beyond noticing write/read errors to the device.
I believe the periodic system get all does read the secondary card.
Doing regular "system copy all -i" would not be a good thing, as it
will hasten the expiry of the card since they have a limited number of
writes.