mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trever Adams <vichu@digitalme.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Total loss with 2.4.0 (release)
Date: Mon, 15 Jan 2001 21:50:29 GMT	[thread overview]
Message-ID: <20010115215047Z131660-403+523@vger.kernel.org> (raw)

I had a similar experience.  All I can say is windows 98 
and ME seem to have it out for Linux drives running late 
2.3.x and 2.4.0 test and release.  I had windows completely 
fry my Linux drive and I lost everything.  I had some old 
backups and was able to restore at least the majority of 
older stuff.

Sorry and good luck.

> Hi all,
> 
> I managed to kill my dear files and if anyone can help 
I'd be very
> thankful. The events leading to this were something like:
> Happy system with 2.4.0-test9 -> update to 2.4.0 
(release) -> works
> nicely; no complaints of any kind (no crc errors or dma-
disabling) ->
> reboot -> play Diablo II for some time (win98) -> restart 
linux ->
> VFS: cannot mount root. 
> I have two ext2 partitions plus root and one of them is 
on another disk
> (same ide lead, however) and it survived with no errors.
> 
> When I ran e2fsck (1.18) on root partition, in addition 
to having to
> run it many times before succeeding (segfaulted 
sometimes), nothing was
> left in the partition except lost+found with lots of
> files. Valid superblock wasn't found at 0, but at 8193.
> 
> I really don't get what would have caused this or how to 
cure it. I still
> have my /home in need of repairing, but I won't be 
running fsck on it with
> this good expectancy-of-recovery (I actually tried once 
with a backup on
> another disk and it resulted two VERY old directoried, 
everything else was
> lost...and found(?)).
> 
> I also updated my machine from VIA MVP3 based K6II to VIA 
KT133 (with 868B
> southbridge - ATA100, that is) based Duron, but linux 
(2.4.0-test9) worked
> fine with both configurations. I think this might be some 
sort of DMA
> problem.  
> 
> I read from kernel notes that ac1 fixes root umount 
handling. Might that
> be connected with the symptoms I had? If anyone has any 
suggestions,
> please post them. I would, at least, like to know how 
could I verify if
> the filesystem is really messed (for example, overwritten 
with something
> at the bus at the time) or if it's just some minor issue 
that confuses
> fsck totally.
> 
> -- Heikki Lindholm
> 
> -
> 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/
> 


-
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-15 21:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 21:50 Trever Adams [this message]
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
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=20010115215047Z131660-403+523@vger.kernel.org \
    --to=vichu@digitalme.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®