kernel-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

This really isn't util-linux' fault. If you remove the package of the
running kernel then from then on all module loading will fail as they
went away. I think it would be better to add some safety check into the
kernel's preinst to abort the removal of the currently running kernel. I
think in the past we even had that, but it's not the case in current
utopic (I verified that I can purge the running kernel just fine).

** Summary changed:

- Devices can't be mounted if the current running kernel is missing
+ Don't allow removing the currently running kernel

** Package changed: util-linux (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1380754

Title:
  Don't allow removing the currently running kernel

Status in “linux” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with mount 2.25.1-3ubuntu2 and if the
  current running kernel is being removed (for example because a new one
  is installed but the system wasn't rebooted directly afterwards) and a
  device is trying to be mounted I'm always getting this error:

  sworddragon@ubuntu:~$ sudo mount /dev/sdf1 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
         missing codepage or helper program, or other error

         In some cases useful info is found in syslog - try
         dmesg | tail or so.

  
  All other parts of the system are working fine (for example 3D applications with proprietary graphics driver) even if running for several days so probably this could be a bug/missing feature in mount.

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