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

Bug#535538: marked as done (upgrade-reports: Upgrading the kernel impossible when hda is redirected to hde)

Your message dated Sun, 10 Oct 2010 13:13:24 +0200
with message-id <20101010111324.GA16600@radis.liafa.jussieu.fr>
and subject line Re: Bug#535538: upgrade-reports: Upgrading the kernel impossible when hda is redirected to hde
has caused the Debian Bug report #535538,
regarding upgrade-reports: Upgrading the kernel impossible when hda is redirected to hde
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.)


-- 
535538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535538
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: grave
Tags: security
Justification: renders package unusable


When I enter 

apt-get update
apt-get dist-upgrade

this does work for almost all packages but not for upgrading the kernel. Instead 
of using my own /grub/menu.lst the upgrade-procedure uses its own commands, 
especially 
"kernel  /vmlinuz-2.6.26-2-amd64 root=LABEL=wg-bootpart ro quiet 
[Linux-bzImage ... ]" 
The following messages appear after apt-get dist-upgrade: 

"
.........

Booting the kernel 

.........

Loading, please wait ...

mount: mounting /dev on /root/dev failed: 
       no such file or directory

[The same errors concerning /sys and /proc] 

Target filesystem doesn't have /sbin/init. 
No init found. 

..........

"
Then the system halts and does not work further. 

My desktop owns 1 IDE-controller on the motherboard and 2 PCI-RAID-IDE-controller 
(without using the RAID-facility) on a PCI-card. 

My fstab contains the following lines: 

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc                    /proc           proc     defaults        0       0
LABEL=wg-rootpart       /               reiserfs defaults        0       1
LABEL=wg-bootpart       /boot           reiserfs notail          0       2
LABEL=wg-swappart       none            swap     sw              0       0
/dev/hdb        /media/cdrom0   udf,iso9660      user,noauto     0       0
/dev/fd0        /media/floppy0  auto             rw,user,noauto  0       0

My /boot/grub/menu.lst contains the following lines:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-legacy-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=LABEL=wg-bootpart ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(single-user) single
# altoptions=(single-user mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Debian GNU/Linux, kernel 2.6.26-2-amd64
password  ... 
root		(hd0,0)
kernel		/vmlinuz-2.6.26-2-amd64 
root=UUID=8e1b2e49-3dfb-4942-8eb6-9868733c5d15 ro splash=verbose
initrd		/initrd.img-2.6.26-2-amd64

title		Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode)
password  ... 
root		(hd0,0)
kernel		/vmlinuz-2.6.26-2-amd64 
root=UUID=8e1b2e49-3dfb-4942-8eb6-9868733c5d15 ro single splash=verbose
initrd		/initrd.img-2.6.26-2-amd64

### END DEBIAN AUTOMAGIC KERNELS LIST


-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Wed, Jul 29, 2009 at 18:03:48 +0200, Simon Paillard wrote:

> Hello,
> 
> On Fri, Jul 03, 2009 at 08:26:07AM +0200, Micronius wrote:
> > Package: upgrade-reports
> > Severity: grave
> > Tags: security
> > Justification: renders package unusable
> > 
> > When I enter 
> > 
> > apt-get update
> > apt-get dist-upgrade
> 
> By the way, note that the release-notes recommends to "aptitude update;
> aptitude, upgrade, aptitude dist-upgrade":
> http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.en.html#aptupgrade1st
>  
> > this does work for almost all packages but not for upgrading the kernel. Instead 
> > of using my own /grub/menu.lst the upgrade-procedure uses its own commands, 
> > especially 
> > "kernel  /vmlinuz-2.6.26-2-amd64 root=LABEL=wg-bootpart ro quiet 
> > [Linux-bzImage ... ]" 
> > The following messages appear after apt-get dist-upgrade: 
> 
> It may be related to udev.
> The release-notes have a specifi chapter about the kernel upgrade at
> http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.en.html#newkernel
> 
> It assumes udev and initramfs are present, and give some example of
> device enumeration reordering.
> 
> Were both of these tools 
> 
> > "
> > Booting the kernel 
> > .........
> > Loading, please wait ...
> > 
> > mount: mounting /dev on /root/dev failed: no such file or directory
> > [The same errors concerning /sys and /proc] 
> > 
> > Target filesystem doesn't have /sbin/init. 
> > No init found. 
> > ..........
> > "
> > Then the system halts and does not work further. 
> 
> Thanks for your feedback and best regards.
> 
No reply in over a year, I'm assuming this is fixed now everything
should be using stable device names, so closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: