| dorcsssc |
05-21-2017 05:53 PM |
Just ran into the exact same symptoms when transplanting a drive between two systems w/ removable trays/rails.
The new system it was going into was identical make & model motherboard, same # CPUs, same amount of memory, but had to had to have its CMOS battery replaced. So, combining your observations with mine, it sure looks you have a battery hold-up issue. In my case, I had done a warm re-boot of the system since installing the battery, but had never re-run LILO since. So after 2 weeks, when returning to the 2nd location and doing a cold boot, LILO hung with the same message as yours.
I suspect LILO stores the ldconfig check-sums in a spot in the CMOS battery-backed RAM, so this new machine doesn't yet have a valid checksum for it. In your case, looks like the battery is marginal altogether. If you search around the net, you'll see that all other similar posts on this topic urge re-running LILO anyway. A new battery plus LILO should do the trick.
|
