Re: issue with mdadm and mirroring drives
25/01/2012 19:16, Joey L wrote:
In-line reply ;
> Okay..I am telling all in this email -:)
>
> My configuration is as such:
> /dev/md0 = /dev/sdc1 and /dev/sdd1
> /dev/md1 = /dev/sda1 and /dev/sb1
>
> ****My swap partitions are not part of the array or mirror at all -
> they are just regular partitions - they are:
> /dev/sdc2 and /dev/sdd2.
Any particular reason do do that ? If you want your system/applications
to carry on working if a disk fails you need the swap on raid1 too.
>
> When I boot the system with all drives in, I get the superflous error.
>
> So the only way to boot is only to put in /dev/sdc alone and boot.
> when i get to a linux prompt, I insert the second drive into the system /dev/sdd
>
> To sync them, /dev/sdd has already failed, so i run
> sfdisk -d /dev/sdc | sfdisk /dev/sdd
> ** i get an error that nothing has changed - so I run it with the
> --force command to get the partitions identical like:
> sfdisk -d /dev/sdc | sfdisk --force /dev/sdd
Why do you do that ? You are forcing the partitioning of the first disk
onto the second, this could work at raid creation time but isn't the
proper procedure to re-add a failed member to an array. You don't have
to "sync" the data and even less the disk partitioning manually prior to
re-adding it to the raid. mdadm will handle the resync.
>
> Once that is successful - i run mdadm --manage /dev/md0 --add /dev/sdd1
>
> And the sync process starts, and when it is done yesterday, I ran this
> and got these errors:
>
>
> root@rider:~# grub-install --recheck --no-floppy /dev/sdc
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> Installation finished. No error reported.
> root@rider:~# grub-install --recheck --no-floppy /dev/sdd
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> error: superfluous RAID member (2 found).
> Installation finished. No error reported.
> root@rider:~# grub-install --recheck --no-floppy /dev/sdc
>
>
[cut]
>
>
> My parted -l is:
>
>
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sda: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 32.3kB 1000GB 1000GB primary ext3 raid
>
>
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sdb: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 32.3kB 1000GB 1000GB primary ext3 raid
>
>
> Model: ATA ST31000340AS (scsi)
> Disk /dev/sdc: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 1049kB 996GB 996GB primary ext3 raid
> 2 996GB 1000GB 4204MB primary linux-swap(v1)
>
>
> Model: ATA ST31000528AS (scsi)
> Disk /dev/sdd: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
>
> Number Start End Size Type File system Flags
> 1 1049kB 996GB 996GB primary ext4 raid
> 2 996GB 1000GB 4204MB primary linux-swap(v1)
>
Why do you have file-systems on your partitions ? Only the "md" raid
devices should be formatted with a file-system, not the underlying
partitions !
I would be curious to know what "fsck" says about your md devices (fsck
/dev/md0 for example) ?
> Warning: Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0
> has been opened read-only.
>
> Error: /dev/fd0: unrecognised disk label
>
> Model: Linux Software RAID Array (md)
> Disk /dev/md0: 996GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 996GB 996GB ext4
>
>
> Model: Linux Software RAID Array (md)
> Disk /dev/md1: 1000GB
> Sector size (logical/physical): 512B/512B
> Partition Table: loop
>
> Number Start End Size File system Flags
> 1 0.00B 1000GB 1000GB ext4
>
>
>
[cut]
>
>
>
> I am currently terrified to reboot my box --- any help would be appriciated -
>
> I have NOT run the command "update-initramfs -u -k all " and do not
> know if i should.
>
>
> thanks
> mjh
You seem to be walking in the dark awaiting to hit the next pole ;-) .
Updating the initrd won't solve file-system or raid inconsistencies, it
would only be necessary if the content of mdadm.conf had changed.
I am starting to think that you have much lower level problems. When you
created this system, where the disks "clean", or did you use "sfdisk"
over existing formatted partitions ? Where the disks used in a raid
before ? If this is the case you should consider backing up and
recreating the raid properly.
Also, if one disk is repeatedly dropping from the raid array, consider
looking at the "smart" values, it may be dying.
Reply to: