I've seen this problem on a number of websites and mailing lists and even experienced it myself. Here's my story: I had initially installed LM 8.0 on a PII 350, Asus mobo, Maxtor 8 gig HD, 128 meg ram, 3Com NIC, and generic SVGA about a month ago, no problems. One caveat regarding the install was it was on the second HD in the system at the time (Windows 98 was on the first HD) so I had to install the lilo bootloader to /dev/hdb1 on install then use Powerquest BootMagic from Windows to set up a bootloader for the first HD that would optionally load linux. I recently bought a new server Azza PVMD mobo and AMD K6 II 500mhz CPU and planned to move the lone maxtor drive containing LM 8.0 over to it (along with the same VGA and 3Com NI adapters) but faced a dilemma. LILO was on first partition superblock, not the hard drive bootblock. Not knowing how to fix that manually at the time, I figured: just reinstall LM 8.0 over top of the existing filesystems, making sure NOT to reformat the partitions. The original partitions were all ReiserFS, I'm wondering if that was a problem for this technique to work. Not sure, however the first error I got was 'ldconfig failed' shortly after it copied all the packages over to /usr followed by an "hdlists not found" error then a kernel panic. The second try produced the ldconfig failed msg just after I selected all my packages, not installing anything. I couldn't reformat the whole drive since I had valuable data on there I needed to retrieve. I had a suspicion that it might be the ReiserFS, or wacked out partition table, but the 'ldconfig failed' message was a too vague to be sure. Solution: I managed to mount the drive on another machine, copy the files I needed off, then put the drive back in the K6 II 500. I completely removed all partitions, rewrote the Partition table, then created new partitions (expert mode) After that, the install worked like a charm. No problems. In the end, I'm still not 100% what the problem was, but I'd have to say 'ldconfig failure' and 'hdlists not found' errors at that point in the install (after package install or selection) seem to relate directly to the condition of the destination harddrive and / or partitions. If you're trying to install overtop of an existing linux install (esp. with filesystems other than Ext2) you may encounter this problem. If your harddrive is blank (no partitions) and you still get this error, you might have a bad or incompatible Hard Drive or controller (rare, but happens) If you have an error loading the secondary stage, this could also have to do with insufficient memory or bad memory in your system (also happens occasionally =( ) Incidentally, I could NOT get the 'Upgrade' feature to work in the LM Install at all - couldn't find my root partition for some reason - this may also have to do with the ReiserFS that the original install had used for all partitions (sans swap part.) The HD partitioning/package installation/bootloader installation portion of the install needs a lot of work, IMO. It would be nice to be able to jump right to the bootloader config section and simply config lilo/grub right from the CD-ROM as opposed to requiring a floppy drive and bootdisk (something I don't have in this case - I hate everything about floppies; very unreliable) There is no reason why there shouldn't be a fairly easy-to-use recovery tool on the CD-ROM to assist in reconfiguring your bootloader, boot method and partition tables without having to reinstall everytime. Hope this helps some of you. Jt __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
