From owner-mint@fishpool.com Tue May 6 23:58:31 2003 Subject: Re: [MiNT] Harddisk crash (again) From: Petr Stehlik To: mint@lists.fishpool.fi In-Reply-To: <20030506210142.A04F41884C@core.preferuje.luzik.pl> References: <20030506210142.A04F41884C@core.preferuje.luzik.pl> Content-Type: text/plain Organization: Message-Id: <1052257748.2282.2.camel@joy.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 06 May 2003 23:49:08 +0200 Content-Transfer-Encoding: 7bit Delivered-To: mint@lists.fishpool.fi 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: On St, 2003-05-07 at 01:06, Adam Klobukowski wrote: > The symptoms are the same as previously (it is the third time it > happened like this), it seems that track 0 on HDD was erased. (That > involves: boot record, partition table and begining of FAT of C:). TOS 4.0x (x < 4) used to do that, IIRC. It may have something to do with a nearly full partition. The sector counter overflows, simply said, and so TOS starts writing data from sector 0. But this would not remove boot record. What harddisk driver do you use? An old version of AHDI? Completely different possibility is a HW fault. An error on the bus, for example. Flipped bit of the word that addresses the track and you're done. Petr