RAID problems 2008.1 - Mandriva

This is a discussion on RAID problems 2008.1 - Mandriva ; After upgrading from 2008.0 to 2008.1 on a software RAID0 volume half the items in drakconf did not function anymore. When I clicked something I got a pop-up telling me that the program exited abnormally. After trying for hours in ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: RAID problems 2008.1

  1. RAID problems 2008.1

    After upgrading from 2008.0 to 2008.1 on a software RAID0 volume half
    the items in drakconf did not function anymore. When I clicked
    something I got a pop-up telling me that the program exited
    abnormally. After trying for hours in collaboration with the guys at
    #mandriva IRC I tried a reinstall. Installation gave me a similar
    error as below, so I removed the RAID volume, recreated the volume,
    now I am typing from that fresh 2008.1 KDE installation. Bit... the
    same things that did not work in the old installation, still give the
    same "program exited abnormally"

    when i run drakconf from cmdline:

    [maarten@localhost ~]$ su
    Password:
    [root@localhost maarten]# drakconf
    [root@localhost maarten]# "/usr/sbin/drakvirt" is not executable
    [Virtualization] at /usr/sbin/drakconf.real line 1415.
    INTERNAL ERROR: unknown device mapper/isw_dgdhbejcea_RAIDVOL 1
    MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/
    devices.pm:119
    devices::entry() called from /usr/lib/libDrakX/devices.pm:183
    devices::make() called from /usr/lib/libDrakX/fs/type.pm:275
    fs::type::call_vol_id() called from /usr/lib/libDrakX/fs/type.pm:283
    fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/
    fsedit.pm:247
    fsedit::get_hds() called from /usr/sbin/diskdrake:74

    This was when trying to open, local disks, manage disk partitions.

    I then installed drakvirt:

    [root@localhost maarten]# drakconf
    [root@localhost maarten]# INTERNAL ERROR: unknown device mapper/
    isw_dgdhbejcea_RAIDVOL 1
    MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/
    devices.pm:119
    devices::entry() called from /usr/lib/libDrakX/devices.pm:183
    devices::make() called from /usr/lib/libDrakX/fs/type.pm:275
    fs::type::call_vol_id() called from /usr/lib/libDrakX/fs/type.pm:283
    fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/
    fsedit.pm:247
    fsedit::get_hds() called from /usr/sbin/drakboot:41

    similar error when trying to open, boot, setup autologin to
    automaticly login.

    dmesg | grep RAID

    Kernel command line: BOOT_IMAGE=linux
    root=UUID=f0cda63d-919c-4a0e-8eb4-605bdfebe9f4 resume=/dev/mapper/
    isw_dgdhbejcea_RAIDVOL5 splash=silent vga=788
    ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl
    RAID mode


    I'm pretty stuck here (and I was so happy with Mandriva 2008.0). Any
    help is appreciated

  2. Re: RAID problems 2008.1

    On Mon, 14 Jul 2008 07:49:44 -0400, Maarten wrote:

    > [root@localhost maarten]# "/usr/sbin/drakvirt" is not executable
    > [Virtualization] at /usr/sbin/drakconf.real line 1415.


    Ignore the error about drakvirt. It just means drakvirt is not installed.
    It's normal to see this error.

    > INTERNAL ERROR: unknown device mapper/isw_dgdhbejcea_RAIDVOL 1
    > MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/
    > devices.pm:119
    > devices::entry() called from /usr/lib/libDrakX/devices.pm:183
    > devices::make() called from /usr/lib/libDrakX/fs/type.pm:275
    > fs::type::call_vol_id() called from /usr/lib/libDrakX/fs/type.pm:283
    > fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/
    > fsedit.pm:247
    > fsedit::get_hds() called from /usr/sbin/diskdrake:74
    > This was when trying to open, local disks, manage disk partitions.


    I'm wondering if this is related to problems diskdrake, and the underlying
    modules have with some fstab entry names. See
    https://qa.mandriva.com/show_bug.cgi?id=41172#c6

    Editing the fstab to use symlinks of /dev/$LVMVolumeGroup/$LogicalVolumeName
    instead of the /dev/mapper/$LVMVolumeGroup-$LogicalVolumeName is a workaround
    that fixes the problem for lvm filesystems. A similar workaround may work
    for the raid volumes. I don't use raid, so can't test it.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  3. Re: RAID problems 2008.1

    Tanks for the reply.

    But how do I edit the fstab, or the way diskdrake looks up the volumes
    during install?

    regards,
    maarten

    On Jul 14, 8:05 pm, "David W. Hodgins"
    wrote:
    > On Mon, 14 Jul 2008 07:49:44 -0400, Maarten wrote:
    > > [root@localhost maarten]# "/usr/sbin/drakvirt" is not executable
    > > [Virtualization] at /usr/sbin/drakconf.real line 1415.

    >
    > Ignore the error about drakvirt. It just means drakvirt is not installed.
    > It's normal to see this error.
    >
    > > INTERNAL ERROR: unknown device mapper/isw_dgdhbejcea_RAIDVOL 1
    > > MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/
    > > devices.pm:119
    > > devices::entry() called from /usr/lib/libDrakX/devices.pm:183

    >\> devices::make() called from /usr/lib/libDrakX/fs/type.pm:275
    > > fs::type::call_vol_id() called from /usr/lib/libDrakX/fs/type.pm:283
    > > fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/
    > > fsedit.pm:247
    > > fsedit::get_hds() called from /usr/sbin/diskdrake:74
    > > This was when trying to open, local disks, manage disk partitions.

    >
    > I'm wondering if this is related to problems diskdrake, and the underlying
    > modules have with some fstab entry names. Seehttps://qa.mandriva.com/show_bug.cgi?id=41172#c6
    >
    > Editing the fstab to use symlinks of /dev/$LVMVolumeGroup/$LogicalVolumeName
    > instead of the /dev/mapper/$LVMVolumeGroup-$LogicalVolumeName is a workaround
    > that fixes the problem for lvm filesystems. A similar workaround may work
    > for the raid volumes. I don't use raid, so can't test it.
    >
    > Regards, Dave Hodgins
    >
    > --
    > Change nomail.afraid.org to ody.ca to reply by email.
    > (nomail.afraid.org has been set up specifically for
    > use in usenet. Feel free to use it yourself.)



  4. Re: RAID problems 2008.1

    On Mon, 14 Jul 2008 12:49:01 -0700 (PDT), Maarten wrote:
    >
    > But how do I edit the fstab,


    First thing I do is make a backup copy.
    cp /etc/fstab /etc/fstab_works
    I then
    umount /whatever/Ima/about_2_change
    You can then use the editor of your choice to edit /etc/fstab
    You save the file, then test by mounting whatever you changed.

    Now if you are modifying / then I recommend a reboot to verify
    system comes up.

    Of course you show know how to use a live cd to repair whatever
    you changed or at least know how to mount your / and
    cp fstab_works fstab

    > or the way diskdrake looks up the volumes during install?


    Latest release uses UUID. I found I can label partition using
    e2label. During install, I click Expert Mode in diskdrake,
    click the partition, select label, highlight, clt-c.
    click mount point, click and paste ctl-v.

    I have no experience with raid.

  5. Re: RAID problems 2008.1

    On Mon, 14 Jul 2008 15:49:01 -0400, Maarten wrote:

    > But how do I edit the fstab, or the way diskdrake looks up the volumes
    > during install?


    Open a terminal program such as konsole,
    su -l root
    cp /etc/fstab /etc/fstab.mybackup
    kwrite /etc/fstab

    Might be better to post a copy of the current fstab here, then after
    a few questions about what symlinks exist under /dev, a workaround
    setting might get figured out.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

+ Reply to Thread