- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- StoreEasy Storage
- >
- SALDM.exe using 50% CPU on NAS4000
StoreEasy Storage
1754014
Members
3424
Online
108811
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
05-25-2006 07:52 AM
05-25-2006 07:52 AM
SALDM.exe using 50% CPU on NAS4000
Hi,
I have 2x HP NAS4000s (ProLiant DL380 G3) with W2K3 Enterprise. On one of them I noticed that the SALDM.exe process is running and it is using up about 50% of the CPU resources. The other one does not even have the process running and with more users and a heavier load on it the CPU is only around 2-10% utilization.
I have seen in other postings that the SALDM is actually the LED/LCD manager. LDM is the Logical Disk Manager. Typically, when this occurs it is either a problem with the LED/LCD driver.
Any more information on fixing this would be appreciated.
Thanks
Greg
I have 2x HP NAS4000s (ProLiant DL380 G3) with W2K3 Enterprise. On one of them I noticed that the SALDM.exe process is running and it is using up about 50% of the CPU resources. The other one does not even have the process running and with more users and a heavier load on it the CPU is only around 2-10% utilization.
I have seen in other postings that the SALDM is actually the LED/LCD manager. LDM is the Logical Disk Manager. Typically, when this occurs it is either a problem with the LED/LCD driver.
Any more information on fixing this would be appreciated.
Thanks
Greg
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2006 05:44 AM
05-26-2006 05:44 AM
Re: SALDM.exe using 50% CPU on NAS4000
Greg,
saldm.exe is the Server Appliance Local Display Manager, and is a service that is part of the Microsoft Server Appliance Kit (SAK) for NAS systems. It is there to allow server appliances to display information on small local displays (e.g. an LCD on the front panel).
Server Appliances that do not have these displays seem to still have this service installed and running. The service tries to talk to the non-existant display, hence the abnormal CPU usage. It is ok to disable the service "Local Display Manager" (i.e., change Start-up type to "Disabled") and reboot (you cannot stop the service otherwise). This prevents the problem occuring in the future.
saldm.exe is the Server Appliance Local Display Manager, and is a service that is part of the Microsoft Server Appliance Kit (SAK) for NAS systems. It is there to allow server appliances to display information on small local displays (e.g. an LCD on the front panel).
Server Appliances that do not have these displays seem to still have this service installed and running. The service tries to talk to the non-existant display, hence the abnormal CPU usage. It is ok to disable the service "Local Display Manager" (i.e., change Start-up type to "Disabled") and reboot (you cannot stop the service otherwise). This prevents the problem occuring in the future.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP