The _real_ concern is:

do you get the _same_ ID_SERIAL value with and without the sg3-utils-
udev package installed?

Can you compare: /dev/disk/by-id/*<memstick serial*

Which is what curtin is doing; it's been told a disk has a serial
number, curtin looks for this out in /dev/disk/by-id/*serial* to find
the mapping; the serial number isn't present.

Looking at comment #20 the disco syslog, you can see that the 55 rules
are running commands which don't completely work (returns errors):

Aug 30 20:33:56 seidel-FLAKYMEMORY systemd-udevd[1021]: Process 
'/usr/bin/sg_inq --export --inhex=/sys/block/sdd/device/vpd_pg80 --raw' failed 
with exit code 15.
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] Memory: 
65690396K/67088384K available (11964K kernel code, 1734K rwdata, 5100K rodata, 
5568K init, 1160K bss, 1365220K reserved, 32768K cma-reserved)
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] SLUB: HWalign=128, 
Order=0-3, MinObjects=0, CPUs=48, Nodes=1
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] ftrace: allocating 
42707 entries in 167 pages
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] rcu: Hierarchical RCU 
implementation.
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] rcu: #011RCU 
restricting CPUs from NR_CPUS=256 to nr_cpu_ids=48.
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] #011Tasks RCU enabled.
Aug 30 20:33:56 seidel-FLAKYMEMORY kernel: [    0.000000] rcu: RCU calculated 
value of scheduler-enlistment delay is 25 jiffies.
Aug 30 20:33:56 seidel-FLAKYMEMORY systemd-udevd[1021]: Process 
'/usr/bin/sg_inq --export --inhex=/sys/block/sdd/device/vpd_pg83 --raw' failed 
with exit code 15.
Aug 30 20:33:56 seidel-FLAKYMEMORY systemd[1]: Started Flush Journal to 
Persistent Storage.
Aug 30 20:33:56 seidel-FLAKYMEMORY multipath: sdd: can't store path info
Aug 30 20:33:56 seidel-FLAKYMEMORY systemd[1]: Started udev Wait for Complete 
Device Initialization.

And you can see the multipath rules coming in to play as well.

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

Title:
  failing to deploy Ubuntu Disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1833618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to