softraid1 questions

From: Alexander Linkenbach (Linkenbach_at_bigfoot.com)
Date: 10/28/03 

Date: Mon, 27 Oct 2003 23:07:05 +0000 (UTC)

Hi,
I have a softraid1 and had a drive failure recently. I was able to
hotadd a new drive with mdadm -a without hassle but funnily enough I
still get the following in /var/boot.msg:

<6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
<6>md: Autodetecting RAID arrays.
<6> [events: 000000a9]
<6>md: autorun ...
<6>md: considering hdb1 ...
<6>md: adding hdb1 ...
<6>md: created md0
<6>md: bind<hdb1,1>
<6>md: running: <hdb1>
<6>md: hdb1's event counter: 000000a9
<4>md0: former device [dev 08:03] is unavailable, removing from array!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<6>md: RAID level 1 does not need chunksize! Continuing anyway.
<3>kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
<3>md: personality 3 is not loaded!
<4>md :do_md_run() returned -22
<6>md: md0 stopped.
<6>md: unbind<hdb1,0>
^^^^^^^^^^^^^^^^^^^^^
<6>md: export_rdev(hdb1)
<6>md: ... autorun DONE.

<4>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
<4>SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB)
<6> sda: sda1 sda2 sda3

<6>md: raid1 personality registered as nr 3
<6>md: Autodetecting RAID arrays.
<6> [events: 000000a9]
<6> [events: 000000a9]
<6>md: autorun ...
<6>md: considering [dev 08:03] ...
<6>md: adding [dev 08:03] ...
<6>md: adding hdb1 ...
<6>md: created md0
<6>md: bind<hdb1,1>
<6>md: bind<[dev 08:03],2>
<6>md: running: <[dev 08:03]><hdb1>
<6>md: [dev 08:03]'s event counter: 000000a9
<6>md: hdb1's event counter: 000000a9
<6>md: RAID level 1 does not need chunksize! Continuing anyway.
<6>md0: max total readahead window set to 508k
<6>md0: 1 data-disks, max readahead per data-disk: 508k
<6>raid1: device [dev 08:03] operational as mirror 1
<6>raid1: device hdb1 operational as mirror 0
<6>raid1: raid set md0 active with 2 out of 2 mirrors
<6>md: updating md0 RAID superblock on device
<6>md: [dev 08:03] [events: 000000aa]
<6>(write) [dev 08:03]'s sb offset: 8281408
<6>md: hdb1 [events: 000000aa]
<6>(write) hdb1's sb offset: 8281408
<6> [events: 7a697320]
<3>md: invalid raid superblock magic on md0
<4>md: md0 has invalid sb, not importing!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<4>md: no nested md device found
<6>md: ... autorun DONE.
<4>md: swapper(pid 1) used obsolete MD ioctl, upgrade your software to
use new ictls.
<4>reiserfs: found format "3.6" with standard journal
<4>reiserfs: enabling write barrier flush mode
<4>reiserfs: using ordered data mode
<4>reiserfs: checking transaction log (device md(9,0)) ...
<4>for (md(9,0))

Looks stragne to me somehow.
however:

mother:/home/alex # mdadm -D /dev/md0
/dev/md0:
         Version : 00.90.00
   Creation Time : Mon Oct 20 17:50:26 2003
      Raid Level : raid1
      Array Size : 8281408 (7.90 GiB 8.48 GB)
     Device Size : 8281408 (7.90 GiB 8.48 GB)
    Raid Devices : 2
   Total Devices : 2
Preferred Minor : 0
     Persistence : Superblock is persistent

     Update Time : Mon Oct 27 20:09:33 2003
           State : dirty, no-errors
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0

     Number Major Minor RaidDevice State
        0 3 65 0 active sync /dev/hdb1
        1 8 3 1 active sync /dev/sda3
            UUID : 8942b2fa:ffc8e409:5b28a5dc:a4edeef6
          Events : 0.170

And the "dirty" under State is something else I find somehow suspicious..
Can anybody enlighten me, please?

alex

System is a SuSE 9.0 2.4.21-99-smp4G, sda a 10G IBM Ultrastar, hdb a
120G Western Digital

Quantcast