Topic: Different UUIDs

[dvdsmith]

OK.  I'm at a loss, what am I doing wrong?

I have 2 brand new 80Gb Seagate IDE drives in an SME7rc3 server.  I ran RAM and various stability tests on the system with no problems.  I've tested the drives with no problems, but I get the following on bootup every time.

Jun  7 07:13:58 xxxxxx kernel: md: hdc1 has different UUID to hdc2
Jun  7 07:13:58 xxxxxx kernel: md:  adding hda2 ...
Jun  7 07:13:58 xxxxxx kernel: md: hda1 has different UUID to hdc2
Jun  7 07:13:58 xxxxxx kernel: md: created md2

I've tried them in different positions with no difference, and they are currently master drives of both IDE channels.  After reading previous posts, I wiped the secondary master drive and let it rebuild the mirror onto it from the primary master.  No difference.  I read about possibly using drives from other manufacturers, but I'm not about to play musical-hard-drives as I don't have the budget for it.  

Have I missed anything here?  Is this just an issue I'm going to have with software raid and IDE?  FYI everything else is operating fine.

FYI, raidmonitor -v give the following;

[root@xxxxxx ~]# raidmonitor -v

ALARM! RAID configuration problem

Current configuration is:

Personalities : [raid1]
md2 : active raid1 hdc2[1] hda2[0]
      78043648 blocks [2/2] [UU]

md1 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]

unused devices: <none>

Last known good configuration was:

Personalities :
unused devices: <none>

Would this be a result of the UUID message, not allowing raidmonitor to consider it a "good configuration"?

Thanks, and I hope this helps anyelse with my situation.

[dvdsmith]

FWIW, running mdadm --query --detail /dev/md[12] gets the following;

/dev/md1:
        Version : 00.90.01
  Creation Time : Fri May 19 16:25:01 2006
     Raid Level : raid1
     Array Size : 104320 (101.88 MiB 106.82 MB)
    Device Size : 104320 (101.88 MiB 106.82 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Wed Jun  7 07:15:58 2006
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0


    Number   Major   Minor   RaidDevice State
       0       3        1        0      active sync   /dev/hda1
       1      22        1        1      active sync   /dev/hdc1
           UUID : c79b541e:f5825842:9c94ff71:4470abd8
         Events : 0.1131
/dev/md2:
        Version : 00.90.01
  Creation Time : Fri May 19 16:24:02 2006
     Raid Level : raid1
     Array Size : 78043648 (74.43 GiB 79.92 GB)
    Device Size : 78043648 (74.43 GiB 79.92 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Wed Jun  7 08:18:02 2006
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0


    Number   Major   Minor   RaidDevice State
       0       3        2        0      active sync   /dev/hda2
       1      22        2        1      active sync   /dev/hdc2
           UUID : e8fb2483:840bfed0:4e2f3e1d:9e6e0fd6
         Events : 0.231438

Looks good to me  

[CharlieBrady]

OK.  I'm at a loss, what am I doing wrong?

Who says you are doing anything wrong?

I have 2 brand new 80Gb Seagate IDE drives in an SME7rc3 server.  I ran RAM and various stability tests on the system with no problems.  I've tested the drives with no problems, but I get the following on bootup every time.

Jun  7 07:13:58 xxxxxx kernel: md: hdc1 has different UUID to hdc2
Jun  7 07:13:58 xxxxxx kernel: md:  adding hda2 ...
Jun  7 07:13:58 xxxxxx kernel: md: hda1 has different UUID to hdc2
Jun  7 07:13:58 xxxxxx kernel: md: created md2

And what those messages say is that hdc1 and hdc2 should not be matched up into a mirror set, and hda1 and hdc2 should not be matched up into a mirror set. Which is all correct. The matching sets are hda1,hdc1 and hda2,hdc2.

[CharlieBrady]

OK.  I'm at a loss, what am I doing wrong?

Who says you are doing anything wrong?

Other than panicking, that is.

[dvdsmith]

And what those messages say is that hdc1 and hdc2 should not be matched up into a mirror set, and hda1 and hdc2 should not be matched up into a mirror set. Which is all correct. The matching sets are hda1,hdc1 and hda2,hdc2.

I suspected that, as well as the fact I'm panicking

What I should have stated earlier is that Cron Daemon keeps spitting out the stupid message about "RAID configuration problem" every 15 minutes, so I had to comment out the command "raidmonitor -v" in /etc/cron.d/raidmonitor.

Before anyone says anything about doing a search, I did, alot, found nothing that would "fix" it.  If your search skills are better, good on ya, here  is a cookie.

I hate inexplicable errors, but in this case I'll just ignore it and move on.

Thanks

[gordonr]

What I should have stated earlier is that Cron Daemon keeps spitting out the stupid message about "RAID configuration problem" every 15 minutes, so I had to comment out the command "raidmonitor -v" in /etc/cron.d/raidmonitor.

That file is not included in a standard SME7 install - the raidmonitor is a supervised service and does not run from cron.

[dvdsmith]

That file is not included in a standard SME7 install - the raidmonitor is a supervised service and does not run from cron.

My mistake.  I believe the file was from the raidmonitor contrib.  I said "Cron Daemon" because that is the sender listed for the recurring email.  Thanks

[dvdsmith]

I guess this thread should be under contribs.  I found out how to fix the raidmonitor message, and I hope this helps anyone dealing with it in the future.

Running "raidmonitor -i" re-syncs the last known configuration.  After that everything runs as it should.   Thanks to Darrell May for another great contrib.

I found the answer here; http://forums.contribs.org/index.php?topic=14995.0

[CharlieBrady]

I guess this thread should be under contribs.  I found out how to fix the raidmonitor message, and I hope this helps anyone dealing with it in the future.

Running "raidmonitor -i" re-syncs the last known configuration.  After that everything runs as it should.   Thanks to Darrell May for another great contrib.

I found the answer here; http://forums.contribs.org/index.php?topic=14995.0

Your fix will only be temporary. At some time in the future you will start to get similar messages.

The proper fix is to remove the contrib. You do not need to have two raid monitors. SME7 comes with its own raid monitor, which doesn't suffer from this problem that afflicts Darrell's contrib.

[dvdsmith]

Thanks