GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fsck error: Unable to invoke hfs-specific module ...
Operating System - HP-UX
1855764
Members
11733
Online
104103
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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
01-17-2001 09:57 PM
01-17-2001 09:57 PM
I have the following error message when I tried to fsck a HPUX 10.2 box after a power failure.
Error:
Unable to invoke hfs-specific module for the command fsck at /sbin/fs/hfs/fsck
File or directory not found.
Is the corruption was due to a patch problem ?
Here is the output of what /sbin/fs/hfs/fsck on a similar machine.
$Revision: 78.5.1.4 $
PATCH/10.20:PHCO_8764 libc.a_ID@@/main/r10dav/libc_dav/libc_dav_cpe/2
/ux/libc/libs/libc/archive_pa1/libc.a_ID
Oct 2 1996 10:35:25
PATCH_10_20: fsck.o cache.o ufs_tables.o ufs_subr.o hpux_rel.o 97/09/12
Please help me on how to recover this. Thank you.
Error:
Unable to invoke hfs-specific module for the command fsck at /sbin/fs/hfs/fsck
File or directory not found.
Is the corruption was due to a patch problem ?
Here is the output of what /sbin/fs/hfs/fsck on a similar machine.
$Revision: 78.5.1.4 $
PATCH/10.20:PHCO_8764 libc.a_ID@@/main/r10dav/libc_dav/libc_dav_cpe/2
/ux/libc/libs/libc/archive_pa1/libc.a_ID
Oct 2 1996 10:35:25
PATCH_10_20: fsck.o cache.o ufs_tables.o ufs_subr.o hpux_rel.o 97/09/12
Please help me on how to recover this. Thank you.
mk
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2001 04:26 AM
01-18-2001 04:26 AM
Re: fsck error: Unable to invoke hfs-specific module ......
Hi !
If You have an older version use recovery CD-ROM, or a newer one use Core-OS CD.
Run recovery shell and do fsck.
regards, Saa
If You have an older version use recovery CD-ROM, or a newer one use Core-OS CD.
Run recovery shell and do fsck.
regards, Saa
If no problem, don't fixed it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2001 05:45 AM
01-22-2001 05:45 AM
Solution
Hello,
The Response Center has written several documents about recovering a system where boot-up issues are causing trouble. The articles are located in the customer-accessible database in itrc.hp.com.
Sandor mentioned the use of the Support/Recovery or Install CD. The articles listed below tell which you will need to use depending on your version of operating system.
Once booted on the support/recovery CD, doing "chroot_lvmdisk" will automatically fsck both / and /stand. It will also mount both and "change root" down to the disks' / directory, where you can inspect your file systems.
Though the support media has a limited number of commands to work with, it has access to frecover, should you need to restore files from an fbackup tape. The articles have a few examples on techniques.
A word to the wise - the recovery/discovery process may take much more time than the time to reinstall and configure the O.S. Set a deadline for your support/recovery CD efforts, and if you are not making "reasonable" headway, reinstall & reconfigure, or if you did a make_recovery tape - use it.
Depending on the version of O.S. - refer to one of these two documents:
How do I boot my system from Support Media on 10.X ? (OZBEKBRC00000581)
How do I boot my system from Support Media on 11.00 ? (OZBEKBRC00000582)
Regards,
Stephen
The Response Center has written several documents about recovering a system where boot-up issues are causing trouble. The articles are located in the customer-accessible database in itrc.hp.com.
Sandor mentioned the use of the Support/Recovery or Install CD. The articles listed below tell which you will need to use depending on your version of operating system.
Once booted on the support/recovery CD, doing "chroot_lvmdisk" will automatically fsck both / and /stand. It will also mount both and "change root" down to the disks' / directory, where you can inspect your file systems.
Though the support media has a limited number of commands to work with, it has access to frecover, should you need to restore files from an fbackup tape. The articles have a few examples on techniques.
A word to the wise - the recovery/discovery process may take much more time than the time to reinstall and configure the O.S. Set a deadline for your support/recovery CD efforts, and if you are not making "reasonable" headway, reinstall & reconfigure, or if you did a make_recovery tape - use it.
Depending on the version of O.S. - refer to one of these two documents:
How do I boot my system from Support Media on 10.X ? (OZBEKBRC00000581)
How do I boot my system from Support Media on 11.00 ? (OZBEKBRC00000582)
Regards,
Stephen
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 2026 Hewlett Packard Enterprise Development LP