FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 06-14-2010, 12:03 PM
Guido GŁnther
 
Default Bug#585852: Incorrect boot= in lilo.conf after UUID conversion with /boot on LVM

Subject: linux-base: postinst added wrong UUID to /etc/lilo.conf
Package: linux-base
Version: 2.6.32-15
Severity: normal

During the installation of linux-base it offered to switch my configs to
UUIDs. This worked well in /etc/fstab but didn't so for lilo.conf:

#boot = /dev/sda3
boot = "/dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ"

which doesn't exist:

$ ls -l /dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ
ls: cannot access /dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ: No such file or directory

And therefore:

# lilo
Warning: LBA32 addressing assumed
Fatal: raid_setup: stat("/dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ")

/dev/sda3 is a PV with a VG (internal) on it that keeps the LVs root,
home, swap. The above UUID is the PVs UUID:

# pvdisplay
--- Physical volume ---
PV Name /dev/sda3
VG Name internal
PV Size 30,69 GiB / not usable 3,53 MiB
Allocatable yes (but full)
PE Size 4,00 MiB
Total PE 7857
Free PE 0
Allocated PE 7857
PV UUID azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ

So it seems the script doesn't handle /boot on LVM correctly.
Cheers,
-- Guido

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-base depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii libapt-pkg-perl 0.1.24 Perl interface to libapt-pkg
ii libuuid-perl 0.02-3+b1 Perl extension for using UUID inte
ii udev 157-1 /dev/ and hotplug management daemo
ii util-linux 2.16.2-0 Miscellaneous system utilities

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
linux-base/disk-id-manual-boot-loader:
linux-base/disk-id-manual:
* linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-auto: true
linux-base/disk-id-convert-plan: true




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100614120327.GA4942@bogon.sigxcpu.org">http://lists.debian.org/20100614120327.GA4942@bogon.sigxcpu.org
 
Old 06-14-2010, 12:21 PM
maximilian attems
 
Default Bug#585852: Incorrect boot= in lilo.conf after UUID conversion with /boot on LVM

On Mon, Jun 14, 2010 at 02:03:27PM +0200, Guido GŁnther wrote:
> --- Physical volume ---
> PV Name /dev/sda3
> VG Name internal
> PV Size 30,69 GiB / not usable 3,53 MiB
> Allocatable yes (but full)
> PE Size 4,00 MiB
> Total PE 7857
> Free PE 0
> Allocated PE 7857
> PV UUID azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ
>
> So it seems the script doesn't handle /boot on LVM correctly.
> Cheers,
> -- Guido

please post /etc/fstab /etc/lilo.conf and output of mount.

thank you.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100614122113.GJ9869@baikonur.stro.at">http://lists.debian.org/20100614122113.GJ9869@baikonur.stro.at
 
Old 06-14-2010, 01:03 PM
Guido GŁnther
 
Default Bug#585852: Incorrect boot= in lilo.conf after UUID conversion with /boot on LVM

On Mon, Jun 14, 2010 at 02:21:13PM +0200, maximilian attems wrote:
> On Mon, Jun 14, 2010 at 02:03:27PM +0200, Guido GŁnther wrote:
> > --- Physical volume ---
> > PV Name /dev/sda3
> > VG Name internal
> > PV Size 30,69 GiB / not usable 3,53 MiB
> > Allocatable yes (but full)
> > PE Size 4,00 MiB
> > Total PE 7857
> > Free PE 0
> > Allocated PE 7857
> > PV UUID azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ
> >
> > So it seems the script doesn't handle /boot on LVM correctly.
> > Cheers,
> > -- Guido
>
> please post /etc/fstab /etc/lilo.conf and output of mount.
Mount output is:

/dev/mapper/internal-root on / type ext3 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/internal-home on /home type ext3 (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)

The other files are attached.
Cheers,
-- Guido
# Automatically added by lilo postinst script
large-memory

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt' (if you have created it), or |
# | install a new kernel. The computer will most likely fail to |
# | boot if a kernel-image post-install script or you don't |
# | remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#

boot = /dev/sda3
#boot = "/dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ"


# Specifies the device that should be mounted as root. (`/')
#
root=/dev/mapper/internal-root

# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
compact

# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# delay=100
# timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#


# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=

#
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
append="quiet splash"
initrd=/initrd.img

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
append="quiet"
initrd=/initrd.img.old

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/internal-root / ext3 relatime,errors=remount-ro 0 1
/dev/mapper/internal-home /home ext3 relatime 0 2
/dev/mapper/internal-swap none swap sw 0 0
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/cdrom1 /media/cdrom0 udf,iso9660 user,noauto 0 0
 
Old 06-14-2010, 11:53 PM
Ben Hutchings
 
Default Bug#585852: Incorrect boot= in lilo.conf after UUID conversion with /boot on LVM

On Mon, 2010-06-14 at 14:03 +0200, Guido GŁnther wrote:
> Subject: linux-base: postinst added wrong UUID to /etc/lilo.conf
> Package: linux-base
> Version: 2.6.32-15
> Severity: normal
>
> During the installation of linux-base it offered to switch my configs to
> UUIDs. This worked well in /etc/fstab but didn't so for lilo.conf:
>
> #boot = /dev/sda3
> boot = "/dev/disk/by-uuid/azgLkk-WOjh-iwxd-eSUK-32a9-qEVm-Q7CIBJ"
>
> which doesn't exist:
[...]
> /dev/sda3 is a PV with a VG (internal) on it that keeps the LVs root,
> home, swap. The above UUID is the PVs UUID:
[...]
> So it seems the script doesn't handle /boot on LVM correctly.

It deals just fine with a /boot partition on a LV, but not with a boot
*sector* on a PV. I had not noticed that PVs appear in the blkid list
but not under /dev/disk/by-uuid. I'll change the upgrade script to
filter them out.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 

Thread Tools




All times are GMT. The time now is 06:27 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org