- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Disk failure
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
тАО01-29-2016 12:25 PM
тАО01-29-2016 12:25 PM
Disk failure
Hi,
I have an "old" HP rp3410 with HP-UX 11.31.
In an external enclosure, I have 2 300 Gb SCSI disks, attached to an Ultra320 controller.
Today one of these disks stopped functioning; I tried to fsck the disk with the following error:
# fsck -F vxfs -o full,nolog /dev/vg03/lvol1
UX:vxfs fsck: WARNING: V-3-20836: file system had I/O error(s) on meta-data.
pass0 - checking structural files
pass1 - checking inode sanity and blocks
UX:vxfs fsck: ERROR: V-3-26117: bc_read failure devid = 0, bno = 8373899, off = 0, len = 8192
Is there anything else I can try to recover the contents of the file system in it ?
Thank you
Enrico
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2016 01:18 PM
тАО01-29-2016 01:18 PM
Re: Disk failure
What does the disk show in the output from 'ioscan -fnC disk'? If it show's NO_HW, then you're out of luck.
If you did not have the data mirrored then you'll have to restore the data after you replace the disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2016 03:23 PM
тАО01-29-2016 03:23 PM
Re: Disk failure
The status is CLAIMED
# ioscan -fnC disk /dev/dsk/c4t8d0
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 4 0/4/1/0.8.0 sdisk CLAIMED DEVICE HP 300 GMAW3300NC
/dev/dsk/c4t8d0 /dev/rdsk/c4t8d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2016 04:20 PM
тАО01-29-2016 04:20 PM
Re: Disk failure
The status CLAIMED means that the driver could talk to the electronics inside the disk. But the errors indicate that the disk has had a crash and the oxide is damaged. Therefore the data is unreadable and no HP-UX tools can restore this area. Disks are the highest failure item for any computer. Mirroring is simply mandatory for any data that is important.
If money is not o problem, there are several disk recovery companies that may be able to recover the data on the disk. It may cost more than your entire computer though.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2016 02:50 AM
тАО01-30-2016 02:50 AM
Re: Disk failure
About the error reported from fsck, I've found these informations on the veritas.com website (https://www.veritas.com/support/en_US/article.000013525):
Cause
I/O read failure at block offset 32206696 (into the file system) was detected by fsck
Solution
At this point during the fsck, no disk I/O errors are tolerated. Retry the file system check, as the I/O error might be transient. Check the console logs for any I/O errors relating to the filesystem's devices. If the problem is a disk failure, replace the disk.
I will try again to repair the disk, as they suggest, but the possibilities of a success are really limited. In the meantime, I am encountering some problems with frecover in restoring the backup on another disk, but if the problem persists this will be the subject of another post.
Thank you
Enrico
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2016 02:04 AM
тАО02-02-2016 02:04 AM
Re: Disk failure
A brief follow up.
I've tried to put the damaged disk in a -20 C freezer for about 1 and a half hour.
Afterwards, I've reinserted the damaged disk in the server. At the first boot, fsck repaired successfully the disk, and it was mounted without a further manual intervention.
After the data recovery operations ("rsync" was used to copy the last updates performed on the file system to a new disk) I tried to do a last backup of the disk. Many read faults but it reached the end.
Problem solved, with a good amount of luck. Next time I will set up some type of redundancy of the data.
Thank you for your help
Enrico