3 Replies Latest reply on Nov 29, 2006 9:40 AM by 807567

    V480 boot problems

    807567
      Had a power outage yesterday, and now one of out 480's won't boot:

      Rebooting with command: boot -ar
      Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0:a File and args: -ar
      Enter filename [kernel/sparcv9/unix]:
      Enter default directory for modules [platform/SUNW,Sun-Fire-480R/kernel /platform/sun4u/kernel /kernel /usr/kernel]:
      Name of system file [etc/system]:
      SunOS Release 5.8 Version Generic_117350-39 64-bit
      Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
      /
      The /etc/path_to_inst on your system does not exist or is empty.
      Do you want to rebuild this file [n]? y
      root filesystem type [ufs]:
      Enter physical name of root device
      [pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cfb5590a,0:a]:
      Starting VxVM restore daemon...
      VxVM starting in boot mode...
      configuring IPv4 interfaces: ce0 ce1 qfe0 qfe1 qfe2.
      Hostname: ppaunix04
      VxVM starting special volumes ( swapvol rootvol )...
      mount: /dev/vx/dsk/rootvol is not this fstype.
      /sbin/rcS: /etc/dfs/sharetab: cannot create
      failed to open /etc/coreadm.confConfiguring /dev and /devices
      syseventd: Unable to open daemon lock file '/etc/sysevent/syseventd_lock': 'Read-only file system'devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
      devfsadm: open failed for /dev/.devfsadm_dev.lock: Read-only file system
      Configuring the /dev directory (compatibility devices)
      /etc/rcS.d/S50devfsadm: /tmp/sock2path.87: cannot create
      VxVM general startup...
      NOTICE: vxvm:vxdmp: added disk array 60020F200000EB7B0000000000000000, datype = T3

      NOTICE: vxvm:vxdmp: added disk array 60020F200000EBD70000000000000000, datype = T3

      vxvm:vxconfigd: ERROR: Could not open file /etc/vx/array.info for writing

      rm: Unable to remove directory /var/vxvm/tempdb: Read-only file system
      vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
      System error in configuration copy; transactions are disabled.
      vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
      vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
      VxVM: Could not find /etc/vx/reconfig.d/saveconf.d/swapdev.
      dumpadm: failed to open /etc/dumpadm.conf: Read-only file system
      vxvm: Vold is not enabled for transactions
      No volumes started
      UX:vxfs qlogrec: ERROR: Cannot open file /etc/qlog/config.lock
      UX:vxfs qlogrec: ERROR: Problem writing file /etc/qlog/config.lock: Bad file number
      UX:vxfs qlogck: ERROR: Cannot open file /etc/qlog/config.lock
      UX:vxfs qlogck: ERROR: Problem writing file /etc/qlog/config.lock: Bad file number
      UX:vxfs qlogck: TO FIX: Command qlogck was not successful
      UX:vxfs qlogck: WARNING: Fix whatever problem was encountered and rerun
      UX:vxfs qlogck: WARNING: the command qlogck

      UX:vxfs qlogck: WARNING: Running the command qlogck with the -f option
      UX:vxfs qlogck: WARNING: will fix most of the problem(s) but will force
      UX:vxfs qlogck: WARNING: a full consistency check (full fsck)
      UX:vxfs qlogck: WARNING: on the VxFS volume(s) which cannot be fixed.

      The QuickLog routine 'qlogck' encountered the errors mentioned above. It is
      recommended that you enter the maintenance shell and attempt to correct
      these problems. Once all possible corrections have been made, enter
      Control-d to exit the maintenance shell, and initialization will resume.
      See qlogck(1M) for assistance.


      Type control-d to proceed with normal startup,
      (or give root password for system maintenance):

      Any ideas?
        • 1. Re: V480 boot problems
          807567
          Sorted.../etc/path_to_inst file was corrupt; devfsadm -r did the trick
          • 2. Re: V480 boot problems
            807567
            Paul,

            We are having the same problem currently. defsadm -r requires the root path as an argument. Do you remember what you used ?

            Thanks
            • 3. Re: V480 boot problems
              807567
              I did as follows:

              Go to ok prompt and boot from cdrom

              ok> boot cdrom -s
              fsck the root slice
              # fsck -y /dev/rdsk/c1t0d0s0

              mount root
              # mount /dev/dsk/c1t0d0s0 /new

              save old path_to_inst
              # mv /new/etc/path_to_inst /new/etc/path_to_inst.old

              remove old devices
              # rm /new/dev/rdsk/c* ; /new/dev/dsk/c* ; /new/dev/cfg/c*

              rebuild path_to_inst
              # devfsadm -r /new -p /new/etc/path_to_inst

              unmount to /new root slice and reboot
              # umount /new
              # init 6