HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- File system recovery
Operating System - HP-UX
1837176
Members
2635
Online
110113
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
06-15-2000 02:18 AM
06-15-2000 02:18 AM
After a system (9000/HPUX10.20) crash, in single user mode fsck returns "CAN'T READ BLOCK ...." and terminates without repairing the file system.
I tried to use alternate superblock from file /var/adm/sbtab:
# fsck -b block_num /dev/vgxx/rlvolx
The result was the same.
Is there a way to recover the file system.
I tried to use alternate superblock from file /var/adm/sbtab:
# fsck -b block_num /dev/vgxx/rlvolx
The result was the same.
Is there a way to recover the file system.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2000 02:31 AM
06-15-2000 02:31 AM
Re: File system recovery
Reboot the system and interupt the boot process.
Through ISL prompt use the command "hpux -lm" (ie maintenance mode)
run fsck manually.
Through ISL prompt use the command "hpux -lm" (ie maintenance mode)
run fsck manually.
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2000 05:26 AM
06-15-2000 05:26 AM
Solution
can't read block messages are usual defective media.
depending on whether it's hfs or jfs, hfs supports the '-f' option. You could mount it with that and then attempt to backup your data (don't run live with it). Then once backed up, replace the disk
depending on whether it's hfs or jfs, hfs supports the '-f' option. You could mount it with that and then attempt to backup your data (don't run live with it). Then once backed up, replace the disk
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