Bug#328534: Adaptec 2005S Hangs with current experiemental 2.6.13-686-smp kernel
Jurij Smakov wrote:
On Sat, 12 Nov 2005, wolftales wrote:
End of screen ouput:
Begin: Running /scripts/local-top ...
Done.
ALERT! /dev/sda1 does not exist. Dropping to a shell!
Oh, that might be not your controller's bug, but initramfs-tools bug.
You can either use yaird to generate your initrd (check out [0] on how
to do that), or increase the value of sleep immediately after
udevsynthesize call in /usr/share/initramfs-tools/init from 2 to 20.
That should give udev enough time to create the devices. Of course,
there is a possibilty that devices not created because of the driver
problems, but if you use yaird, this possibility may be rules out.
[0] http://kernel-handbook.alioth.debian.org/ch-initrd.html
Best regards,
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
Hi,
I had no luck running this with yaird as I showed below. I tried on two
separate systems at 'testing' level with the same result or error. THe
other system has a similar problem and runs at 2.6.7 which has a kernel
[panic with anything newer. I thought I'd try the 2.6.14 kernel to see
if this might have been loosely related. but this other system has a
qlogic SCSI HBA in it, not adaptec. The only thing this shows is either
I was doing something wrong or there is another dependecy problem with
trying to use yaird instead of initramfs. I did not try this on an
unstable box to see if there was any difference.
I edited the udevsynthesize setting and got a slightly different screen
output but effectively the same error, "/dev/sda1 does not exist":
hdb: DVD-ROM BDV316C, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x3f6 on irq 14
hdb: ATAPI 1X DVD-ROM drive, 512kB cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Done.
Begin: Running /scripts/init-premount ...
ACPI: Fan [FAN] (on)
ACPI: CPU0 (power states: C1[C1])
ACPI: CPU1 (power states: C1[C1])
ACPI: CPU2 (power states: C1[C1])
ACPI: CPU3 (power states: C1[C1])
ACPI: Thermal Zone [THRM] (32 C)
Done.
Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
Done.
ALERT! /dev/sda1 does not exist. Dropping to a shell!
BusyBox v1.01 (Debian 1:1.01-3) Built-in shall (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
/ # dpti0: Trying to Abort cmd=48
When trying to force the system to use yaird, I ran into similar
problems on two separate systems running testing, so I think I do not
have the right versions to run yaird. Here is the output of one of
those attempts:
debian:~# apt-show-versions yaird
yaird/testing uptodate 0.0.11-10
debian:~# dpkg-reconfigure linux-image-2.6.14-1-686-smp
Using /usr/sbin/mkinitramfs to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
Not touching initrd symlinks since we are being reinstalled (2.6.14-2)
Not updating image symbolic links since we are being updated (2.6.14-2)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.14-1-686-smp
Found kernel: /boot/vmlinuz-2.4.27-2-686-smp
Updating /boot/grub/menu.lst ... done
debian:~# vi /etc/kernel-img.conf
debian:~# cat /etc/kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook = /sbin/update-grub
# This line was entered, there was no entry before testing.
ramdisk = /usr/sbin/mkinitrd.yaird
debian:~# dpkg-reconfigure linux-image-2.6.14-1-686-smp
Failed to find suitable ramdisk generation tool for kernel version
2.6.14-1-686-smp on running kernel 2.4.27-2-686-smp in
/usr/sbin/mkinitrd.yaird
Regards,
Ken
Reply to: