error validating amigaos 4.1?

Hi all out of shear boredum i decided to reformat my sam440 and put a fresh install of AOS 4.1 (update 1)
but im getting an error which says "error validating amigaos 4.1" any one got any ideas?

TIA Ray

12 views and no reply?

@carvedeye

Is "amigaos 4.1" the volume name of your boot partition? If so, try booting from your CD and wait until it finishes validating the hard disk partition.

You probably have something which tries to write to your boot partition during startup, and if a partition is written to before it is done validating, the validation can fail.

Best regards,

Niels

@carvedeye

If its an FFS2 partition, you'll need to let it validate before trying to access it. Boot with no startup-sequence and just let the machine idle while the drive validates. Once the drive light goes out, you can execute the startup-sequence manually from the shell.

If its an SFS partition, there is a deeper problem, which normally requires a quick-format to cure.

Simon

I have placed another hard drive in the sam440 and have successfuly installed AOS 4.1 :)

Thanks for the help it was very much appreciated

Cheers Ray

@carvedeye

I'm glad you got it sorted out.

Simon

My HD light is flashing like crazy today, with the amount of reboots I have to do during coding and DSIs, both partitions are SFS2. How long should it take to validate a 1TB drive? Its been going about 4 hours solid now. I assume its validating anyway the light is constantly on, Workbench seems fine, Odyssey running fine, however Codebench is very sluggishly.

SFS2 doesn't need valdiation as far as I remember, only FFS(2) partitions need valdidation after a crash.

You've got another problem there

K thanks. Nvm I've got to the bottom of it (sort of). nmbd which is part of the Samba distribution kept firing up a process continually trying to connect to something. I just went into Internet->Servers and made the netbios-ns Inactive.
Seen it before, can't remind the proper solution.

Quote:

The directory it tries to write its log file to does not exist.