Bug 56648 - ldm_validate_partition_table(): disk read fail
Summary: ldm_validate_partition_table(): disk read fail
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-31 05:11 UTC by James Engel
Modified: 2003-03-31 05:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Engel 2003-03-31 05:11:37 UTC
Version:           3.1.0 (using KDE 3.1.0)
Installed from:    Mandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.13mdk

ldm_validate_partition_table() Disk read fail appears after I installed Mandrake 9.1.

The "ldm_validate_partition_table(): disk read fail" was caused by my SanDisk SDDR-05a Compact Flash Card Reader. Since I didn't have a Compact Flash Card in the Reader the software kept trying to read from it until it timed out and allowed the system to continue loading.

The quick fix is to leave a Compact Flash Card in the Reader while booting up the system.

Two of my devices are listed as SCSI Devices in the Mandrake Control Center, under Hardware, Disk:
sda = Buslink USB 2.0 External Hard Drive "/dev/scsi/host0/bus0/target0/lun0/disc"
sdb = SanDisk SDDR-05a USB 1.1 Compact Flash Card Reader "/dev/scsi/host1/bus0/target0/lun0/disc"

I did notice that the only way I could install Mandrake 9.1 was to unplug my Buslink Drive and reconnect it after the install.

My Buslink 2.0 External Hard Drive is connect up to a Buslink USB 2.0 5-Port PCI Card. 

I reinstalled Mandrake 9.1 one more time; this time I left the Buslink connected and left a Compact Flash Card in the SanDisk Reader. Everything installed correctly.
Comment 1 Thiago Macieira 2003-03-31 05:22:06 UTC
This doesn't appear to be a KDE bug. Actually, it doesn't appear to be a bug at all. 
 
From what I could understand, the situation happens during installation. You may 
want instead to file a bug report with Mandrake. 
 
It seems to me you just hit Report Bug in Konqueror in order to report this issue. The 
thing is, you were directed to the site to report bugs in Konqueror and in other KDE 
applications, not the whole system. Please visit Mandrake's site to find their bug 
tracking system.