I installed Antix 13.2. Since I had quite a few things set up the way I wanted, I thought it would be good to take a snapshot.

Computer -Athlon64 in sig is 7 years old and run 24/7
Root and home were each ~16GB partitions with plenty of free space.
The computer crashed while making the snapshot. (This computer has been doing that when stressed.)

Boot was normal. At the login screen entered username and password which appear to be accepted. I am taken to the login screen again.
Unless there is a simple fix, I will just reinstall and call it a learning experience.

Thanks

Someone with knowledge about this sort of thing will probably be along shortly to help you trouble shoot. What I would likely do is boot a LiveCD, and back-up all my important files and config files, then re-install. For me, that's the quick and easy fix.

But before doing that, I think you need to open that box up and clean the dust bunnies out of your fans and heatsinks, and maybe apply some fresh thermal paste to the CPU heatsink, so it will stop crashing when stressed.

Thanks Neil. I have blown out the dust and given it new life more than once. I will look into the thermal paste, I have never done anything like that before.

I would simply reinstall AntiX 13.2.

When a system crashes, it can be caused by several things;bad memory, bad cpu, bad hard drive, defective motherboard, bad componant plugged in, user error, bad psu.

Use memtest+ to test memory, and let it run about 6 hours. If it passes, the memory is okay. I've bought new memory that was bad and failed,

Run mprime if you want to stress the cpu.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/Stress_Test"
linktext was:"https://wiki.archlinux.org/index.php/Stress_Test"
====================================


Most hd already get checked out during boot-up and use S.M.A.R.T. But if you need to recheck for bad blocks, you will have to unmount the drive to check it, since any changes will effect your system.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://linuxpoison.blogspot.com/2008/01/howto-check-disk-drive-for-errors-and.html"
linktext was:"http://linuxpoison.blogspot.com/2008/01 ... s-and.html"
====================================
AND
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.tldp.org/LDP/GNU-Linux-Tools-Summary/html/x11569.htm"
linktext was:"http://www.tldp.org/LDP/GNU-Linux-Tools ... x11569.htm"
====================================


A defective motherboard or componant are harder to figure out. Any plug-in card can be removed and then you attempt to reproduce the problem. A bad or flakey video card requires you to use the motherboard video or be replaced. I had a video card that overheated ONLY when trying to take a snapshot. SOLUTION: Clean it out once a month. You would be surprised how much dust and cat hair those things collect, even with filters on every air intake.

Check the motherboard with a magnifying glass for leaking or swollen capacitors. They will looked bulged. If you are really good at soldering, you can replace them. If not, it's time for NewEgg.com.

I would say what happened is that you stressed the cpu (heat) and it crashed the system while writing to the hard drive. Hence the loging running over and over.

Replacing therma paste.

@ jdmeaux1952 Thanks for all the information. I just blew out the dust and did not see anything obvious. i will reinstall for now and do further testing.

snapshot needs quite a lot of CPU power.