- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- AutoRAID timeout
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2005 01:18 AM
тАО09-26-2005 01:18 AM
AutoRAID timeout
We recently relocated the D-class server and 12H AutoRAID to a datacenter. The move went fine, all connections were clearly labeled, and had no problems upon startup. The system name did not change, just the ip address information.
After the system started up, I have been getting intermittent errors from the arraymgr:
=======================================
Mon Sep 26 04:11:56 2005
Array Monitor Daemon
=======================================
access error: autoraid server timed out getting disk array status on /dev/rdsk/c3t0d0 at tsihp1
I may get one or two of these a day, no specific time interval. I have not seen these messages in the past 4 years we have had this system running. System performance seems to be fine otherwise, and the user load is much lower than it used to be.
Is this the equivalent to the check engine light coming on when you need your oil changed?
Or is this a deeper issue?
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2005 02:41 AM
тАО09-26-2005 02:41 AM
Re: AutoRAID timeout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2005 03:09 AM
тАО09-26-2005 03:09 AM
Re: AutoRAID timeout
this is maybe a simple network problem that have been introduced by changing the IP address.
Most likely, a DNS lookup by the Array Monitor deamon did not succeed.
Please check if
nslookup hostname
nslookup ipaddress
works fine and gives the correct information.
best regards
Stefan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2005 03:32 PM
тАО09-26-2005 03:32 PM
Re: AutoRAID timeout
/sbin/init.d/hparray stop/start.
If not , do it and observe.
It seems from error that the arraymond deamon is not able to get status of that LUN from the array causing time-out. The deamon runs at every 15 mints interval.
Are you getting this error only for LUN /dev/rdsk/c3t0d0 ?
Do you get any slow response running vgdisplay of a VG to which this LUN belongs or pvdisplay ?
What about the output shown by
arraydsp -a
arraydsp -l /dev/rdsk/c3t0d0
logprint
arraylog -u
arraylog -e
As ACS said above, you need to re-seat each disk after shutting down the array. I believe that if any one of the disks underneath the LUN is not working properly ( like initialising, rotation delays or media problem etc ) consitutes overall delay of LUN response. If the response time of a LUN goes above than that arraymond deamon expects , time-out would occure.
This may happen because of bad seating of disk or any such hardware physical problems which could be possible in the transit.
Check for termination as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2005 07:50 PM
тАО09-26-2005 07:50 PM
Re: AutoRAID timeout
Also examin your /var/adm/syslog/syslog.log file if it contains any "SCSI time out" messages most properly this is an issue in your SCSI bus (cables, and terminators). check them well.
Another thing check the firmware version of your array and installed disks.
check if your array respond well for arraymgr commands. try to shut down the array using
arraymgr -s shut
then go and see the array LCD if it display that the array is shutted down or not. if not, this may prove that you have a problem in your SCSI bus.
use: "arraymgr -s start" to start the array again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2005 01:07 AM
тАО09-27-2005 01:07 AM
Re: AutoRAID timeout
ACS - I changed the timeout to 60 seconds, still got them this morning, I will pump it up to 120.
I did find a SCSI timeout this morning (the only one in syslog.log, even though it has been running for 10 days). It it possible that it will see a timeout when the array is backing up to tape? If arraymond is checking every 15 minutes, I am only seeing the errors once, maybe twice a day.
I don't think it is network related (all the internal references check out).
I did also see some SCSI: Abort Tag messages and and LVM: Recovered Path.
If I try to look at arraydsp or any of the other commands, I get "arraydsp cannot display - may be initializing."
I am having someone look at the unit (we moved it 400 miles away) to see what it reads onboard. But, during testing, it did read all clear.
Thanks everyone, points are forthcoming...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2005 05:52 PM
тАО09-27-2005 05:52 PM
Re: AutoRAID timeout
Check the SCSI cables an Terminiators. try to replace them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2005 07:09 PM
тАО09-27-2005 07:09 PM
Re: AutoRAID timeout
it looks like the ARMserver deamon is not running and this is the reason why you got this message.
I don't think that this is a problem with the Autoraid, because otherwise your syslog should be filled with SCSI errors or/and the luns are not accessible.
In many cases, I saw this error when there have been wrong IP addresses for this host in the /etc/hosts file (in your case: still the old IP ?) and the IP address was one of the things you have changed in this environment.
If the IP configuration is OK, then please try the following:
- /sbin/init.d/hparray stop
- ps -ef | grep ARM
- if ARMserver is still running kill the process
- /sbin/init.d/hparray start
- see if there are any messages on the console or in syslog.log
- after a few minutes run "arraydsp -i". Is this still giving the same message ?
The ARMserver is not needed to access the Luns, but only to control the diskarray (diagnostics, create new luns etc.) so the above can be done online.
best regards
Stefan