Debian Bug report logs - #343042
linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Toggle useless messages

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

From: Paulo Marcel Coelho Aragao <marcelpaulo@yahoo.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 00:34:11 -0200

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system

Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot 
is interrupted with repeated messages:

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

until it finally stops completely, with message:

Device /sys/block/hda/hda1/dev seems to be down

I'm having to reboot with 2.6.12.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
* linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:

Message #12 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Cesare Leonardi <celeonar@tiscali.it>

To: Paulo Marcel Coelho Aragao <marcelpaulo@yahoo.com>, 343042@bugs.debian.org

Subject: Re: Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 04:33:29 +0100

Paulo Marcel Coelho Aragao wrote:
> Package: linux-image-2.6.14-2-686
> Version: 2.6.14-5
> Severity: critical
> Justification: breaks the whole system
> 
> Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot 
> is interrupted with repeated messages:
> 
> /bin/cat: /sys/block/hda/hda1/dev: No such file or directory
> 
> until it finally stops completely, with message:
> 
> Device /sys/block/hda/hda1/dev seems to be down
> 
> I'm having to reboot with 2.6.12.

This happened to me too.
I followed more or less the same steps as Paulo:
- upgrade linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14.5;
- fail to reboot with the error messages above that appears 4 times with 
increasing delay, saying: "Waiting X second for /sys/block/hda/dev to 
show up";
- reboot with kernel 2.4.27 then download and install
linux-image-2.6.12-1-686 to have a system fully functional.

More info related to my system:
Sony Vaio VGN-B3VP
Debian unstable

Cesare.

Message #17 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: 343042@bugs.debian.org

Subject: Additional info

Date: Mon, 12 Dec 2005 03:05:14 -0200

Added to /etc/yaird/Default.cfg:

MODULE		piix
MODULE		generic
MODULE		ide-disk

and ran:

yaird --verbose --output=/boot/initrd.img-2.6.14-2-686 2.6.14-2-686

Exactly the same problem: no joy.

I thought this might be needed:
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
     bridge (AGP disabled) (rev 03)
0000:00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:00:10.0 Communication controller: Agere Systems 56k WinModem (rev 01)
0000:00:13.0 CardBus bridge: Texas Instruments PCI1221
0000:00:13.1 CardBus bridge: Texas Instruments PCI1221
0000:00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3)

Paulo

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

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Paulo Marcel Coelho Aragao <marcelpaulo@yahoo.com>, 343042@bugs.debian.org

Cc: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Re: Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 07:15:58 +0100

On Mon, Dec 12, 2005 at 12:34:11AM -0200, Paulo Marcel Coelho Aragao wrote:
> Package: linux-image-2.6.14-2-686
> Version: 2.6.14-5
> Severity: critical
> Justification: breaks the whole system
> 
> Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot 
> is interrupted with repeated messages:
> 
> /bin/cat: /sys/block/hda/hda1/dev: No such file or directory
> 
> until it finally stops completely, with message:
> 
> Device /sys/block/hda/hda1/dev seems to be down
> 
> I'm having to reboot with 2.6.12.

To help pin down the cause, could you post the output of:

	uname -a
	dpkg -l yaird
	yaird -v -o crap.img 2.6.14-2-686
	yaird -v -o crap.img 2.6.14-5-686

(assuming these are the last kernel that boots and the first that works)

Thanks,
Erik

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

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Cesare Leonardi <celeonar@tiscali.it>, 343042@bugs.debian.org

Subject: Re: [Yaird-devel] Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 07:18:30 +0100

On Mon, Dec 12, 2005 at 04:33:29AM +0100, Cesare Leonardi wrote:
> Paulo Marcel Coelho Aragao wrote:
> > Package: linux-image-2.6.14-2-686
> > Version: 2.6.14-5
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot 
> > is interrupted with repeated messages:
> > 
> > /bin/cat: /sys/block/hda/hda1/dev: No such file or directory
> > 
> > until it finally stops completely, with message:
> > 
> > Device /sys/block/hda/hda1/dev seems to be down
> > 
> > I'm having to reboot with 2.6.12.
> 
> This happened to me too.
> I followed more or less the same steps as Paulo:
> - upgrade linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14.5;
> - fail to reboot with the error messages above that appears 4 times with 
> increasing delay, saying: "Waiting X second for /sys/block/hda/dev to 
> show up";
> - reboot with kernel 2.4.27 then download and install
> linux-image-2.6.12-1-686 to have a system fully functional.

To help pin down the cause, could you post the output of:

        uname -a
	dpkg -l yaird
	yaird -v -o crap.img 2.6.14-2-686
	yaird -v -o crap.img 2.6.14-5-686

(assuming these are the last kernel that boots and the first that works)

Thanks,
Erik

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

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: 343042@bugs.debian.org

Subject: Re: (INFO) linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 04:55:50 -0200

> Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, 
> boot is interrupted with repeated messages:
> 
> /bin/cat: /sys/block/hda/hda1/dev: No such file or directory
> 
> until it finally stops completely, with message:
> 
> Device /sys/block/hda/hda1/dev seems to be down

Erik,

I saw you requesting additional info from someone that bumped into exactly the 
same problem I had. I thought that it might be useful if I sent you the same 
info.

Paulo

Linux cortazar 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686 GNU/Linux

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  yaird          0.0.12-1       Yet Another mkInitRD

yaird -v -o crap.img 2.6.12-1-686

yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/bitblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/font.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/tileblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/fbcon.ko {optionList=-- }
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:07.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda1 {sysname=hda/hda1 }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda1 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

yaird -v -o crap.img 2.6.14-2-686

yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:07.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda1 {sysname=hda/hda1 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda1 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

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

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: 343042@bugs.debian.org

Subject: Workaround

Date: Mon, 12 Dec 2005 10:03:56 -0200

Taking a lead from Ricardo, worked around the problem with:

1. Added to /etc/yaird/Default.cfg:

MODULE		ide-generic
MODULE		ide-disk

2. Created new initrd image:

rm /boot/initrd.img-2.6.14-2-686
yaird -v -o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686

3. Reboot.

hda now properly recognized and boot completes.

Paulo

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

From: Richard Antony Burton <richardaburton@hotmail.com>

To: Debian Bug Tracking System <343042@bugs.debian.org>

Subject: Re: #343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat

Date: Mon, 12 Dec 2005 16:24:26 +0000

Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042

Confirmed Paulo's suggestion above to be working.

This problem is hitting everyone I know who has updated today. The fact that the
broken yaird was released on the same day as a new kernel means that a lot of
people are going to hit this, because they will actually be using yaird today.

Unfortunaly on a couple of boxes I only had the one kernel installed, and with
the minor update it overwrote the exisitng version instead of installing along
side, leaving me with unbootable boxes.

Considering the potential for harm I wonder if there could be something done to
mitigate this happening again in future. Avoiding releasing yaird at the same
time as a minor kernel update would have helped, because the bug would have only
been hit by a small number before it could be fixed. However perhaps the more
important issue is that of releasing minor kernel updates that overwrite the
existing kernel, this is obviously vunerable to more problems than just a badly
timed yaird break. That's obviously an issue for the kernel maintainers.

Richard.

p.s. before anyone tells me, i have been reminded of why it's a good idea to
keep a known working kernel on the box ;-)

Message #52 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: Richard Antony Burton <richardaburton@hotmail.com>, 343042@bugs.debian.org

Subject: Re: [Yaird-devel] Bug#343042: #343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat

Date: Mon, 12 Dec 2005 17:58:33 +0100

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

On Mon, 12 Dec 2005 16:24:26 +0000
Richard Antony Burton <richardaburton@hotmail.com> wrote:

> Considering the potential for harm I wonder if there could be
> something done to mitigate this happening again in future. Avoiding
> releasing yaird at the same time as a minor kernel update would have
> helped, because the bug would have only been hit by a small number
> before it could be fixed. However perhaps the more important issue is
> that of releasing minor kernel updates that overwrite the existing
> kernel, this is obviously vunerable to more problems than just a
> badly timed yaird break. That's obviously an issue for the kernel
> maintainers.

One appreach that you could do locally is to copy your /boot/initrd.*
to /boot/initrd.*.good or whatever. Then if problems occur (and you are
using GRUB) you can edit the GRUB menu item to load the alternative
image.

Such approach is tightly related to the capabilities of your
bootloader, while the ramdisk image is generated from your kernel
package postinst. Enhancing this for the distribution (rather than
each admin doing local hacks depending on their choice of bootloader
+kernel+arch) probably requires something like
http://wiki.debian.org/FlexibleKernelHandling


> p.s. before anyone tells me, i have been reminded of why it's a good
> idea to keep a known working kernel on the box ;-)

Ahh - too late I guess (or look the other way when those other two
replies of mine hits your inbox) :-P


 - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDnaw5n7DbMsAkQLgRAuIsAJ91bT/Wqc+Ft59qp2y6nA5MrYtYowCfZfVR
8HWNh+MrNWtzfRKIz25f/UI=
=iWOO
-----END PGP SIGNATURE-----

Message #57 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Cesare Leonardi <celeonar@tiscali.it>

To: Erik van Konijnenburg <ekonijn@xs4all.nl>

Cc: 343042@bugs.debian.org

Subject: Re: [Yaird-devel] Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Mon, 12 Dec 2005 21:31:28 +0100

[Message part 1 (text/plain, inline)]

Erik van Konijnenburg wrote:
> To help pin down the cause, could you post the output of:
> 
>         uname -a
> 	dpkg -l yaird
> 	yaird -v -o crap.img 2.6.14-2-686
> 	yaird -v -o crap.img 2.6.14-5-686
> 
> (assuming these are the last kernel that boots and the first that works)

To avoid my mail client autowrap, i've attached the output of the two 
yaird commands.

uname -a:
Linux tommaso 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686 GNU/Linux
	
dpkg -l yaird:
||/ Name           Version        Description
+++-==============-==============-============================================
ii  yaird          0.0.12-1       Yet Another mkInitRD

Cesare.

[2.6.12-1-686.txt (text/plain, inline)]

yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/bitblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/font.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/tileblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/video/console/fbcon.ko {optionList=-- }
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.12-1-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

[2.6.14-2-686.txt (text/plain, inline)]

yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

Message #62 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Kees Cook <kees@osdl.org>

To: Debian Bug Tracking System <343042@bugs.debian.org>

Subject: yaird: IDE init fails

Date: Mon, 12 Dec 2005 15:22:10 -0800

Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042


I'm seeing the same problems with yaird.  Made 2.6.14 unbootable.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686-smp
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.3-1     The Debian Almquist Shell
ii  libc6                        2.3.5-8.1   GNU C Library: Shared libraries an
ii  libhtml-template-perl        2.7-1       HTML::Template : A module for usin
ii  libparse-recdescent-perl     1.94.free-1 Generates recursive-descent parser
ii  perl                         5.8.7-9     Larry Wall's Practical Extraction 

yaird recommends no packages.

-- debconf-show failed

Message #67 received at 343042@bugs.debian.org (full text, mbox, reply):

From: dann frazier <dannf@dannf.org>

To: 343042@bugs.debian.org

Subject: kernel bug or yaird bug

Date: Wed, 14 Dec 2005 00:24:50 -0700

fyi, I just reassigned/merged a bug here, but messages on debian-kernel
lead me to believe this should actually be fixed in linux-2.6.  Please
reassign if that is the case.
-- 
dann frazier <dannf@dannf.org>

Message #74 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Alister Winfield <alister.winfield@uk.easynet.net>

To: 343042@bugs.debian.org

Subject: Yaird fails to add correct device modules

Date: Wed, 14 Dec 2005 10:09:35 +0000

I've seen the same and got it to work by manually adding the
module lines to the yaird Template for my boot disk.

This suggests that the automatic module selection done for the boot disk
is going wrong somewhere. Haven't looked any deeper at this.

--
Alister Winfield.

Message #79 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Richard Antony Burton <richardaburton@hotmail.com>

To: Debian Bug Tracking System <343042@bugs.debian.org>

