Topic: Is this are problem - doesn't contain a valid partition tab

[beeboob]

Hey all

I am running are sme 7.2 Upgrade from 7. Running 2 hdd i software raid.

I get this mail

A DegradedArray event had been detected on md device /dev/md1

A DegradedArray event had been detected on md device /dev/md2

At them same time...

So i want to check

When i

fdisk -l

Disk /dev/hda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   fd  Linux raid autodetect
/dev/hda2              14       19929   159975270   fd  Linux raid autodetect

Disk /dev/hdc: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1          13      104391   fd  Linux raid autodetect
/dev/hdc2              14       19929   159975270   fd  Linux raid autodetect

Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md2: 163.8 GB, 163814572032 bytes
2 heads, 4 sectors/track, 39993792 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/dm-0: 162.7 GB, 162738995200 bytes
2 heads, 4 sectors/track, 39731200 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 1040 MB, 1040187392 bytes
2 heads, 4 sectors/track, 253952 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/dm-1 doesn't contain a valid partition table


But a

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hda1[0]
      104320 blocks [2/1] [U_]

shows that

But do i have are BIG problem. And how do i fix this??

[TrevorB]

Disk /dev/md1 doesn't contain a valid partition table

These are standard messages and can be ignored.

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hda1[0]
      104320 blocks [2/1] [U_]

shows that

But do i have are BIG problem. And how do i fix this??

Yes, this shows that your raid array is now working with 1 disk ONLY (/dev/hda)
You can get more detail by

Code: [Select]

mdadm --detail /dev/md1
mdadm --detail /dev/md2By the looks of your other commands (fdisk), /dev/hdc is still running, so you may be able to get away with

Code: [Select]

mdadm /dev/md1 -r /dev/hdc1
mdadm /dev/md1 -a /dev/hdc1
mdadm /dev/md2 -r /dev/hdc2
mdadm /dev/md2 -a /dev/hdc2Or you may have to replace your second drive.

But in either case you need to look in the logs to see if you can see what caused the failure. Even if it comes back, it may fail soon.

Trevor B

[beeboob]

So many thanks for the replay...

I try

mdadm --detail /dev/md1

/dev/md1:
        Version : 00.90.01
  Creation Time : Wed Dec 28 23:38:51 2005
     Raid Level : raid1
     Array Size : 104320 (101.89 MiB 106.82 MB)
    Device Size : 104320 (101.89 MiB 106.82 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Fri Aug 10 02:53:51 2007
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : cd8b3012:87336a15:7196b657:0592ed17
         Events : 0.18325

    Number   Major   Minor   RaidDevice State
       0       3        1        0      active sync   /dev/hda1
       1       0        0        -      removed

and

/dev/md1:
        Version : 00.90.01
  Creation Time : Wed Dec 28 23:38:51 2005
     Raid Level : raid1
     Array Size : 104320 (101.89 MiB 106.82 MB)
    Device Size : 104320 (101.89 MiB 106.82 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Fri Aug 10 02:53:51 2007
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : cd8b3012:87336a15:7196b657:0592ed17
         Events : 0.18325

    Number   Major   Minor   RaidDevice State
       0       3        1        0      active sync   /dev/hda1
       1       0        0        -      removed

I dont understand what the comand are doing:

mdadm /dev/md1 -r /dev/hdc1
mdadm /dev/md1 -a /dev/hdc1
mdadm /dev/md2 -r /dev/hdc2
mdadm /dev/md2 -a /dev/hdc2

Can i jusdt run thoes command and se what happens and what output i get?
or do i have to replace my 2 drive??

[pfloor]

I dont understand what the comand are doing:

mdadm /dev/md1 -r /dev/hdc1
mdadm /dev/md1 -a /dev/hdc1
mdadm /dev/md2 -r /dev/hdc2
mdadm /dev/md2 -a /dev/hdc2

mdadm /dev/md1 -r /dev/hdc1 <This "removes" (-r) hdc1 from the md1 raid array
mdadm /dev/md1 -a /dev/hdc1 <This "adds" (-a) hdc1 back to the md1 array.
mdadm /dev/md2 -r /dev/hdc2 <This "removes" (-r) hdc2 from the md2 raid array
mdadm /dev/md2 -a /dev/hdc2 <This "adds" (-a) hdc2 back to the md2 array.

That will cause the arrays to rebuild themeselves.  Don't turn off the server until the arrays are done rebuilding.  You can check progress with "cat /proc/mdstat"

Can i jusdt run thoes command and se what happens and what output i get?

See if the drives will resync and then keep a VERY close eye on them.

or do i have to replace my 2 drive??

If they go out of sync again then you will need to replace the one that is failing.

Some words of advice from my past experiences:

1-Replace the IDE cables with NEW GOOD FLAT 80 wire cables. Don't use the fancy ones with the wrapping around them.
2-Make sure you have a GOOD power supply, not a $20 one.
3-Don't use IBM Deskstar drives (or Hitachi for that matter), they won't stay in sync.  This has happened to me several times.
4-Check your memory - Boot with the CD and type memtest <enter>.  This test can take a LONG time but let it run completely through at least once.  Bad memory can cause your drives to go out of sync.
5-If you are not using the CDROM, unplug it from the cable and the power supply.

[TrevorB]

Paul answered quite succinctly (and correctly). But, please look at the logs and watch that second drive, as there was a reason that it was removed from the raid array the first time (and it is likely to happen again).

Your mdadm --detail commands show that the /dev/hdc drive has already been removed, so now you only need to do

Code: [Select]

mdadm /dev/md1 -a /dev/hdc1
mdadm /dev/md2 -a /dev/hdc2to add the partitions from your second drive back into the raid arrays.

TrevorB

[beeboob]

pfloor Thats was are very god answer. Now i understand.

 I try the

 mdadm /dev/md1 -a /dev/hdc1
mdadm: hot added /dev/hdc1

And

mdadm /dev/md2 -a /dev/hdc2
mdadm: hot added /dev/hdc2

And the run

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hdc2[2] hda2[0]
      159975168 blocks [2/1] [U_]
      [>....................]  recovery =  0.2% (471808/159975168) finish=208.4min speed=12751K/sec
md1 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]

Is it not ok now?

[TrevorB]

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hdc2[2] hda2[0]
      159975168 blocks [2/1] [U_]
      [>....................]  recovery =  0.2% (471808/159975168) finish=208.4min speed=12751K/sec
md1 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]

