Results 1 to 8 of 8

Thread: Ubuntu has forced sda into a RAID

  1. #1
    Join Date
    Jun 2009
    Location
    SE England
    Beans
    19
    Distro
    Ubuntu 10.04 Lucid Lynx

    Ubuntu has forced sda into a RAID

    Last night my PC was working fine, I allowed some updates to be added but this morning when I switched it on I could not access my Windows partiton after accessing the Ubuntu partition. Fortunately the partition is backed up daily with Ghost so nothing much was lost.

    I did a blkid and got this result;

    dev/sda: TYPE="nvidia_raid_member"
    /dev/sdb: TYPE="nvidia_raid_member"
    /dev/mapper/nvidia_bjcedagc1: UUID="427a4888-dde0-4f51-8f4d-f8c1c414eed9" TYPE="ext4"
    /dev/mapper/nvidia_bjcedagc6: UUID="acf62ee1-dd77-4990-afb9-06b23e999a58" TYPE="ext4"
    /dev/sdc5: UUID="5E04774C047725E5" LABEL="Western Digital USB" TYPE="ntfs"

    I was quite surprised as I had at no point instructed the system to use the disks as a RAID. Any ideas on how to turn them back into 2 seperate entities?

  2. #2
    Join Date
    Nov 2006
    Location
    Wisconsin, USA
    Beans
    920
    Distro
    Ubuntu 13.04 Raring Ringtail

    Re: Ubuntu has forced sda into a RAID

    Did the updates happy to include going from 9.04 jaunty to 9.10 karmic? Karmic's use of "dmraid" is much more aggressive than previous systems, and it's tending to pick up on false positive remnants of software "fakeraid" setups long dead, e.g. from OEM vendor windows installs. Things that might help:
    * turn off RAID in your BIOS, if it's on
    * if you ever reinstall from scratch, from a live linux CD prior to installing any operating systems zero out the beginning of the disks with something like for d in sda sdb; do sudo dd if=/dev/zero of=/dev/$d bs=64k count=1000; fi WARNING! Zeroing out the start of the disks will wipe out the partition table, boot loader, and file system metadata, and some files, rendering the PC into a blank slate. But it will get rid of any lingering software RAID configuration.
    * you could try disabling mistaken software raid by booting a live CD, running sudo apt-get remove dmraid in a terminal window, and seeing if fdisk -lu shows your real disk partitions. If so, mount your filesystems by hand, and then use chroot to repeat the dmraid removal. E.g. if you have one root partition on sda1, something like
    Code:
    sudo -i
    apt-get remove dmraid
    fdisk -l
    mkdir /media/sda1
    mount /dev/sda1 /media/sda1
    cd /media/sda1
    for m in dev proc sys; do mount -o bind /$m $m; done
    chroot .
    apt-get remove dmraid

  3. #3
    Join Date
    Jun 2009
    Location
    SE England
    Beans
    19
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Ubuntu has forced sda into a RAID

    Unfortunately I was forced into a complete reinstall of both Windows and XP but did as you suggested, zeroed both HDDs and removed DMRAID prior to install, everything seems ok now. I have read elsewhere that gparted will install DMRAID if you use that so that is something to be aware of.

    I think the future for me lies with two seperate PCs networked together to prevent anything like this accidentally happening again.

  4. #4
    Join Date
    Sep 2008
    Location
    Philadelphia, PA
    Beans
    5,193
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Ubuntu has forced sda into a RAID

    I did this taken from another thread to which I lost the link. fortunately I saved the instructions to a file:

    Also there is a bug in 9.10 that mounts raid arrays that you have deleted. To fix it first turn off raid in your bios. Then load up the 9.10 live CD and open gparted. If you get a drive with a funny name like nvidia_ahahdhjdfsjkf then you have mounted a raid drive that you don't want.

    To get rid of it, Open a terminal and type
    Code:
    sudo dmraid -E -r /dev/name_of_your_disk
    . Note you want the disk name not the partition name. You can see your disk names in gparted. Mine was sda and sdb and my partition names were sda1 and sda5 and sdb1. I had to do both sda and sdb.

    Once you have erased the raid meta data you should see the funny named disk disappear after restarting gparted.

    Once you have verified the raid disk is gone reboot and your OS should boot.
    Multi-boot: Arch linux, Ubuntu 12.04, Windows 7 & Windows 8

  5. #5
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,660
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Ubuntu has forced sda into a RAID

    @presence, was the data on the drives still there? I was trying to help someone with this problem and wish I knew this before. For things to be even stranger, he had only one drive and still marked as raid.
    If he executes those commands will he have to reinstall everything?

  6. #6
    Join Date
    Sep 2008
    Location
    Philadelphia, PA
    Beans
    5,193
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Ubuntu has forced sda into a RAID

    Quote Originally Posted by darkod View Post
    @presence, was the data on the drives still there? I was trying to help someone with this problem and wish I knew this before. For things to be even stranger, he had only one drive and still marked as raid.
    If he executes those commands will he have to reinstall everything?
    Yes all data remained intact! I only had one disk marked as RAID also. I have 3 internal disks: 160 Gb IDE , 250 GB & 500 GB SATA. All are seagate. The 250 GB was marked as RAID
    Last edited by presence1960; November 17th, 2009 at 03:54 PM.
    Multi-boot: Arch linux, Ubuntu 12.04, Windows 7 & Windows 8

  7. #7
    Join Date
    Feb 2008
    Beans
    2
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: Ubuntu has forced sda into a RAID

    For everyone who experiences this problem here's some help on
    recovering the Windows partition without a re-install.

    http://support.microsoft.com/kb/927392

    The included note was key for me.

    Note If rebuilding the BCD does not resolve the startup issue, you can export and delete the BCD, and then run this option again. By doing this, you make sure that the BCD is completely rebuilt. To do this, type the following commands at the Windows RE command prompt:

    * bcdedit /export C:\BCD_Backup
    * c:
    * cd boot
    * attrib bcd -s -h -r
    * ren c:\boot\bcd bcd.old
    * bootrec /RebuildBcd


    Of course if you haven't created a recovery disk already (or have the install disk)
    you're in the weeds...

    A caveat worth mentioning...

    This erases the grub bootstrap allowing you to boot Windows and I can tell from
    using the Ubuntu recovery mode that the linux partitions are still intact if not
    bootable.

    I needed the Windows partition ASAP and am now tracking the Ubuntu end for an appropiate
    grub fix...

    Thanks for the help!
    Last edited by jcmoore; November 19th, 2009 at 04:28 AM. Reason: Additional data

  8. #8
    Join Date
    Jun 2009
    Location
    SE England
    Beans
    19
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Ubuntu has forced sda into a RAID

    Quote Originally Posted by presence1960 View Post
    I did this taken from another thread to which I lost the link. fortunately I saved the instructions to a file:

    Also there is a bug in 9.10 that mounts raid arrays that you have deleted. To fix it first turn off raid in your bios. Then load up the 9.10 live CD and open gparted. If you get a drive with a funny name like nvidia_ahahdhjdfsjkf then you have mounted a raid drive that you don't want.

    To get rid of it, Open a terminal and type
    Code:
    sudo dmraid -E -r /dev/name_of_your_disk
    . Note you want the disk name not the partition name. You can see your disk names in gparted. Mine was sda and sdb and my partition names were sda1 and sda5 and sdb1. I had to do both sda and sdb.

    Once you have erased the raid meta data you should see the funny named disk disappear after restarting gparted.

    Once you have verified the raid disk is gone reboot and your OS should boot.
    This has solved another problem for me as well. When I've been trying to install other distros they have all failed or hung at the partitioning part of the install. That has gone now and I have Sabayon and Mandriva installed and running happily.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •