Re: [foxboro] rcopy, rmount on AW51D very slow

  • From: Joe Riccardi <joe@xxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Mon, 17 Feb 2014 20:58:45 -0800

Let me explain a little more... I'm building off site test beds with system 
parts from other nodes not in operation. I have a number of earlier posts 
looking for help because I don't know if anyone has gone this far. I am 
restoring the spare boxes from streaming tapes from the production system. My 
intent is to create a mini-cloned Node of the production system for just the 
critical AWs. Just FYI, all AWs have mirrored external drives. Then, when a 
critical AW fails, the plan is to swap out the production AW/external drive 
with the test bed cloned AW/external drive. I have a older V6.3 UNIX and V6.4 
Windows-NT node. I have had success cloning the Windows node, but am struggling 
with the idiosyncrasies of the UNIX node. The common, but not too 
understandable issue of marrying AW51Es with replacement drives, NVRAM issues, 
blah, blah, blah. I still have not seen anything in writing from anyone that 
actually explains the exact problem, and the procedure to reinstall and reboot 
replacement AW51Es with replacement drives. 

The backups are fairly old in my opinion so I would like to get more up to date 
ones. I don't think we have to shutdown and reboot the Windows-NT boxes but we 
definitely have to for the UNIX boxes.

Soooooooo, wish me luck...

Sent from my iPhone

