Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: Jaunty Broke Software Raid

  1. #1
    Join Date
    Sep 2007
    Beans
    28
    Distro
    Ubuntu 8.04 Hardy Heron

    Unhappy Jaunty Broke Software Raid [SOLVED]

    I did the Jaunty yesterday and after reboot my mdadm raid won't work

    I had one raid 0 at /dev/md0 made up from /dev/sda and /dev/sdb since the upgrade those disks are now /dev/sdc and /dev/sdd

    Please help.

    Code:
    root@griffie:/home/nutchy# mdadm -Asv
    mdadm: looking for devices for /dev/md0
    mdadm: cannot open device /dev/sdc: Device or resource busy
    mdadm: /dev/sdc has wrong uuid.
    mdadm: cannot open device /dev/sdd: Device or resource busy
    mdadm: /dev/sdd has wrong uuid.
    mdadm: no devices found for /dev/md0
    mdadm: looking for devices for further assembly
    mdadm: cannot open device /dev/sdc: Device or resource busy
    mdadm: cannot open device /dev/sdd: Device or resource busy
    Code:
    root@griffie:/home/david# mdadm -E /dev/sdc /dev/sdd
    mdadm: metadata format 00.90 unknown, ignored.
    mdadm: metadata format 00.90 unknown, ignored.
    /dev/sdc:
              Magic : a92b4efc
            Version : 00.90.00
               UUID : 616e78cd:fc386bed:b928cd6d:81a874bc (local to host griffie)
      Creation Time : Sat Mar  7 18:56:48 2009
         Raid Level : raid0
      Used Dev Size : 0
       Raid Devices : 2
      Total Devices : 2
    Preferred Minor : 0
    
        Update Time : Sat Mar  7 18:56:48 2009
              State : active
     Active Devices : 2
    Working Devices : 2
     Failed Devices : 0
      Spare Devices : 0
           Checksum : d5088fc1 - correct
             Events : 1
    
         Chunk Size : 64K
    
          Number   Major   Minor   RaidDevice State
    this     0       8        0        0      active sync   /dev/sda
    
       0     0       8        0        0      active sync   /dev/sda
       1     1       8       16        1      active sync   /dev/sdb
    /dev/sdd:
              Magic : a92b4efc
            Version : 00.90.00
               UUID : 616e78cd:fc386bed:b928cd6d:81a874bc (local to host griffie)
      Creation Time : Sat Mar  7 18:56:48 2009
         Raid Level : raid0
      Used Dev Size : 0
       Raid Devices : 2
      Total Devices : 2
    Preferred Minor : 127
    
        Update Time : Sat Mar  7 18:56:48 2009
              State : active
     Active Devices : 2
    Working Devices : 2
     Failed Devices : 0
      Spare Devices : 0
           Checksum : d5089052 - correct
             Events : 1
    
         Chunk Size : 64K
    
          Number   Major   Minor   RaidDevice State
    this     1       8       16        1      active sync   /dev/sdb
    
       0     0       8        0        0      active sync   /dev/sda
       1     1       8       16        1      active sync   /dev/sdb
    Code:
    root@griffie:/home/david# cat /etc/mdadm/mdadm.conf
    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #
    
    # by default, scan all partitions (/proc/partitions) for MD superblocks.
    # alternatively, specify devices to scan, using wildcards if desired.
    DEVICE /dev/sdc /dev/sdd ##partitions
    
    # auto-create devices with Debian standard permissions
    CREATE owner=root group=disk mode=0660 auto=yes
    
    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>
    
    # instruct the monitoring daemon where to send mail alerts
    MAILADDR root
    
    # definitions of existing MD arrays
    
    # This file was auto-generated on Thu, 25 Dec 2008 17:01:49 +1300
    # by mkconf
    ARRAY /dev/md0 level=raid0 num-devices=2 metadata=0.90 UUID=616e78cd:fc386bed:b928cd6d:81a874bc
    #devices=/dev/sdc,/dev/sdd
    Code:
    root@griffie:/home/david# fdisk -l
    
    Disk /dev/sda: 81.9 GB, 81964302336 bytes
    255 heads, 63 sectors/track, 9964 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x869726ba
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        9872    79296808+  83  Linux
    /dev/sda2            9873        9964      738990    5  Extended
    /dev/sda5            9873        9964      738958+  82  Linux swap / Solaris
    
    Disk /dev/sdb: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x94719471
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1       30401   244196001   83  Linux
    
    Disk /dev/sdc: 203.9 GB, 203928109056 bytes
    255 heads, 63 sectors/track, 24792 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/sdc doesn't contain a valid partition table
    
    Disk /dev/sdd: 203.9 GB, 203928109056 bytes
    255 heads, 63 sectors/track, 24792 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/sdd doesn't contain a valid partition table
    Last edited by flick152; May 14th, 2009 at 10:37 AM. Reason: Wrong mdadm.conf file dunno why I have two
    It's fun fun fun in the sun sun sun, They're Hardy Hardy Herons???

    Ubuntu 8.04 Hungry Hippo Forever

  2. #2
    Join Date
    Sep 2007
    Beans
    28
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Jaunty Broke Software Raid

    Ok so i've played around some it looks a bit more promising but still no cigar

    Code:
    root@griffie:/home/nutchy# mdadm -Asv
    mdadm: looking for devices for /dev/md0
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 0.
    mdadm: /dev/sdd is identified as a member of /dev/md0, slot 1.
    mdadm: added /dev/sdd to /dev/md0 as 1
    mdadm: failed to add /dev/sdc to /dev/md0: Invalid argument
    mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
    mdadm: looking for devices for further assembly
    mdadm: cannot open device /dev/sdd: Device or resource busy
    /dev/md0: File exists
    mdadm: /dev/sdc is identified as a member of /dev/md/0, slot 0.
    mdadm: SET_ARRAY_INFO failed for /dev/md/0: Device or resource busy
    mdadm: looking for devices for further assembly
    It's fun fun fun in the sun sun sun, They're Hardy Hardy Herons???

    Ubuntu 8.04 Hungry Hippo Forever

  3. #3
    Join Date
    Oct 2005
    Beans
    7

    Re: Jaunty Broke Software Raid

    same problem with a test raid5 in a vmware virtual machine

    updating kernel crash the raid at boot time

    but the info is still in the raid

  4. #4
    Join Date
    Feb 2007
    Location
    Cameron Park CA USA
    Beans
    4,561
    Distro
    Ubuntu Development Release

    Re: Jaunty Broke Software Raid

    The old /etc/mdadm/mdadm.conf file is no longer valid. Try this and then re-boot:

    Code:
    sudo mdadm --examine --scan --config=mdadm.conf >> /etc/mdadm/mdadm.conf
    That should do it, if not, come back here.
    Regards, frank, at http://yantrayoga.typepad.com/noname/
    Homebuilt Lian-Li PC-Q33WB, Intel i7-4790K 4.6GHz, SSDs,16G RAM | Dell Laptop 11.6" N3050.
    Oracle VBox w/ WinXP/Win8 running Xara Designer, PaintShopPro, and InDesign CS.

  5. #5
    Join Date
    Oct 2005
    Beans
    7

    Re: Jaunty Broke Software Raid

    thanks, it's works for me.

  6. #6
    Join Date
    Sep 2007
    Beans
    28
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Jaunty Broke Software Raid

    Code:
    root@griffie:/home/nutchy# mdadm --examine --scan
    ARRAY /dev/md0 level=raid0 num-devices=2 UUID=616e78cd:fc386bed:b928cd6d:81a874bc
    root@griffie:/home/nutchy# mdadm --examine --scan >> /etc/mdadm/mdadm.conf
    Then I #'ed out the old line in mdadm.conf

    Code:
    root@griffie:/home/nutchy# mdadm -Asv
    mdadm: looking for devices for /dev/md0
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 0.
    mdadm: /dev/sdd is identified as a member of /dev/md0, slot 1.
    mdadm: added /dev/sdd to /dev/md0 as 1
    mdadm: failed to add /dev/sdc to /dev/md0: Invalid argument
    mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
    mdadm: looking for devices for further assembly
    mdadm: cannot open device /dev/sdd: Device or resource busy
    mdadm: /dev/sdc is identified as a member of /dev/md/0, slot 0.
    mdadm: SET_ARRAY_INFO failed for /dev/md/0: Device or resource busy
    mdadm: looking for devices for further assembly
    It's fun fun fun in the sun sun sun, They're Hardy Hardy Herons???

    Ubuntu 8.04 Hungry Hippo Forever

  7. #7
    Join Date
    Feb 2007
    Location
    Cameron Park CA USA
    Beans
    4,561
    Distro
    Ubuntu Development Release

    Re: Jaunty Broke Software Raid

    Flick152: Show us your mdadm.conf file... we can get to the bottom of this with patience (and knowledge).
    Regards, frank, at http://yantrayoga.typepad.com/noname/
    Homebuilt Lian-Li PC-Q33WB, Intel i7-4790K 4.6GHz, SSDs,16G RAM | Dell Laptop 11.6" N3050.
    Oracle VBox w/ WinXP/Win8 running Xara Designer, PaintShopPro, and InDesign CS.

  8. #8
    Join Date
    Sep 2007
    Beans
    28
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Jaunty Broke Software Raid

    This is my mdadm.conf as it is atm

    Code:
    root@griffie:/home/david# cat /etc/mdadm/mdadm.conf
    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #
    
    # by default, scan all partitions (/proc/partitions) for MD superblocks.
    # alternatively, specify devices to scan, using wildcards if desired.
    DEVICE /dev/sdc /dev/sdd #partitions
    
    # auto-create devices with Debian standard permissions
    CREATE owner=root group=disk mode=0660 auto=yes
    
    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>
    
    # instruct the monitoring daemon where to send mail alerts
    MAILADDR root
    
    # definitions of existing MD arrays
    
    # This file was auto-generated on Thu, 25 Dec 2008 17:01:49 +1300
    # by mkconf
    #ARRAY /dev/md0 level=raid0 num-devices=2 metadata=0.90 UUID=616e78cd:fc386bed:b928cd6d:81a874bc
    
    ARRAY /dev/md0 level=raid0 num-devices=2 UUID=616e78cd:fc386bed:b928cd6d:81a874bc
    It's fun fun fun in the sun sun sun, They're Hardy Hardy Herons???

    Ubuntu 8.04 Hungry Hippo Forever

  9. #9
    Join Date
    Feb 2007
    Location
    Cameron Park CA USA
    Beans
    4,561
    Distro
    Ubuntu Development Release

    Re: Jaunty Broke Software Raid

    Hmmm... this is not the mdadm.conf file created by the --scan.

    Code:
    DEVICE /dev/sdc /dev/sdd #partitions
    Also I'm not sure if this hurts or not. Please just use this:

    Code:
    DEVICE partitions
    See if this gets your array to mount.
    Regards, frank, at http://yantrayoga.typepad.com/noname/
    Homebuilt Lian-Li PC-Q33WB, Intel i7-4790K 4.6GHz, SSDs,16G RAM | Dell Laptop 11.6" N3050.
    Oracle VBox w/ WinXP/Win8 running Xara Designer, PaintShopPro, and InDesign CS.

  10. #10
    Join Date
    Sep 2007
    Beans
    28
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Jaunty Broke Software Raid

    Ok I made that change

    Code:
    root@griffie:/home/nutchy# cat /etc/mdadm/mdadm.conf
    ...
    DEVICE partitions
    ...
    ARRAY /dev/md0 level=raid0 num-devices=2 UUID=616e78cd:fc386bed:b928cd6d:81a874bc
    got this...

    Code:
    root@griffie:/home/nutchy# mdadm -Asv
    mdadm: looking for devices for /dev/md0
    mdadm: cannot open device /dev/sdb1: Device or resource busy
    mdadm: /dev/sdb1 has wrong uuid.
    mdadm: cannot open device /dev/sdb: Device or resource busy
    mdadm: /dev/sdb has wrong uuid.
    mdadm: cannot open device /dev/sda5: Device or resource busy
    mdadm: /dev/sda5 has wrong uuid.
    mdadm: no RAID superblock on /dev/sda2
    mdadm: /dev/sda2 has wrong uuid.
    mdadm: cannot open device /dev/sda1: Device or resource busy
    mdadm: /dev/sda1 has wrong uuid.
    mdadm: cannot open device /dev/sda: Device or resource busy
    mdadm: /dev/sda has wrong uuid.
    mdadm: /dev/sdd is identified as a member of /dev/md0, slot 1.
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 0.
    mdadm: added /dev/sdd to /dev/md0 as 1
    mdadm: failed to add /dev/sdc to /dev/md0: Invalid argument
    mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
    mdadm: looking for devices for further assembly
    mdadm: cannot open device /dev/sdd: Device or resource busy
    mdadm: cannot open device /dev/sdb1: Device or resource busy
    mdadm: cannot open device /dev/sdb: Device or resource busy
    mdadm: cannot open device /dev/sda5: Device or resource busy
    mdadm: no RAID superblock on /dev/sda2
    mdadm: cannot open device /dev/sda1: Device or resource busy
    mdadm: cannot open device /dev/sda: Device or resource busy
    mdadm: /dev/sdc is identified as a member of /dev/md/0, slot 0.
    mdadm: SET_ARRAY_INFO failed for /dev/md/0: Device or resource busy
    mdadm: looking for devices for further assembly
    mdadm: no recogniseable superblock on /dev/sda2
    dmesg output
    Code:
    [   52.186155] md: sdd has same UUID but different superblock to sdc
    [   52.186162] md: sdd has different UUID to sdc
    [   52.186164] md: export_rdev(sdd)
    [   52.676682] ppdev0: registered pardevice
    [   52.759687] ppdev0: unregistered pardevice
    [   60.352032] eth1: no IPv6 routers present
    [   99.310705] md: md0 stopped.
    [   99.310729] md: unbind<sdc>
    [   99.310841] md: export_rdev(sdc)
    [   99.342162] md: bind<sdd>
    [   99.342727] md: sdc has same UUID but different superblock to sdd
    [   99.342731] md: sdc has different UUID to sdd
    [   99.342733] md: export_rdev(sdc)
    [   99.348211] md: array md0 already has disks!
    [126944.368242] md: md0 stopped.
    [126944.368266] md: unbind<sdd>
    [126944.368463] md: export_rdev(sdd)
    [126944.419330] md: bind<sdd>
    [126944.419822] md: sdc has same UUID but different superblock to sdd
    [126944.419826] md: sdc has different UUID to sdd
    [126944.419828] md: export_rdev(sdc)
    [126944.446430] md: array md0 already has disks!
    Last edited by flick152; May 2nd, 2009 at 09:39 AM. Reason: Highlight relevant lines
    It's fun fun fun in the sun sun sun, They're Hardy Hardy Herons???

    Ubuntu 8.04 Hungry Hippo Forever

Page 1 of 3 123 LastLast

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
  •