Subject: Re: #343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat

Date: Wed, 14 Dec 2005 10:42:58 +0000

Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042

FYI the above workaround does not work for machines with SATA drives. I couldn't
find a combination of modules that would get it to boot.

Switching back to previous yaird (0.0.11-12) fixes the problem on both PATA &
SATA systems.

Richard.

Message #84 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Richard Antony Burton <richardaburton@hotmail.com>, 343042@bugs.debian.org

Subject: Re: [Yaird-devel] Bug#343042: #343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat

Date: Wed, 14 Dec 2005 15:06:27 +0100

On Wed, Dec 14, 2005 at 10:42:58AM +0000, Richard Antony Burton wrote:
> Package: yaird
> Version: 0.0.12-1
> Followup-For: Bug #343042
> 
> FYI the above workaround does not work for machines with SATA drives. I couldn't
> find a combination of modules that would get it to boot.
> 
> Switching back to previous yaird (0.0.11-12) fixes the problem on both PATA &
> SATA systems.

Hmm, you're the first to report problems with SATA, and considering
what was changed between 0.0.11 and 0.0.12, I would not expect any
problems in this area.

To help debugging, could you post your version of /etc/yaird/Default.cfg,
plus the output of yaird -v for the working version and the broken version?

Thanks,
Erik

Message #89 received at 343042@bugs.debian.org (full text, mbox, reply):

From: "Richard Burton" <richardaburton@hotmail.com>

To: ekonijn@xs4all.nl, 343042@bugs.debian.org

Subject: Re: [Yaird-devel] Bug#343042: #343042: linux-image-2.6.14-2-686: Boot aborts wit

Date: Thu, 15 Dec 2005 09:42:50 +0000

>From: Erik van Konijnenburg <ekonijn@xs4all.nl>
> >On Wed, Dec 14, 2005 at 10:42:58AM +0000, Richard Antony Burton wrote:

> > FYI the above workaround does not work for machines with SATA drives. I 
>couldn't
> > find a combination of modules that would get it to boot.

>To help debugging, could you post your version of /etc/yaird/Default.cfg,
>plus the output of yaird -v for the working version and the broken version?

I can no longer recreate the problem. To give more background, which may 
explain why, this was a clean install on a new box with SATA, using Debian 
From Scratch 0.6.19. I was under the 2.6.11 kernel from the CD when I build 
the initrd in a chroot to my new install. /proc and /sys were both mounted, 
and yaird appeared to complete sucessfully.

I have tried booting from the DFS CD again under the same kernel and still 
cannot recreate the problem. The bootstrapped version of sid from the CD 
contained quite a few backlevel packages, which have since been updated, so 
maybe this has some bearing on it? I don't have another box like this I can 
reinstall now to try again from scratch.

Anyway, in my current system state I can build a working initrd from the 
latest yaird, and since there is no upgrade path to 2.6.14/yaird from Sarge 
(and so probably no official upgrade path from anything else either) this 
can probably be discounted as an odd one-off.

Regards, Richard.

Message #94 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Dimitry Andric <dimitry@andric.com>

To: 343042@bugs.debian.org

Subject: Possible fix?

Date: Thu, 15 Dec 2005 14:05:45 +0100

[Message part 1 (text/plain, inline)]

It seems that even in 2.6.14, you always need the ide-generic module
if you use any other ide module.  This is because ideprobe_init() is
ONLY called from the ide-generic module initialization!

There's a comment in /usr/lib/yaird/perl/Hardware.pm which says:

        # Hmm, via82cxxx (2.6.8) also needs ide-generic
        # to load it seems.  That could be because ide-generic
        # contains a call to ide_probe_init() which is in
        # the ide-core module.  After loading ide-generic
        # it's still the via82cxxx module that manages the device;
        # see /sys/bus/pci/drivers/VIA_IDE/.
        # The above error persists in 2.6.12, and is solved
        # in 2.6.14.

The last sentence is NOT true, I just completely grepped through a
full 2.6.14 source tree, and ideprobe_init() is ONLY called from
ide_generic_init().

