On Mon, 15 Apr 2002 09:21:05 +0400
Oleg Drokin <[EMAIL PROTECTED]> wrote:
> Hello!
>
> On Mon, Apr 15, 2002 at 12:26:51AM +0200, Thomas Wiedemann wrote:
>
> > i cannot mount my reiserfs partition any more, because of that:
> > super-459: read_super_block: super found at block 16 is within its own log. It
>must not be of this format type.
>
> What kernel version do you have?
> Relocated/nonstandard journal support is only available in 2.5 kernel series
> for now.
2.4.18-rc4
ok, then i'll try it with the development kernel later.
>
> > so, here's the story how i "created" this error and some details:
> > due a hardware failure (the harddisk?), i got some weird error messages:
> > Apr 13 17:32:13 hq kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete
>Error }
> > Apr 13 17:32:13 hq kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > (...)
> There are bad hardware for sure. BAd hardware is dealt with on a special basis
> described in http://namesys.com/support.html, as Hans outlined already.
of course it was a hardware failure that created the whole mess, but that is not my
problem...i just missed a warning or something that reiserfsck --no-journal-available
deletes the journal and doesn't create a new one, if the kernel it is used on does not
support external journals. it failed with just using --rebuild-sb, so i tried it that
way. and there is no way to tell fsck that the journal should just be ignored, right?
thnx, thomas
--
"Windows is the most documented operating system that has ever been."
--Bill Gates
