- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Unable to create a crash dump after a vpar cra...
Operating System - HP-UX
1752280
Members
4352
Online
108786
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
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
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-14-2010 01:30 AM
тАО05-14-2010 01:30 AM
Unable to create a crash dump after a vpar crashed.
Hi
MY VPAR crashed and not able to create a crash dump with below error on console
Any clue on this . what it could mean ?
Unable to assign ASL device \_SB_.N005.S080.IOC0.L002.S2F0 for crash dump - will retry for 5 minutes
Still unable to assign device. Retrying...
Still unable to assign device. Retrying...
Still unable to assign device. Retrying...
It hanged to had to do a reset to get the servers up, but no crash dump and no RCA.
Regards
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2010 07:45 AM
тАО05-16-2010 07:45 AM
Re: Unable to create a crash dump after a vpar crashed.
i think you have given, TOC at GSP
is crash dump device is configured on the system??
#more /etc/crashconf
check below entry
/etc/rc.config.d/crashconf:CRASHCONF_ENABLED=1
/etc/rc.config.d/crashconf:CRASHCONF_READ_FSTAB=1
/etc/rc.config.d/crashconf:CRASHCONF_REPLACE=0
is crash dump device is configured on the system??
#more /etc/crashconf
check below entry
/etc/rc.config.d/crashconf:CRASHCONF_ENABLED=1
/etc/rc.config.d/crashconf:CRASHCONF_READ_FSTAB=1
/etc/rc.config.d/crashconf:CRASHCONF_REPLACE=0
Sanjeev Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2010 06:54 PM
тАО05-16-2010 06:54 PM
Re: Unable to create a crash dump after a vpar crashed.
>>Unable to assign ASL device
This suggest that you have configured dump device on other than vg00,
is it a SAN disk??
You may have to update dump device by
lvlnboot -d
It is highly recommened that you configure dump on vg00 (lvol2)
BR,
Kapil+
This suggest that you have configured dump device on other than vg00,
is it a SAN disk??
You may have to update dump device by
lvlnboot -d
It is highly recommened that you configure dump on vg00 (lvol2)
BR,
Kapil+
I am in this small bowl, I wane see the real world......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2010 09:00 PM
тАО05-16-2010 09:00 PM
Re: Unable to create a crash dump after a vpar crashed.
@ Sanjeev, Yes crashconf is correctly configured.
Thanks.
@ Kapil , dump device is configured OK ,
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c10t0d0s2 (5/0/2/1/0/4/0.0.0) -- Boot Disk
/dev/dsk/c20t0d0 (6/0/10/1/0/4/0.0.0)
Boot: lvol1 on: /dev/dsk/c10t0d0s2
Root: lvol3 on: /dev/dsk/c10t0d0s2
Swap: lvol2 on: /dev/dsk/c10t0d0s2
Dump: lvol2 on: /dev/dsk/c10t0d0s2, 0
Is there anyway I can interpret "_SB_.N005.S080.IOC0.L002.S2F0" which device does it mean?
Thanks.
@ Kapil , dump device is configured OK ,
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c10t0d0s2 (5/0/2/1/0/4/0.0.0) -- Boot Disk
/dev/dsk/c20t0d0 (6/0/10/1/0/4/0.0.0)
Boot: lvol1 on: /dev/dsk/c10t0d0s2
Root: lvol3 on: /dev/dsk/c10t0d0s2
Swap: lvol2 on: /dev/dsk/c10t0d0s2
Dump: lvol2 on: /dev/dsk/c10t0d0s2, 0
Is there anyway I can interpret "_SB_.N005.S080.IOC0.L002.S2F0" which device does it mean?
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