- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Disk Errors
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
тАО11-16-2006 02:28 AM
тАО11-16-2006 02:28 AM
I am new to the forum. I am running an analyze/disk/norepair and found the following issues on a disk:
%ANALDISK-W-ALLOCSET, blocks incorrectly marked free
LBN 4835952 to 4835963, RVN 1
%ANALDISK-W-BADHEADER, file (16121,381,1)
invalid file header
-ANALDISK-I-BAD_FIDSEQ, unexpected FID_SEQ field
%ANALDISK-W-LOSTHEADER, file (19425,9,1) B02000015.TRD;1
not found in a directory
I got a few of each of the previous messages, but I am just curious if these issues can be resolved without having to replace a disk. Any suggests are welcome. Thank you in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 02:39 AM
тАО11-16-2006 02:39 AM
Re: Disk Errors
The files not in a directory will be put in [SYSLOST]
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 02:57 AM
тАО11-16-2006 02:57 AM
Re: Disk Errors
%ANALDISK-W-LOSTHEADER
All of the other errors went away.
Also, I wanted to ask is it always good to run anal/disk/repair two times? I was told that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 02:59 AM
тАО11-16-2006 02:59 AM
SolutionI agree with Ian. ANALYZE/REPAIR should be able to make the needed corrections to the data structures.
These errors do not necessarily indicate hardware disk errors. These are inconsistencies in the data structures maintained by the file system.
The most worrying message is the one about "blocks incorrectly marked as free". I would suggest checking as to which file actually has those blocks in use. If the blocks were marked as free incorrectly, it could mean that at one point, the files were doubly allocated.
Keep careful notes of the precise messages that you received, and a full, possibly physical backup of the disk would be a good idea.
If the problem recurs, then more investigation is definitely in order.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 03:44 AM
тАО11-16-2006 03:44 AM
Re: Disk Errors
DFU is also good for this and can be quicker.
Do keep a note of what was reported and its worth working out what the files are.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 03:59 AM
тАО11-16-2006 03:59 AM
Re: Disk Errors
And maybe "$ SHOW DEVICE/FILE disk" also shows that file? Perhaps /REPAIR is unable to cure a LOSTHEADER condition (by upating INDEXF.SYS and entering the file in [SYSLOST] directory) for an open file?
If this is the case then it's likely that the application holding the file open will likely clean-up/dispose of it once done.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 04:04 AM
тАО11-16-2006 04:04 AM
Re: Disk Errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 05:20 AM
тАО11-16-2006 05:20 AM
Re: Disk Errors
to begin with,
Welcome to the VMS forum!
%ANALDISK-W-LOSTHEADER is only a warning (indicated by the -W- )
A typical way to achieve this situation, is by replacing an INSTALLed file, and purging while not all references are gone yet.
@VMSINSTALL, and answering the default YES to the purge question, is a quite common way to generate it. An example of a bad choice of default answer: HIGHLY disadvisable, especially in cluster!
I do agree with Ian and Bob on the potentially bad situation with ALLOCSET.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 06:29 PM
тАО11-16-2006 06:29 PM
Re: Disk Errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2006 04:21 AM
тАО11-17-2006 04:21 AM
Re: Disk Errors
/Guenther