My Debian System is toast

Okay, so I had a PIII system that was running Debian etch and everything was good. All it was doing was running Apache2, PHP5, and Postgres. It had been running fine for months. However, it was a PIII and I happened to come across a P4 2Ghz IBM that had failed with a bad hard drive. So I don't have another hard drive other than the one in my system, so I decide that I can migrate my server quite simply by moving the PIII's hard disk to the newer machine. I read a little online and everyone seems to think that there's no issues in relation to do this for Linux systems (not windows apparently).

So I do it. At first there's no network, but that's pretty easy, I just had to detect what interface the new network card was under and change the network/interfaces. I even find the udev and comment out the original hardware and make my interface card go back to eth0.

Now I'm really having problems, every few days I can no longer write to the database with new information through my PHP5 scripts. I do some searching and realize I should disable ssl for postgres because it has a key generated off my old hardware (and I don't use it). When I try to "reboot" or "poweroff" it sends out the message it is shutting down, but it doesn't. Everything slows down and "top" no longer able to work.

I have no idea what to do, I dpkg -reconfigure initscripts and I still can't even reboot! I don't know what I should do aside from a clean install, which seems kind of extreme, I don't want to have to reconfigure everything (especially postgres).

[edit]
Sorry, to add -> Over and SSH session, I run top and it does nothing, no errors or anything. I can stop the job and do something else, but top will not load.

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: My Debian System is toast

It sounds like there could be any number of problems, including a failing HD. But first, put butter and honey on it while the toast is still warm.

If booting is erratic, or reading from the HD takes long, there is usually another problem. It could be faulty electronics or just a bad or poorly seated ribbon connector. Another thing to do is run 'memcheck' on it to see that all the memory is fine.

The problem with shutting down can be due to the choice of ACPI or APM; you need to check the BIOS settings and the kernel boot messages to see if you're using ACPI or APM.

For SSL, a key generated on one machine should work fine on another. There is just one problem with Debian SSL since 2006 - some silly person removed a very important line of code so that he would get no warnings from testing tools. The result is, if your kernel does not have a /dev/urandom device, the keys generated are useless because they can be predicted. Debian has fixed the problem in the past few days, but you need to download the latest SSL fixes and replace the old keys.

If your system no longer boots, it is convenient to have a live CD to boot from and check things; I'm pretty sure most CDs were bootable by the Pentium4 era.

Re: My Debian System is toast

I believe I am running ACPI, is there a way to just reconfigure something like this? I never selected between those when I installed previously, so if Debian could just reconfigure the package again perhaps this might fix it? I'm not running anything custom at all, so I figure perhaps it's hardware, as you suggest, or perhaps something to reconfigure (hopefully as in dpkg -reconfigure!)

There appears to be no problem booting, neither anything seemingly pertinent in the logs.

I will check the hardware unless someone has any other suggestions.

PS There appears to be no such thing as memcheck, what package is it included with?

Re: My Debian System is toast

Oops ... that's "memtest", but specifically "memtest86+"
It is actually a stand-alone program; the installer should set up your bootloader so that you can boot it and run tests; when you're tired of all the testing you just tell memtest to reboot again.

For the ACPI/APM thing, try booting linux with the following parameters:
acpi noapm

The only other thing I can think of that would cause a machine to slow down would be use of swap space, but in that case you should have had the same problem on the P3.

Syndicate content