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

Bug#595094: marked as done (linux-base: /etc/initramfs-tools/conf.d/resume^old causes trouble)

Your message dated Wed, 01 Sep 2010 00:24:17 +0100
with message-id <1283297057.7653.199.camel@localhost>
and subject line Re: Bug#595094: linux-base: /etc/initramfs-tools/conf.d/resume^old causes trouble
has caused the Debian Bug report #595094,
regarding linux-base: /etc/initramfs-tools/conf.d/resume^old causes trouble
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.)


-- 
595094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595094
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-base
Version: 2.6.33-1~experimental.4
Severity: normal

Hello

Since upgrading to 2.6.32-5-amd64 my system does not boot every time. It then
hangs after identifying all SATA discs in script called "local-premount" with a
message saying that it cannot find the resume drive /dev/sda2 and I should
press enter.
As my USB keyboard is not working at this point I usually do a hard reset and
then most of the time the boot continues.

I was wondering where the /dev/sda2 was coming from as my GRUB and fstab
contain UUID resp. /dev/disk/by-name labels. The only occurence which grep
found was a /etc/initramfs-tools/conf.d/resume^old with a timestamp from
2008-01-14 next to a file "resume" which contains the correct UUID.

As I would never use a ^ character in a filename I looked in /var/lib/dpkg/info
and found linux-base.postinst which does so an has an interesting comment next
to it:

                    {packages => 'initramfs-tools',
                     path => '/etc/initramfs-tools/conf.d/resume',
                     list => \&initramfs_resume_list,
                     update => \&initramfs_resume_update,
                     # udev will source all files in this directory,
                     # with few exceptions.  Such as including a '^'.
                     suffix => '^old'},

I could not find a corresponding filter in the udev sources so I would assume
that this exception is no longer given.

Can you check this and if true add a line to the postinst file that removes all
present resume^old files? They might cause trouble to others as well.

bye,

-christian-



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

Kernel: Linux 2.6.32-5-amd64 (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/bash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0]         1.5.35     Debian configuration management sy
ii  libapt-pkg-perl               0.1.24+b1  Perl interface to libapt-pkg
ii  libuuid-perl                  0.02-4     Perl extension for using UUID inte

linux-base recommends no packages.

linux-base suggests no packages.

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

--- End Message ---
--- Begin Message --- 
On Wed, 2010-09-01 at 01:00 +0200, Christian Hammers wrote:
> Package: linux-base
> Version: 2.6.33-1~experimental.4
> Severity: normal
> 
> Hello
> 
> Since upgrading to 2.6.32-5-amd64 my system does not boot every time. It then
> hangs after identifying all SATA discs in script called "local-premount" with a
> message saying that it cannot find the resume drive /dev/sda2 and I should
> press enter.
> As my USB keyboard is not working at this point I usually do a hard reset and
> then most of the time the boot continues.
> 
> I was wondering where the /dev/sda2 was coming from as my GRUB and fstab
> contain UUID resp. /dev/disk/by-name labels. The only occurence which grep
> found was a /etc/initramfs-tools/conf.d/resume^old with a timestamp from
> 2008-01-14 next to a file "resume" which contains the correct UUID.
> 
> As I would never use a ^ character in a filename I looked in /var/lib/dpkg/info
> and found linux-base.postinst which does so an has an interesting comment next
> to it:
> 
>                     {packages => 'initramfs-tools',
>                      path => '/etc/initramfs-tools/conf.d/resume',
>                      list => \&initramfs_resume_list,
>                      update => \&initramfs_resume_update,
>                      # udev will source all files in this directory,
>                      # with few exceptions.  Such as including a '^'.
>                      suffix => '^old'},
> 
> I could not find a corresponding filter in the udev sources so I would assume
> that this exception is no longer given.

This really has nothing to do with udev - that comment is a brain-fart
on my part.  The mkinitramfs script in initramfs-tools looks for
configuration files like this:

for i in /usr/share/initramfs-tools/conf.d/* ${CONFDIR}/conf.d/*; do
	[ -e $i ] && EXTRA_CONF="${EXTRA_CONF} $(basename $i \
		| grep '^[[:alnum:]][[:alnum:]\._-]*$' | grep -v '\.dpkg-.*$')";
done

You can see that this excludes configuration files with the '^'.

> Can you check this and if true add a line to the postinst file that removes all
> present resume^old files? They might cause trouble to others as well.

These files should be kept.

The problem lies in your old initramfs images which still include the
old 'resume' configuration.  Since these are kernel version-specific and
are therefore not affected by the libata transition, linux-base does not
update them automatically.  You can update them to use the UUID with
'update-initramfs -u -k <kernel-abi-version>'.

Ben.

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

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: