Results 1 to 5 of 5

Thread: RAID broken after upgrade, unable to repair

Hybrid View

  1. #1
    Join Date
    Mar 2009
    Beans
    12

    RAID broken after upgrade, unable to repair

    More specifically, after upgrading, the device names seem to have shuffled around a bit, and raid broke. I'm unable to rebuild the array, it seems to value the old device names more highly than the uuid's, and errors out.

    Pastebin of the current drive situation is at http://www.pastebin.com/2AT9fQYF . The drives used to be sda, sdb and sdc, but somehow the dvd drive took over sdb post-upgrade. You can see my attempts to sort the situation here, and the results: http://www.pastebin.com/t8wPxZHu .

    I can get to busybox on the PC, and am using a liveCD to try to repair it. Any help you can provide is much appreciated... but please don't 'guess', I have a lot of important data on this array that I would much prefer not to lose if possible.

    Many thanks.

  2. #2
    Join Date
    Mar 2009
    Beans
    12

    Re: RAID broken after upgrade, unable to repair

    bump

  3. #3
    Join Date
    Mar 2009
    Beans
    12

    Re: RAID broken after upgrade, unable to repair

    bump again, this is a critical problem, please help.

    This is the latest situation: http://pastebin.com/TzMnu8q1
    Last edited by TheSilverHornet; May 3rd, 2010 at 09:21 PM.

  4. #4
    Join Date
    May 2010
    Beans
    1

    Re: RAID broken after upgrade, unable to repair

    This is the only relevant message in your logs:

    Code:
    mdadm: no recogniseable superblock on /dev/sde1
    mdadm: /dev/sde1 has wrong uuid.
    You've never posted the output of this though:

    Code:
    mdadm --examine /dev/sde1
    sdb bumped the drives up to sde, but I don't see where you ever tried assembling the array from a,c,d,e. You should run this, and see what it says:

    Code:
    mdadm --assemble -v /dev/md0 /dev/sd{a,c,d,e}1

  5. #5
    Join Date
    Mar 2009
    Beans
    12

    Re: RAID broken after upgrade, unable to repair

    It's been sorted now, something very bizarre happened & I had to recreate the array ... which has caused another issue I should make a separate post about. Cheers anyway.

Tags for this Thread

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
  •