Re: VxVM : Can't open /dev/vx/rdsk/bootdg/rootvol

From: Sivakanth Mundru (mundru.sun_at_gmail.com)
Date: 05/20/05

  • Next message: Joerg Schilling: "Re: GPIB board drivers for Solaris" 
    Date: 20 May 2005 03:07:02 -0700

    M.H wrote:
    > Hello everybody,
    >
    > 1. My /etc/vfstab is correct :
    >
    > /dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol /
    > ufs 1 no -
    >
    > 2. I'm using VxVM 4.0 so having bootdg in /etc/vfstab is normal.
    >
    > 3. Just to clarify something about my broblem:
    > This is a test server with two disks ( boot(c0t0d0s0 &
    > bootmirror(c0t1d0s0) disks). I want to test the "VERITAS[TM] Volume
    > Manager 3.x/4.x: Installing Kernel patches" below (when i want to
    > install a solaris kernel patch, i want to put the bootmirror disk
    > OFFLINE anf if the patching goes wrong I can boot from the bootmirror

    > disk as explained in the document).
    >
    > - 1st problem: When I offline the bootmirror(c0t1d0s0) disk ,
    after
    > I booting from cdrom, the /dev/dsk/c0t1d0s0 is not clean, I should
    fsck
    > and correct some problems.
    > -2nd problem: When I reboot the system from the bootmirror disk
    and
    > before "Reattaching the plexes rootvol-01, swapvol-01, to the
    relevant
    > volume and resync." (see below) , the system drops on the maintenance

    > shell because it can't mount /dev/vx/dsk/bootdg/rootvol as I said on
    the
    > my first mail.
    >
    > Thanks for the help.
    >
    >
    > ======= Begin of the document=======
    > Document Audience: SPECTRUM
    >
    > Document ID: 79356
    >
    > Title: VERITAS[TM] Volume Manager 3.x/4.x: Installing Kernel patches.
    >
    > Update Date: Tue Jan 04 00:00:00 MST 2005
    >
    > Products: VERITAS Volume Manager 3.5 Software, VERITAS Volume
    Manager
    > 4.0 Software
    >
    > Technical Areas: Administration
    >
    > Last Updated By: Fiona Turnbull
    >
    > Keyword(s):VxVM installing kernel patches
    >
    > Description:
    >
    > If a problem occurs during patching, a customer may wish to recover
    from
    > the mirrored rootdisk. Since all plexes will be in a clean state,
    the
    > procedure differs from recovering after disk failure.
    >
    >
    > Document Body:
    >
    > When a customer installs Kernel patches in single-user mode, vxvol
    will
    > automatically resynchronize the data from the rootdisk to the
    rootmirror
    > as all plexes are in a clean state after a reboot.
    >
    > If there has been a problem during the patching process and the
    customer
    > needs to restore from the rootmirror, they need to ensure that this
    > resync does not occur.
    >
    > In order to achieve this, each plex on the rootmirror needs to be
    > off-lined. It is then possible to boot from its underlying
    partitions
    > of the root mirror and change the state of the rootdisk to detached.
    > Then, booting from the mirror, vxvol will mirror the data from the
    > rootmirror to the rootdisk.
    >
    > Below is the recommended procedure when splitting a VxVM mirror for
    > patching.
    >
    > The plexes are defined as follows:
    >
    > rootvol-01
    > swapvol-01
    > var-01
    > usr-01
    >
    >
    > The rootmirror has the following plexes:
    >
    > rootvol-02 swapvol-02 var-02 usr-02
    >
    > 1. Split the mirror
    >
    > Offline the mirrors for the system volumes via the command line:
    >
    > # vxmend off rootvol-02
    > # vxmend off swapvol-02
    > # vxmend off var-02
    > # vxmend off usr-02
    >
    > 2. Patch the software
    >
    > Bring the system to the correct run-level to perform the software
    patching.
    >
    > 3. If successful, re-enable the mirrors and resync them:
    >
    > # vxmend on rootvol-02
    > # vxmend on swapvol-02
    > # vxmend on var-02
    > # vxmend on usr-02
    > # vxrecover -s
    >
    >
    > 4. If unsuccesful, use the procedure below.
    >
    > *
    > Boot the system
    >
    > OBP> boot cdrom -sw
    >
    >
    > *
    >
    > After mounting the root partition of the rootmirror disk,
    backup
    > and edit the /etc/vfstab file. Replace the /dev/vx entries with
    > underlying slice entries for all filesystems that reside on the
    system disk.
    > *
    >
    > Backup and edit the /etc/system file, removing the following
    two
    > entries:
    >
    > rootdev:/pseudo/vxio@0:0
    > set vxio:vol_rootdev_is_volume=1
    >
    >
    > *
    >
    > Touch the /etc/vx/reconfig.d/state.d/install-db file to
    prevent
    > VxVM from starting on the next boot from this disk.
    > *
    >
    > Shutdown and explicitly boot from the mirror disk.
    > *
    >
    > Start-up VxVM processes manually.
    >
    > # rm /etc/vx/reconfig.d/state.d/install-db
    > # vxiod set 10
    > # vxconfigd -d
    > # vxdctl init <hostname>
    > # vxdctl enable
    >
    >
    > *
    > Change the states of the volumes rootvol, swapvol and var so
    that
    > rootvol-01, swapvol-01, var-01 and usr-01 plexes are detached, and
    > rootvol-02, swapvol-02, var-02 and usr-02 plexes are now the only
    clean
    > plex in each of the volumes.
    >
    > # vxplex -f det rootvol-01
    > # vxmend on rootvol-02
    > # vxmend fix clean rootvol-02
    >
    >
    > *
    > Restore the saved /etc/vfstab and /etc/system files.
    >
    > *
    >
    > Reboot the system, booting explicitly from the mirror disk
    again.
    > *
    >
    > Reattach the plexes rootvol-01, swapvol-01, var-01 and usr-01
    to
    > the relevant volume and resync.
    >
    > # vxplex att rootvol-01 rootvol-02
    > # vxplex att swapvol-01 swapvol-02
    > # vxplex att var-01 var-02
    > # vxplex att usr-02 usr-02
    > ===END of the Document===========
    >
    > BR
    >
    > haed.
    >
    > Groups Poster wrote:
    > > M.H wrote:
    > >
    > >>Hi,
    > >>
    > >>When the server started, it drops on the maintenance shell because
    > >
    > > it
    > >
    > >>can't mount the /dev/vx/rdsk/bootdg/rootvol.
    > >
    > >
    > > Can you please cut and paste what you have for rootvol in the
    vfstab.
    > > Is it maybe trying to mount the raw device?
    > >
    > >
    > >
    > >
    > >>bash-2.03# mount /dev/vx/rdsk/bootdg/rootvol /mnt
    > >>mount: /dev/vx/rdsk/bootdg/rootvol not a block device
    > >
    > >
    > > Like Darren said you should mount the dsk and not rdsk.
    > >
    > >
    > >
    > >>bash-2.03# vxdiskadm
    > >>VxVM vxdiskadm ERROR V-5-2-3540 Cannot create lock file
    > >>/var/spool/locks/.DISKAD
    > >>D.LOCK
    > >
    > >
    > > Probably because /var isnt mounted.
    > >
    > >
    > >>================
    > >>bash-2.03# vxprint -Ath
    > >>Disk group: rootdg
    > >
    > >
    > > The vxprint looks ok. Can you post an output of vxdisk list too?
    > >
    > >
    > >
    > >>BR
    > >>haed
    > >
    > >

    If you are booted off of bootdisk disassociate the plexes corresponding
    to bootmirror and vice versa.

    Mount the slice 0 of the removed disk on /mnt and edit the
    /mnt/etc/vfstab
    to point the rootvol and swapvol to raw slices.

    Comment the rootdev entries in /mnt/etc/system file.

    This way even if your patches fail and if you are at ok prompt you can
    just do a boot vx-bootmirror

    Once you are up on the raw slices you can encapsulate the disk and
    mirror the patched disk to get back to where the bootdisk was before
    patch install to have a mirrored bootdisk until next patch schedule.

    HTH,
    S

  • Next message: Joerg Schilling: "Re: GPIB board drivers for Solaris"

    Relevant Pages

    • Re: Move to new hardware
      ... I'll try backup (I still have the original hard disk mirror set), ... install a new basic volume and restore from Full + System State. ... would not start as the hardware was too different. ...
      (microsoft.public.windowsxp.setup_deployment)
    • A couple raid questions
      ... I would like to install a second drive and set it up as a mirror using ... If I install a new disk, ... but the kernel is not raid enabled? ...
      (comp.os.linux.misc)
    • Re: Patching Solaris 9 systems to "current"
      ... This will bring the systems up to date, patch wise. ... If the system has mirrored boot drives, ... Install any patch utility patches first. ... Install the most recent patch cluster*, ...
      (comp.unix.solaris)
    • Re: Booting Directly from Mirror after losing Primary
      ... >>can't mirror on separate controllers, so if a controller goes down, you've ... >>FDISK), because the server will try to boot from the disk (as defined in the ... >>driver when it starts from the hard disk? ... the correct location during GUI mode install. ...
      (microsoft.public.win2000.setup_deployment)
    • Major problem after XP GDI patch (KB833987)
      ... - a second XP install on a 2nd partition to recover some data from C: ... I cannot Repair C: ... but my Medion PC came with a full XP disk, ... Are there any known problems with this MS patch? ...
      (microsoft.public.windowsupdate)