question on mount verification loop

[antonio elder prado]

Hi guys,

thank you very much for the info, i will be trying this afternoon and will submit the results later to the forum.
once again,

thank you very much, / muito obrigado,
./antonio/.

[antonio elder prado]

Hi,

i did check the machine and still got the mount verification messages.
i did boot out of the cd,
and under the prompt $$
did what Volker suggested, the only problem i see is on the last mount, it says something about bad label, and repair, then gives me the prompt back.
if i do a show device dka100/full it shows me mounted device.
another strangeness:
after long time of those messages, i can see in between the login, i do type the system and its password, and i can have the $ prompt (of course comes with those messages).
anyway,
i will keep on trying and if you have any extra suggestions it would be greatly appreciate,
thank you/obrigado.
./antonio/.

[Andy Bustamante]

Please try

$ mount ovms$dka100: /over=ident

from the $ prompt. If someone has modified either the startup file which mounts the disk or modified the volume lablel the automated startup will not be able to mount the device.

[Andy Bustamante]

>>>it says something about bad label, and repair, then gives me the prompt back

What is the message?

[Hoff]

V8.2 was _the_ first public release of OpenVMS for Itanium, and that release shipped out on January 13, 2005.

Accordingly, the default (shotgun) answer....

Upgrade to V8.3 or V8.3-1H1; to a newer and more current and likely more stable release.

And yes, this could well (still) be indicative of a hardware problem.

Heat, flaky disk, etc.

Which means the first part of the upgrade is a full and complete disk BACKUP of anything you need to save.

Given you have possibly-flaky storage or flaky system hardware, I'd start with a full backup of DKA100: and any other disks you have data on, regardless.

[antonio elder prado]

okay;

i spoke with one of the developers and we need to have the lowest possible OS available (in this case 8.2), so i need to stick with 8.2 crossing my fingers.

regarding the errors:
on the boot from the cd / 8.3
$$$ MOUNT/FOR DKA100:
the output of this mounting is:
MOUNT-I-MOUNTED, I64SYS mounted on _DKA100;

$$$ DISM/NOUNL DKA100
just got the $$$ back

$$$ MOUNT/OVER=ID/NOASSI DKA100
*** this time the error comes back as ***
MOUNT-W-IDX MAPPER
I/O ERROR ON INDEX FILE BITMAP, VOLUME LOCKED
SYSTEM-F-PARITY, PARITY ERROR
MOUNT-I-MOUNTED, I64SYS MOUNTED ON _DKA100;
$$$


thank you all for helping me with this,

./antonio/.

[Andy Bustamante]

The most likely out come is that anything on this disk has been lost.

You can attempt to load the latest ECOs for 8.2, get the current update plus any fiber_scsi and sys patches. This may or may not be productive in correcting this situation, but may help prevent the situation again. Don't expect this to resolve the issue.

Once you've decided data the disk isn't going to be recovered, you could attempt to initialize the disk and mount again. If this is hardware issue, the disk will soon fail again. Watch the error counts ($ show error) and check the error log for details. See the help for anal/error/elv for how to read error logs. If you start logging errors, replace the disk. If you have hardware support, replace it now.

[P Muralidhar Kini]

Hi Antonio,

>> MOUNT-W-IDXMAPPER
Here's the DCL help for IDXMAPERR

IDXMAPERR, I/O error on index file bitmap; volume locked

Facility: MOUNT, Mount Utility

Explanation: An I/O error was encountered during a mount operation.
Existing files in the volume can be accessed, but other
operations (for example, create and delete) are not possible.

User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE/REPAIR
command.


But in your case the disk is getting in to mount verification during the boot
operation and hence you would not get a chance to run
ANALYZE/DISK_STRUCTURE/REPAIR on the disk.

>> SYSTEM-F-PARITY
Looks like there is some problem with the disk.
Did the disk work before ?
When did you start seeing the problem ?

Also as Andy had mentioned, you need to look out for the error count field in the
"SHOw DEVICE" output of the device. If this number keeps on increasing then
its a sign of problem.

For now, looks like ther is a problem with the disk $dka100.
If you have another system disk in the node then you can boot the node with the
other system disk. And once the node comes up, you can run
ANALYZE/DISK/LOCK on the $dka100 disk to check for errors.

Hope this helps.

Regards,
Murali

[Shriniketan Bhagwat]

Hi,

SYSTEM-F-PARITY message indicates some problem with the disk. The exact meaning of this message depends on the device. Use the DIAGNOSE command to examine the system error log for more information related to an error occurring on the device. On the disk drives one or more of the following conditions can cause this error:

1. Drive parity error
2. ECC hard error
3. Header compare error
4. Map parity error
5. Header CRC error
6. MASSBUS control parity error

Regards,
Ketan

[Shriniketan Bhagwat]

Hi,

Please refer the below link on PARITY errors.

http://h71000.www7.hp.com/wizard/wiz_6021.html
http://h71000.www7.hp.com/wizard/wiz_6418.html
http://h71000.www7.hp.com/wizard/wiz_9580.html


Regards,
Ketan