Latest working kernel version: 2.6.25 Earliest failing kernel version:2.6.27 Distribution: archlinux, ubuntu, debian, sidux Hardware Environment:Intel Pentium 4, IDE interface: Silicon Integrated Systems [SiS] module: sata_sis 182 SATA/RAID Controller, ATA WDC WD2500JS-55N Problem Description: I use Archlinux (2008.06) and last working kernel is 2.6.25. When I do kernel update I can't mount my system: Root device '/dev/sda1' doesn't exist, attempting to create it ERROR: Failed to parse block device name for 'dev/sda1' ERROR: Unable to create/detect root device '/dev/sda1' Dropping to a recovery shell... type 'exit' to reboot NOTE: klibc contains no 'ls' binary, use 'echo *' instead When I try to install Ubuntu 8.10, Debian (Stable, Testing) or Sidux, they couldn't find my Harddisk. hwd -s (with 2.6.25): Testing: kernel (2.6.25-ARCH) supports uevents HARDWARE DETECT ver 5.4.2 (simple mode) Kernel : 2.6.25-ARCH CPU & Cache: Processor 0: Intel(R) Pentium(R) 4 CPU 3.06GHz 3066MHz, 1024 KB Cache Processor 1: Intel(R) Pentium(R) 4 CPU 3.06GHz 3066MHz, 1024 KB Cache Sound(m) : AC'97 Sound Controller module: snd_intel8x0 Video : RV515 [Radeon X1300] server: Xorg (vesa) Driver : xf86-video-vesa module: - Monitor : Generic Monitor H: 28.0-96.0kHz V: 50.0-75.0Hz Mouse : Microsoft Corp. Basic Optical Mouse xtype: IMPS2 device: /dev/input/mice HDD : 182 SATA/RAID Controller module: sata_sis USB : USB 2.0 Controller module: ehci_hcd USB Reader : Genesys Logic, Inc. USB 2.0 33-in-1 Ethernet : 191 Gigabit Ethernet Adapter module: sis190 Network : No wireless card Firewire : VT6306 Fire II IEEE 1394 OHCI Link Layer Controller module: ohci1394 Menu : Main menu: hwd All : Detect all hardwares: hwd -e X sample : Generate X sample: hwd -x
Created attachment 20355 [details] dmesg dmesg (2.6.25)
Hello, can you please post the kernel boot log which shows the failure? Most installation media has an emergency shell of some sort and you can mount a usb stick or set up network and upload the log file from there even if disk is not accessible.
Created attachment 20361 [details] kern.log kern.log from Sidux Ouranos.
Created attachment 20362 [details] kern.log kern.log from Ubuntu 8.10
In the Sidux one, can you specify module parameter "libata.force=3:nohrst"? Distros have different mechanism to pass in module parameters from boot prompt to modules which are loaded from initrd and unfortunately I don't have any experience with sidux, so you'll need to dig its documentation. Thanks.
Hi I've tried with Debian, Ubuntu, Sidux and Arch. I don't now if I've done it right, but when I try to boot whit kernel option: libata.force=3:nohrst, I have the following information: Unknown boot option `libata.force=3:nohrst': ignoring. For example Arch Linux: Feb 26 20:00:23 arch Kernel command line: root=/dev/disk/by-uuid/f53df57c-df2d-4926-9f42-6591bc014f60 ro libata.force=3:nohrst Feb 26 20:00:23 arch Unknown boot option `libata.force=3:nohrst': ignoring And this I've tried with Ubuntu 8.10: Feb 26 19:29:25 ubuntu kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash -- libata.force=3:nohrst debian-installer/language=de console-setup/layoutcode?=de Feb 26 19:29:25 ubuntu kernel: [ 0.000000] Unknown boot option `libata.force=3:nohrst': ignoring And Sidux: Feb 26 18:28:54 sidux kernel: Kernel command line: lang=de_DE boot=fll quiet vga=791 libata.force=3:nohrst Feb 26 18:28:54 sidux kernel: Unknown boot option `libata.force=3:nohrst': ignoring Have I gone wrong?
Hmmm.... yeah, the kernel itself doesn't know about the parameter, so it will whine about it but the initrd being loaded afterwards can fetch the parameter and pass it to respective modules. Some distros have such mechanism while some don't. I'm familiar only with the booting process of openSUSE and it will pass over the parameter correctly. If you don't know about the sidux one, can you please try openSUSE 11.1?
Yes, I tried openSUSE 11.1 and it works perfectly. But only openSUSE... And I like to have Archlinux or Debian. gparted-live-0.4.1-2 also has the problem with my disc.
Maggie, does SL111 work w/o the parameter? Or do you need to specify the parameter?
Also, please post /var/log/boot.msg.
openSUSE works with this parameter -> libata.force=3:nohrst. Now I'll try install oS 11.1 on my HDD.
So, you need to specify the parameter. If you're gonna install sl111, I can prep a debug kernel for you to try. Please lemme know when you have the system running. Also, please post /var/log/boot.msg. Thanks.
Created attachment 20379 [details] boot.msg It's boot.msg from openSUSE 11.1
The kernel from OpenSUSE (with libata.force=3:nohrst parameter) works good, but system boots very slowly :(
What do you mean by 'boots slowly'? Can you please boot with kernel parameter "printk.printk_time=1" and post /var/log/boot.msg? Or are you saying that nothing seems wrong but it's just slow?
Created attachment 20400 [details] boot.msg openSUSE 11.1 with 2.6.27.19-3.2-debug kernel. (using libata.force=3:nohrst and printk.printk_time=1 as boot parameters)
I don't now openSUSE, but I thinkt it works not wrong, but slower than other distributions which I know. Since 3 years I work every time (at home and in job) with Debian and last with Archlinux.
Ah... okay. I was worried whether you were reporting kernel problem. The slowness is probably due to ext3 barrier=1 + beagle. Anyways, I'll prepare a debug kernel for you. Please wait a bit. Thanks.
Thank you :)
Can you please try the following kernel? http://htj.dyndns.org/export/testing/sl111-i586-kernel12775_dbg0/ You'll need to download kernel-default-base, kernel-default and kernel-default-extra packages and update w/ force parameter (rpm -Uvh --force ALL_THREE_RPMS). Thanks.
I've installed your kernel and it works very good, but it boots faster with libata.force=3:nohrst parameter (beagle is off).
What do you mean by boot faster? Can you please post logs with printk.printk_time=1 in both cases? Please note that you had a typo before. You typed printk.prinkt_time=1.
Created attachment 20422 [details] boot.msg
Oops, you need to turn on CONFIG_PRINTK_TIME under "Kernel Hacking". Also, can you please describe the slowness a bit? Thanks.