From mint-bounce@lists.fishpool.fi Sat Jan 8 23:58:25 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] Weird Disk problem From: Petr Stehlik To: MiNT Mailing List In-Reply-To: <41E031EF.2020803@gabo.pl> References: <41E031EF.2020803@gabo.pl> Content-Type: text/plain; charset=ISO-8859-2 Date: Sat, 08 Jan 2005 23:57:07 +0100 Message-Id: <1105225027.3897.35.camel@joy.home> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ms1.avonet.cz id j08MvFtQ024211 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: joy@sophics.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=3.8 tests=BAYES_00 X-Spam-Level: Adam K=B3obukowski p=ED=B9e v So 08. 01. 2005 v 20:18 +0100: > From time to time few first sectors of my HDD get zeroed, for no known= =20 > reason. >=20 > Fortunetly I do not keep valuable information on my C partition, and I=20 > do backups of it often, so recovery is just a matter of minutes. >=20 > If anybody does have any reasonable explanation of this, please rise=20 > your hand and step forward. Nothing reasonable, just some thoughts. I have often heard in Atari realm that it's good to partition disk to contain a small C: with just boot stuff and then D: (and possibly more partitions) for valuable data since sometimes the C: partition is lost. Don't remember the reason but I do remember this used to be suggested... Also, I do remember that TOS 4.01 had a bug in its GEMDOS and when a partition was almost full (or was it just the FAT table full?) it simply started writing from the beginning. A GEMDOS bug would not rewrite boot record and partition table, though. I think I heard about a similar but slightly less dangerous bug in TOS 4.04, I might even have a test program that proves the GEMDOS problem somewhere. So maybe that the problem in 4.01 was not a GEMDOS bug but something deeper, more dangerous. At last, your disk driver might be doing some nasty things. Which one do you use? Petr