> On Feb 17, 2014, at 5:44 PM, "Joseph M. Riccardi" <Joe@xxxxxxxxxxxxx> wrote:
> 
> Welllllllllllllllllllll, my previous instructions to the site were that we
> need to get more up to date streaming tape backups.  But that would require
> a reboot and if a critical AW51 will not reboot if the NVRAM battery is
> dead...  Without knowing the condition of the NVRAM battery, we cannot take
> a chance so my instructions now to the site are DO NOT ATTEMPT TO DO ANY
> STREAMING TAPE BACKUPS.  I always have avoided rebooting the old AW51s for
> that specific reason.  Having verrrrrrrry old backup tapes is not ideal;
> having a critical AW51 not reboot successfully would be disastrous...
> Soooooooooooooo, we are caught between a rock and a hard place as they
> say...
> 
> PS.  It is still not clear to me if this occurs on a reboot or a power loss,
> or both?
> 
> 
> Joseph M. Riccardi
> 386-441-0250 Office
> 386-451-7607 Cell
> 
> Joe@xxxxxxxxxxxxx
> 
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A. Adams
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Gunter, Matt
> Sent: Monday, February 17, 2014 3:11 PM
> To: 'foxboro@xxxxxxxxxxxxx'
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> So Joe,
> 
> What would you do if you knew the NVRAM battery was dead?  Would you try to
> replace it while the box running in order to keep the eeprom values?  Don't
> you eventually have to shut down the box to replace?
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Joseph M. Riccardi
> Sent: Thursday, February 13, 2014 6:20 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> I forgot to ask, how can I find out if the NVRAM battery is dead?  It seems
> like a failure to reboot is a little too late...
> 
> 
> Joseph M. Riccardi
> 386-441-0250 Office
> 386-451-7607 Cell
> 
> Joe@xxxxxxxxxxxxx
> 
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A. Adams
> 
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of William C Ricker
> Sent: Thursday, February 13, 2014 2:57 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> OK, permit me to revise and extend my remarks.
> 
> The Solaris standard command for looking at and changing NVRAM is "eeprom"
> There's a man page on it.  Without arguments, it prints out the full set of
> entries.
> 
> "prom_aw" is the Foxboro one.  It's in the system with the Mirrored Drive/
> Disksuite stuff, under /usr/local/medusa.  I can't say now that I know
> exactly what it does, but it does apply the settings for the mirrored drive
> which allow the station to boot from a backup if the first in a mirrored
> pair has failed.
> 
> Further, I can't say which of these commands is used to program NVRAM
> settings on system install, but that programming function is performed
> during this install process.
> 
> Regards,
> 
> William C Ricker
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of William C Ricker
> Sent: Thursday, February 13, 2014 3:32 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> NVRAM is also programmed by the IA Install process.  Further, to see what's
> in it, the Solaris command "eeprom" works as does the Foxboro command
> "awprom".
> Both of these can also change the content.  I know "eeprom" does individual
> settings and "awprom" is used to put in the full set as required by the
> Foxboro install.  I think, however, that each can do both functions. (I
> think I have both names right)
> 
> If you're going to play with them, I suggest offline.  You can always reset
> the NVRAM by doing the "ia_install" part of a Day 0 install.  That leaves
> the NVRAM set up even if you then swap out the disk.
> 
> William C Ricker
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Joseph M. Riccardi
> Sent: Thursday, February 13, 2014 3:04 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> Stanley,
> 
> Thanks for the feedback but I know I can set the NVRAM using the setenv
> command at the ok prompt.  However I cannot find any manual that
> shows/explains the choices.
> 
> But what I am asking is can I read (printenv) the NVRAM
> parameters/configuration on a running AW (without shutting it down, stop a)?
> I need to know the NVRAM parameters/configuration on all of the running AWs
> before they fail, but I cannot shut them down to do it...
> 
> 
> Joseph M. Riccardi
> 386-441-0250 Office
> 386-451-7607 Cell
> 
> Joe@xxxxxxxxxxxxx
> 
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A. Adams
> 
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Brown, Stanley
> Sent: Thursday, February 13, 2014 11:26 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> Yes, you can set the NVRAM manually from the OK prompt. Given a working
> machine there really are not all that many things to change, although some
> of them are a bit long (path names).
> 
> 
> -----Original Message-----
> From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Joseph M. Riccardi
> Sent: Thursday, February 13, 2014 01:06 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> Tom,
> 
> Your comment about the NVRAM battery has me wondering if that is the problem
> I am having with this AW51E I just restored.  Everything goes well until I
> powered down and tried to reboot.  That is when I get the error "Can't open
> boot device".  And I remember in the past that when the NVRAM battery died,
> the symptoms were always that the hard drive failed.  Is this correct about
> the symptom and the error message; are they related to a dead NVRAM battery?
> 
> This now generates another question...  Is there any other way to get the
> NVRAM configuration besides Stop A... printenv?  Can I get them from a
> running AW without shutting it down?  Once the AW51 dies from a dead NVRAM
> battery, and the box is replaced, it's too late to get the old NVRAM
> parameters then...
> 
> The UNIX Gods have not been kind to me these last 2 weeks...
> 
> Thanks
> 
> 
> Joseph M. Riccardi
> 386-441-0250 Office
> 386-451-7607 Cell
> 
> Joe@xxxxxxxxxxxxx
> 
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A. Adams
> 
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Tom Vandewater
> Sent: Thursday, February 13, 2014 5:57 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
> 
> Glad that solved your problem Dave. And very glad the NVRAM didn't get you.
> I wonder if Duc was wearing khakis when you called him?  Like Jake in the
> State Farm commercial;<)   Scott gave you some good advice but it is hard to
> give up on AW's that were so stable. Alas, your hand is being forced by both
> Foxboro and Sun.
> Cheers,
> Tom
> 
>> On Feb 13, 2014, at 5:02 AM, <dave.caldwell@xxxxxxxxxxxxxx> wrote:
>> 
>> Many thanks to all for the assistance. :>)
>> 
>> I started killing urfs_xserver (unix remote file system? - just a
>> hunch)
> processes since I removed all remote mounts across the entire system and
> still had 22 of these processes running, but after killing about 8 or so I
> chickened out and rebooted.
>> 
>> Problem solved.
>> 
>> I did speak to Duc yesterday. Had I known it was $3.99 a minute I 
>> would
> have asked him what he was wearing!
>> 
>> To Scott's comment... I seem to remember Duc hugging an AW51 and 
>> mumbling
> something like "I'll give you my Sun box when you pry it  from my cold dead
> hands..." ;>)
>> 
>> 
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx
>> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Landry, Scott
>> Sent: Thursday, February 13, 2014 2:01 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
>> 
>> 
>> 
>> 
>>  Don't be the last plant on earth with a SUN box.
>> 
>> 
>>   Just saying,
>> 
>> 
>>   Scott
>> 
>> ________________________________________
>> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Tom Vandewater [tjvandew@xxxxxxxxx]
>> Sent: Wednesday, February 12, 2014 9:00 PM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] rcopy, rmount on AW51D very slow
>> 
>> Dave,
>>   I remember this happening on the Sun boxes before. We never figured 
>> out
> why but I can almost guarantee that rebooting 04AW01 will solve the problem.
> If you let Duc know you are going to reboot it he will probably come in free
> of charge because he wants the Sun boxes to run forever. It pains him so to
> reset the uptime counter to 0 days;<). He also knows that the NVRAM battery
> may be dead and the box may not be able to reboot. That creates an even more
> serious issue that will probably result in you paying Duc whatever price he
> demands;<)
>> 
>> Tom VandeWater
>> Control Conversions, Inc.
>> 
>>> On Feb 12, 2014, at 1:06 PM, Duc M Do <duc@xxxxxxxxxx> wrote:
>>> 
>>> My answering the phone at Duc's Technical Support will cost you 3.99 
>>> a minute.
>>> Duc
>>> 
>>> 
>>>> On Wed, Feb 12, 2014 at 11:01 AM, <dave.caldwell@xxxxxxxxxxxxxx> wrote:
>>>> 
>>>> All Knowing List,
>>>> 
>>>> I have an AW51D(04AW01) that is extremely slow to rmount from any 
>>>> another AW (or to respond to commands across the remote connection 
>>>> once
> rmounted).
>>>> The rmount takes about 5 minutes, as does the ls -l, cp, etc...
>>>> 
>>>> I can rmount other AW file systems to 04AW01 no problem-- just very 
>>>> slow when others rmount 04AW01.
>>>> 
>>>> Ping, telnet, diplays, icc, etc. are all good.
>>>> 
>>>> I checked disk usage on the AW in question and it looked good.
>>>> 
>>>> I noticed many processes belonging to /usr/fox/exten/urfs_xserver -m 
>>>> /etc/fox/dsamap and one for urfs_om_daemon.
>>>> My limited understanding is that these processes govern the remote 
>>>> file system.
>>>> I did not attempt to kill or restart any processes, but was tempted.
>>>> 
>>>> Lastly, I'd like to do as my friend Duc suggests and avoid rebooting 
>>>> this box (answer your phone Duc).
>>>> 
>>>> Any ideas???
>>>> Thanks,
>>>> Dave
>>> 
>>> 
>>> 
>>> 
>>> _____________________________________________________________________
>>> _ _ 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:             //www.freelists.org/list/foxboro
>>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>> 
>> 
>> ______________________________________________________________________
>> _ 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:             //www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then delete
> this message from your system. Please do not copy it or use it for any
> purposes, or disclose its contents to any other person. This email comes
> from a division of the Invensys Group, owned by Invensys plc, which is a
> company registered in England and Wales with its registered office at 3rd
> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
> a list of European legal entities within the Invensys Group, please select
> the Legal Entities link at invensys.com. Invensys PLC is owned by the
> Schneider-Electric Group.
>> 
>> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
> affiliates).
>> 
>> 
>> 
>> 
>> ______________________________________________________________________
>> _ 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:             //www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>> 
>> 
>> 
>> 
>> 
>> ______________________________________________________________________
>> _ 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:             //www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> ________________________________
> 
> The information contained in this message and any attached files may be
> privileged and/or confidential and protected from disclosure. If you are not
> the intended recipient, any disclosure, copying, distribution or use of any
> of the information contained in or attached to this transmission is strictly
> prohibited. If you have received this transmission in error, please so
> notify the sender immediately without reading it. Also, please promptly
> destroy the original transmission and its attachments. Any views or opinions
> presented in this message or attachments are those of the author and do not
> necessarily represent those of KapStone Paper and Packaging Corporation or
> its subsidiaries.
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 140213-1, 02/13/2014 Tested on: 2/13/2014 3:32:02 PM
> avast! - copyright (c) 1988-2014 AVAST Software.
> http://www.avast.com
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 140213-1, 02/13/2014 Tested on: 2/13/2014 5:56:38 PM
> avast! - copyright (c) 1988-2014 AVAST Software.
> http://www.avast.com
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 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:             //www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 
 
 
_______________________________________________________________________
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:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts:

  1. Home
  2. foxboro
  3. Archive
  4. 02-2014