Re: [foxboro] /rem/r0 File system error?

We've had a few customer units in for refurbishment lately that were
acting "funny". Sometimes not booting, sometimes not keeping time and
sometimes complaining about missing partitions. This NVRAM chip stores
various configuration parameters (e.g. boot device, amount of RAM to
test), maintains the clock, and also contains the IDPROM data, which is
composed of the Ethernet address, date of manufacture, hostid, a version
number, and a checksum. The battery in the NVRAM is only good for 5 to 8
years. Process industries probably get more years out of them because
the workstations run 24/7. Most times, when the workstation was acting
"funny" [according to customer reports], replacing and re-programming
the NVRAM fixed the problem.

You can check it by going to the OpenBoot monitor and typing "banner".
This will display your banner. If your boot banner has FF:FF:FF:FF:FF:FF
(or 00:00:00:00:00:00) for it's MAC address then your NVRAM is bad. This
is not an absolute test. Other indications include complains of "Invalid
NVRAM Format" and "Invalid IDPROM Contents".=20

The best approach is to replace and program the NVRAM every 5-10 years
before there is a problem. Just make it part of your regular PM.

So, this may not be your particular problem, but it's something to
consider based upon experience.

Best Regards,=20
Ken Heywood=20
Process Control Services, Inc.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Duc M Do
Sent: Monday, November 12, 2007 10:05 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] /rem/r0 File system error?

Hmm, I don't remember right off the top of my head, but I bet it's the
original NVRAM that came with the box, which is mid-to-late 90s vintage.

What's your reason for this question?

Duc


On Mon, November 12, 2007 8:15 pm, Ken Heywood wrote:

> When was the last time you changed the NVRAM?
>
> Best Regards,=3D20
> Ken Heywood=3D20
> Process Control Services, Inc.
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of duc.do@xxxxxxxxxxxxxx
> Sent: Monday, November 12, 2007 4:29 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] /rem/r0 File system error?
>
> Hi list,
>
> I got an AW-51B box that went flaky on me and it's got me perplexed.
> Seems like /rem/r0 is corrupted per these responses:
>
>    17AW01# cd /rem
>    17AW01# ls -lad r*
>    r0: Bad file number
>    drwxrwxr-x   2 root     staff        512 Jun  8  1999 r1
>
>    17AW01# rm -r r0
>    r0: Bad file number
>
>    17AW01# rm -r ./r0
>    ./r0: Bad file number
>
>    17AW01# mv ./r0 ./r00
>    mv: cannot access ./r0
>
> There's no problem with /rem/r1:
>
>    17AW01# rm -r r1
>    17AW01# mkdir r1
>
>    17AW01# ls -ld r1
>    drwxr--r--   2 root     other        512 Nov 12 16:27 r1
>
> I shut it down to single user and ran fsck. Nothing is flagged as
wrong
> or corrupted (aside from the usual "FILE SYSTEM STATE IN SUPERBLOCK IS
> WRONG; FIX?" message).
>
> I've also rebooted it completely (-i6) without any improvment.
>
> Pertinent information:
>
> AW-51B running V6.2.1 (Solaris 2.5.1). Plenty of disk space:
>
>    17AW01# df -kt
>    Filesystem            kbytes    used   avail capacity  Mounted on
>    /dev/md/dsk/d0         49855   15539   29336    35%    /
>    /dev/md/dsk/d4        822151  274368  465573    38%    /usr
>    /proc                      0       0       0     0%    /proc
>    fd                         0       0       0     0%    /dev/fd
>    /dev/md/dsk/d2         37927   13949   20188    41%    /var
>    swap                  231976      84  231892     1%    /tmp
>    /dev/md/dsk/d5       2719925  692877 1755058    29%    /opt
>
> Any idea? Thanks!
>
>
> Duc
>
> --=3D3D20
> DCS Group
> Carrollton Plant
> Dow Corning Corp
> Carrollton, KY, US=3D3D20




=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: