Unable to boot : Rootdg cannot be imported during boot - Veritas Volume Manager

This is a discussion on Unable to boot : Rootdg cannot be imported during boot - Veritas Volume Manager ; Hi, We are unable to boot our server after a restore. See below the boot sequence Any help would be greatly appreciated. {2} ok boot Resetting ... Sun Fire 880, No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Unable to boot : Rootdg cannot be imported during boot

  1. Unable to boot : Rootdg cannot be imported during boot


    Hi,
    We are unable to boot our server after a restore.
    See below the boot sequence
    Any help would be greatly appreciated.


    {2} ok boot
    Resetting ...

    Sun Fire 880, No Keyboard
    Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.6, 4096 MB memory installed, Serial #52533663.
    Ethernet address 0:3:ba:21:99:9f, Host ID: 8321999f.

    Rebooting with command: boot
    Boot device: vx-rootdisk File and args:
    SunOS Release 5.8 Version Generic_108528-18 64-bit
    Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    WARNING: forceload of drv/pci failed
    Configuring Sun Trunking devices
    nettr:qfe10 no such interface
    nettr:qfe11 no such interface
    Starting VxVM restore daemon...
    VxVM starting in boot mode...
    vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
    No valid disk found containing disk group; transactions are disabled.
    vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during boot
    /etc/rcS.d/S25vxvm-sysboot: egettxt: not found

    Halting system...
    syncing file systems... done

    Program terminated
    {2} ok

  2. Re: Unable to boot : Rootdg cannot be imported during boot

    Well, have to ask:


    What did you restore ?
    Did you just re-install the OS or did you do a "cold-metal" restore ?


    OK, now the reason for all the questions.

    When Volume Manager controls a disk (seems like Volume Manager is
    supposed to control your boot disk, and that is why it is not booting),
    Volume Manager will always put an extra slice on your disk. This slice
    holds information particular to Volume Manager (called the private region).

    Now, you might have restored the "data" but not the private region.

    OK, now what to do next.

    1. Boot from CD
    2. Mount your boot disk (say on /a)
    3. Then either edit your /a/etc/vfstab or erplace with the Veritas saved
    file in /a/etc/vfstab.prevm This would enable you to boot from
    slices and thus take Volume Manager out of the picture (just hope you've
    got your old slices still there)
    4. Now, also edit your /a/etc/system file and remove the lines that sets
    the boot device to the volume (you should see this, you can just delete
    this - or restore an older version of the system file)
    5. Now, you're ready to boot from slices again. (The above procedure is
    also described in the Trouble Shooting Guide and is known as manula
    un-encapsulation)
    6. Once booted up again, from your boot disk, without Volume Manager,
    you can redo the rootdg and boot disk. This is done by:
    a) for older versions, just run vxinstall
    b) for new versions (4.0 and above), run vxinstall, then vxdiskadm
    and select to encapsulate the bootdisk


    And if all fails, call Veritas Support (you have a support contract ??
    That is what they are for)

    F. QUIQUET wrote:
    > Hi,
    > We are unable to boot our server after a restore.
    > See below the boot sequence
    > Any help would be greatly appreciated.
    >
    >
    > {2} ok boot
    > Resetting ...
    >
    > Sun Fire 880, No Keyboard
    > Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
    > OpenBoot 4.6, 4096 MB memory installed, Serial #52533663.
    > Ethernet address 0:3:ba:21:99:9f, Host ID: 8321999f.
    >
    > Rebooting with command: boot
    > Boot device: vx-rootdisk File and args:
    > SunOS Release 5.8 Version Generic_108528-18 64-bit
    > Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    > WARNING: forceload of drv/pci failed
    > Configuring Sun Trunking devices
    > nettr:qfe10 no such interface
    > nettr:qfe11 no such interface
    > Starting VxVM restore daemon...
    > VxVM starting in boot mode...
    > vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
    > No valid disk found containing disk group; transactions are disabled.
    > vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during boot
    > /etc/rcS.d/S25vxvm-sysboot: egettxt: not found
    >
    > Halting system...
    > syncing file systems... done
    >
    > Program terminated
    > {2} ok


  3. Re: Unable to boot : Rootdg cannot be imported during boot


    Hi, below the result :

    >1. Boot from CD => OK
    >2. Mount your boot disk (say on /a) => NOK


    # ls /
    a dev kernel opt reconfigure usr
    bin devices lib platform sbin var
    cdrom etc mnt proc tmp webstart

    # mount /dev/dsk/c1t0d0s0 /mnt
    mount: the state of /dev/dsk/c1t0d0s0 is not okay
    and it was attempted to be mounted read/write
    mount: Please run fsck and try again

    # mount /dev/dsk/c1t0d0s0 /a
    mount: the state of /dev/dsk/c1t0d0s0 is not okay
    and it was attempted to be mounted read/write
    mount: Please run fsck and try again

    # mount /dev/dsk/c1t0d0s1 /mnt
    mount: the state of /dev/dsk/c1t0d0s1 is not okay
    and it was attempted to be mounted read/write
    mount: Please run fsck and try again

    # fsck /dev/dsk/c1t0d0s0
    ** /dev/dsk/c1t0d0s0
    ** Last Mounted on /
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    UNREF FILE I=427176 OWNER=root MODE=20600
    SIZE=0 MTIME=Dec 14 04:05 2005
    CLEAR? n

    # mount /dev/dsk/c1t0d0s0 /a
    mount: the state of /dev/dsk/c1t0d0s0 is not okay
    and it was attempted to be mounted read/write
    mount: Please run fsck and try again

    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfb49ba6,0
    1. c1t1d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfb45ecd,0
    2. c1t2d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfb49d2e,0
    3. c1t3d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfb49bad,0
    4. c1t4d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfb4267c,0
    5. c1t5d0
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000014c35028aa,0
    Specify disk (enter its number): 0
    selecting c1t0d0
    [disk formatted]
    format> p
    partition> p
    Current partition table (original):
    Total disk cylinders available: 14087 + 2 (reserved cylinders)

    Part Tag Flag Cylinders Size Blocks
    0 root wm 0 - 1021 4.96GB (1022/0/0) 10399872
    1 - wu 0 - 14086 68.35GB (14087/0/0) 143349312
    2 backup wm 0 - 14086 68.35GB (14087/0/0) 143349312
    3 swap wu 1022 - 1846 4.00GB (825/0/0) 8395200
    4 var wm 1847 - 3907 10.00GB (2061/0/0) 20972736
    5 unassigned wm 0 0 (0/0/0)
    0
    6 unassigned wm 0 0 (0/0/0)
    0
    7 - wu 14086 - 14086 4.97MB (1/0/0) 10176



  4. Re: Unable to boot : Rootdg cannot be imported during boot


    The mount is OK after a manually FSCK

    # fsck -Y /dev/rdsk/c1t0d0s0
    ** /dev/rdsk/c1t0d0s0
    ** Last Mounted on /
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Cyl groups
    FREE BLK COUNT(S) WRONG IN SUPERBLK
    SALVAGE? yes
    52424 files, 2656180 used, 2464634 free (2554 frags, 307760 blocks, 0.0%
    fragmentation)
    ***** FILE SYSTEM WAS MODIFIED *****

    # mount /dev/dsk/c1t0d0s0 /mnt

    # df -k
    Filesystem kbytes used avail capacity Mounted on
    /pci@8,700000/scsi@1/disk@6,0:b
    85194 78050 0 100% /
    swap 3968512 248 3968264 1% /tmp
    proc 0 0 0 0% /proc
    mnttab 0 0 0 0% /etc/mnttab
    /tmp/devices 3968512 248 3968264 1% /devices
    /tmp/dev 3968512 248 3968264 1% /dev
    /devices/pci@8,700000/scsi@1/sd@6,0:a
    503232 503232 0 100% /cdrom
    /cdrom/Solaris_8/Tools/Boot/usr
    503232 503232 0 100% /usr
    fd 0 0 0 0% /dev/fd
    /dev/dsk/c1t0d0s0 5120814 2656180 2413426 53% /mnt

    # more /etc/vfstab
    #device device mount FS fsck mount mount
    #to mount to fsck point type pass at boot options
    #
    fd - /dev/fd fd - no -
    /proc - /proc proc - no -
    /dev/vx/dsk/swapvol - - swap - no -
    /dev/vx/dsk/rootvol /dev/vx/rdsk/rootvol / ufs 1 no
    -
    /dev/vx/dsk/var /dev/vx/rdsk/var /var ufs 1 no -
    /dev/vx/dsk/appli /dev/vx/rdsk/appli /appli ufs 2 yes
    -
    /dev/vx/dsk/opt /dev/vx/rdsk/opt /opt ufs 2 yes -
    swap - /tmp tmpfs - yes -
    #NOTE: volume rootvol (/) encapsulated partition c1t0d0s0
    #NOTE: volume swapvol (swap) encapsulated partition c1t0d0s3
    #NOTE: volume var (/var) encapsulated partition c1t0d0s4
    #NOTE: volume opt (/opt) encapsulated partition c1t0d0s5
    #NOTE: volume appli (/appli) encapsulated partition c1t0d0s6
    /dev/vx/dsk/stockagedg/stockage /dev/vx/rdsk/stockagedg/stockage /stockage
    ufs 1 yes -
    /dev/vx/dsk/stockagedg/gsn /dev/vx/rdsk/stockagedg/gsn /gsn ufs
    1 yes -

    # more /etc/vfstab.prevm
    #device device mount FS fsck mount mount
    #to mount to fsck point type pass at boot options
    #
    fd - /dev/fd fd - no -
    /proc - /proc proc - no -
    /dev/dsk/c1t0d0s3 - - swap - no -
    /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no
    -
    /dev/dsk/c1t0d0s4 /dev/rdsk/c1t0d0s4 /var ufs 1 no
    -
    /dev/dsk/c1t0d0s6 /dev/rdsk/c1t0d0s6 /appli ufs 2 yes
    -
    /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /opt ufs 2 yes
    -
    swap - /tmp tmpfs - yes -

    # more /etc/system
    *ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
    *
    * SYSTEM SPECIFICATION FILE
    *

    * moddir:
    *
    * Set the search path for modules. This has a format similar to the
    * csh path variable. If the module isn't found in the first directory
    * it tries the second and so on. The default is /kernel /usr/kernel
    *
    * Example:
    * moddir: /kernel /usr/kernel /other/modules



    * root device and root filesystem configuration:
    *
    * The following may be used to override the defaults provided by
    * the boot program:
    *
    * rootfs: Set the filesystem type of the root.
    *
    * rootdev: Set the root device. This should be a fully
    * expanded physical pathname. The default is the
    * physical pathname of the device where the boot
    * program resides. The physical pathname is
    * highly platform and configuration dependent.
    *
    * Example:
    * rootfs:ufs
    * rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
    *
    * (Swap device configuration should be specified in /etc/vfstab.)



    * exclude:
    *
    * Modules appearing in the moddir path which are NOT to be loaded,
    * even if referenced. Note that `exclude' accepts either a module name,
    * or a filename which includes the directory.
    *
    * Examples:
    * exclude: win
    * exclude: sys/shmsys



    * forceload:
    *
    * Cause these modules to be loaded at boot time, (just before mounting
    * the root filesystem) rather than at first reference. Note that
    * forceload expects a filename which includes the directory. Also
    * note that loading a module does not necessarily imply that it will
    * be installed.
    *
    * Example:
    * forceload: drv/foo



    * set:
    *
    * Set an integer variable in the kernel or a module to a new value.
    * This facility should be used with caution. See system(4).
    *
    * Examples:
    *
    * To set variables in 'unix':
    *
    * set nautopush=32
    * set maxusers=40
    *
    * To set a variable named 'debug' in the module named 'test_module'
    *
    * set test_module:debug = 0x13


    *
    * Values set for install boottime environment
    *
    set scsi_options=0x58
    set scsi_reset_delay=10000
    set tmpfs:tmpfs_minfree=1
    set swapfs_minfree=0x040


    "F. QUIQUET" wrote:
    >
    >Hi,
    >We are unable to boot our server after a restore.
    >See below the boot sequence
    >Any help would be greatly appreciated.
    >
    >
    >{2} ok boot
    >Resetting ...
    >
    >Sun Fire 880, No Keyboard
    >Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
    >OpenBoot 4.6, 4096 MB memory installed, Serial #52533663.
    >Ethernet address 0:3:ba:21:99:9f, Host ID: 8321999f.
    >
    >Rebooting with command: boot
    >Boot device: vx-rootdisk File and args:
    >SunOS Release 5.8 Version Generic_108528-18 64-bit
    >Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    >WARNING: forceload of drv/pci failed
    >Configuring Sun Trunking devices
    >nettr:qfe10 no such interface
    >nettr:qfe11 no such interface
    >Starting VxVM restore daemon...
    >VxVM starting in boot mode...
    >vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration

    copies
    > No valid disk found containing disk group; transactions are disabled.
    >vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during boot
    >/etc/rcS.d/S25vxvm-sysboot: egettxt: not found
    >
    >Halting system...
    >syncing file systems... done
    >
    >Program terminated
    >{2} ok



  5. Re: Unable to boot : Rootdg cannot be imported during boot

    OK - so now you mounted the old root filesystem.

    As mentioned, you should change the vfstab not to have any Volume
    Manager in there (thus, replace the vfstab with vfstab.prevm - but make
    a copy of vfstab)

    OK, then the system file below, also does not contain any reference to
    volume manager (if this is the complete system file)


    OK, next thing is to touch /a/etc/vx/reconfig.d/state.d/install-db
    OK, so, next you should boot from your original boot disk again


    Then you can just re-run vxinstall (or use vxdiskadm) to er-encapsulate
    again

    F. QUIQUET wrote:
    > The mount is OK after a manually FSCK
    >
    > # fsck -Y /dev/rdsk/c1t0d0s0
    > ** /dev/rdsk/c1t0d0s0
    > ** Last Mounted on /
    > ** Phase 1 - Check Blocks and Sizes
    > ** Phase 2 - Check Pathnames
    > ** Phase 3 - Check Connectivity
    > ** Phase 4 - Check Reference Counts
    > ** Phase 5 - Check Cyl groups
    > FREE BLK COUNT(S) WRONG IN SUPERBLK
    > SALVAGE? yes
    > 52424 files, 2656180 used, 2464634 free (2554 frags, 307760 blocks, 0.0%
    > fragmentation)
    > ***** FILE SYSTEM WAS MODIFIED *****
    >
    > # mount /dev/dsk/c1t0d0s0 /mnt
    >
    > # df -k
    > Filesystem kbytes used avail capacity Mounted on
    > /pci@8,700000/scsi@1/disk@6,0:b
    > 85194 78050 0 100% /
    > swap 3968512 248 3968264 1% /tmp
    > proc 0 0 0 0% /proc
    > mnttab 0 0 0 0% /etc/mnttab
    > /tmp/devices 3968512 248 3968264 1% /devices
    > /tmp/dev 3968512 248 3968264 1% /dev
    > /devices/pci@8,700000/scsi@1/sd@6,0:a
    > 503232 503232 0 100% /cdrom
    > /cdrom/Solaris_8/Tools/Boot/usr
    > 503232 503232 0 100% /usr
    > fd 0 0 0 0% /dev/fd
    > /dev/dsk/c1t0d0s0 5120814 2656180 2413426 53% /mnt
    >
    > # more /etc/vfstab
    > #device device mount FS fsck mount mount
    > #to mount to fsck point type pass at boot options
    > #
    > fd - /dev/fd fd - no -
    > /proc - /proc proc - no -
    > /dev/vx/dsk/swapvol - - swap - no -
    > /dev/vx/dsk/rootvol /dev/vx/rdsk/rootvol / ufs 1 no
    > -
    > /dev/vx/dsk/var /dev/vx/rdsk/var /var ufs 1 no -
    > /dev/vx/dsk/appli /dev/vx/rdsk/appli /appli ufs 2 yes
    > -
    > /dev/vx/dsk/opt /dev/vx/rdsk/opt /opt ufs 2 yes -
    > swap - /tmp tmpfs - yes -
    > #NOTE: volume rootvol (/) encapsulated partition c1t0d0s0
    > #NOTE: volume swapvol (swap) encapsulated partition c1t0d0s3
    > #NOTE: volume var (/var) encapsulated partition c1t0d0s4
    > #NOTE: volume opt (/opt) encapsulated partition c1t0d0s5
    > #NOTE: volume appli (/appli) encapsulated partition c1t0d0s6
    > /dev/vx/dsk/stockagedg/stockage /dev/vx/rdsk/stockagedg/stockage /stockage
    > ufs 1 yes -
    > /dev/vx/dsk/stockagedg/gsn /dev/vx/rdsk/stockagedg/gsn /gsn ufs
    > 1 yes -
    >
    > # more /etc/vfstab.prevm
    > #device device mount FS fsck mount mount
    > #to mount to fsck point type pass at boot options
    > #
    > fd - /dev/fd fd - no -
    > /proc - /proc proc - no -
    > /dev/dsk/c1t0d0s3 - - swap - no -
    > /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no
    > -
    > /dev/dsk/c1t0d0s4 /dev/rdsk/c1t0d0s4 /var ufs 1 no
    > -
    > /dev/dsk/c1t0d0s6 /dev/rdsk/c1t0d0s6 /appli ufs 2 yes
    > -
    > /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /opt ufs 2 yes
    > -
    > swap - /tmp tmpfs - yes -
    >
    > # more /etc/system
    > *ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
    > *
    > * SYSTEM SPECIFICATION FILE
    > *
    >
    > * moddir:
    > *
    > * Set the search path for modules. This has a format similar to the
    > * csh path variable. If the module isn't found in the first directory
    > * it tries the second and so on. The default is /kernel /usr/kernel
    > *
    > * Example:
    > * moddir: /kernel /usr/kernel /other/modules
    >
    >
    >
    > * root device and root filesystem configuration:
    > *
    > * The following may be used to override the defaults provided by
    > * the boot program:
    > *
    > * rootfs: Set the filesystem type of the root.
    > *
    > * rootdev: Set the root device. This should be a fully
    > * expanded physical pathname. The default is the
    > * physical pathname of the device where the boot
    > * program resides. The physical pathname is
    > * highly platform and configuration dependent.
    > *
    > * Example:
    > * rootfs:ufs
    > * rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
    > *
    > * (Swap device configuration should be specified in /etc/vfstab.)
    >
    >
    >
    > * exclude:
    > *
    > * Modules appearing in the moddir path which are NOT to be loaded,
    > * even if referenced. Note that `exclude' accepts either a module name,
    > * or a filename which includes the directory.
    > *
    > * Examples:
    > * exclude: win
    > * exclude: sys/shmsys
    >
    >
    >
    > * forceload:
    > *
    > * Cause these modules to be loaded at boot time, (just before mounting
    > * the root filesystem) rather than at first reference. Note that
    > * forceload expects a filename which includes the directory. Also
    > * note that loading a module does not necessarily imply that it will
    > * be installed.
    > *
    > * Example:
    > * forceload: drv/foo
    >
    >
    >
    > * set:
    > *
    > * Set an integer variable in the kernel or a module to a new value.
    > * This facility should be used with caution. See system(4).
    > *
    > * Examples:
    > *
    > * To set variables in 'unix':
    > *
    > * set nautopush=32
    > * set maxusers=40
    > *
    > * To set a variable named 'debug' in the module named 'test_module'
    > *
    > * set test_module:debug = 0x13
    >
    >
    > *
    > * Values set for install boottime environment
    > *
    > set scsi_options=0x58
    > set scsi_reset_delay=10000
    > set tmpfs:tmpfs_minfree=1
    > set swapfs_minfree=0x040
    >
    >
    > "F. QUIQUET" wrote:
    >
    >>Hi,
    >>We are unable to boot our server after a restore.
    >>See below the boot sequence
    >>Any help would be greatly appreciated.
    >>
    >>
    >>{2} ok boot
    >>Resetting ...
    >>
    >>Sun Fire 880, No Keyboard
    >>Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
    >>OpenBoot 4.6, 4096 MB memory installed, Serial #52533663.
    >>Ethernet address 0:3:ba:21:99:9f, Host ID: 8321999f.
    >>
    >>Rebooting with command: boot
    >>Boot device: vx-rootdisk File and args:
    >>SunOS Release 5.8 Version Generic_108528-18 64-bit
    >>Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    >>WARNING: forceload of drv/pci failed
    >>Configuring Sun Trunking devices
    >>nettr:qfe10 no such interface
    >>nettr:qfe11 no such interface
    >>Starting VxVM restore daemon...
    >>VxVM starting in boot mode...
    >>vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration

    >
    > copies
    >
    >> No valid disk found containing disk group; transactions are disabled.
    >>vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during boot
    >>/etc/rcS.d/S25vxvm-sysboot: egettxt: not found
    >>
    >>Halting system...
    >>syncing file systems... done
    >>
    >>Program terminated
    >>{2} ok

    >
    >


  6. Re: Unable to boot : Rootdg cannot be imported during boot


    Fred.
    Past experience is that if the disk is not formatted for rootdisk it will
    not work on a restore. The private area and public area is different between
    root disk and other disk.

+ Reply to Thread