HECnet April 2013

hecnet@lists.dfupdate.se

32 participants
287 discussions

by sampsa＠mac.com

I rebuilt GORVAX, it was very weirdly unstable - it's using UCX now, not MULTINET. For now, route through SG1. sampsa <sampsa at mac.com> mobile +961 788 10537 On 27 Apr 2013, at 18:49, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote: Hello, Since some days all my traffic is being routed by SG1. My "primary" circuit should go via GORVAX, thru 46.65.175.115, but that IP address does not answer my pings. Did I miss an announced change, or is it simply temporarily down? Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

12 years, 1 month

Link to GORVAX down

by jg＠jordi.guillaumes.name

Hello, Since some days all my traffic is being routed by SG1. My "primary" circuit should go via GORVAX, thru 46.65.175.115, but that IP address does not answer my pings. Did I miss an announced change, or is it simply temporarily down? Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by b4＠gewt.net

On Thu, 25 Apr 2013, Brian Schenkenberger, VAXman- wrote: "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> writes: Sampsa Laine <sampsa at mac.com> writes: I've somehow managed to screw up the boot node of HILANT, basically = KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to = boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status =3D 0072832C Any ideas? $ EXIT %X0072832C %MOUNT-F-DIFVOLMNT, different volume already mounted on this device You have the system disk mounted elsewhere in the cluster. Go to one of the other members: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO DISMOUNT/OVER=CHECK <the-volume-designation> FYI, when in doubt, $ HELP/MESSAGE can be your friend too: $ HELP/MESSAGE DIFVOLMNT .... or ... $ HELP/MESSAGE/STATUS=%x0072832C Both will return: DIFVOLMNT, different volume already mounted on this device Facility: MOUNT, Mount Utility Explanation: Previously, a different volume was mounted on this device on another node in the cluster. The device may be in mount verification on the other node. Either the original volume was removed from the device and replaced with another, or its volume identification was overwritten. User Action: Restore the previously mounted volume to the device. If this is not possible, dismount the device on all nodes that currently have it mounted. Then retry the mount operation. All those good people, now made redundant by HP, in the VMS documentation department didn't write all this stuff simply because they couldn't get a book published in the boof-of-the-month club. ;) Very unfortunate. The VMS documentation is fantastic. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity. -- Cory Smelosky http://gewt.net/ Personal stuff http://gimme-sympathy.org Experiments

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by hvlems＠zonnet.nl

