[Bug 1032326] [NEW] Cannot boot of relative path of / is not /

Kasper Dupont 1032326 at bugs.launchpad.net
Thu Aug 2 18:39:34 UTC 2012


Public bug reported:

I'm not sure if this should be classified as a bug or a feature request.

The scripts to install a new kernel will call "grub-mkrelpath /boot" and
use the result to properly handle a /boot directory located in unusual
locations. However they do not do any "grub-mkrelpath /" call at any
point, and simply assumes the result is always "/" (with a minor
exception in the case the file system is btrfs).

With a bit of manual work, it is possible to configure a system where
"grub-mkrelpath /" does not report "/". However such a system will be
rendered non-bootable after the next kernel update.

The attached patch fixes it for me.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: initramfs-tools 0.99ubuntu13 [modified: usr/share/initramfs-tools/init]
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
Date: Thu Aug  2 20:27:38 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to precise on 2012-05-08 (85 days ago)

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 precise

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

Title:
  Cannot boot of relative path of / is not /

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  I'm not sure if this should be classified as a bug or a feature
  request.

  The scripts to install a new kernel will call "grub-mkrelpath /boot"
  and use the result to properly handle a /boot directory located in
  unusual locations. However they do not do any "grub-mkrelpath /" call
  at any point, and simply assumes the result is always "/" (with a
  minor exception in the case the file system is btrfs).

  With a bit of manual work, it is possible to configure a system where
  "grub-mkrelpath /" does not report "/". However such a system will be
  rendered non-bootable after the next kernel update.

  The attached patch fixes it for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initramfs-tools 0.99ubuntu13 [modified: usr/share/initramfs-tools/init]
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Thu Aug  2 20:27:38 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to precise on 2012-05-08 (85 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1032326/+subscriptions




More information about the foundations-bugs mailing list