Thanks for pointing me into the right direction. The issue indeed was with rc.sysinit script. When we updated kernel on this system almost a year ago, we had to manually edit this script (as the system wouldn't come up at all.. Kind RH wipes any custom configs), and I have found that the VxVM part was pasted in the wrong place.
I would imagine, it didn't work since then. Thanks, -Andrey -----Original Message----- From: Brad Boyer [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 7:00 PM To: Andrey Dmitriev; [EMAIL PROTECTED] Cc: veritas-vx@mailman.eng.auburn.edu Subject: RE: [Veritas-vx] vxconfigd not coming up on reboot The Red Hat Enterprise Linux 4.0 support in VxVM 4.1MP1 uses the rc.sysinit script to load VxVM. The VxVM package install applies a patch to this script to load the modules and start vxconfigd at the right place in the startup process. However, these actions are supposed to happen after the root filesystem has been mounted read-write. It appears that your system has the script wrong in one way or another. The changes made to the rc.sysinit script should be in /etc/vx/rc.sysinit.vxvm_patch, so you can see the appropriate changes. Newer releases of VxVM 4.1 for Linux no longer use this method. Is there a particular reason you are still using 4.1MP1? The current release is 4.1MP4. Did this system ever work, or is this a fresh install of VxVM? My first suggestion would be to apply the latest MP, since the boot process is handled differently in 4.1MP4. The startup of VxVM now happens in rc.modules on these systems, which is less sensitive to changes that may happen in system updates. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrey Dmitriev Sent: Monday, March 10, 2008 2:35 PM To: [EMAIL PROTECTED] Cc: veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] vxconfigd not coming up on reboot Dmitry, This is a RH 4.0 Linux system. Version is 4.1.10. Seems consistent between systems [EMAIL PROTECTED] rc2.d]$ls -ltrh|grep vx lrwxrwxrwx 1 root root 21 Aug 11 2005 S95vxrsyncd -> ../init.d/vxrsyncd.sh lrwxrwxrwx 1 root root 21 Aug 11 2005 S11vxnm-vxnetd -> ../init.d/vxnm-vxnetd lrwxrwxrwx 1 root root 22 Aug 11 2005 S02vxvm-recover -> ../init.d/vxvm-recover lrwxrwxrwx 1 root root 23 Aug 11 2005 S01vxvm-reconfig -> ../init.d/vxvm-reconfig lrwxrwxrwx 1 root root 15 May 4 2006 K68vxfen -> ../init.d/vxfen lrwxrwxrwx 1 root root 15 May 4 2006 K65vxgms -> ../init.d/vxgms lrwxrwxrwx 1 root root 15 May 4 2006 K64vxodm -> ../init.d/vxodm lrwxrwxrwx 1 root root 15 May 4 2006 K69vxglm -> ../init.d/vxglm [EMAIL PROTECTED] rc2.d]# ls -ltrh|grep vx lrwxrwxrwx 1 root root 21 Aug 4 2005 S95vxrsyncd -> ../init.d/vxrsyncd.sh lrwxrwxrwx 1 root root 21 Aug 4 2005 S11vxnm-vxnetd -> ../init.d/vxnm-vxnetd lrwxrwxrwx 1 root root 22 Aug 4 2005 S02vxvm-recover -> ../init.d/vxvm-recover lrwxrwxrwx 1 root root 23 Aug 4 2005 S01vxvm-reconfig -> ../init.d/vxvm-reconfig lrwxrwxrwx 1 root root 15 May 4 2006 K68vxfen -> ../init.d/vxfen lrwxrwxrwx 1 root root 15 May 4 2006 K65vxgms -> ../init.d/vxgms lrwxrwxrwx 1 root root 15 May 4 2006 K64vxodm -> ../init.d/vxodm -----Original Message----- From: Dmitry Glushenok [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 4:33 PM To: Andrey Dmitriev Cc: veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] vxconfigd not coming up on reboot Hi, Solaris/VxVM verisons? Anyway - vxvm is trying to start before fylesystem is remounted for write access. S02 is too early, which runlevel btw? Start scripts from Solaris 9/VxVM 4.1: ./rcS.d/ S25vxvm-sysboot S35vxvm-startup1 S85vxvm-startup2 S86vxvm-reconfig ./rc2.d/ S95vxvm-recover Andrey Dmitriev wrote: > Any clue? > > Starts fine manually. Seems like system tries to bring it up before it can. > > Mar 6 18:02:46 sun kernel: CPU 0(1) -> Node 0 Mar 6 17:55:35 sun > vxvm:vxconfigd: V-5-1-7601 vxvm:vxconfigd: ERROR: > Could not open file /etc/vx/array.info for writing <29>Mar 6 17:55:35 > vxvm:vxconfigd: > Mar 6 18:02:46 sun kernel: Using local APIC NMI watchdog using > perfctr0 Mar 6 17:55:35 sun vxvm:vxconfigd: V-5-1-1589 enable failed: > Cannot create portal <27>Mar 6 17:55:35 vxvm:vxconfigd: Read-only > file system; aborting Mar 6 18:02:46 sun kernel: CPU: L1 I Cache: 64K > (64 bytes/line), D cache 64K (64 bytes/line) Mar 6 17:56:44 sun fsck: > /: clean, 10198/1048576 files, 128316/2096474 blocks Not even sure > what starts it.. found vxconfigbackdup & line in this script: > > S02vxvm-recover > > > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx -- Dmitry Glushenok <[EMAIL PROTECTED]> Jet Infosystems Tel: +7 (495) 411 76 04 Fax: +7 (495) 411 76 05 _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
