HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dumpsys() failed returned 4294967295 on F30 server
Operating System - HP-UX
1836611
Members
3788
Online
110102
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
04-15-2004 11:31 PM
04-15-2004 11:31 PM
hello admins,
we have become helpless because of the hp's discontinuation of support to older nova (F30)servers. we even checked www.openpa.net for some detail in vain.
As a last resort we have decided to put up the query to your reverend legs in Indian princely style. Any help will be aptly rewarded with rubies...diamonds...etc.
basically, jokes apart ..we are unable to boot the server, with the following message spat on the console everytime.....
Error message
boot
:disk (52.1.0;0)/stand/vmunix)
inet_clts:ok inet_cots:ok networking memory for fragment reassembly is restrs
swap device table:(start & size is 512 block
entry 0-auto-configured or root device; ignored-can't open device
warning ; no dump dvice configured dump is disabled
mountfs:opend
panic(display==0xbf00,flags==0x0) all vfs_mount root failed; need drivers??
pc-off stack trace (read across most recent is 1st)
0x0020c31c 0x000700b4 0x00807e8 0x000e0bbc 0x0019e7e0
end of stack
sync'ing disk (0 bufers to flush;0 buffer to flush)
0 buffer not flushed
0 buffer still dirty
it was not possible for the kernel to find process that caused this crash
dumpsys() called
WARNING dump was disable during configuration
dumpsys() failed returned 4294967295
we have become helpless because of the hp's discontinuation of support to older nova (F30)servers. we even checked www.openpa.net for some detail in vain.
As a last resort we have decided to put up the query to your reverend legs in Indian princely style. Any help will be aptly rewarded with rubies...diamonds...etc.
basically, jokes apart ..we are unable to boot the server, with the following message spat on the console everytime.....
Error message
boot
:disk (52.1.0;0)/stand/vmunix)
inet_clts:ok inet_cots:ok networking memory for fragment reassembly is restrs
swap device table:(start & size is 512 block
entry 0-auto-configured or root device; ignored-can't open device
warning ; no dump dvice configured dump is disabled
mountfs:opend
panic(display==0xbf00,flags==0x0) all vfs_mount root failed; need drivers??
pc-off stack trace (read across most recent is 1st)
0x0020c31c 0x000700b4 0x00807e8 0x000e0bbc 0x0019e7e0
end of stack
sync'ing disk (0 bufers to flush;0 buffer to flush)
0 buffer not flushed
0 buffer still dirty
it was not possible for the kernel to find process that caused this crash
dumpsys() called
WARNING dump was disable during configuration
dumpsys() failed returned 4294967295
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2004 11:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2004 11:54 PM
04-15-2004 11:54 PM
Re: dumpsys() failed returned 4294967295 on F30 server
shri,shri,.....marthanda...prince of siliguri,stately prince of rathnagiri.....but most importantly traitor of swarnagiri...his highness venugopalakrishna..,
please spare my paltry reply.I would suggest u to do basic troubleshooting.Firstly you can try booting from CD and check whether the system trows the same error.If same error is found u can conclude that it is not the problem with HDD otr the filesystem...Also u can swap the RAM slots .I guess the F30 server has 12 RAM slots...
Please do not forget your prescious gift ,I mean diamonds...etc to remind...
Senthil
(spy of swarnagiri...)
please spare my paltry reply.I would suggest u to do basic troubleshooting.Firstly you can try booting from CD and check whether the system trows the same error.If same error is found u can conclude that it is not the problem with HDD otr the filesystem...Also u can swap the RAM slots .I guess the F30 server has 12 RAM slots...
Please do not forget your prescious gift ,I mean diamonds...etc to remind...
Senthil
(spy of swarnagiri...)
Let your effort be such, the very words to define it, by a layman - would sound like a "POETRY" ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2004 12:24 AM
04-16-2004 12:24 AM
Re: dumpsys() failed returned 4294967295 on F30 server
Hi ... I think Kapil is on the right track to start:
While booting the server
Press a key ......
bo
Interact with IPL Y/N ==== Y
hpux -lm
From there I would do the following:
vgchange -a y /dev/vg00
lvlnboot -v /dev/vg00
It probably states at this point that there is "No boot logical volume".
If it says that, then type:
lvlnboot -b /dev/vg00/lvol1
then:
lvlnboot -v /dev/vg00
to verify it lists a boot lvol
Then:
sync
sync
reboot
And all should be well.
Best regards,
Kent M. Ostby
While booting the server
Press a key ......
bo
Interact with IPL Y/N ==== Y
hpux -lm
From there I would do the following:
vgchange -a y /dev/vg00
lvlnboot -v /dev/vg00
It probably states at this point that there is "No boot logical volume".
If it says that, then type:
lvlnboot -b /dev/vg00/lvol1
then:
lvlnboot -v /dev/vg00
to verify it lists a boot lvol
Then:
sync
sync
reboot
And all should be well.
Best regards,
Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
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