HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fsck on 11.00
Operating System - HP-UX
1833784
Members
2502
Online
110063
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
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
08-02-2001 01:19 PM
08-02-2001 01:19 PM
fsck on 11.00
Replaced a tape drive that was told to me by HP was
a hot swap tape drive. HP stated you could replace
the tape while users were on as long as nothing else was
on the bus. Well this did work for about 2 days then the
system crashed. The inittab became corrupt so I put in
another and was able to reboot the server.
The system seems to be slow at times and disk I/0 and
cpu are pretty high at times.
Was wondering if and fsck should be done? Hopefully it does
not take too long with Advanced JFS. - Thanks
a hot swap tape drive. HP stated you could replace
the tape while users were on as long as nothing else was
on the bus. Well this did work for about 2 days then the
system crashed. The inittab became corrupt so I put in
another and was able to reboot the server.
The system seems to be slow at times and disk I/0 and
cpu are pretty high at times.
Was wondering if and fsck should be done? Hopefully it does
not take too long with Advanced JFS. - Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 03:29 PM
08-02-2001 03:29 PM
Re: fsck on 11.00
Without a crash dump analysis, it is not possible to determine the reason for the crash. fsck is run automatically when the system reboots and fixes directory structures. It will never fix corrupted data files or bad spots on the disk. Without a lot more details, it would be impossible to determine the reason for the slowdown.
Bill Hassell, sysadmin
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2001 04:43 PM
08-02-2001 04:43 PM
Re: fsck on 11.00
Hi James,
it might be just a coincedence that the box crashed. As Bill already said, you need to have a look at the crash dump.
Here are a few things you can check for a possible answer:
1) check etc/shutdownlog
2) /var/adm/syslog/OLDsyslog.log
3) see if you have a crash dump in /var/adm/crash with the correct timestamp.
Usually you find an INDEX file there and you might see a string for panic ... in there.
You can check this site for help on q4 for analysing the dump
if you see HPMC somewhere it probably points to hardware problem.
Hope that helps a bit,
Steffi Jones
it might be just a coincedence that the box crashed. As Bill already said, you need to have a look at the crash dump.
Here are a few things you can check for a possible answer:
1) check etc/shutdownlog
2) /var/adm/syslog/OLDsyslog.log
3) see if you have a crash dump in /var/adm/crash with the correct timestamp.
Usually you find an INDEX file there and you might see a string for panic ... in there.
You can check this site for help on q4 for analysing the dump
if you see HPMC somewhere it probably points to hardware problem.
Hope that helps a bit,
Steffi Jones
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