[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssag::ask_ssag

Title:	Ask the Storage Architecture Group
Notice:	Check out our web page at http://www-starch.shr.dec.com
Moderator:	SSAG::TERZAN

Created:	Wed Oct 15 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6756
Total number of notes:	25276

6601.0. "%mount-f-badchksum" by AXCL04::LAGIOIA (We do ...the best) Mon Apr 21 1997 03:40

    Hello!
    
    I had this error during a boot %mount-f-badchksum. Vax running openvms
    v6.2
    
    The mount/over=security fails. We have done anal/disk/repair and no
    errors were found.
    
    I suppose doing an init of this disk all will work perfectly. 
    I can not found any information about this problem.
    Can someone give me an explanation or a solution?
    
    Regards
    Domenico

T.R Title User Personal
Name Date Lines

6601.1 MOVIES::WIDDOWSON Rod OpenVMS Engineering. Project Rock Mon Apr 21 1997 08:41 17

T.R	Title	User	Personal Name	Date	Lines
6601.1		MOVIES::WIDDOWSON	Rod OpenVMS Engineering. Project Rock	`Mon Apr 21 1997 08:41`	17
	This may be better in VMSNOTES, if you do cross post, please say so.. The %mount-f-badchksum is just MOUNT repaying a SYS-F-BADCHKSUM which came (most likely) from the filesystem. Mount itself never reports this error, unless someone passes it up. The filesystem will emit this error in when it tries to update the security and also when openning a file if the header is corrupted. Sounds like MOUNT is calling the XQP to do something and that is what is causing the problem. If /over=security fails, then try /noquota. If that doesn't work turn on SET WATCH and see what the XQP says... By the way, how did you get anal/disk/repair to work if the disk won't mount ?

    This may be better in VMSNOTES, if you do cross post, please say so..
    
    The %mount-f-badchksum is just MOUNT repaying a SYS-F-BADCHKSUM which
    came (most likely) from the filesystem.  Mount itself never reports
    this error, unless someone passes it up.
    
    The filesystem will emit this error in when it tries to update the
    security and also when openning a file if the header is corrupted.
    
    Sounds like MOUNT is calling the XQP to do something and that is what
    is causing the problem.  If /over=security fails, then try /noquota. 
    If that doesn't work turn on SET WATCH and see what the XQP says...
    
    By the way, how did you get anal/disk/repair to work if the disk won't
    mount ?