- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: fsck fail
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО10-12-2001 04:47 AM
тАО10-12-2001 04:47 AM
fsck fail
i'm having a problem on boot.
On an HP9000 J200, OS 10.20, during boot i have:
Checking root file system:
/dev/rroot: Cannot read BLK 1258608
/dev/rroot: unexpected inconsistency: run fsck manually.
/sbin/fsclean:/dev/vg00/lvol3 not ok, run fsck.
File system non properly shutdown, beginning file system repair.
/dev/rroot: Cannot read BLK 1258608
/dev/rroot: unexpected inconsistency: run fsck manually.
Could not fix file system with fsck.
Cannot read: BLK 1258608
Continue ?
Cannot read: BLK 1258608
Continue ?
Failed read of Block #1258608, retried 2 times.
Disk media problems encountered .....
Then with CTRL + D the system goes up.
I also tried by sam to modify the option of /dev/dsk/lvol3 "Use Bad Block Relocation" but after boot i have same problems.
Is there on HP a way to erase or to skip or move that bad block, not using it more, so at boot i don't encounter this problem?
Thanks in advance for your help.
Tarek
- Tags:
- fsck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 05:01 AM
тАО10-12-2001 05:01 AM
Re: fsck fail
Have you tried booting into LVM maintainance mode and running fsck. Then use reboot inplace of shutdown.
To boot into lvm maintainance mode, interrupt the boot process and proceed like this
at the boot prompt type
bo pri
type "Y" to interact with the IPL. at the ipL prompt type
IPL>hpux -lm (;0)/stand/vmunix
It will boot into the maintainance mode. Run fsck on /dev/dsk/lvol3 and then reboot, don't do a shutdown.
hope this helps.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 05:03 AM
тАО10-12-2001 05:03 AM
Re: fsck fail
This doesn't look good. The inability of 'fsck' to read a block suggests that the filesystem or the disk is badly damaged. You are probably not going to be able to retrieve the data.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 05:26 AM
тАО10-12-2001 05:26 AM
Re: fsck fail
Is it possible that there is no command that allows to eliminate that bad block? On Sun with format command you can do that. What is the same commnad on HP?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 06:09 AM
тАО10-12-2001 06:09 AM
Re: fsck fail
I trust you have an Ignite recovery tape. If not, I'd make one as soon as possible.
The next thing I think I'd do to attempt to differentiate between as hard disk error and a logical volume or filesystem corruption is this:
# dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k
See if any errors are detected via this.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 06:52 AM
тАО10-12-2001 06:52 AM
Re: fsck fail
dd read error: I/O error
1967+0 records in
1967+0 records out
What does it mean?
Thanks again,
Tarek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2001 06:55 AM
тАО10-12-2001 06:55 AM
Re: fsck fail
I'd definitely arrange to have this disk replaced. This is a physical level error.
Regards!
...JRF...