Bad path in 25disable_cdrom.mount

Bug #1495873 reported by QkiZ on 2015-09-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
High
Colin Watson

Bug Description

When system or user run command update-initramfs it prints errors:

update-initramfs: Generating /boot/initrd.img-3.19.0-28-generic
ln: nie udało się utworzyć dowiązania symbolicznego „/root/lib/systemd/system/cdrom.mount”: Nie ma takiego pliku ani katalogu
update-initramfs: Generating /boot/initrd.img-3.19.0-27-generic
ln: nie udało się utworzyć dowiązania symbolicznego „/root/lib/systemd/system/cdrom.mount”: Nie ma takiego pliku ani katalogu
update-initramfs: Generating /boot/initrd.img-3.19.0-26-generic
ln: nie udało się utworzyć dowiązania symbolicznego „/root/lib/systemd/system/cdrom.mount”: Nie ma takiego pliku ani katalogu

This means that there is no such file like /root/lib/systemd/system/cdrom.mount. After editing initramfs-tools/scripts/casper-bottom/25disable_cdrom.mount and correct path from:
/root/lib/systemd/system/cdrom.mount
to
/lib/systemd/system/cdrom.mount
generating initramfs stops printing errors.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: casper 1.360 [modified: usr/share/initramfs-tools/scripts/casper-bottom/25disable_cdrom.mount]
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
Date: Tue Sep 15 10:44:43 2015
InstallationDate: Installed on 2014-04-19 (514 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: casper
UpgradeStatus: Upgraded to vivid on 2015-04-30 (137 days ago)

Related branches

QkiZ (qkiz) wrote :
Colin Watson (cjwatson) wrote :

Have you changed something else about initramfs-tools? Files in /usr/share/initramfs-tools/scripts/ are not normally run at update-initramfs time; they run in the context of the initramfs, and in that context, the path starting with /root is perfectly correct.

Can you please investigate and find out why that script is being run at all at update-initramfs time for you? It really shouldn't be.

Changed in casper (Ubuntu):
status: New → Incomplete
Colin Watson (cjwatson) wrote :

Oh no, I see the problem - it's not the path, that script is lacking the usual prereqs handling. I'll fix.

Changed in casper (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
importance: Undecided → High
status: Incomplete → Triaged
status: Triaged → Fix Committed
QkiZ (qkiz) wrote :

No, I was change only /usr/share/initramfs-tools/scripts/casper-bottom/25disable_cdrom.mount file.

When fix will be available to download from repo?

Colin Watson (cjwatson) wrote :

I don't intend to upload it to vivid, because we aren't intending to do a point release of 15.04 and casper is mostly only useful if actually on the installation medium. It'll be in wily later today.

Colin Watson (cjwatson) wrote :

But that said, I have absolutely no idea whether downloading the wily casper package and installing it on a running 15.04 live session is a remotely sensible thing to do. Of course, running update-initramfs on a system with casper installed isn't normally a sensible thing to do either. If this isn't a live session, why do you have casper installed?

QkiZ (qkiz) wrote :

No, it's regular hard disk installation. I have checked why I have this package and it's required by systemback package.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.365

---------------
casper (1.365) wily; urgency=medium

  * Add prereqs handling to several scripts that lacked it (LP: #1495873).
  * Fix inverted warning message in copy_live_to (LP: #1494123).
  * Simplify and improve the grammar of the installation medium removal
    prompt (LP: #1159207).

 -- Colin Watson <email address hidden> Tue, 15 Sep 2015 13:44:27 +0100

Changed in casper (Ubuntu):
status: Fix Committed → Fix Released
Colin Watson (cjwatson) wrote :

OK, systemback isn't in Ubuntu. The error is cosmetic and you can just ignore it, or else get the maintainer of the PPA you're using to cherry-pick the patch.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers