Update from 2.6.24-12 to -14 or -15 results in ata SRST failed (errno=-16)

In have the same issue. even after todays upgrades.
I was able to boot with the .14 kernel so no real harm done.

Booting with the .15 kernel in recovery mode gives me this message:
Quote
parport0: Pc-style at 0x378 (0x778) irg7, dma3 [pcspp, trista,compat,epp,ecp,dma]

it sits there for about 3-5 minutes then turns up: "fail"
continues to boot, comes up with a recovery screen with:
resume boot, drop to root, fix xserver.

I chose "continue boot" from which I have to login from the cli and get to my gui.

No sound, no network.

So back to kernel .14 for now.

any ideas?

Hello,

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information. It sounds like we may need to know what kind of drive you are using. Also, the two cases reported may have slightly different root causes as it sounds like the original reporter's computer (Linda) is unable to find the root partition whereas the second reporter's symptoms (Fred) suggest that the root partition is found but some other error is causing the problem. Fred, perhaps you can submit a separate bug, but for both...

Please include the following additional information (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies

Thanks in advance!

Hello Emil,

sorry for the missing information, I'm a new convert to linux and this was my first bug report. I figured someone would ask for more details and tell me what to do if it was needed.. and you did.

1.
linda@indigo:~$ uname -a
Linux indigo 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux

3.
Is attached

And here is dmesg

I'm running the 2.6.24-12-generic kernel, because the -14 and -15 won't boot.

And the cat /proc/version_signature > version.log
which the wiki said I should include too.

Hope this helps

Okay this is the output:
fred1@fintanws2:~$ uname -a
Linux fintanws2 2.6.24-14-generic #1 SMP Thu Apr 3 04:49:29 UTC 2008 i686 GNU/Linux

After reboot:

fred1@fintanws2:~$ dmesg > dmesg.log
fred1@fintanws2:~$ sudo lspci -vvnn > lspci-vvnn.log
fred1@fintanws2:~$

so what now?

Problem boot, network and soundcard not work
After boot i have message:
Internal error
failed to initialize HAL!
version.log -> Ubuntu 2.6.24-15.26-generic
auth.log -> Apr 7 23:58:01 medo-desktop gnome-keyring-daemon[5747]: Scheduling hal init retry
Apr 7 23:58:32 medo-desktop gnome-keyring-daemon[5747]: failed to initialize a HAL context: (null)
syslog ->
pulseaudio[5816]: module-hal-detect.c: Couldn't connect to hald: (null): (null)
pulseaudio[5816]: module.c: Failed to load module "module-hal-detect" (argument: ""): initialization failed.
pulseaudio[5816]: main.c: Module load failed.
pulseaudio[5816]: main.c: Failed to initialize daemon.
hcid[5523]: Default passkey agent (:1.17, /org/bluez/passkey) registered
hcid[5523]: Default authorization agent (:1.17, /org/bluez/auth) registered
NetworkManager: <info> Updating allowed wireless network lists.
NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..

Hi,

There are what appears to be three different issues here. Each separate issue needs to be in a separate bug report so that it can be addressed independently of the others, without confusing developers by mixing up information. Fred and medo, can you take re-submit your information as a new bug and push the appropriate bug numbers here?

Linda, it looks like perhaps there's something that changed with the way that these kernels handle your disks. I assume that this problem still continues with the latest kernel package? If so, can you also attach the contents of /etc/fstab?

Thank you for your help in submitting these issues and keeping the organized.

Hi Emil,

I installed all the updates that Kubuntu found had for me, so I suppose the latest kernel packages too.
I just gave the -15 kernel another try, but still nothing... so here's my fstab.

Cheers
Linda

Okay thanks. One possibility is that the new kernels are not recognizing your regular hard drives. It would be most useful if we can get some information from the newer kernels when they fail to boot, such as the output of 'dmesg'. To do that may require some playing around at the (initramfs): since you have no network at that point, the best option may be to see if we can mount a USB key (or external USB drive) and store the output of dmesg and some other commands on that. Are you comfortable enough with Unix shells to do so? The rough steps would be:

* At the prompt, attach a USB key/drive.
* Run dmesg to see what new device was recognized... should be something like sda or sdb, such as:
    [ 8072.023195] sdb: sdb1
* In this case, sdb1 is the new attached device. Mount that new device:
   mkdir /mnt
   mount /dev/sdb1 /mnt

* Then try running:
   ls -l /dev > /mnt/dev.txt
   dmesg > /mnt/dmesg.txt
   cat /proc/modules > /mnt/modules.txt
   umount /mnt

After that you should be able to reboot into your working kernel and re-attach the key/disk and attach the 3 files (dev.txt, dmesg.txt, modules.txt) to this bug.

Ok, I just tried out what you instructed.. it recognised my card reader with the sd-card in it.. dmesg said [numbers] sde :sde1
I did the mkdir /mnt and tried
mount /dev/sde1 /mnt

but I got an error: Failed Mounting /dev/sde1 on /mnt : Invalid Argument

So I rebooted.. got back in Kubuntu with the -12 kernel. Then I thought well maybe I could make some screenshots then with my camera, so I rebooted again to the -15 kernel.. but instead of the busybox I got this:

[150.583498] ata3: SRST failed (errno = -16)

and nothing happened after that, no busybox..
I rebooted to try the -14 kernel, but there I got the ata3 error too, and no busybox anymore either... guess I killed something?? :S

any hints would be helpful.. I'm pretty new to linux, very little experience with console/shells.. I have no idea what the invalid argument was, or why busybox is gone now..

Hello all. Since I have the same problem as you all, here's my contribution.

Emil, unfortunately, when trying to mount the USB pen drive, something like this appears: "mount /dev/sdb1 to /mnt: invalid argument"
I am quite confortable to ask "what the hell is invalid here?" when I do the mounting.

Do have any (more) suggestion?

Cheers

Linda, Se7h,

Thanks for playing along with these instructions. You may be able to get the device to mount by running:

$ mount -t vfat /dev/sde1 /mnt

(replacing sde1 as appropriate).

However, the error message Linda found was useful in helping Google a potential solution; see:
   http://ubuntuforums.org/archive/index.php/t-637776.html
which suggests that the problem is caused by a western digital drive (which Linda's dmesg indicates she has).
The most useful looking suggestion is:
== Someone on a mailing list pointed out this thread: http://ubuntuforums.org/showthread.php?t=586894&page=4
== Switching the drive to Single Drive mode (no jumper) fixed the problem.
== It looks like the problem is a Western Digital drive with a motherboard using the SiS chipset.

This probably involves opening up your case and unplugging a jumper from the back of your drive.

Is that something you can try doing? If it doesn't work, definitely try the mount -t vfat to get the dmesg and other
log messages I suggested originally.

Emil,

The fs mount option did work to get rid of the "invalid argument", but gave me a brand new one "no such device".
This is really odd, since the ls shows all devices in the machine, including the one I'm trying to mount.

I'm ok with openening my case and all.. but I wonder if single drive mode is a good thing to do in my rig?
I have a 160GB WD pata disk, on which I have my windows and kubuntu. and a 500GB Sata disk for all my data.
My mobo is a Asus K8V se Deluxe, with AMD64bits processor, I think the 3000+ (2GHz). I run Kubuntu 32bits though.

I will try the new mount option tomorrow, before I try the Hard disk thing ^_^ I'll let you know what happens.

On Wed, 09 April 2008 at 21:47 (-0000), Linda Polman wrote:
> I'm ok with openening my case and all.. but I wonder if single drive
> mode is a good thing to do in my rig? I have a 160GB WD pata disk, on
> which I have my windows and kubuntu. and a 500GB Sata disk for all my
> data.

The "single" setting is for the individual ATA controller. PATA
controllers support up to two drives per controller. When there is only
one drive, it can be configured to act as a "single" drive or a "master"
drive. When there are two drives, one must be the "master", and the
other a "slave". This is typically configured by a small jumper on the
rear of the drive (where all the cables plug in). Often the pin
configurations are on the drive itself; you may want to Google your
drive as well.

This suggestion from an Ubuntu Forum member suggests that re-configuring
the driver from "master" to "single" should fix the problem. This
should be safe for your system because the 500GB SATA disk is on a
separate controller: it is SATA, not PATA. Hopefully, re-configuring
the drive will work out and allow you to use the more recent kernels.

That said, please understand that I (nor Ubuntu) are providing
any warranty as to the safety of your data. You should absolutely
have backups of everything you deem important!

--
Emil Sit / http://www.emilsit.net/

Hey Emil

I just removed the jumper from my harddisk, and guess what: kernel-15 loaded like it should!
Even more: grub did not take 30+seconds for stage1.5 (it took ages to get into the bootmenu ever since I had the sata disk in.. a friend said it's crappy hardware, nothing you can do.. but removing the jumper helped).. Perhaps that's the reason too that the openSUSE installer would not see my pata disk either.. just my sata disk..

anyways
It just booted up fine :D:D
not sure if you'll still need the dmesg, but I ran one for you just after reboot.

Thanks again for your help :D

Linda,

I'm glad we were able to get your system to boot.

For reference, mounting the USB keys probably failed because the initial boot system did not yet support the FAT filesystem used on USB keys.

I will mark this bug as confirmed and assign it to the kernel team so they can decide if the problem where your WD drive was not recognized in the -14 and -15 kernel when configured as a master is a regression that they want to fix; if they do, you might be asked to test the fix.

Thanks!

Note for kernel team: you can ignore comments not from Linda Polman or myself for the purposes of this bug; I've asked the other commenters to re-file their issues as separate bugs. From discussions on #ubuntu-kernel, this may possibly be related to bug 210200.

>if they do, you might be asked to test the fix.

Sure no problem :-)

Thanks again!

I'm still having problems with this. Kernel updates keep coming, but none appears to be fixing this issue.

This forces me to select last release kernel version (2.6.22-14-generic) to have a usable system, which is very frustrating if we look the date this bug was first posted.

Any comments on this is appreciated. Cheers

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Linda Polman, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]