[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#810965: marked as done (Cannot boot when init is on a separate /usr filesystem)

Your message dated Mon, 18 Jan 2016 17:49:46 +0000
with message-id <E1aLDw2-0005QB-OY@franck.debian.org>
and subject line Bug#810965: fixed in initramfs-tools 0.121
has caused the Debian Bug report #810965,
regarding Cannot boot when init is on a separate /usr filesystem
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
810965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810965
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: usrmerge
Version: 6
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I installed usrmerge on a system to try it out, and ended up with system
that could not be rebooted.  I'll try to outline the status as best I
recall in the hopes that you can recreate the issue.

   * What led up to the situation?

I installed usrmerge, and got the following during configuration:

--------------------
Setting up usrmerge (6) ...

WARNING: renaming /bin/ (for the purpose of replacing it with a symlink
to /usr/bin/) has failed with the EBUSY error.
This is probably caused by a systemd service started with the
ProtectSystem option. Before running again this program you will need to
stop the relevant daemon(s) or reboot the system.
Do not install or update other Debian packages until the program
has been run successfully.

WARNING: renaming /sbin/ (for the purpose of replacing it with a symlink
to /usr/sbin/) has failed with the EBUSY error.
This is probably caused by a systemd service started with the
ProtectSystem option. Before running again this program you will need to
stop the relevant daemon(s) or reboot the system.
Do not install or update other Debian packages until the program
has been run successfully.

WARNING: renaming /lib/ (for the purpose of replacing it with a symlink
to /usr/lib/) has failed with the EBUSY error.
This is probably caused by a systemd service started with the
ProtectSystem option. Before running again this program you will need to
stop the relevant daemon(s) or reboot the system.
Do not install or update other Debian packages until the program
has been run successfully.

WARNING: renaming /lib64/ (for the purpose of replacing it with a
symlink
to /usr/lib64/) has failed with the EBUSY error.
This is probably caused by a systemd service started with the
ProtectSystem option. Before running again this program you will need to
stop the relevant daemon(s) or reboot the system.
Do not install or update other Debian packages until the program
has been run successfully.
dpkg: error processing package usrmerge (--configure):
 subprocess installed post-installation script returned error exit
 status 1
 Errors were encountered while processing:
  usrmerge
--------------------

I could not figure out which processes/daemons in particular were
causing the errors.

At this point, I examined the disk layout, and noticed that basically
everything* in /{bin,sbin,lib} had been moved to /usr/{bin,sbin,lib}, and
replaced with symlinks in /{bin,sbin,lib}, but /{bin,sbin,lib} still
existed as real directories (not symlinks).

(* - I noticed two exceptions in /lib, both of which were directories,
but unfortunately I can't remember exactly what they were, and the
history is beyond the top of my terminal buffer.  My best guess is that
they were systemd and x86_64-linux-gnu, but again, I'm not certain of
that.)

Since I couldn't figure out which daemon was causing the problem, I
rebooted the system as suggested in the usrmerge configure error
messages.  It didn't come back up: it failed to start with an error that
/sbin/init was not found on the disk.  Oddly, however, I could run ls
/sbin/init which *did* show an existing symlink and target.

I tried rebooting with init=/usr/sbin/init, but that also did not work.
Eventually I got the system to boot using init=/usr/lib/systemd/systemd
after which a dpkg --configure usrmerge completed the merge (turning
/{bin,sbin/lib} into symlinks).  After this, rebooting without
specifying init= was successful.

Please let me know if there's any other information I can provide to
keep this from happening to others.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages usrmerge depends on:
ii  libfile-find-rule-perl  0.34-1

usrmerge recommends no packages.

usrmerge suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: can't check usrmerge file /usr/share/doc/usrmerge/changelog.gz (Wide character in subroutine entry)

--- End Message ---
--- Begin Message --- 
Source: initramfs-tools
Source-Version: 0.121

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 810965@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings <ben@decadent.org.uk> (supplier of updated initramfs-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 18 Jan 2016 17:43:22 +0000
Source: initramfs-tools
Binary: initramfs-tools initramfs-tools-core
Architecture: source
Version: 0.121
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: Ben Hutchings <ben@decadent.org.uk>
Description:
 initramfs-tools - generic modular initramfs generator (automation)
 initramfs-tools-core - generic modular initramfs generator (core tools)
Closes: 781239 809204 810965
Changes:
 initramfs-tools (0.121) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * [19422ac] debian/NEWS: Fix typo in reference to initramfs.conf configuration
     file
 .
   [ Ben Hutchings ]
   * [bf445db] Restore automatic selection between busybox and klibc by default
     (Closes: #809204)
   * [4251397] init: Always mount /usr before looking for the real init
   * [c6d067c] init: Remove use of switch_root
   * [3c8b67c] init: Use run-init -n option to validate real init
     (Closes: #810965)
   * [40f2132] scripts/functions: Fix fsck display options (Closes: #781239)
Checksums-Sha1:
 f6b8da94fa65497ea988fd5c24da939ea2e42308 1811 initramfs-tools_0.121.dsc
 c7915cc71c2fe0d8cb62f1fea9f7475d5c78feae 81816 initramfs-tools_0.121.tar.xz
Checksums-Sha256:
 182840d3969f8e9fea741bf4508c2e66ff34bb5816f993f63e8179553981a50c 1811 initramfs-tools_0.121.dsc
 d4750da34e27217aed0b5e2a737ad1a203dce4dd86e13ee7250a866694ceda26 81816 initramfs-tools_0.121.tar.xz
Files:
 d6d019a95eceb532aefb3ef82c9ad7ac 1811 utils optional initramfs-tools_0.121.dsc
 0db3373445b096facbe084b19c6803eb 81816 utils optional initramfs-tools_0.121.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVp0lPue/yOyVhhEJAQpdKhAAtwW5H3W2LrIw7F4jTHa/VBvNsrglGpsU
TUL1/XAkwm5hN7yb7LLP8VYWkuL7OU3Z76DVhoJcqJDz9/9LTheEIrNR1qO6uxLr
oeHNrL1es1YedFurzLOfXSdRLU99K9uas1XdP7qU9IZheFgVRQ+kOwfps2Ukt0iR
x+q37adaWhybYMGrGPeMpbiLEX4DTuty7hLkFDCq7GjwLtg00ak7JZN4lBCLqdRc
7pKB23qOy/eF6ymVV8gtHVXYSSuKZlWelOOnsuwVZJbUfwAbROR78LLnupksT1fK
pw31EY4tEmNETbfLpF48sGU6dLkpgGMLawVsgwshTnmnh41xsAldhYnV5E88SHx/
xic6TmliLbJLmgdysbGFI9utw1CyNVdHp9pZ9E0TFJT3qgEIr0x352kzPSmomLQx
LBSoQxXJ5SV1HBmO/a1GdOfJkdSvHuvoLBWJB9dlfdFuO9JhFAsZVI/gIfw2BryW
2IBuxm5inJ7Mv2r570nEjOsfE4KnQMSrR1zcZKVkKZu7Jg73STYemE0uY8ryhOdl
XlsYLFf9Y7MaqUqNeZxK0Xp3HAO+dax0MbFU5Z2/1jRJVWhTGYkXSq32avZ9TsHO
gpQJMAXPe4jv/0zlEfv8VXWYxiLO/zQS42AZHYbE1XPIyJiWTaxnrnMcc0j4mytQ
YH8Lymw/8B0=
=CAxT
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: