Debian Bug report logs - #340344
yaird: Fail to create initrd on s390/s390x

version graph

Package: yaird; Maintainer for yaird is (unknown);

Reported by: "Ivan S. Warren" <ivan@vmfacility.fr>

Date: Tue, 22 Nov 2005 21:03:01 UTC

Severity: important

Found in version yaird/0.0.11-12

Fixed in version 0.0.13-5+rm

Done: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to "Ivan S. Warren" <ivan@vmfacility.fr>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: "Ivan S. Warren" <ivan@vmfacility.fr>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: yaird: Fail to create initrd on s390/s390x
Date: Tue, 22 Nov 2005 21:39:50 +0100
Package: yaird
Version: 0.0.11-12
Severity: important


When attempting installing linux-image-2.6.14-3-s390x, the install script
invokes yaird.

yaird fails as follow :

# yaird -o /tmp/a 2.6.14-2-s390x
yaird error: can't open /proc/bus/input/devices (fatal)

I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg
(since input devices on S/390 z/Arch is irrelevant) as well
as anything relating to mouse, etc..

The following then occurs :

# yaird -o /tmp/a 2.6.14-2-s390x
yaird error: unsupported device required: dasda (fatal)

As a consequence, I am unable to upgrade to the 2.6.14 kernel (since
linux-image-2.6.14-3-s390x and linux-image-2.6.14-3-s390 both insist on 
only using yaird).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: s390 (s390x)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-s390x
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages yaird depends on:
ii  cpio                         2.6-9       GNU cpio -- a program to manage ar
ii  dash                         0.5.2-8     The Debian Almquist Shell
ii  libc6                        2.3.5-8     GNU C Library: Shared libraries an
ii  libhtml-template-perl        2.6-2       HTML::Template : A module for usin
ii  libparse-recdescent-perl     1.94.free-1 Generates recursive-descent parser
ii  perl                         5.8.7-8     Larry Wall's Practical Extraction 

yaird recommends no packages.

-- no debconf information



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to Erik van Konijnenburg <ekonijn@xs4all.nl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #10 received at submit@bugs.debian.org (full text, mbox):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: "Ivan S. Warren" <ivan@vmfacility.fr>, 340344@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Tue, 22 Nov 2005 22:31:56 +0100
On Tue, Nov 22, 2005 at 09:39:50PM +0100, Ivan S. Warren wrote:
> 
> # yaird -o /tmp/a 2.6.14-2-s390x
> yaird error: can't open /proc/bus/input/devices (fatal)
> 
> I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg
> (since input devices on S/390 z/Arch is irrelevant) as well
> as anything relating to mouse, etc..

OK, manageable so far ...

> The following then occurs :
> 
> # yaird -o /tmp/a 2.6.14-2-s390x
> yaird error: unsupported device required: dasda (fatal)
> 
> As a consequence, I am unable to upgrade to the 2.6.14 kernel (since
> linux-image-2.6.14-3-s390x and linux-image-2.6.14-3-s390 both insist on 
> only using yaird).

Could you post
* output of yaird --debug -o blah.img
* output of yaird --test
* output of ls -lR /sys under your old kernel
* advice as to what modules you expect to be loaded to get dasda
  operational

You may also want to look at initramfs-tools.

Thanks,
Erik





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to Erik van Konijnenburg <ekonijn@xs4all.nl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to "Ivan Warren" <ivan@vmfacility.fr>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #20 received at 340344@bugs.debian.org (full text, mbox):

From: "Ivan Warren" <ivan@vmfacility.fr>
To: "'Erik van Konijnenburg'" <ekonijn@xs4all.nl>, <340344@bugs.debian.org>
Subject: RE: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Wed, 23 Nov 2005 00:00:31 +0100
[Message part 1 (text/plain, inline)]
> > 
> > I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg
> > (since input devices on S/390 z/Arch is irrelevant) as well
> > as anything relating to mouse, etc..
> 
> OK, manageable so far ...
> 

Agreed.. although something needs to be done about it - eventually
(otherwise dependent packages just won't install)

> > The following then occurs :
> > 
> > # yaird -o /tmp/a 2.6.14-2-s390x
> > yaird error: unsupported device required: dasda (fatal)
> > 
> > As a consequence, I am unable to upgrade to the 2.6.14 kernel (since
> > linux-image-2.6.14-3-s390x and linux-image-2.6.14-3-s390 
> both insist on 
> > only using yaird).
> 
> Could you post

.. Most certainly...

> * output of yaird --debug -o blah.img
> * output of yaird --test
> * output of ls -lR /sys under your old kernel

Output attached - 3 files (with hopefully self-explanatory file names)
If file attachment is not accepted by BTS, I will look in the FAQ on how to
achieve this (I am no real expert in reporting bugs !)

> * advice as to what modules you expect to be loaded to get dasda
>   operational

s390/s390x may need (from what I can gather)

- dasd_eckd_mod (ECKD Device support) < That's what I need in my particular
case
- dasd_fba_mod (FBA Device support)
- dcssblk (z/VM Shared segment support - although I'm not sure if this can
be used as a rootfs)
- xpram (Expanded storage - same restriction as above)
- zfcp (QDIO/Fiber Channel devices - SCSI over FC)

Because of the architectural constraint related to S/390 & z/Arch these may
be the only ones needed - all I/O is standardized on this architecture.

> 
> You may also want to look at initramfs-tools.
> 

I did (this option was suggested by the debian-s390 people) ! Although the
initramfs gets built, it fails to boot (the module is not included as part
of the ram root fs)

> Thanks,
> Erik
> 

Of course, should you need more information, I'll be glad to provide you
with anything you need !

Thanks for your help !

--Ivan
[bug340344-1-isw.tgz (application/x-compressed, attachment)]

Bug 340344 cloned as bug 340508. Request was from maximilian attems <maks@sternwelten.at> to control@bugs.debian.org. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to Erik van Konijnenburg <ekonijn@xs4all.nl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #27 received at 340344@bugs.debian.org (full text, mbox):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: Ivan Warren <ivan@vmfacility.fr>, 340344@bugs.debian.org
Subject: Re: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Wed, 30 Nov 2005 23:31:10 +0100
On Wed, Nov 23, 2005 at 12:00:31AM +0100, Ivan Warren wrote:
> > > # yaird -o /tmp/a 2.6.14-2-s390x
> > > yaird error: unsupported device required: dasda (fatal)
> > > 
> > Could you post
> 
> .. Most certainly...

Thanks, that helps.  After looking at your output and a debian kernel
for s390 it seems that the kernel uses a module mapping table similar
to that used for usb and pci; the modules listed in that table match
closely with what you describe in your note.

Perhaps you could test the version that is now in the development tree?
Instructions:

	apt_get install bzr
	http_proxy=http://whatever.domain:port/ export http_proxy
	bzr get http://www.xs4all.nl/~ekonijn/yaird.bzr/
	cd yaird.bzr
	sh bootstrap.sh
	./configure --prefix=$HOME/local
	make install
	cd $HOME/local/etc
	ln -s Debian.cfg Templates.cfg
	cd /tmp
	sudo $HOME/local/sbin/yaird -v -o junk.img

You're the first one to use this temporary, throw-away, bazaar-NG
repository, so you may find suprises.  Let me know if you need a tarball
instead of this repository.

The code is untested and will probably break.  If this happens and the cause is
not immediately obvious, could you add a load of Base::debug statements
to Ccw*.pm and post the diffs and output?

Note that the repository also contains EVMS support and ide-generic stuff;
the differences are a bit much for a patch.  Lets get this working first,
sort out the packaging afterwards ...

Regards,
Erik





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to "Ivan Warren" <ivan@vmfacility.fr>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #32 received at 340344@bugs.debian.org (full text, mbox):

From: "Ivan Warren" <ivan@vmfacility.fr>
To: "'Erik van Konijnenburg'" <ekonijn@xs4all.nl>, <340344@bugs.debian.org>
Subject: RE: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Thu, 1 Dec 2005 02:49:03 +0100
> 
> The code is untested and will probably break.  If this 
> happens and the cause is
> not immediately obvious, could you add a load of Base::debug 
> statements
> to Ccw*.pm and post the diffs and output?
> 

Erik,

Well..

The build went ok.. however, here is what I get :

deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/home/ivan/local/etc/yaird/Default.cfg:56)
yaird: goal: mountdir, / (/home/ivan/local/etc/yaird/Default.cfg:143)
yaird error: unsupported device required: dasda (fatal)

(that's after removing the input device goals that are irrelevant on that
arch..)

Looks pretty much the same as before..

Now.. Unfortunatelly, I am completelly Perl ignorant - so I wouldn't even
know where to put any debug statement :-(

I'll try to see if I can squeeze more information out of this later on (it's
a bit late !)

However, If you have any idea, I'll be willing to accomodate for any test
you may find usefull.

--Ivan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to Erik van Konijnenburg <ekonijn@xs4all.nl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #37 received at 340344@bugs.debian.org (full text, mbox):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: Ivan Warren <ivan@vmfacility.fr>, 340344@bugs.debian.org
Subject: Re: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Thu, 1 Dec 2005 06:45:03 +0100
On Thu, Dec 01, 2005 at 02:49:03AM +0100, Ivan Warren wrote:

> The build went ok.. however, here is what I get :
> 
> deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
> yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52)
> yaird: action: prologue,  {}
> yaird: goal: module, fbcon (/home/ivan/local/etc/yaird/Default.cfg:56)
> yaird: goal: mountdir, / (/home/ivan/local/etc/yaird/Default.cfg:143)
> yaird error: unsupported device required: dasda (fatal)

Could you test a corrected version?

- cd yaird.bzr
- bzr pull			# get update
- grep dasd perl/Plan.pm	# oops, that was missing
- make install			# rest as before

Thanks,
Erik



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to "Ivan Warren" <ivan@vmfacility.fr>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #42 received at 340344@bugs.debian.org (full text, mbox):

From: "Ivan Warren" <ivan@vmfacility.fr>
To: "'Erik van Konijnenburg'" <ekonijn@xs4all.nl>, <340344@bugs.debian.org>
Subject: RE: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Thu, 1 Dec 2005 12:03:58 +0100
> 
> On Thu, Dec 01, 2005 at 02:49:03AM +0100, Ivan Warren wrote:
> 
> > The build went ok.. however, here is what I get :
> > 
> > deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
> > yaird: goal: template, prologue 
> (/home/ivan/local/etc/yaird/Default.cfg:52)
> > yaird: action: prologue,  {}
> > yaird: goal: module, fbcon 
> (/home/ivan/local/etc/yaird/Default.cfg:56)
> > yaird: goal: mountdir, / 
> (/home/ivan/local/etc/yaird/Default.cfg:143)
> > yaird error: unsupported device required: dasda (fatal)
> 
> Could you test a corrected version?
> 
> - cd yaird.bzr
> - bzr pull			# get update
> - grep dasd perl/Plan.pm	# oops, that was missing
> - make install			# rest as before
> 
> Thanks,
> Erik
> 

Morning Erik !

Apparently we're getting somewhere !

This is how things are going now :

1) Hardware.pm was missing "load CcwDev" and "load CcwMap" (easy fix)

<PATCH>
--- /home/ivan/yaird.bzr/perl/Hardware.pm       2005-12-01
02:24:02.000000000 +0100
+++ /home/ivan/local/lib/yaird/perl/Hardware.pm 2005-12-01
10:34:36.000000000 +0100
@@ -32,6 +32,8 @@
 use PciTab;
 use UsbDev;
 use UsbTab;
+use CcwDev;
+use CcwTab;
 package Hardware;
</PATCH>

2) The initramfs gets built :

<LOG>
deb390-1:/boot# /home/ivan/local/sbin/yaird -v -o initrd.img-2.6.14-2-s390x
2.6.14-2-s390x
yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/home/ivan/local/etc/yaird/Default.cfg:56)
yaird: goal: mountdir, / (/home/ivan/local/etc/yaird/Default.cfg:143)
yaird: action: insmod,
/lib/modules/2.6.14-2-s390x/kernel/drivers/s390/block/dasd_mod.ko
{optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.14-2-s390x/kernel/drivers/s390/block/dasd_eckd_mod.ko
{optionList=-- }
yaird: hardware: completed css0/0.0.0004/0.0.0108
yaird: action: mkbdev, /dev/dasda {sysname=dasda }
yaird: action: mkbdev, /dev/dasda1 {sysname=dasda/dasda1 }
yaird: action: mount, /mnt {device=/dev/dasda1 fsType=ext3 isRoot=1
options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/home/ivan/local/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}
deb390-1:/boot#
</LOG>

3) Boot fails :

<LOG>
/bin/cat: /sys/block/dasda/dev: No such file or directory
Waiting 1 seconds for /sys/block/dasda/dev to show up
/bin/cat: /sys/block/dasda/dev: No such file or directory
Waiting 2 seconds for /sys/block/dasda/dev to show up
/bin/cat: /sys/block/dasda/dev: No such file or directory
Waiting 4 seconds for /sys/block/dasda/dev to show up
/bin/cat: /sys/block/dasda/dev: No such file or directory
Waiting 8 seconds for /sys/block/dasda/dev to show up
/bin/cat: /sys/block/dasda/dev: No such file or directory
Waiting 16 seconds for /sys/block/dasda/dev to show up

/bin/cat: /sys/block/dasda/dev: No such file or directory

Device /sys/block/dasda/dev seems to be down.
Debugging opportunity, type ^D to continue.
/bin/dash: can't access tty; job control turned off
# echo /sys/block/*
/sys/block/ram0 /sys/block/ram1 /sys/block/ram10 /sys/block/ram11
/sys/block/ram
12 /sys/block/ram13 /sys/block/ram14 /sys/block/ram15 /sys/block/ram2
/sys/block
/ram3 /sys/block/ram4 /sys/block/ram5 /sys/block/ram6 /sys/block/ram7
/sys/block
/ram8 /sys/block/ram9
# insmod dasd_eckd.ko
insmod: can't read 'dasd_eckd.ko': No such file or directory
# insmod dasd_eckd_mod.ko
insmod: error inserting 'dasd_eckd_mod.ko': -1 File exists
#
</LOG>

Possible explanation :

dasd_mod won't autodetect dasds unless specifically requested to do so !
Apparently, the appropriate parameter would be :

dasd=autodetect

(based on drivers/s390/block/dasd_devmap.c)

However, this would mean guaranteed failure on some dasd configuration
changes (this requires a small explanation of the S/390 and z/Arch I/O
architecture : Each device is known by 2 ids : A subchannel number and a
device number. The "device number" represents the 'physical' connection (ex
: 010A means device 0A on channel 01).. The subchannel number is a sequence
number in the configuration, and *THAT* is what is used to perform I/O
operations (a device cannot be addressed directly by its device number -
ONLY by its subchannel number).. Furthermore, any autodetection scheme would
most probably use that subchannel numbering to name devices (or more exactly
to assign minor numbers). If 0108 is your 1st dasd device it will most
probably be named 'dasda'.. If a new dasd is inserted at 0100, chances are
0108 will now be called 'dasdb' - *however* if dasd_mod is passed a specific
list of dasd devices, the naming will probably remain unchanged - regardless
of any configuration change - the 1st device listed will be named 'dasda').

The sequence numbering is also model dependent. on IBM real iron, they are
usually related to the order in which they appear in the IOCDS (a microcode
configuration file that describes the system's I/O configuration). On z/VM
(IBM's virtualization solution) the numbering is related to the order in
which the devices are declared in the CP directory (The virtual machines
definition file). On hercules (an open source S/370, S/390 and z/Arch
emulator, which I am using for these tests) the subchannels are numbered
based on the order in which they appear in the hercules configuration
file... However, the architecture makes *NO* guarantee whatsoever as to the
actual order and even whether that number remains identical between each POR
(Power On Reset) - The only architectural guarantee is that the numbering is
contiguous (no holes).

I am sorry this is so complicated (maybe *I* am making it more complicated
than it really is !)..

Thanks,

--Ivan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#340344; Package yaird. Full text and rfc822 format available.

Acknowledgement sent to Erik van Konijnenburg <ekonijn@xs4all.nl>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #47 received at 340344@bugs.debian.org (full text, mbox):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: Ivan Warren <ivan@vmfacility.fr>
Cc: 340344@bugs.debian.org
Subject: Re: Bug#340344: yaird: Fail to create initrd on s390/s390x
Date: Thu, 1 Dec 2005 22:59:31 +0100
On Thu, Dec 01, 2005 at 12:03:58PM +0100, Ivan Warren wrote:
> 1) Hardware.pm was missing "load CcwDev" and "load CcwMap" (easy fix)
Oops, thanks for the fix, is in the repo now.

> 2) The initramfs gets built :
OK, looks normal.

> 3) Boot fails :

> Device /sys/block/dasda/dev seems to be down.
> Debugging opportunity, type ^D to continue.

So there's something extra we need to figure out ...

> Possible explanation :
> 
> dasd_mod won't autodetect dasds unless specifically requested to do so !
> Apparently, the appropriate parameter would be :
> 
> dasd=autodetect
> 
> (based on drivers/s390/block/dasd_devmap.c)

Possibly.

If you do

	echo options dasd_mod > /etc/modprobe.d/test123

and rerun yaird, the parameter should be added to the image
(you can see this happening in the -v and -d output)

However, I'm curious why this would be necessary now and not for
your old kernel.  Lets see if we can get this to work without
needing changes to your modprobe configuration.

If I'm correct, you're running under 2.6.11
with initrd-tools, trying to get 2.6.14 to boot with yaird.
Could you extract the /sbin/init script from a 2.6.11 initrd
and post it?  If it's convenient to place the whole content
of initrd somewhere online that could also be usefull, but
mostly i'm after the /sbin/init.

Is there any difference in kernel command line parameters when booting?


