HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error messages in syslog.log and system becomes sl...
Operating System - HP-UX
1838264
Members
3546
Online
110125
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
01-22-2001 05:36 AM
01-22-2001 05:36 AM
I'm getting in the syslog.log file some error messages related to some SCSI disc drives.
What can be the problem I'm facing and how to avoid it.
The autoraid has two controllers. One is connected to an HP-PB Fast/wide controller and the other is connected to a HSC Fast/wide controller.
Alternate path are configured on the lvm structure. But all alternate paths are on the other controller (ie: when system is running one controller is fully loaded and the other is idle).
can we load balance the controllers and how.
Thanks in advance for any help.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2001 06:28 AM
01-22-2001 06:28 AM
Re: Error messages in syslog.log and system becomes slow.
Are you running Predictive? It could be that Predictive is requesting the Primary Defect List (PDL) from the drives which can take more than the time allocated by the diagnostic routines. ( The list contains all the defects identified and spared by manufacturing process prior to shipping). Predictive only needs the defects which occur after factory shipping.
The latest Predictive patch should solve this, if this is the case.
Berlene
The latest Predictive patch should solve this, if this is the case.
Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2001 08:03 AM
01-22-2001 08:03 AM
Re: Error messages in syslog.log and system becomes slow.
Perhaps your hardware( cables) are not correctly plugged or terminated.In facts there are timeouts on your file: dev dev: 1f024200 and dev: 1f024300 are identifiers of disks.
In this situation less of perfomance is typical.
unsupported
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2001 04:48 AM
01-23-2001 04:48 AM
Solution
That is the standard layout after configuring alternate paths. There are two ways to correct it one temporary(until next boot) and one permanent.
Step 1, get a list of your primary/alt paths and make sure you know which goes with which.
example;
pri /dev/dsk/c1t1d0
alt: /dev/dsk/c2t3d0
run: pvchange -s /dev/dsk/c2t3d0
You have now swapped traffic to c2t3d0
Continue on and do 1 half of you disks.
The system will revert back after a reboot.
To correct this you need to rearrange the order the paths are listed in the lvmtab file.
do: strings /etc/lvmtab and note the order
Check and double check that the paths are corrct.
Now you should have;
pri: c2t3d0
alt: c1t1d0
run: vgreduce /dev/vg01 /dev/dsk/c1t1d0
run: vgextend /dev/vg01 /dev/dsk/c1t1d0
do; strings /etc/lvmtab and compare to results
above. The order shold have changed so that your
new primaries come before your alternates
Ref Doc: W3695486
Step 1, get a list of your primary/alt paths and make sure you know which goes with which.
example;
pri /dev/dsk/c1t1d0
alt: /dev/dsk/c2t3d0
run: pvchange -s /dev/dsk/c2t3d0
You have now swapped traffic to c2t3d0
Continue on and do 1 half of you disks.
The system will revert back after a reboot.
To correct this you need to rearrange the order the paths are listed in the lvmtab file.
do: strings /etc/lvmtab and note the order
Check and double check that the paths are corrct.
Now you should have;
pri: c2t3d0
alt: c1t1d0
run: vgreduce /dev/vg01 /dev/dsk/c1t1d0
run: vgextend /dev/vg01 /dev/dsk/c1t1d0
do; strings /etc/lvmtab and compare to results
above. The order shold have changed so that your
new primaries come before your alternates
Ref Doc: W3695486
If it ain't broke, let me have a look at it.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP