Solved

Error messages on boot after mirroring two new IDE disks in an Ultra 5 system.

Posted on 2004-09-15
4
1,725 Views
Last Modified: 2013-12-27
After mirroring two IDE drives on a Sun Ultra 5 system, I get the following error messages.

1) Warning: add-spec: No major number for mpt;
2) /usr/sbin/vold[285]: [ID 159315 daemon.error] vol_init: already a daemon running
3) md-mirror: [ID437521 Kern.info] NOTICE md:d14:B-FAILFAST I/O disabled.

Here's the metastat output:
# metastat
d33: Mirror
    Submirror 0: d13
      State: Okay        
    Submirror 1: d23
      State: Okay        
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 11665584 blocks (5.6 GB)

d13: Submirror of d33
    State: Okay        
    Size: 11665584 blocks (5.6 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t0d0s4          0     No            Okay   Yes

d23: Submirror of d33
    State: Okay        
    Size: 11665584 blocks (5.6 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t3d0s4          0     No            Okay   Yes

d32: Mirror
    Submirror 0: d12
      State: Okay        
    Submirror 1: d22
      State: Okay        
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10240272 blocks (4.9 GB)

d12: Submirror of d32
    State: Okay        
    Size: 10240272 blocks (4.9 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t0d0s3          0     No            Okay   Yes

d22: Submirror of d32
    State: Okay        
    Size: 10240272 blocks (4.9 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t3d0s3          0     No            Okay   Yes

d31: Mirror
    Submirror 0: d11
      State: Okay        
    Submirror 1: d21
      State: Okay        
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 2097648 blocks (1.0 GB)

d11: Submirror of d31
    State: Okay        
    Size: 2097648 blocks (1.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t0d0s1          0     No            Okay   Yes

d21: Submirror of d31
    State: Okay        
    Size: 2097648 blocks (1.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t3d0s1          0     No            Okay   Yes

d30: Mirror
    Submirror 0: d10
      State: Okay        
    Submirror 1: d20
      State: Okay        
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 8389584 blocks (4.0 GB)

d10: Submirror of d30
    State: Okay        
    Size: 8389584 blocks (4.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t0d0s0          0     No            Okay   Yes

d20: Submirror of d30
    State: Okay        
    Size: 8389584 blocks (4.0 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t3d0s0          0     No            Okay   Yes

d34: Mirror
    Submirror 0: d14
      State: Okay        
    Submirror 1: d24
      State: Okay        
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 7413840 blocks (3.5 GB)

d14: Submirror of d34
    State: Okay        
    Size: 7413840 blocks (3.5 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t0d0s5          0     No            Okay   Yes

d24: Submirror of d34
    State: Okay        
    Size: 7413840 blocks (3.5 GB)
    Stripe 0:
        Device     Start Block  Dbase        State Reloc Hot Spare
        c0t3d0s5          0     No            Okay   Yes

hsp001: is empty

Device Relocation Information:
Device   Reloc  Device ID
c0t3d0   Yes    id1,dad@AST320011A=3HT5PHJM
c0t0d0   Yes    id1,dad@AST320011A=3HT5R3HH


What do these error messages mean and what to do to get rid of them?


0
Comment
Question by:dee43
  • 2
  • 2
4 Comments
 
LVL 38

Expert Comment

by:yuzh
Comment Utility
Please read the following Sun doc:
#-------------------------------------------------------------------------------------------------------
Document ID: 74181
Title: Solaris[TM]: "WARNING: add_spec: No major number for mpt"
Synopsis: Solaris[TM]: "WARNING: add_spec: No major number for mpt"
Update Date: Mon Aug 02 00:00:00 MDT 2004
Products:  Solaris 8 Operating System
Technical Areas:  Patch

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Keyword(s):add_spec, mpt, major number

Problem Statement: Top

After installing a patch to update /etc/driver_classes with
an "mpt" entry (for example, 108528-xx with xx>21), the system may
generate the following WARNING messages at boot time:

 SunOS Release 5.8 Version Generic_108528-29 64-bit
 Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
 WARNING: add_spec: No major number for mpt
 WARNING: add_spec: No major number for mpt
 WARNING: add_spec: No major number for mpt
 WARNING: add_spec: No major number for mpt
 [...]
 WARNING: add_spec: No major number for mpt
 WARNING: add_spec: No major number for mpt
 WARNING: add_spec: No major number for mpt
 configuring IPv4 interfaces: hme0.
 configuring IPv6 interfaces: hme0.

The following message appears in the /var/sadm/patch/<patchid>/log file
when the entry has not been successfully added to the /etc/name_to_major
file:
          SUNWcsr: failed to add mpt to  /etc/name_to_major:
          (mpt) already in use as a driver or alias.

Explanation:
============
The problem is due to a reference in /etc/driver_classes to the
mpt driver. The mpt driver isn't added to the system because the
/etc/driver_aliases file already had an entry with the mpt driver. Because
of this, the add_drv failed when trying to install the driver.

This is an example of the inconsistencies described in Bug ID 4939994,
"Inconsistency between name_to_major and driver_aliases."
Resolution: Top

To solve this problem, a script has been created to identify the
inconsistencies between /etc/driver_aliases and /etc/name_to_major.
This script can also add the missing entries if they are listed in a
"reference" name_to_major file.

Here is an example of the way to use the attached script:

# cksum InconsitencyFixTool.tar.gz
1091730651      4410    InconsitencyFixTool.tar.gz

# gzip -dc InconsitencyFixTool.tar.gz | tar -xvf -
x InconsitencyFixTool, 0 bytes, 0 tape blocks
x InconsitencyFixTool/README, 1364 bytes, 3 tape blocks
x InconsitencyFixTool/name_to_major.InconsitencyFix, 4928 bytes, 10 tape blocks
x InconsitencyFixTool/name_to_major.i386.5.8, 841 bytes, 2 tape blocks
x InconsitencyFixTool/name_to_major.i386.5.9, 889 bytes, 2 tape blocks
x InconsitencyFixTool/name_to_major.sparc.5.8, 1831 bytes, 4 tape blocks
x InconsitencyFixTool/name_to_major.sparc.5.9, 1815 bytes, 4 tape blocks

# cd InconsitencyFixTool
# ./name_to_major.InconsitencyFix
Saving original files into .
Inconsistency found between //etc/driver_aliases and //etc/name_to_major on
the following driver(s):
mpt

Add  mpt  to //etc/name_to_major ? [y] y
Adding the following devices to //etc/name_to_major :
mpt 215
#

Reboot the system.
Temporary Workaround: Top

If the above script cannot be used, there are two other ways to fix the
problem:

1. Remove the "mpt" lines from /etc/driver_classes and /etc/driver_aliases.

   They should look like the following:
     driver_aliases:mpt "pci1000,30"
     driver_classes:mpt      scsi

   Next, install (or remove and reinstall) a patch updating all
   those files [/etc/driver_aliases /etc/driver_classes  
   /etc/name_to_major]. For example, install the mpt patch 115275-01 (or
   above) or a new kernel Update patch.

   OR

2. Add the missing "mpt" entry in the /etc/name_to_major file
   to correct the problem with the patch installation.

   You must manually append the "mpt" entry at the end
   of the /etc/name_to_major file as follows:

          mpt XXX

   Where XXX is the maximum+1 of the numbers already given to
   the other drivers in this file. Separate "mpt" and the given number with
   a space character.

   For example:

   # tail /etc/name_to_major
   fasttrap 223
   dmfe 224
   todds1307 225
   pool 226
   zcons 227
   ipf 228
   pfil 229
   ctsmc 230
   bl 231
   mpt 232

   Reboot the system.

Additional Information: Top

History:
========
Two patches have been identified that can cause the problem:

    108974-31(or greater): SunOS 5.8: dada, uata, dad, sd, ssd and scsi
    drivers patch
   
    OR

    109885-14 SunOS 5.8: glm patch

    Only on top of a kernel patch 108528-xx where xx <= 21.

Note: If you have a more recent version than -21 before installing
the above patches, the problem will not occur.

Impact:
=======
The mpt driver would not be installed correctly and cannot be used.
Attachments: Top

76676 - InconsistencyFixTool.tar.gz

Follow the following link (at the buttom of the page) and download InconsistencyFixTool.tar.gz :
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-25-74181-1

0
 

Author Comment

by:dee43
Comment Utility
Yuzh,

Thanks!  I added the missing "mpt" entry to the /etc/name_to_major file. No more warning message at boot up

Any ideas on the other error messages?  

 
0
 
LVL 38

Accepted Solution

by:
yuzh earned 300 total points
Comment Utility
You can ignore 2) and 3).

    2) means that you have more than one startup script try to run vold, and you only need
one.
    3). It is not an error! see the following doc to learn more details:

#----------------------------------------------------------------------------------------------------
Document ID: 74915
Title: Solstice Disksuite[TM] (SDS) / Solaris Volume Manager (SVM):Information message: md_mirror: B_FAILFAST I/O disabled
Synopsis: Solstice Disksuite[TM] (SDS) / Solaris Volume Manager (SVM):Information message: md_mirror: B_FAILFAST I/O disabled
Update Date: Tue Sep 14 00:00:00 MDT 2004
Products:  Solstice DiskSuite 4.2.1 Software  Solaris Volume Manager Software
Technical Areas:  Troubleshooting  RAID (Redundant Array of Independent Disks)

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Keyword(s):md_mirror, B_FAILFAST, message, FailFast, RAID5, metadevice

Problem Statement: Top

The following messages are seen:

  md_mirror: NOTICE: md: d1: B_FAILFAST I/O disabled
  md_mirror: NOTICE: md: d2: B_FAILFAST I/O disabled
  md_mirror: NOTICE: md: d3: B_FAILFAST I/O disabled
  md_mirror: NOTICE: md: d4: B_FAILFAST I/O disabled
  md_mirror: NOTICE: md: d5: B_FAILFAST I/O disabled
What are these trying to tell me?

Resolution: Top

These are not errors. These are informational (NOTICE) messages
telling you that the driver underlying your metadevices does not
support the B_FAILFAST option and, as a result, that capability will
not be active for speedier recovery. There is no way to disable these
messages.

One reason you would get this informational message is if the disk
driver doesn't have failfast support (ddi-failfast-supported property
not defined in the driver).

These messages, if printed, can be printed whenever a driver reloads.
Typically, that is when the system boots, but can also occur more
infrequently at other times once the system is up and running.

FYI: What is failfast support? In a nutshell, it allows for the driver
to fail an underlying disk device "faster" than normal if the device is
part of a redundant (mirrored or RAID5) metadevice.

FailFast support was added to the Solaris 'sd' and 'ssd' drivers in a
patch on Solaris[TM] 8 and 9. If you are using one or both of these
drivers, you should upgrade to the latest version of the patch to get
the failfast support.

To determine if any of the drivers on the system have failfast support,
you can run:

       # prtconf -vP | grep ddi-failfast-supported
of course, you will have to look at the actual output of the 'prtconf
-vP' command to see what drivers have the 'ddi-faildast-supported' flag
turned on.

At the time this doc was written, no failfast support existed on x86
versions of Solaris 8 or 9.

Temporary Workaround: Top


Additional Information: Top

#--------------------------------------------------------------------------------------------------

From: http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-25-74915-1

Cheers!
0
 

Author Comment

by:dee43
Comment Utility
Thanks for the technical docs and explaining what these messages mean.  I may have antoher question on making a mirror disk bootable... I'm having trouble booting to the mirror disk.  I will try a few more things before I post the question. . . so be on the look out for my question.

Thanks so much!!

Dee
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Hello fellow BSD lovers, I've created a patch process for patching openjdk6 for BSD (FreeBSD specifically), although I tried to keep all BSD versions in mind when creating my patch. Welcome to OpenJDK6 on BSD First let me start with a little …
Introduction Regular patching is part of a system administrator's tasks. However, many patches require that the system be in single-user mode before they can be installed. A cluster patch in particular can take quite a while to apply if the machine…
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now