Therefore, you always need to include the ide-generic module if the
system uses IDE.

[signature.asc (application/pgp-signature, attachment)]

Message #99 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Andrew Sackville-West <andrew@farwestbilliards.com>

To: 343042@bugs.debian.org

Subject: Re: Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message, '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

Date: Fri, 16 Dec 2005 14:11:54 -0800

I can confirm, as others have mentioned, that this bug affects AMD 
systems as well. All of my symptoms were identical to others reported.

I chose to downgrade yaird to testing and this resolved the problem (now 
running 2.6.14-5). I appears to me that the patch mentioned above 
doesn't apply yet to AMD so I chose this route.

I encountered another problem at the same time and I'm trying to 
determine if they are related. If anyone else encountered this as well, 
please let me know.

All boots now (whether 2.8.14, or 2.6.12 my old kernel) fail with fsck 
errors on every partition(!). something along the lines of:

UNEXEPCTED DISCREPANCY: SuperBlock last write time is in the future.

I realise this is likely not related to this bug (especially because it 
was all part of a massive apt-get upgrade), but since this bug involved 
ide issues I thought it might apply.
any help appreciated.

Message #104 received at 343042@bugs.debian.org (full text, mbox, reply):

From: Carlos González <carlosgd@madridwireless.net>

To: 343042@bugs.debian.org

Subject: linux-image-2.6.14-2-686 don't boot, yaird fail

Date: Sun, 18 Dec 2005 00:36:15 +0100

[Message part 1 (text/plain, inline)]

package: yaird
version: 0.0.12-1

The linux-image2.6.14-2-686 fail to boot with this errors:
 /bin/cat: /sys/block/hda/hda1/dev: No such file or directory

This is using yaird for create the initrd, for solve(how I see in some
bugreport), I downgrade my yaird to the version 0.0.11-12, and:
dpkg-reconfigure linux-image-2.6.14-2-686

[signature.asc (application/pgp-signature, inline)]

Message #109 received at 343042-close@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: 343042-close@bugs.debian.org

Subject: Bug#343042: fixed in yaird 0.0.12-2

Date: Sun, 25 Dec 2005 05:32:10 -0800

Source: yaird
Source-Version: 0.0.12-2

We believe that the bug you reported is fixed in the latest version of
yaird, which is due to be installed in the Debian FTP archive:

yaird_0.0.12-2.diff.gz
  to pool/main/y/yaird/yaird_0.0.12-2.diff.gz
yaird_0.0.12-2.dsc
  to pool/main/y/yaird/yaird_0.0.12-2.dsc
yaird_0.0.12-2_powerpc.deb
  to pool/main/y/yaird/yaird_0.0.12-2_powerpc.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 343042@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <dr@jones.dk> (supplier of updated yaird package)

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


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

Format: 1.7
Date: Fri,  9 Dec 2005 04:00:25 +0100
Source: yaird
Binary: yaird
Architecture: source powerpc
Version: 0.0.12-2
Distribution: unstable
Urgency: low
Maintainer: Yaird Team <yaird-devel@lists.alioth.debian.org>
Changed-By: Jonas Smedegaard <dr@jones.dk>
Description: 
 yaird      - Yet Another mkInitRD
Closes: 342652 342904 343042 343280
Changes: 
 yaird (0.0.12-2) unstable; urgency=low
 .
   * Patch in upstream development as of today.
     + Support modules that alias aes. Closes: bug#342652 (thanks to
       Stefan Schmidt <stefan@datenfreihafen.org>).
     + Avoid generating an initrd image if errors occur. Would have
       caused the ide-generic bugs fixed below to be non-fatal as no
       non-working ramdisk would have been generated (and overwritten
       the older working one).
     + Mention USB hardware as working in documentation.
     + Fix non-sysfs-aware Sparc input devices. Closes: bug#342904
       (thanks to Frans Pop <aragorn@tiscali.nl>).
     + Add ide-generic quirk for piix and amd74xx chipsets. Closes:
       bug#343042, #343280 (and possibly #343592 too but leaving open
       for now). Thanks to Paulo Marcel Coelho Aragao
       <marcelpaulo@yahoo.com>, Rick Friedman <rickfriedman@verizon.net>
       and everyone else helping out with this bad one.
   * Declare empty CDBS_BUILD_DEPENDS as a trick to avoid build-essential
     (considered fatal by ftpmasters) when auto-building debian/control.
   * Update local cdbs snippet buildinfo.mk (adjust its namespace).
Files: 
 d2926302e815f781cf23a49cc2ce4a4e 746 utils optional yaird_0.0.12-2.dsc
 1085c8a1e7efb0fba42c5b4afe855464 18941 utils optional yaird_0.0.12-2.diff.gz
 d239d766b85d57330ba6331b324d1d2d 174958 utils optional yaird_0.0.12-2_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDrpwxn7DbMsAkQLgRAorGAJsE+UwAx22ZI2K7bqQaIZytLAHa5QCgphe3
dSiqkBt+o7xmV7VRw9tl29s=
=cTLF
-----END PGP SIGNATURE-----

Message #114 received at 343280-close@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: 343280-close@bugs.debian.org

Subject: Bug#343280: fixed in yaird 0.0.12-2

Date: Sun, 25 Dec 2005 05:32:10 -0800

Source: yaird
Source-Version: 0.0.12-2

We believe that the bug you reported is fixed in the latest version of
yaird, which is due to be installed in the Debian FTP archive:

yaird_0.0.12-2.diff.gz
  to pool/main/y/yaird/yaird_0.0.12-2.diff.gz
yaird_0.0.12-2.dsc
  to pool/main/y/yaird/yaird_0.0.12-2.dsc
yaird_0.0.12-2_powerpc.deb
  to pool/main/y/yaird/yaird_0.0.12-2_powerpc.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 343280@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <dr@jones.dk> (supplier of updated yaird package)

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


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

Format: 1.7
Date: Fri,  9 Dec 2005 04:00:25 +0100
Source: yaird
Binary: yaird
Architecture: source powerpc
Version: 0.0.12-2
Distribution: unstable
Urgency: low
Maintainer: Yaird Team <yaird-devel@lists.alioth.debian.org>
Changed-By: Jonas Smedegaard <dr@jones.dk>
Description: 
 yaird      - Yet Another mkInitRD
Closes: 342652 342904 343042 343280
Changes: 
 yaird (0.0.12-2) unstable; urgency=low
 .
   * Patch in upstream development as of today.
     + Support modules that alias aes. Closes: bug#342652 (thanks to
       Stefan Schmidt <stefan@datenfreihafen.org>).
     + Avoid generating an initrd image if errors occur. Would have
       caused the ide-generic bugs fixed below to be non-fatal as no
       non-working ramdisk would have been generated (and overwritten
       the older working one).
     + Mention USB hardware as working in documentation.
     + Fix non-sysfs-aware Sparc input devices. Closes: bug#342904
       (thanks to Frans Pop <aragorn@tiscali.nl>).
     + Add ide-generic quirk for piix and amd74xx chipsets. Closes:
       bug#343042, #343280 (and possibly #343592 too but leaving open
       for now). Thanks to Paulo Marcel Coelho Aragao
       <marcelpaulo@yahoo.com>, Rick Friedman <rickfriedman@verizon.net>
       and everyone else helping out with this bad one.
   * Declare empty CDBS_BUILD_DEPENDS as a trick to avoid build-essential
     (considered fatal by ftpmasters) when auto-building debian/control.
   * Update local cdbs snippet buildinfo.mk (adjust its namespace).
Files: 
 d2926302e815f781cf23a49cc2ce4a4e 746 utils optional yaird_0.0.12-2.dsc
 1085c8a1e7efb0fba42c5b4afe855464 18941 utils optional yaird_0.0.12-2.diff.gz
 d239d766b85d57330ba6331b324d1d2d 174958 utils optional yaird_0.0.12-2_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDrpwxn7DbMsAkQLgRAorGAJsE+UwAx22ZI2K7bqQaIZytLAHa5QCgphe3
dSiqkBt+o7xmV7VRw9tl29s=
=cTLF
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.