All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark van Walraven <markv@wave.co.nz>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Total loss with 2.4.0 (release)
Date: Sat, 27 Jan 2001 14:24:32 +1300	[thread overview]
Message-ID: <20010127142432.B29823@mail.wave.co.nz> (raw)
In-Reply-To: <Pine.LNX.4.32.0101261611300.791-100000@asdf.capslock.lan> <000d01c087ed$82ffb950$0201010a@runestig.com>
In-Reply-To: <000d01c087ed$82ffb950$0201010a@runestig.com>; from Peter 'Luna' Runestig on Sat, Jan 27, 2001 at 12:12:53AM +0100

On Sat, Jan 27, 2001 at 12:12:53AM +0100, Peter 'Luna' Runestig wrote:
> In what situation would NT4 default to "fry the whole disk"? I've mixed
> Linux/DOS/Win98/NT4/Win2000 several ways on various hardware (>8 GB disks),
> with no problems at all actually.

I've had Windows suddenly using the 'begin' and 'end' (CHS) fields in
the partition table entry for a FAT32 partition when it should have been
using 'start' and 'length' (LBA) fields.  The result was that everything
on the FAT32 partition disappeared (according to Windows) and a couple
of block groups in an ext2 partition were clobbered.

Another time, I found what looked like bits of the page file in the
middle of a wrong partition when swapping onto the second disk.

Two associates have had ext2 partitions partially overwritten by
re-installing Win98.

>                                   Maybe "one single person having a problem
> does not mean in any way that this is the way it occurs for 100% of the
> userbase" ?

All the problems in the thread smell like geometry problems to me.  I
never experienced one myself until I got an evil combination of disk,
BIOS and filesystem.  Then, ZAP!

Regards,

Mark.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-27  1:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 21:50 Total loss with 2.4.0 (release) Trever Adams
2001-01-23  5:33 ` Mike A. Harris
2001-01-23  7:01   ` Alan Olsen
2001-01-23 10:03   ` Trever L. Adams
2001-01-23 10:32     ` Patrizio Bruno
2001-01-23 14:57       ` Trever L. Adams
2001-01-23 15:25         ` Richard B. Johnson
2001-01-23 11:27           ` Mark I Manning IV
2001-01-23 10:53             ` Ben Ford
2001-01-23 17:42         ` Mike A. Harris
2001-01-23 18:28     ` Mike A. Harris
2001-01-25 13:43       ` Kjartan Maraas
2001-01-26 21:40         ` Mike A. Harris
2001-01-26 23:12           ` Peter 'Luna' Runestig
2001-01-27  1:24             ` Mark van Walraven [this message]
2001-01-23 10:22   ` Heikki Lindholm
2001-01-23 12:43   ` Ragnar Hojland Espinosa
2001-01-23 18:13     ` Total loss with 2.4.0 (release) (win98 not honoring partitioning) Jason Venner
2001-01-23 18:36       ` J Sloan
2001-01-23 20:17     ` Total loss with 2.4.0 (release) Mike A. Harris
  -- strict thread matches above, loose matches on Subject: below --
2001-01-15 13:40 Heikki Lindholm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010127142432.B29823@mail.wave.co.nz \
    --to=markv@wave.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.