Re: System Crash using Volutil (161 Views)
Reply
Occasional Visitor
Robert Ripley
Posts: 1
Registered: ‎08-25-2003
Message 1 of 3 (161 Views)

System Crash using Volutil

Got a stumper for you people. HP939, A3699A HSC I/O bus converter going to a A1828A 14 slot expansion module with a 28696 FW SCSI card and a 12H Autoraid on the end. Autoraid has 4 - 18gig drives and two controllers. X is the primary and Y is totally termianted (not used). 3 LUNs 0,1, and 2 @ 4g, 6g, 6g respectively. ODE see them. DSTAT ALL sees them, but when you put a "test" volume label on it and confirm the system crashes. Any ideas???? Note: all hardware was tested under the same config with a base load of 6.5 plus patches and it worked on other HP939.
Honored Contributor
Eric Sorensen_1
Posts: 573
Registered: ‎10-08-2000
Message 2 of 3 (161 Views)

Re: System Crash using Volutil

Hello Robert,

What command causes the crash-- newset? or newvol? What is the system abort number, and the subsystem, chassis codes, etc?

Have you seen the 12H config doc KBRC00006220 ?

A problem well defined is half solved.
Trusted Contributor
Lars Appel
Posts: 131
Registered: ‎12-27-1996
Message 3 of 3 (161 Views)

Re: System Crash using Volutil

You might want to compare timestamps of VOLUTIL and MIRVUTIL in
PUB.SYS; if you had Mirrored Disk in the past, but no longer have it under
update maintenance, you might have an older MIRVUTIL version in place,
which gets invoked instead of VOLUTIL, if present.
see www.google.com/search?q=lars+appel
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.