Not at all I should hope. Mounting devices in sylogicals is a bad habit, although I did earn money helping people out of their own made trap. Sylogicals is always called irrespective of systartup_p1. So a mistake in a device name in a mount command will hang the system . Of course mount can survive /recover but not the sysadmins that called me.... Hans Van: Cory Smelosky Verzonden: donderdag 25 april 2013 05:58 PM Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C On 24 Apr 2013, at 23:52, "Sampsa Laine" <sampsa at mac.com> wrote: > > I've somehow managed to screw up the boot node of HILANT, basically KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to boot it as the boot node for the cluster I get this error: > > %SYSINIT-E, error mounting system device, status = 0072832C > > Any ideas? > > Here's the full output: > > (BOOT/R5:1 DUA0 > > > > 2.. > -DUA0 > 1..0.. > > > SYSBOOT> SET VAXCLUSTER 2 > > SYSBOOT> CONT > > %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk > %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped > %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk > %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS > OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 > %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. > %SYSINIT, waiting to form or join a VMScluster system > %VAXcluster-I-LOADSECDB, loading the cluster security database > %MSCPLOAD-I-LOADMSCP, loading the MSCP disk server > %CNXMAN, sending VAXcluster membership request to system SIIRI > %CNXMAN, now a VAXcluster member -- system KUHAVX > %SYSINIT-E, error mounting system device, status = 0072832C > > > sampsa <sampsa at mac.com> > mobile +961 788 10537 How are you mounting the system device in SYLOGICALS? > > > >

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by system＠TMESIS.COM

"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> writes: Sampsa Laine <sampsa at mac.com> writes: I've somehow managed to screw up the boot node of HILANT, basically = KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to = boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status =3D 0072832C Any ideas? $ EXIT %X0072832C %MOUNT-F-DIFVOLMNT, different volume already mounted on this device You have the system disk mounted elsewhere in the cluster. Go to one of the other members: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO DISMOUNT/OVER=CHECK <the-volume-designation> FYI, when in doubt, $ HELP/MESSAGE can be your friend too: $ HELP/MESSAGE DIFVOLMNT ... or ... $ HELP/MESSAGE/STATUS=%x0072832C Both will return: DIFVOLMNT, different volume already mounted on this device Facility: MOUNT, Mount Utility Explanation: Previously, a different volume was mounted on this device on another node in the cluster. The device may be in mount verification on the other node. Either the original volume was removed from the device and replaced with another, or its volume identification was overwritten. User Action: Restore the previously mounted volume to the device. If this is not possible, dismount the device on all nodes that currently have it mounted. Then retry the mount operation. All those good people, now made redundant by HP, in the VMS documentation department didn't write all this stuff simply because they couldn't get a book published in the boof-of-the-month club. ;) -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by system＠TMESIS.COM

Sampsa Laine <sampsa at mac.com> writes: I've somehow managed to screw up the boot node of HILANT, basically = KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to = boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status =3D 0072832C Any ideas? $ EXIT %X0072832C %MOUNT-F-DIFVOLMNT, different volume already mounted on this device You have the system disk mounted elsewhere in the cluster. Go to one of the other members: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO DISMOUNT/OVER=CHECK <the-volume-designation> -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by e.olofsen＠xs4all.nl

It happened to me one time and in that case it was because of the second case mentioned here: http://h71000.www7.hp.com/wizard/wiz_9685.html A volume with the same label was mounted on one of the other cluster members. On Thu, Apr 25, 2013 at 06:52:03AM +0300, Sampsa Laine wrote: I've somehow managed to screw up the boot node of HILANT, basically KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status = 0072832C Any ideas? Here's the full output: (BOOT/R5:1 DUA0 2.. -DUA0 1..0.. SYSBOOT> SET VAXCLUSTER 2 SYSBOOT> CONT %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. %SYSINIT, waiting to form or join a VMScluster system %VAXcluster-I-LOADSECDB, loading the cluster security database %MSCPLOAD-I-LOADMSCP, loading the MSCP disk server %CNXMAN, sending VAXcluster membership request to system SIIRI %CNXMAN, now a VAXcluster member -- system KUHAVX %SYSINIT-E, error mounting system device, status = 0072832C sampsa <sampsa at mac.com> mobile +961 788 10537

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by gregg.drwho8＠gmail.com

On Wed, Apr 24, 2013 at 11:57 PM, Cory Smelosky <b4 at gewt.net> wrote: On 24 Apr 2013, at 23:52, "Sampsa Laine" <sampsa at mac.com> wrote: I've somehow managed to screw up the boot node of HILANT, basically KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status = 0072832C Any ideas? Here's the full output: (BOOT/R5:1 DUA0 2.. -DUA0 1..0.. SYSBOOT> SET VAXCLUSTER 2 SYSBOOT> CONT %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. %SYSINIT, waiting to form or join a VMScluster system %VAXcluster-I-LOADSECDB, loading the cluster security database %MSCPLOAD-I-LOADMSCP, loading the MSCP disk server %CNXMAN, sending VAXcluster membership request to system SIIRI %CNXMAN, now a VAXcluster member -- system KUHAVX %SYSINIT-E, error mounting system device, status = 0072832C sampsa <sampsa at mac.com> mobile +961 788 10537 How are you mounting the system device in SYLOGICALS? Hello! Good point. However what's the system running on? How come we haven't heard from Dave within the past few days? After all this problem isn't your fault Sampsa, (The system may live with you, but that's all.) It's really Dave's fault. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by b4＠gewt.net

On 24 Apr 2013, at 23:52, "Sampsa Laine" <sampsa at mac.com> wrote: I've somehow managed to screw up the boot node of HILANT, basically KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status = 0072832C Any ideas? Here's the full output: (BOOT/R5:1 DUA0 2.. -DUA0 1..0.. SYSBOOT> SET VAXCLUSTER 2 SYSBOOT> CONT %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. %SYSINIT, waiting to form or join a VMScluster system %VAXcluster-I-LOADSECDB, loading the cluster security database %MSCPLOAD-I-LOADMSCP, loading the MSCP disk server %CNXMAN, sending VAXcluster membership request to system SIIRI %CNXMAN, now a VAXcluster member -- system KUHAVX %SYSINIT-E, error mounting system device, status = 0072832C sampsa <sampsa at mac.com> mobile +961 788 10537 How are you mounting the system device in SYLOGICALS?

12 years, 1 month

Cluster problem - %SYSINIT-E, error mounting system device, status = 0072832C

by sampsa＠mac.com

I've somehow managed to screw up the boot node of HILANT, basically KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to boot it as the boot node for the cluster I get this error: %SYSINIT-E, error mounting system device, status = 0072832C Any ideas? Here's the full output: (BOOT/R5:1 DUA0 2.. -DUA0 1..0.. SYSBOOT> SET VAXCLUSTER 2 SYSBOOT> CONT %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. %SYSINIT, waiting to form or join a VMScluster system %VAXcluster-I-LOADSECDB, loading the cluster security database %MSCPLOAD-I-LOADMSCP, loading the MSCP disk server %CNXMAN, sending VAXcluster membership request to system SIIRI %CNXMAN, now a VAXcluster member -- system KUHAVX %SYSINIT-E, error mounting system device, status = 0072832C sampsa <sampsa at mac.com> mobile +961 788 10537

12 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet April 2013