- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Bad location found in Memory
Operating System - Tru64 Unix
1747985
Members
4816
Online
108756
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
12-10-2008 01:19 PM
12-10-2008 01:19 PM
Bad location found in Memory
When I change the mirror disk in order to rebuild the domainX with error:
The system and SAP show to be up but still getting the "balancing error"
I have verify LAN connectivity and is good.
The following warnings appear when system was being "boot"
1. Warning: Bad location found in Memory, memory interleaving is disable to prevent O.S.. occupation of bad memory space, use SIMM_Callout to isolate failure".
2. Chk_bf_quota: group quota underflow for group 7
3. /sbin/vc3d/s95xlogin/usr/df/config/xconfig.nc not found
Please help me on this, thanks in advanced!!
The system and SAP show to be up but still getting the "balancing error"
I have verify LAN connectivity and is good.
The following warnings appear when system was being "boot"
1. Warning: Bad location found in Memory, memory interleaving is disable to prevent O.S.. occupation of bad memory space, use SIMM_Callout to isolate failure".
2. Chk_bf_quota: group quota underflow for group 7
3. /sbin/vc3d/s95xlogin/usr/df/config/xconfig.nc not found
Please help me on this, thanks in advanced!!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2008 04:53 AM
12-11-2008 04:53 AM
Re: Bad location found in Memory
1. Warning: Bad location found in Memory, memory interleaving is disable to prevent O.S.. occupation of bad memory space, use SIMM_Callout to isolate failure".
The system detected a problem with a memory SIMM during boot. SIMM_CALLOUT is an SRM console variable you can set before booting on some Alphas. On the next boot, more extensive information will be provided about the possible hardware problem.
2. Chk_bf_quota: group quota underflow for group 7.
A mostly harmless error caused by AdvFS quota information getting out of sync in the fileset. (AdvFS keeps quota information even if you don't enforce quotas.) You can safely ignore this, or if it really bothers you, you can try running quotacheck -v on the fileset.
3. /sbin/vc3d/s95xlogin/usr/df/config/xconfig.nc not found.
If the system doesn't have a graphics console, this is also probably harmless. Otherwise, something is wrong with your X Windows configuration.
Martin
The system detected a problem with a memory SIMM during boot. SIMM_CALLOUT is an SRM console variable you can set before booting on some Alphas. On the next boot, more extensive information will be provided about the possible hardware problem.
2. Chk_bf_quota: group quota underflow for group 7.
A mostly harmless error caused by AdvFS quota information getting out of sync in the fileset. (AdvFS keeps quota information even if you don't enforce quotas.) You can safely ignore this, or if it really bothers you, you can try running quotacheck -v on the fileset.
3. /sbin/vc3d/s95xlogin/usr/df/config/xconfig.nc not found.
If the system doesn't have a graphics console, this is also probably harmless. Otherwise, something is wrong with your X Windows configuration.
Martin
I work for HPE
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
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