[Bug 1663725] [NEW] root on raid device doesn't get /dev/disk/by-id/md-{name, uuid} symlinks after boot

Ryan Harper 1663725 at bugs.launchpad.net
Fri Feb 10 19:43:38 UTC 2017


Public bug reported:

ubuntu at ubuntu:~$ lsb_release -rd
Description:    Ubuntu Zesty Zapus (development branch)
Release:        17.04
ubuntu at ubuntu:~$ uname -a
Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

ubuntu at ubuntu:~$ apt-cache policy systemd
systemd:
  Installed: 232-8
  Candidate: 232-8
  Version table:
 *** 232-8 500
        500 http://ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages
        100 /var/lib/dpkg/status


3) root at ubuntu:~# ls -al /dev/disk/by-id/md-*
lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-name-ubuntu:foobar -> ../../md0
lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-uuid-bd97a135:166d5e7e:29e6b0eb:a3cad7c3 -> ../../md0


4)root at ubuntu:~# ls -al /dev/disk/by-id/md-* returns nothing


Note, I can re-trigger events on md0 and the links will appear.

udevadm test $(udevadm info -q path -n /dev/md0)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-8
ProcVersionSignature: User Name 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic ppc64le
.var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
ApportVersion: 2.20.4-0ubuntu1
Architecture: ppc64el
CustomUdevRuleFiles: main_disk-part1.rules.rules third_disk.rules.rules md0.rules.rules second_disk-part1.rules.rules second_disk.rules.rules third_disk-part1.rules.rules main_disk-part2.rules.rules fourth_disk.rules.rules fourth_disk-part1.rules.rules main_disk.rules.rules
Date: Fri Feb 10 19:38:42 2017
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.9.0-15-generic root=UUID=a8f0a084-efb9-11e6-9e80-525400123456 ro console=hvc0
ProcLoadAvg: 0.32 0.17 0.06 1/146 6210
ProcLocks:
 1: POSIX  ADVISORY  WRITE 5006 00:12:22238 0 EOF
 2: POSIX  ADVISORY  WRITE 5015 00:12:22033 0 EOF
 3: FLOCK  ADVISORY  WRITE 5007 00:12:22011 0 EOF
 4: POSIX  ADVISORY  WRITE 4979 00:12:21491 0 EOF
 5: POSIX  ADVISORY  WRITE 2643 00:12:13926 0 EOF
ProcSwaps:
 Filename				Type		Size	Used	Priority
 /swap.img                               file		1157056	0	-1
ProcVersion: Linux version 4.9.0-15-generic (buildd at bos01-ppc64el-020) (gcc version 6.3.0 20161229 (User Name 6.3.0-2ubuntu1) ) #16-User Name SMP Fri Jan 20 15:28:49 UTC 2017
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 1
cpu_coreson: Number of cores online = 1
cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug curtin ppc64el uec-images zesty

** Tags added: curtin

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

Title:
  root on raid device doesn't get /dev/disk/by-id/md-{name,uuid}
  symlinks after boot

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu at ubuntu:~$ lsb_release -rd
  Description:    Ubuntu Zesty Zapus (development branch)
  Release:        17.04
  ubuntu at ubuntu:~$ uname -a
  Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ubuntu at ubuntu:~$ apt-cache policy systemd
  systemd:
    Installed: 232-8
    Candidate: 232-8
    Version table:
   *** 232-8 500
          500 http://ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages
          100 /var/lib/dpkg/status

  
  3) root at ubuntu:~# ls -al /dev/disk/by-id/md-*
  lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-name-ubuntu:foobar -> ../../md0
  lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-uuid-bd97a135:166d5e7e:29e6b0eb:a3cad7c3 -> ../../md0

  
  4)root at ubuntu:~# ls -al /dev/disk/by-id/md-* returns nothing

  
  Note, I can re-trigger events on md0 and the links will appear.

  udevadm test $(udevadm info -q path -n /dev/md0)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: User Name 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: ppc64el
  CustomUdevRuleFiles: main_disk-part1.rules.rules third_disk.rules.rules md0.rules.rules second_disk-part1.rules.rules second_disk.rules.rules third_disk-part1.rules.rules main_disk-part2.rules.rules fourth_disk.rules.rules fourth_disk-part1.rules.rules main_disk.rules.rules
  Date: Fri Feb 10 19:38:42 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.9.0-15-generic root=UUID=a8f0a084-efb9-11e6-9e80-525400123456 ro console=hvc0
  ProcLoadAvg: 0.32 0.17 0.06 1/146 6210
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 5006 00:12:22238 0 EOF
   2: POSIX  ADVISORY  WRITE 5015 00:12:22033 0 EOF
   3: FLOCK  ADVISORY  WRITE 5007 00:12:22011 0 EOF
   4: POSIX  ADVISORY  WRITE 4979 00:12:21491 0 EOF
   5: POSIX  ADVISORY  WRITE 2643 00:12:13926 0 EOF
  ProcSwaps:
   Filename				Type		Size	Used	Priority
   /swap.img                               file		1157056	0	-1
  ProcVersion: Linux version 4.9.0-15-generic (buildd at bos01-ppc64el-020) (gcc version 6.3.0 20161229 (User Name 6.3.0-2ubuntu1) ) #16-User Name SMP Fri Jan 20 15:28:49 UTC 2017
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable

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



More information about the foundations-bugs mailing list