[Bug 280034] Re: disk/by-uuid only created for md0 (rootfs raid)

[Davias]

I then updated with no problem up to 12.04 lts on the same hw and same arrays, still formatted as ext3.
So it seems to work perfectly!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/280034

Title:
  disk/by-uuid only created for md0 (rootfs raid)

Status in “mdadm” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mdadm

  I have set up of 2 disks, 4 partitions on both and 4 arrays: one array
  for partition.

  After upgrade from Edgy -> Feisty caused boot failure with new 2.6.20-17-server kernel 
  From grub I chosed old 2.6.17-10-server kernel, boot was succesfull but automount fails for arrays md1 -> md3. 

  This was fixed with:

  root at intranet1:/# mount -a

  Second upgrade from Feisty - > Gutsy: same problems: boot failure with
  2.6.20-17-server kernel and automount fails with old one

  Third upgrade from Gutsy -> Hardy: okay, new  2.6.24-19-server kernel
  doesn't boot, 2.6.20-17-server kernel doesn't boot. Boot with
  2.6.17-10-server kernel, automount fails again -> trying to mount
  with:

  root at intranet1:/# mount -a

  and I get this:

  special device /dev/md1 does not exist
  special device /dev/md2 does not exist

  I did check all arrays with:

  root at intranet1:~# mdadm --query --detail /dev/md1
  /dev/md1:
          Version : 00.90.03
    Creation Time : Tue Jan  2 15:50:54 2007
       Raid Level : raid1
       Array Size : 195310144 (186.26 GiB 200.00 GB)
    Used Dev Size : 195310144 (186.26 GiB 200.00 GB)
     Raid Devices : 2
    Total Devices : 2
  Preferred Minor : 1
      Persistence : Superblock is persistent

      Update Time : Wed Oct  8 10:33:53 2008
            State : clean
   Active Devices : 2
  Working Devices : 2
   Failed Devices : 0
    Spare Devices : 0

             UUID : 74e35a8a:62d61b58:c470fcf6:6ee6893c
           Events : 0.13359100

      Number   Major   Minor   RaidDevice State
         0       8        2        0      active sync   /dev/sda2
         1       8       18        1      active sync   /dev/sdb2

  and

  root at intranet1:~# mdadm --query --detail /dev/md2
  /dev/md2:
          Version : 00.90.03
    Creation Time : Tue Jan  2 15:51:02 2007
       Raid Level : raid1
       Array Size : 7815552 (7.45 GiB 8.00 GB)
    Used Dev Size : 7815552 (7.45 GiB 8.00 GB)
     Raid Devices : 2
    Total Devices : 2
  Preferred Minor : 2
      Persistence : Superblock is persistent

      Update Time : Wed Oct  1 14:12:01 2008
            State : clean
   Active Devices : 2
  Working Devices : 2
   Failed Devices : 0
    Spare Devices : 0

             UUID : 01092e16:0548fd51:5f6fb4b6:e8d1bb90
           Events : 0.34

      Number   Major   Minor   RaidDevice State
         0       8        3        0      active sync   /dev/sda3
         1       8       19        1      active sync   /dev/sdb3

  All seems to be fine. I also checked fstab:

  root at intranet1:~# more /etc/fstab
  # /etc/fstab: static file system information.
  #
  # <file system> <mount point>   <type>  <options>       <dump>  <pass>
  proc            /proc           proc    defaults        0       0
  # /dev/md0
  UUID=814d48e5-0d42-4bd8-b85a-ba4a1d7f0313 /               ext3    defaults,errors=remount-ro 0       1
  # /dev/md3
  UUID=75e1b3c7-dead-47ad-9e3a-571a87ff1f84 /home           ext3    defaults        0       2
  # /dev/md1
  UUID=a1fa8567-7b3b-4a69-a4fb-f79117304979 /var            ext3    defaults        0       2
  # /dev/md2
  UUID=0a4b4464-a5db-403b-8ef2-41baa605f7e7 none            swap    sw              0       0
  /dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0
  /dev/           /media/floppy0  auto    rw,user,noauto  0       0

  and mdadm.conf with:

  root at intranet1:~# more /etc/mdadm/mdadm.conf
  DEVICE partitions
  ARRAY /dev/md0 level=raid1 num-devices=2 UUID=ce7d6916:81209a6f:d1ae2073:a284d027
  ARRAY /dev/md1 level=raid1 num-devices=2 UUID=74e35a8a:62d61b58:c470fcf6:6ee6893c
  ARRAY /dev/md2 level=raid1 num-devices=2 UUID=01092e16:0548fd51:5f6fb4b6:e8d1bb90
  ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5d08ef71:acabec82:5a9924c4:cdc352bb
  MAILADDR root

  and drivers uuids with:

  root at intranet1:~# /usr/share/mdadm/mkconf
  ARRAY /dev/md0 level=raid1 num-devices=2 UUID=ce7d6916:81209a6f:d1ae2073:a284d027
  ARRAY /dev/md1 level=raid1 num-devices=2 UUID=74e35a8a:62d61b58:c470fcf6:6ee6893c
  ARRAY /dev/md2 level=raid1 num-devices=2 UUID=01092e16:0548fd51:5f6fb4b6:e8d1bb90
  ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5d08ef71:acabec82:5a9924c4:cdc352bb

  All those specks do match.
  Problem seems to be that mdadm doesn't create symlinks to /dev/disk/by-uuid. After boot there is only one link as

  root at intranet1:~# ls -l /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root 9 2008-10-07 09:20 814d48e5-0d42-4bd8-b85a-ba4a1d7f0313 -> ../../md0

  After manually created missing symlinks like:

  root at intranet1:~# ls -l /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root 9 2008-10-07 10:05 0a4b4464-a5db-403b-8ef2-41baa605f7e7 -> ../../md2
  lrwxrwxrwx 1 root root 9 2008-10-07 10:06 75e1b3c7-dead-47ad-9e3a-571a87ff1f84 -> ../../md3
  lrwxrwxrwx 1 root root 9 2008-10-07 09:20 814d48e5-0d42-4bd8-b85a-ba4a1d7f0313 -> ../../md0
  lrwxrwxrwx 1 root root 9 2008-10-07 10:05 a1fa8567-7b3b-4a69-a4fb-f79117304979 -> ../../md1

  and then mount with

  root at intranet1:~# mount -a

  everything works fine. Those links must be done after every system
  reboot, since I don't know way to fix this.

  System specks:
  Linux intranet1 2.6.17-10-server #2 SMP Tue Dec 5 22:29:32 UTC 2006 i686 GNU/Linux
  Distributor ID: Ubuntu
  Description:    Ubuntu 8.04.1
  Release:        8.04
  Codename:       hardy

  No additional updates made after upgrade to Hardy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/280034/+subscriptions