[Bug 1301451] Re: System doesn't start correct if it has a separate /usr filesystem

Crashbit crashbit at gmail.com
Thu Apr 3 00:12:45 UTC 2014


*** This bug is a duplicate of bug 1301544 ***
    https://bugs.launchpad.net/bugs/1301544

The bug has been fixed

https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1301544

-- 
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/1301451

Title:
  System doesn't start correct if it has a separate /usr filesystem

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hi! I use Ubuntu 14.04 testing

  My problem: System doesn't start after reboot, It don't mount all
  filesystems

  crashbit at crashbit-Dell-System-XPS-L321X:~$ lsb_release -rd
  Description:	Ubuntu Trusty Tahr (development branch)
  Release:	14.04

  I update the system and restart it every time, today I see an updates of systemd, udev and kernel.
  When the process ends I restart the system, but it don't mount all filesystems.

  My configuration:
  crashbit at crashbit-Dell-System-XPS-L321X:~$ lsblk
  NAME                  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
  sda                     8:0    0 238,5G  0 disk
  ├─sda1                  8:1    0   3,7G  0 part
  │ └─sda1_crypt (dm-0) 252:0    0   3,7G  0 crypt [SWAP]
  ├─sda2                  8:2    0     1K  0 part
  ├─sda5                  8:5    0   7,5G  0 part  /
  ├─sda6                  8:6    0   428M  0 part  /boot
  ├─sda7                  8:7    0  24,2G  0 part  /usr
  └─sda8                  8:8    0 202,7G  0 part
    └─sda8_crypt (dm-1) 252:1    0 202,7G  0 crypt

  /dev/sda5                on  /                         type  ext4             (rw,errors=remount-ro)
  proc                     on  /proc                     type  proc             (rw,noexec,nosuid,nodev)
  sysfs                    on  /sys                      type  sysfs            (rw,noexec,nosuid,nodev)
  none                     on  /sys/fs/cgroup            type  tmpfs            (rw)
  none                     on  /sys/fs/fuse/connections  type  fusectl          (rw)
  none                     on  /sys/kernel/debug         type  debugfs          (rw)
  none                     on  /sys/kernel/security      type  securityfs       (rw)
  udev                     on  /dev                      type  devtmpfs         (rw,mode=0755)
  devpts                   on  /dev/pts                  type  devpts           (rw,noexec,nosuid,gid=5,mode=0620)
  tmpfs                    on  /run                      type  tmpfs            (rw,noexec,nosuid,size=10%,mode=0755)
  none                     on  /run/lock                 type  tmpfs            (rw,noexec,nosuid,nodev,size=5242880)
  none                     on  /run/shm                  type  tmpfs            (rw,nosuid,nodev)
  none                     on  /run/user                 type  tmpfs            (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
  none                     on  /sys/fs/pstore            type  pstore           (rw)
  cgroup                   on  /sys/fs/cgroup/cpuset     type  cgroup           (rw,relatime,cpuset)
  cgroup                   on  /sys/fs/cgroup/cpu        type  cgroup           (rw,relatime,cpu)
  /dev/sda6                on  /boot                     type  ext2             (rw)
  /dev/sda7                on /usr                         type  btrfs            (rw)
  /dev/mapper/sda8_crypt   on  /home                     type  btrfs            (rw,subvol=@home)
  systemd                  on  /sys/fs/cgroup/systemd    type  cgroup           (rw,noexec,nosuid,nodev,none,name=systemd)
  /home/crashbit/.Private  on  /home/crashbit            type  ecryptfs         (ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs,ecryptfs_sig=XXXXXXXXXX,ecryptfs_fnek_sig=XXXXXXXXXXXXX)
  gvfsd-fuse               on  /run/user/1000/gvfs       type  fuse.gvfsd-fuse  (rw,nosuid,nodev,user=crashbit)

  Normally the system starts perfect, but after this upgrades the system doesn't start.
  I try tu reboot in recovery mode and moun manually /usr partition, but if I do it, the system does not starts correctly.

  I've also tried to start with an old kernel, but does not work

  Finally I moved  all files of /usr partition tu root partition and rename it, and system starts correctly.
  I think it happens becouse I have a separated /usr partition, but I don't know how package creates this problem.

  Sorry for my bad English

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



More information about the foundations-bugs mailing list