Message-ID: <001401c241bc$e6eaf490$0200010a@jennifer>
Reply-To: "Dhr N. Van Alphen" <mastex@servicez.org>
From: "Dhr N. Van Alphen" <mastex@servicez.org>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: <linux-kernel@vger.kernel.org>
References: <20020811175252.GB755@gallifrey>
Subject: Re: 2.4.19 eat my disc (contents)
Date: Mon, 12 Aug 2002 06:58:26 +0200
Organization: Genetics BV
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3034
Lines: 76

go install again and boot after each little step wich might been the
problem,
then u should know what caused it, and post the real bug here.
There are too many possibilities now.

Niek van alphen.
MasteX@servicez.org


----- Original Message -----
From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: <linux-kernel@vger.kernel.org>
Cc: <axp-list@redhat.com>; <debian-alpha@lists.debian.org>
Sent: Sunday, August 11, 2002 7:52 PM
Subject: 2.4.19 eat my disc (contents)


> Hi,
>   I've just lost the contents of my disc on my Alpha to 2.4.19 - be
> careful! (luckily there wasn't anything important on it...or at least if
> there was I can't remember what....)
>
> Some details:
> 2.4.19 straight
> Alpha 21164A on LX164 board
> Compiled for LX164 architecture
> Hard drive is an IBM 34GB Deathstar connected to the on board CMD646
> controller.
>
> It has been running Linux/Debian happily for ages; booted into 2.4.17,
> compiled 2.4.19, booted into that and saw two problems;
>   1) RTL8139 network card was identified but would not connect.  I got
> giant packet errors - it spitted out a 32 bit identifier which looked
> like it might have got some ASCII where some value should have lived.
> (It is an RTL8139 prior to the -c)
>
> 2) I tried to go into the directory which I'd built the kernel in and
> found it didn't actually agree that it was a directory; but thought it
> was a file of many GB with odd permissions.  I unmounted the partition
> and fsck'd - lots of errors; most complaining of invalid blocks.
> debugfs seemed to indicate that lots of things in the inode had been
> cleared to -1 (size, uid, gid, pretty much everything).
>
> 3) I hit reset and the AlphaBIOS came to the conclusion there was no
> OS and it looks like the partition table has gone to the great block
> in the sky.
>
> All tools were from Debian/unstable; updated immediatly prior to the
> kernel build.
>
> I'd give you a log and .config if it weren't for the fact that it has
> just wiped itself from the disc. hdparm looked OK from the brief look;
> I think it got the drive size right.  I had seen some DMA negotiation
> alike errors go past during the boot.
>
> Oh well - time to try the Debian/Woody install process on Alpha....
>
> Dave
>
>  ---------------- Have a happy GNU millennium! ----------------------
> / Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \
> \ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
>  \ _________________________|_____ http://www.treblig.org   |_______/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 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
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/