kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

illmat · 2010-08-26 11:23:36

Hey guys,

After I updated from .34 to .35 i got the following error messages during the boot process:

ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata6: link is slow to respond, please be patient (ready=0)
ata6: device not ready (errno=-16), forcing hardreset
ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata6: link is slow to respond, please be patient (ready=0)
ata6: device not ready (errno=-16), forcing hardreset
ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata6: link is slow to respond, please be patient (ready=0)
ata6: device not ready (errno=-16), forcing hardreset
done.
Waiting 10 seconds for device /dev/disk/by-uuid/defe50f0-7570-467d-a527-579680d4a ...
Root device '/dev/disk/by-uuid/defe50f0-7570-467d-a527-579680d4a' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/defe50f0-7570-467d-a527-579680d4a'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]# exit
Trying to continue (this will most likely fail) ...
error: /dev/disk/by-uuid/defe50f0-7570-467d-a527-579680d4a: No such file or directory
ERROR: Unable to determine the file system type of /dev/disk/by-uuid/defe50f0-7570-467d-a527-579680d4a:
Either it contains no filesystem, an unkown filesystem, or more than one valid file system signature was found.
Try adding
rootfstype=your_filesystem_type to the kernel command line.
You are now being dropped into an emergency shell.
/bin/sh: can't access tty; job control turned off
[ramfs /]#

I'm running Arch64 and using a sata harddisk.

I have 4 partitions on this harddisk:
/sda1 = ext3 root partition
/sda2 = swap
/sda3 = ext3
/sda4 = ntfs windows installation

Windows boots without any problems

What I've done so far:
1. added rootfstype=ext3 to the kernel command line
2. i could mount all the partition without any problems in a live system
3. forced fsck on sda1 with a live system [no problems]

I've no clue what i could do now.

Best regards
illmat

combuster · 2010-08-26 11:37:35

https://bbs.archlinux.org/viewtopic.php?id=103362

illmat · 2010-08-31 20:54:21

i've tried evereything mentioned in this thread

finally i've downgraded the kernel to 2.6.34

KoFish · 2010-09-01 11:51:01

I'm having the same problem and would really like to know what in the update caused it and when it is fixed. I think it's really bad for the archlinux community that updating from the main repositories can make a computer unbootable...

Dieter@be · 2010-09-02 19:41:40

which motherboard, sata chipset, and hard disk do you use?
maybe it's the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=16606

illmat · 2010-09-02 21:32:06

motherboard: asus P5Q
sata: Silicon Image Sil5723 controller
hdd: Model=WDC WD6400AAKS-75A7B0, FwRev=01.03B01

Google · 2010-09-03 03:30:51

I had this problem last night, after reboot it worked.

Dieter@be · 2010-09-03 11:00:46

illmat wrote:

motherboard: asus P5Q
sata: Silicon Image Sil5723 controller
hdd: Model=WDC WD6400AAKS-75A7B0, FwRev=01.03B01

I suggest you try the same patches as mentioned on the kernel bugtracker. And see if you get the same results as me.
Either way you should report this to upstream.

edit: setting rootfs type etc won't help, because the sata driver creates no devicefile for the device, so their is no blockdevice file. (see kernel ticket for more info)

Last edited by Dieter@be (2010-09-03 11:01:52)

tanja · 2010-09-13 07:41:22

Hello,

I've got the same problem with the same motherboard (asus P5Q)
Is there any solution yet?

Best regards

Dieter@be · 2010-09-13 07:43:11

yes, there is a patch available: https://bugzilla.kernel.org/show_bug.cgi?id=16606
I suspect this patch will be in a 2.6.35 stable patch soon.

SergeyZ · 2010-09-13 13:51:06

I also had a similar problem. After numerous attempts, i realized y mistake.

My new menu.lst was like:
title Arch Linux kernel 2.6.35
root (hd0,1)
kernel /vmlinuz26 root=/dev/disk/by-uuid/d2674bd5-bfc6-4e26-9b6a-64c14324efd8 ro
initrd /kernel26-35.img

The error was in line /vmlinuz26. I edit it to /vmlinuz26-35 and fixed menu.lst:

title Arch Linux kernel 2.6.35
root (hd0,1)
kernel /vmlinuz26-35 root=/dev/disk/by-uuid/d2674bd5-bfc6-4e26-9b6a-64c14324efd8 ro
initrd /kernel26-35.img

After that system booted normally.

Arch Linux

#1 2010-08-26 11:23:36

kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#2 2010-08-26 11:37:35

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#3 2010-08-31 20:54:21

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#4 2010-09-01 11:51:01

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#5 2010-09-02 19:41:40

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#6 2010-09-02 21:32:06

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#7 2010-09-03 03:30:51

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#8 2010-09-03 11:00:46

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#9 2010-09-13 07:41:22

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#10 2010-09-13 07:43:11

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

#11 2010-09-13 13:51:06

Re: kernel 2.6.34 -> 2.6.35 trouble with sata harddisk

Board footer