I solved the problems, it was a bad DIMM. I got it out now and: - memtest86 is succesfull - disk diagnostics are succesfull - touch /forcefsck reports no more problems - tarring and gzipping works perfectly for all situations Only problem now is that I have half my RAM ;) Thanks for the help, guys. Jeroen On Saturday 01 May 2004 07:54, J.L. Coenders wrote: > Although fsck indicates a lot of problems, I think it is not the disk which > is malfunctioning. I have run the Maxtor diagnostics over it and that gave > 'a certified functioning device', so no bad sectors or anything. > > But I ran memtest86 afterwards and discovered that two addresses are > broken, so that might be the problem. I am going to get it out today and > see if everything will work then. > > Jeroen > > On Friday 30 April 2004 22:00, Alexander Dalloz wrote: > > Am Fr, den 30.04.2004 schrieb J.L. Coenders um 21:24: > > > How can I manually start fsck? Usually it only starts when power > > > fails... when I try to start manually, it warns me about the device > > > which is mounting. When I try to unmount, it wont work, probably > > > because it is the main disk. > > > > > > Jeroen > > > > touch /forcefsck > > > > and then reboot > > > > Alexander
