close

Privacy guaranteed - Your email is not shared with anyone.

RAID bug in Linux?

Discussion in 'Tech Talk' started by aspartz, Aug 5, 2010.


  1. aspartz

    aspartz
    Expand Collapse

    Joined:
    Oct 19, 2000
    3,273
    128
    Location:
    Sandstone, MN 55072
    I just updated to teh 2.6.32.16 kernel (PAE) and put in a new RAID.

    It seems that the UUID of the RAID is the same as that of the 1st drive in the array. This caused me great displeasure as it refused to remount (UUID in /etc/fstab) after long period of restoring from backups....

    Is this new behavior?

    ARS
     
  2. Linux3

    Linux3
    Expand Collapse

    Joined:
    Dec 31, 2008
    1,399
    0
    Hummm, need a little more info.
    You had a system running Ubuntu, or some flavor of Debian, with a single drive?
    Installed a raid and am trying to restore the system from backup?

    What kind of raid? Hardware, software or "win-raid" (like a win-modem is not a real modem so is a win-raid not hardware).
    If you have a software raid I would expect that the uuid would be that of the first hard drive. With a hardware raid I would expect a new UUID. With a win-raid..... Who knows.
    Either way, you can change it.
    blkid -o value -s UUID
     

  3. aspartz

    aspartz
    Expand Collapse

    Joined:
    Oct 19, 2000
    3,273
    128
    Location:
    Sandstone, MN 55072
    It was a mdadm RAID, level 0. I used this in the past (but was raid 5) and I had no issues.
    I gets stranger. blkid reports UUIDs as I stated, but mdam --examine -- scan repprts a different UUID for the RAID.

    I'm mounting with /dev/md0 now and it works, but I would prefer to be able to mount bu UUID.

    The UUID from mdadm also does not work.

    ARS