Is it not ok now?

Yes, it is now rebuilding your array, and will take a little over 3hrs to do it (ie. it has to make them look the same).

/dev/md1  has already synced.

Trevor B

[beeboob]

My  

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hdc1[2](F) hda1[0]
      104320 blocks [2/1] [U_]

But i get are admin mail whit:

A Fail event had been detected on md device /dev/md1.

So do i have to replace md1????

And i am very unsure on who to see what raid there is faling

Or can i ""just""

1-Replace the IDE cables with NEW GOOD FLAT 80 wire cables. Don't use the fancy ones with the wrapping around them.
2-Make sure you have a GOOD power supply, not a $20 one.
3-Don't use IBM Deskstar drives (or Hitachi for that matter), they won't stay in sync. This has happened to me several times.
4-Check your memory - Boot with the CD and type memtest <enter>. This test can take a LONG time but let it run completely through at least once. Bad memory can cause your drives to go out of sync.
5-If you are not using the CDROM, unplug it from the cable and the power supply.

[TrevorB]

My  

cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hdc1[2](F) hda1[0]
      104320 blocks [2/1] [U_]

Your last one showed that it was rebuilding, so it has obviously failed again.

But i get are admin mail whit:

A Fail event had been detected on md device /dev/md1.

So do i have to replace md1????

And i am very unsure on who to see what raid there is faling

A good place to start is /var/log/messages

Or can i ""just""

1-Replace the IDE cables with NEW GOOD FLAT 80 wire cables. Don't use the fancy ones with the wrapping around them.
2-Make sure you have a GOOD power supply, not a $20 one.
3-Don't use IBM Deskstar drives (or Hitachi for that matter), they won't stay in sync. This has happened to me several times.
4-Check your memory - Boot with the CD and type memtest <enter>. This test can take a LONG time but let it run completely through at least once. Bad memory can cause your drives to go out of sync.
5-If you are not using the CDROM, unplug it from the cable and the power supply.

You can certainly try, but if it continues, I'd get a new drive (or stick with only one and put in a good backup regime).

Trevor B

[beeboob]

Many thanks...

I will get are new harddrive.

And find out off, whit off the 2 hdd i have to replace. Whit are new one...  But is ther are tips to find out off whit disk i have to change. Something like,, Is it the first on the cable og the second

And also get are better backup regime. Something that are better then the manuel backup to desktop.

from my /var/log/messages

Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 0
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 0
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 8
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 1
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 16
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 2
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 24
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 3
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 32
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 4
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 40
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 5
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 48
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 6
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 56
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 7
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 64
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 8
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 72
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 9
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 80
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 10
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 88
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 11
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 96

[TrevorB]

Something like,, Is it the first on the cable og the second

/dev/hdc is the master drive on your secondary IDE channel (ie. it should be the first drive on the second controller).

Trevor B

[beeboob]

Hey TrevorB and many thanks...

And the repport i get i /var/log/messages that s.... or??

Can it some how be are problem whit my fstab? And thats way i have all this problems.

In my fstab i have:

/dev/vg_primary/lv_root /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/vg_primary/lv_swap swap                    swap    defaults        0 0
/dev/hdd                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0


But i can only see one hdd and not 2. But on the other hand, i have software raid.

[pfloor]

Can it some how be are problem whit my fstab? And thats way i have all this problems.

No, your fstab is system generated and is fine.

In my fstab i have:

/dev/vg_primary/lv_root /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/vg_primary/lv_swap swap                    swap    defaults        0 0
/dev/hdd                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0


But i can only see one hdd and not 2. But on the other hand, i have software raid.

hda and hdc are mirrored together and become mirrored partitions in fstab.  You won't see hda or hdc in fstab.  This does tell us however, that your CDROM and hdc are on the same cable.  Try turning off the machine, unplugging the CDROM, replacing the IDE cable, starting the machine and adding hdc back into the arrays and see if it will stay synced.

Your problem is that you have I/O errors on hdc on both partitions as shown here:

Code: [Select]

Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 0
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 0
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 8
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 1
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 16
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 2

hdc (or the related hardware such as a cable, IDE controller or power problems) has gone bad on you and you need to either replace the drive or find the hardware malfunction.

[beeboob]

ahhh many thanks...

I think i am start to get some off all the things... And who my server works.

I have read are lot, But this post, have give me are lot..

Do my cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]
     
unused devices: <none>

have to like this?

[pfloor]

Do my cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
      159975168 blocks [2/1] [U_]
     
md1 : active raid1 hdc1[1] hda1[0]
      104320 blocks [2/2] [UU]
     
unused devices: <none>

have to like this?

You still have a problem.  hdc2 is not part of your md2 raid set.  It looks like hdc has gone bad on you.  You should replace it.  The new disk needs to be identical or larger.  A smaller (even 1kb smaller) disk won't work.