MDV2008.1+software Raid1+boot failure - Mandriva

This is a discussion on MDV2008.1+software Raid1+boot failure - Mandriva ; Hi, I have fresh set up a software raid-1 with 2 SATA disks successfully on my new Mandriva 2008.1 (spring). This is my first instalation MDV 2008.1. Everything seemed to work well until I tried to imitate a disk failure. ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: MDV2008.1+software Raid1+boot failure

  1. MDV2008.1+software Raid1+boot failure

    Hi,

    I have fresh set up a software raid-1 with 2 SATA disks successfully on my
    new Mandriva 2008.1 (spring). This is my first instalation MDV 2008.1.
    Everything seemed to work well until I tried to imitate a disk failure. I
    turned the box off and unplugged one (any of two disk in mirror) HDD. After
    I did that it was impossible to reboot because system didn't mount . If I
    unplugged third disk (/dev/sdc) was the same situation. Now I have plugged
    both drives again and everything works again. Why did this failure test not
    work?

    [..]
    fsck.ext3:Unable to resolve 'UUID=7ce1aa96-....'
    Podczas sprawdzania systemu plikow wystapil blad
    [..]

    cat /etc/fstab

    # Entry for /dev/md1 :
    UUID=f39562fc-9f86-4af3-97c0-c769acc2d9bb / ext3 relatime 1 1
    # Entry for /dev/md0 :
    UUID=aceb278f-1acc-4c81-be85-4abe0dd291c4 /boot ext3 relatime 1 2
    # Entry for /dev/sdc1 :
    UUID=7ce1aa96-a604-4eea-bd48-897d7013c779 /opt/kopie ext3 relatime 1 2
    [..]


    partitions on sda
    /dev/sda1 * 1 127 1020096 fd Linux raidautodetect
    /dev/sda2 128 19457 155268225 5 Extended
    /dev/sda5 128 257 1044193+ 82 Linux swap / Solaris
    /dev/sda6 258 19457 154223968+ fd Linux raidautodetect

    partitions on sdb
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 127 1020096 fd Linux raidautodetect
    /dev/sdb2 128 19457 155268225 5 Extended
    /dev/sdb5 128 257 1044193+ 82 Linux swap / Solaris
    /dev/sdb6 258 19457 154223968+ fd Linux raidautodetect

    sda1 and sdb1 is md0 and mount point - /boot
    sda5 and sdb5 is swap
    sda6 and sdb6 is md1 and mount point - /

    cat /etc/lilo.conf

    default="linux"
    boot=/dev/md0
    raid-extra-boot=mbr-only
    map=/boot/map
    install=menu
    keytable=/boot/pl.klt
    menu-scheme=wb:bw:wb:bw
    compact
    prompt
    nowarn
    timeout=100
    message=/boot/message
    image=/boot/vmlinuz
    label="linux"
    root="UUID=f39562fc-9f86-4af3-97c0-c769acc2d9bb"
    initrd=/boot/initrd.img
    append=" resume=/dev/sda5 splash=silent"
    vga=788
    [..]


    cat /etc/fstab

    # Entry for /dev/md1 :
    UUID=f39562fc-9f86-4af3-97c0-c769acc2d9bb / ext3 relatime 1 1
    # Entry for /dev/md0 :
    UUID=aceb278f-1acc-4c81-be85-4abe0dd291c4 /boot ext3 relatime 1 2
    /dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0
    # Entry for /dev/sdc1 :
    UUID=7ce1aa96-a604-4eea-bd48-897d7013c779 /opt/kopie ext3 relatime 1 2
    none /proc proc defaults 0 0
    # Entry for /dev/sda5 :
    UUID=d79f9efa-fc4d-4075-8e14-751756cf384d swap swap defaults 0 0
    # Entry for /dev/sdb5 :
    UUID=1c6fc805-dbbf-4bab-823e-85cb7817eb02 swap swap defaults 0 0


    Please help me but I spend many time looking for solution on google

    Thanks
    Przemko

    P.S.
    Please be patient because my english is not really good (


  2. Re: MDV2008.1+software Raid1+boot failure

    Przemko wrote:

    > Hi,
    >
    > I have fresh set up a software raid-1 with 2 SATA disks successfully on my
    > new Mandriva 2008.1 (spring). This is my first instalation MDV 2008.1.
    > Everything seemed to work well until I tried to imitate a disk failure. I
    > turned the box off and unplugged one (any of two disk in mirror) HDD.
    > After I did that it was impossible to reboot because system didn't mount .
    > If I
    > unplugged third disk (/dev/sdc) was the same situation. Now I have
    > plugged both drives again and everything works again. Why did this failure
    > test not work?
    >
    > [..]
    > fsck.ext3:Unable to resolve 'UUID=7ce1aa96-....'
    > Podczas sprawdzania systemu plikow wystapil blad
    > [..]
    >
    > cat /etc/fstab
    >
    > # Entry for /dev/md1 :
    > UUID=f39562fc-9f86-4af3-97c0-c769acc2d9bb / ext3 relatime 1 1
    > # Entry for /dev/md0 :
    > UUID=aceb278f-1acc-4c81-be85-4abe0dd291c4 /boot ext3 relatime 1 2
    > # Entry for /dev/sdc1 :
    > UUID=7ce1aa96-a604-4eea-bd48-897d7013c779 /opt/kopie ext3 relatime 1 2
    > [..]
    >
    >
    > partitions on sda
    > /dev/sda1 * 1 127 1020096 fd Linux
    > raidautodetect
    > /dev/sda2 128 19457 155268225 5 Extended
    > /dev/sda5 128 257 1044193+ 82 Linux swap /
    > Solaris
    > /dev/sda6 258 19457 154223968+ fd Linux
    > raidautodetect
    >
    > partitions on sdb
    > Device Boot Start End Blocks Id System
    > /dev/sdb1 * 1 127 1020096 fd Linux
    > raidautodetect
    > /dev/sdb2 128 19457 155268225 5 Extended
    > /dev/sdb5 128 257 1044193+ 82 Linux swap /
    > Solaris
    > /dev/sdb6 258 19457 154223968+ fd Linux
    > raidautodetect
    >
    > sda1 and sdb1 is md0 and mount point - /boot
    > sda5 and sdb5 is swap
    > sda6 and sdb6 is md1 and mount point - /
    >
    > cat /etc/lilo.conf
    >
    > default="linux"
    > boot=/dev/md0
    > raid-extra-boot=mbr-only
    > map=/boot/map
    > install=menu
    > keytable=/boot/pl.klt
    > menu-scheme=wb:bw:wb:bw
    > compact
    > prompt
    > nowarn
    > timeout=100
    > message=/boot/message
    > image=/boot/vmlinuz
    > label="linux"
    > root="UUID=f39562fc-9f86-4af3-97c0-c769acc2d9bb"
    > initrd=/boot/initrd.img
    > append=" resume=/dev/sda5 splash=silent"
    > vga=788
    > [..]
    >

    Guess you should substitute the UUID stanzas with the "md" names wherever
    possible, in lilo.conf and in fstab. Since hdc is not part of the md array,
    it may as well be wise to not mount it automagically at bootup, rather use
    autofs (the auto.misc table) and place a symlink to the misc mountpoint on
    the current location.

+ Reply to Thread