liquidzoo Posted May 13, 2003 Report Share Posted May 13, 2003 I think this is a hardware problem I get this error that says ldm_validate_partition_table ( ): Disk Read Failed When I am booting up and if I don't enter in any login info right away. The first time I see it is during the startup when it says Finding Module Dependencies, and then again when it starts up CUPS When I get the message at first, my Zip drive (USB 250) acts like it's being accessed. Nothing happens before I get it the second time (or third). This is really bothering me. It doesn't seem to be affecting anything esle other than it's annoying. If someone has a clue where to start, I would be greatly appreciative. Info on my system: Biostar M7VIB Mobo Amd Athlon 1000 Socket A 512 MB PC 2700 DDR RAM NVidia GeForce 4 MX 440 80 GB Western Digital (Partitioned for Windows and share drives) 40 GB IBM Deskstar (Only for Linux) Pioneer DVD ROM GoldStar 24x10x40x CD-RW SoundBlaster Live! X-Gamer (The original one from line 5 years ago) Lite-On 10/100 NIC 250 MB USB Zip Quote Link to comment Share on other sites More sharing options...
beesea Posted May 13, 2003 Report Share Posted May 13, 2003 i have the same problem, but i only see it once. i know you get that error if there's no disk in the zip drive. its annoying, but it doesn't seem to be anything to worry about. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted May 13, 2003 Author Report Share Posted May 13, 2003 That's what I thought too, but I seem to remember getting it when there was a disk in the zip drive as well. Oh well; if it doesn't mess anything up, I'll be happy with it. Quote Link to comment Share on other sites More sharing options...
bvc Posted May 13, 2003 Report Share Posted May 13, 2003 urpmf ldm gives kernel-source:/usr/src/linux-2.4.21-0.13mdk/Documentation/ldm.txt vi /usr/src/linux-2.4.21-0.13mdk/Documentation/ldm.txt Overview-------- Windows 2000 and XP use a new partitioning scheme. It is a complete replacement for the MSDOS style partitions. It stores its information in a 1MiB journalled database at the end of the physical disk. The size of partitions is limited only by disk space. The maximum number of partitions is nearly 2000. Any partitions created under the LDM are called "Dynamic Disks". There are no longer any primary or extended partitions. Normal MSDOS style partitions are now known as Basic Disks. If you wish to use Spanned, Striped, Mirrored or RAID 5 Volumes, you must use Dynamic Disks. The journalling allows Windows to make changes to these partitions and filesystems without the need to reboot. Once the LDM driver has divided up the disk, you can use the MD driver to assemble any multi-partition volumes, e.g. Stripes, RAID5. To prevent legacy applications from repartitioning the disk, the LDM creates a dummy MSDOS partition containing one disk-sized partition. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted May 13, 2003 Author Report Share Posted May 13, 2003 Ok....but I'm not using RAID, does that make a difference? Still doesn't explain what the error means, though. Quote Link to comment Share on other sites More sharing options...
bvc Posted May 13, 2003 Report Share Posted May 13, 2003 Were you or are you using XP or Win2k? I don't use them but if I understand it correctly, it's another case of M$ doing something you know nothing about, without asking, don't need, and screwing you up in the process :wink: If you don't need it....I'd say don't worry about it. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted May 13, 2003 Author Report Share Posted May 13, 2003 Dual boot with WinXP Pro...that's the cause of this? Strange. Oh well, not bothering anything else, so I'll let it be. Quote Link to comment Share on other sites More sharing options...
Ixthusdan Posted May 13, 2003 Report Share Posted May 13, 2003 I discovered, painfully, that winxpluck places data at the end of the partition. It prevented me recently from installing linux!!! :shock: So I had to install linux first, in order to partition the drive, remove lilo, install wnnie x pooh, reinstall lilo, and finally have a happy system. But I am not getting the error that you describe. Quote Link to comment Share on other sites More sharing options...
beesea Posted May 13, 2003 Report Share Posted May 13, 2003 i don't think this is a windows-related problem. when i upgraded to 9.1 (as opposed to a clean install) i started getting this error message only when i started using 9.1's kernel. if go back to using the old 2.4.19 kernel from 9.0 then i don't get that message anymore. Quote Link to comment Share on other sites More sharing options...
bvc Posted May 13, 2003 Report Share Posted May 13, 2003 Just guessing.......the old kernels probably either didn't have ldm support (they have for a while), or the option wasn't compiled into the kernel for it to be available. Quote Link to comment Share on other sites More sharing options...
Ixthusdan Posted May 13, 2003 Report Share Posted May 13, 2003 Just to clarify, I am using 9.1 straight off the net. And, since I lost my /home partition that I had preserved since the beginning of time, or there abouts, I do not have any special changes installed. The Mandrake partition tool could not shrink the windlessxp partition, and I saw what bvc has found; data at the end of the partition, which could not be moved. I don't have a clue as to what is causing your error, I just know that it doesn't happen on my system. I do not have any zip devices. I have via vt400, nvidia video, maxtor drives, cdrom and cdrw, and soundblaster live. Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted May 13, 2003 Report Share Posted May 13, 2003 I think its more likely to be a partition table error. Window's use to corrupt my table anytime I had linux on it. If diskdrake sees something that it doesn't understand or doesn't pass verification then it often refuses to do anything (good move!) Usually the best fix is to remove all your partitions, zero out your partition table, and re-create them from scratch. Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted May 13, 2003 Author Report Share Posted May 13, 2003 I think it might have something to do with the fact that I have unpartitioned space on my master drive (the 80 GB one). I recently (like a day before I installed 9.1, maybe even same day) deleted a 10 gig partition and haven't recreated it, or put anything new in its place. I wanted to wait and see what I actually needed before I allocated the space in Windows and realized I wanted it in Linux, or vice versa. I don't reboot all that often, and it seems to only appear at boot; so I think I'll let it be for now. Quote Link to comment Share on other sites More sharing options...
scoopy Posted May 14, 2003 Report Share Posted May 14, 2003 ldm_validate_partition_table ( ): Disk Read Failed is stemming from systems with either a zip drive or flash card readers (probally USB connected). As for a solution, I haven't found one... yet. A workaround is to leave a disk inside the drive on shutdown and rebooting. I had another error message showing up ( insmod: sd_mod already exists) that I cleared up by unplugging my USB card reader, then booting without. Shutting down and boot with it plugged back in and a card inside. As long as I keep a card in ( I knew I kept that bad card for a reason ) this message does not appear. The moment I boot without it, this message reappears. I was gonna try and rework its line in fstab to find a fix, but haven't gotten to it yet. Plus I really don't think that's gonna fix it. Its gotta be in the kernel ( 2.4.21-0.13mdk to be exact ) and I am not into messing with that. Quote Link to comment Share on other sites More sharing options...
zenrox Posted May 18, 2003 Report Share Posted May 18, 2003 i had to recompile the kernel and enable probe all scsi luns to get ride of that error and my 6-in 1 meadia card reader stared working Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.