> However, this would mean guaranteed failure on some dasd configuration
> changes (this requires a small explanation of the S/390 and z/Arch I/O
> architecture : Each device is known by 2 ids : A subchannel number and a
> device number. The "device number" represents the 'physical' connection (ex
> : 010A means device 0A on channel 01).. The subchannel number is a sequence
> number in the configuration, and *THAT* is what is used to perform I/O
> operations (a device cannot be addressed directly by its device number -
> ONLY by its subchannel number).. Furthermore, any autodetection scheme would
> most probably use that subchannel numbering to name devices (or more exactly
> to assign minor numbers). If 0108 is your 1st dasd device it will most
> probably be named 'dasda'.. If a new dasd is inserted at 0100, chances are
> 0108 will now be called 'dasdb' - *however* if dasd_mod is passed a specific
> list of dasd devices, the naming will probably remain unchanged - regardless
> of any configuration change - the 1st device listed will be named 'dasda').
> 
> The sequence numbering is also model dependent. on IBM real iron, they are
> usually related to the order in which they appear in the IOCDS (a microcode
> configuration file that describes the system's I/O configuration). On z/VM
> (IBM's virtualization solution) the numbering is related to the order in
> which the devices are declared in the CP directory (The virtual machines
> definition file). On hercules (an open source S/370, S/390 and z/Arch
> emulator, which I am using for these tests) the subchannels are numbered
> based on the order in which they appear in the hercules configuration
> file... However, the architecture makes *NO* guarantee whatsoever as to the
> actual order and even whether that number remains identical between each POR
> (Power On Reset) - The only architectural guarantee is that the numbering is
> contiguous (no holes).

There's a known issue that if the hardware changes, the yaird image will
not automatically cope with that.

However, for the case you describe the path in /sys/devices may change,
but the path in /sys/block should remain stable.  Otherwise your initrd
would need to use /dev/disk/by-label/ to boot reliably, and I don't think
support for that is in initrd-tools.

For now, lets look at differences between initrd and yaird-generated image,
and keep the sequence numbering in mind as a possible alternative lead.

Thanks,
Erik




Reply sent to Debian FTP Masters <ftpmaster@ftp-master.debian.org>:
You have taken responsibility. (Sat, 14 May 2011 11:51:57 GMT) Full text and rfc822 format available.

Notification sent to "Ivan S. Warren" <ivan@vmfacility.fr>:
Bug acknowledged by developer. (Sat, 14 May 2011 11:51:58 GMT) Full text and rfc822 format available.

Message #52 received at 340344-done@bugs.debian.org (full text, mbox):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
To: 327762-done@bugs.debian.org,328508-done@bugs.debian.org,335315-done@bugs.debian.org,336392-done@bugs.debian.org,336454-done@bugs.debian.org,336514-done@bugs.debian.org,336518-done@bugs.debian.org,336599-done@bugs.debian.org,336688-done@bugs.debian.org,336995-done@bugs.debian.org,337065-done@bugs.debian.org,337724-done@bugs.debian.org,338734-done@bugs.debian.org,338951-done@bugs.debian.org,339941-done@bugs.debian.org,340344-done@bugs.debian.org,340593-done@bugs.debian.org,340746-done@bugs.debian.org,340759-done@bugs.debian.org,340873-done@bugs.debian.org,341273-done@bugs.debian.org,341498-done@bugs.debian.org,341522-done@bugs.debian.org,343592-done@bugs.debian.org,343911-done@bugs.debian.org,343918-done@bugs.debian.org,344926-done@bugs.debian.org,345374-done@bugs.debian.org,346093-done@bugs.debian.org,346294-done@bugs.debian.org,348293-done@bugs.debian.org,350880-done@bugs.debian.org,352677-done@bugs.debian.org,352757-done@bugs.debian.org,360665-done@bugs.debian.org,365818-done@bugs.debian.org,369965-done@bugs.debian.org,370616-done@bugs.debian.org,372834-done@bugs.debian.org,377801-done@bugs.debian.org,378481-done@bugs.debian.org,378936-done@bugs.debian.org,381299-done@bugs.debian.org,382788-done@bugs.debian.org,382945-done@bugs.debian.org,386483-done@bugs.debian.org,387081-done@bugs.debian.org,387543-done@bugs.debian.org,388066-done@bugs.debian.org,389441-done@bugs.debian.org,391221-done@bugs.debian.org,391446-done@bugs.debian.org,391456-done@bugs.debian.org,394190-done@bugs.debian.org,394389-done@bugs.debian.org,394480-done@bugs.debian.org,396963-done@bugs.debian.org,401050-done@bugs.debian.org,403203-done@bugs.debian.org,404859-done@bugs.debian.org,405804-done@bugs.debian.org,422412-done@bugs.debian.org,429629-done@bugs.debian.org,429928-done@bugs.debian.org,446242-done@bugs.debian.org,457177-done@bugs.debian.org,457460-done@bugs.debian.org,457462-done@bugs.debian.org,457465-done@bugs.debian.org,457466-done@bugs.debian.org,457467-done@bugs.debian.org,459777-done@bugs.debian.org,496500-done@bugs.debian.org,516465-done@bugs.debian.org,518315-done@bugs.debian.org,519866-done@bugs.debian.org,520535-done@bugs.debian.org,552872-done@bugs.debian.org,584565-done@bugs.debian.org,626612-done@bugs.debian.org,
Cc: yaird@packages.debian.org, yaird@packages.qa.debian.org
Subject: Bug#626688: Removed package(s) from unstable
Date: Sat, 14 May 2011 11:46:56 +0000
Version: 0.0.13-5+rm

Dear submitter,

as the package yaird has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/626688

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sun, 12 Jun 2011 07:37:44 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 13:59:31 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.