2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )

[Tom Verdaat]

I'm testing Hardy and ran into the following issue:

The 2.6.24-12 kernel boots and the system works just fine. Both the 2.6.24-14 and -16 do not boot. Immediately after selecting the kernel in GRUB, it hangs while loading the kernel, giving a load of ATA related errors and endig with the message:

ldm_validate_partition_table(): Disk read failed.

I've taken a picture of the screen output and added it as an attachment to this bug report. The hard disk uses PATA. Below is the lspci for some info about the hardware it's running on.

$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04

$ uname -r
2.6.24-12-generic

$ lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
04:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

[Nick (nickharlow)]

I'm having an identical problem to this.

Hardware I'm on:

nick@ubuntu:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller (rev 14)
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:09.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:09.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:09.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
00:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a)
00:0c.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface
01:05.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01)
01:05.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01)

[Nicolas (dawar)]

Linux ubuntu 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux

Seem to have the same problem on my storage disk :

dmesg :
[ 22.389443] ata4.00: status: { DRDY ERR }
[ 22.389445] ata4.00: error: { ICRC ABRT }
[ 22.389469] ata4: soft resetting link
[ 22.732276] ata4.00: configured for UDMA/33
[ 22.903945] ata4.01: configured for UDMA/33
[ 22.903968] ata4: EH complete
[ 22.911206] ldm_validate_partition_table(): Disk read failed.
[ 22.911216] Dev sdc: unable to read RDB block 0

sudo fdisk -l
[sudo] password for dawar:

[...]

Disque /dev/sdc: 250.0 Go, 250059350016 octets
255 heads, 63 sectors/track, 30401 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Identifiant disque: 0x0001ed9d

Périphérique Amorce Début Fin Blocs Id Système
/dev/sdc1 1 30401 244196001 83 Linux

But I can mount the disk, /dev/sdc1 does not exist !

I can read all the files on this disk with my Ubuntu 6.06 liveCD.

lspci (I'm not using raid, only ATA disk):
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0b.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
00:0c.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:0c.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01)
01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01)

[Don Malcolm (lpad6)]

Guys,

I have resolved this issue for my system. It turns out that there has been a rewrite, and that it is less tolerant of bad IDE cabling and bad jumper settings. For details, refer to https://bugzilla.redhat.com/show_bug.cgi?id=444334

[Nicolas (dawar)]

Thanks Don. But opening the computer to change the cabling is not a perfect solution.

Do you think this bug is related to bug#213639 ? I will try tomorow to "backport" the kernel module to 2.6.24-12 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639/comments/8 )

[Nicolas (dawar)]

I just try to use the "old via" modules, and it works ! It's the same bug than bug#213639

Just folow this post : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639/comments/8

Your no-working disk will be hdXX instead of sdXX, but now you can mount it...

[Spohl (bernfresse)]

Is there a chance that this will get fixed sometime?

The problem still exists with the new kernel in the proposed sources (2.6.24-17)
I'm not keen on switching the modules for every kernel version. Till now I'm still using the old gutsy kernel.

[rusart (ruslan-levitskiy)]

Yes, this problem is still exists. The solution with "old via modules" hasn't effect.

[rusart (ruslan-levitskiy)]

UPD:
Sorry, it works for me (kernel 2.6.24-17-generic) with solution https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639/ and modules from this post: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639/comments/10

[Spohl (bernfresse)]

Unfortunately, the old modules dont work for me.
There is still the problem, that no harddisk can be found, no matter if i try sda, hda or UUID.

No error appears, booting just stops after detecting the USB-devices. After a few min, the ALERT-Warning appears:
"/dev/disk/by-UUID ... does not exist ..." etc..

[Tom Verdaat (tom-verdaat)]

I see the status has been set to 'Triaged'. Don't know what was done but the -17 kernel does not solve this error. I manually have to set this to the -12 series again!

I'm sorry to have to say this but this is unacceptable, most certainly for a LTS release. The only reason I can run Hardy on this machine is because I started using it when it was still Beta, otherwise I wouldn't have a 2.6.24-12 kernel. This is a critical bug because people with older machines won't get Ubuntu to boot. Please fix this a.s.a.p.

[Tom Verdaat (tom-verdaat)]

Not fixed in 2.6.24-17 kernel release.

[kiev1 (sys-sys-admin)]

((( yes - "Not fixed in 2.6.24-17 kernel release." (((

if You see in /var/log/syslog ata error messages after copy large (2Gb) files
then this kernel bug -> http://bugzilla.kernel.org/show_bug.cgi?id=9115#c18

[Spohl (bernfresse)]

I solved this problem

As one can read in this bug-report(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639), someone tried a 80-wire ide-cable instead of a 40-wire. And it worked. And for me it also works with this bug. The 80-wire cable has a blue plug for the mainboard, the other two plugs are grey and black. After switching to this cable I could boot Live-CD.

[Tom Verdaat (tom-verdaat)]

Just updated the computer that I've experienced this bug on and it is not fixed in the 2.6.24-19 kernel release.

[Leann Ogasawara (leannogasawara)]

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.

[MdMax (mdmaxlp)]

I just wanted to confirm, the 80-wire IDE cable works also for me: Ubuntu 8.04.1 with a Gigabyte GA-6VTX motherboard (VIA 694T AGPset).

[Launchpad Janitor (janitor)]

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.

[Andy Whitcroft (apw)]

There has been little activity on the bug report for a number of months and I am therefore wondering if this bug still exhibits itself with the latest hardy kernels. The latest kernel in -proposed is 2.6.24-24.53. If you are able to reproduce this could you include dmesg output at the time the problem occurs. Thanks for testing.

[Andy Whitcroft (apw)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks!

[Tom Verdaat (tom-verdaat)]

I'm unable to test this. Fixed the issue a long time ago by changing cables as described in the comment by Spohl (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/216353/comments/14).