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

Bug#403191: marked as done (Problems with initramfs-tools and xen.)



Your message dated Fri, 15 Dec 2006 11:50:10 +0100
with message-id <20061215105009.GL21469@baikonur.stro.at>
and subject line Bug#403191: Problems with initramfs-tools and xen.
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: initramfs-tools
Version: 0.85c

The situation and all history:

I have PC with at least 2 hard disks:
One disk - sata on ICH6, and other - SCSI on some Adaptec SCSI PCI
controler.
The operating system is placed on SATA disk and runs from it.
So till I used 2.6.18-3-amd64 linux kernel and yaird tool to generate
initrd image - all was fine.

But I desided to run xen kernel image (2.6.18-3-xen-amd64), and
installed it. As dependency it installed
initramfs-tools to generate initrd images, and instalation process
regenerated all
active initrd images on system.

And affter all system does not reboot at all and I was in wery bad
situation.
( in general not so bad for me only because I leaved some old kernels
and initrd images and I was
able to boot these ones).

The problem is that initramfs-tools generates bad initrd images, and
on system boot
the SCSI disk for some reason becomes sda, and SATA disk - sdb, and
kernel does not find
root file system at all.

I try to find way to change this using config files - but without success.
I don't fing even how to change config to force to use yaird for not
xen initrd images generation.

Best regards,

Tomas Martišius
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFgmYtAMslIG6CXk4RAsqCAJ0bphf8Kaqp6ziqg5fy2OLehYjHcACgil8v
vFRxF7JRcJwQtS9K/UbxGVw=
=Z7Bh
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
On Fri, Dec 15, 2006 at 11:09:02AM +0200, Tomas Martišius wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Package: initramfs-tools
> Version: 0.85c
> 
> The situation and all history:
> 
> I have PC with at least 2 hard disks:
> One disk - sata on ICH6, and other - SCSI on some Adaptec SCSI PCI
> controler.
> The operating system is placed on SATA disk and runs from it.
> So till I used 2.6.18-3-amd64 linux kernel and yaird tool to generate
> initrd image - all was fine.
> 
> But I desided to run xen kernel image (2.6.18-3-xen-amd64), and
> installed it. As dependency it installed
> initramfs-tools to generate initrd images, and instalation process
> regenerated all
> active initrd images on system.
> 
> And affter all system does not reboot at all and I was in wery bad
> situation.
> ( in general not so bad for me only because I leaved some old kernels
> and initrd images and I was
> able to boot these ones).
> 
> The problem is that initramfs-tools generates bad initrd images, and
> on system boot
> the SCSI disk for some reason becomes sda, and SATA disk - sdb, and
> kernel does not find
> root file system at all.
> 
> I try to find way to change this using config files - but without success.
> I don't fing even how to change config to force to use yaird for not
> xen initrd images generation.
> 
> Best regards,
> 
> Tomas Martišius
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFFgmYtAMslIG6CXk4RAsqCAJ0bphf8Kaqp6ziqg5fy2OLehYjHcACgil8v
> vFRxF7JRcJwQtS9K/UbxGVw=
> =Z7Bh
> -----END PGP SIGNATURE-----

the kernel gives _zero_ guarantee on device ordering.
thus closing
if you want to use stable devices use uuid. see ->
http://michael-prokop.at/blog/2006/08/11/stable-root-device-aka-uuid/

-- 
maks

--- End Message ---

Reply to: