Hi!

I have a strange issue with and old computer.

During the installation, at 76% the PC suddenly power off. I have tested several times and the computer shutdown at the same point, 76%

Looks like a hardware issue, but is weird, the error always come at the same point and doing other operations with the live CD not cause the power off.

There is any log from the installation process?
Any one knows what happens at 76% that should cause a hardware failure?

Do you have enough space?

Check your bios, make sure that PnP (plug and play) OS is turned off. or make sure the answer is no.
You can use some diagnostic software to check the system.
Here is a link to a tool that I use. It's great for testing and preformating a computer for OS installations.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ultimatebootcd.com/"
linktext was:"http://www.ultimatebootcd.com/"
====================================

I have enough space on sda1 (4 GB)
I have check BIOS and there is no PnP OS option

Console installation also fails.

cli-installer has some command like option for debug?

You may have an Write-Protect Boot Sector. Check the bios, and disable virus protection options in the bios it cannot distinguish between legitimate programs and viruses.
Can you post the make, and model of the computer. So I'm not just guessing what the problem may be.

The shutdown is during the copy.
SDA1 is writeable and antix instalation copy some files (1.4GB) but the installation not finish correctly.
Looks like something done during the installation, after copy the files cause the problem.

The computer is a socket A + Semprom 1800+ SIS 741GX motherboard + 1GB DRR 400 + HDD IDE 80GB, comes from a old computer that was working fine 3 weeks ago with Windows XP, also works fine with the Live CD without install.

Maybe the harddrive has badblocks.

The full version of antiX copies about 2.7GB of files and base about 1.4GB.

You could try the cli-installer

anticapitalista wrote:Maybe the harddrive has badblocks.

The full version of antiX copies about 2.7GB of files and base about 1.4GB.

You could try the cli-installer

Yes, the hard drive has 3 bad blocks. Ext4 not handle it?

cli-installer also fails

EDIT. Badblocks report 0 bad blocks found at /dev/sda1... maybe they are on other partition (not used)

CGarces wrote:The shutdown is during the copy.
SDA1 is writeable and antix instalation copy some files (1.4GB) but the installation not finish correctly.
Looks like something done during the installation, after copy the files cause the problem.

The computer is a socket A + Semprom 1800+ SIS 741GX motherboard + 1GB DRR 400 + HDD IDE 80GB, comes from a old computer that was working fine 3 weeks ago with Windows XP, also works fine with the Live CD without install.

Are you installing the 64 bit version of antix? ( the 32bit version will run on the live disk. the install will fail.)
Do you still have XP on the system?
If you dedicated the computer to antiX no need for the next questions..
How did you format the partition for antix?
What format did you use?

Try the Ultimate Boot Disk to diagnose any hardware problems. Could be a power supply problem after the disk has been running for an extended period of time.

I'm using the 32 bits version, I don't understand why you said that the install will fail.
This system is just for testing HDD is empty, 80 GB with 4 GB on Ext4 and 1 GB for swap.
The motherboard + CPU was working during 8 years without error, the power supply is new.

The HDD comes from my desktop computer. It fails on the past (3 bad sector) and was replaced by a SATA and used as second disk without know problems.

BTW I have reproduced the issue with Ultimate Boot Disk (shutdown while try to identify the HDD).
Maybe some specific area (boot?) is damaged and the rest of the disk (more or less) works

=" I have reproduced the issue with Ultimate Boot Disk (shutdown while try to identify the HDD).
Maybe some specific area (boot?) is damaged and the rest of the disk (more or less) works

Looks like a bad hard drive.

You should partition and format the hard drive yourself from within the Live system. You can use gparted to do the partitioning but wait and create the filesystem yourself from the command line with:where $DEVICE will be something like"/dev/sda1".

The two -c arguments (yes, there are two) will force it to check for bad blocks the slow (presumably better/safer) way. During the install choose to use the existing partition. I think this is the best we can do to deal with bad blocks.

I suspect the hard drive is on its way out. If your drive supports smartmon tools you can use them to check it health:Some of the output is rather cryptic.

@Eino: is it really true the 32-bit version won't install? This seems like a rather significant bug.

zeroing (writing zeros to all areas) the drive may help"refinish" the drive. I had a couple of bad drives that were not really bad, just overused and very"dirty". formatting a drive does not really remove all the data, so you can end up with very confused sectors when reading (may show as bad). IIRC the command is dd if =/dev/zero of=/dev/sd? and it takes quite a while.

That S.M.A.R.T. stuff isn't switched on in the BIOS, is it, shutting down the system when you reach the bad blocks?

I'd go with what dave says, zero out the drive completely, including the boot sector.
( dd if=/dev/zero of=/dev/sd? ) + ( dd if=/dev/zero of=/dev/sd? bs=512 count=1 )(boot sector only)