This is fascinating. It reminds me of Star Trek calm conversation in
control center during laser shooting on enemy spaceship. :)
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=1521738, sector=1501515
end_reque
Hi all,
after some hours playing with RAID-1 recovery I wrote a tiny HOWTO-proposal,
suitable mainly for newbies (I hope!).
Please, comment it, send me all the corrections and flames, so it eventually
can help constitute a needed section in the "real" HOWTO.
The URL:
http://www.chance.cz/~egon
On Fri, 23 Jul 1999, Brian Murphy wrote:
> "Stanley, Jeremy" wrote:
>
> > I think the question was whether there was a way to successfully mirror
> > the MBR and boot kernel onto a second drive for redundancy...
> > > From: Brian Murphy[SMTP:[EMAIL PROTECTED]]
> > > Sent: Friday,
> I think _both_ lines are necessary to release the inode.
> ...
> + clear_inode(rdev->inode);
It works for me! However, I think there's another bug hiding. When I erase
the contents of one partition (to learn at last how to recover from a RAID1
failure :) ), 'active inodes' show up again
"Stanley, Jeremy" wrote:
> I think the question was whether there was a way to successfully mirror
> the MBR and boot kernel onto a second drive for redundancy...
> --
> Jeremy Stanley Trend CMHS
> Network Engineer http://www.trendcmhs.org
>
> The opinions expressed he
On Fri, Jul 23, 1999 at 08:33:31AM -0400, Brian Geisel wrote:
> >From: Robert Purdy <[EMAIL PROTECTED]>
>
> >Does anyone know how far ext3 is off? Also I heard SGI had released thier
> >code for journaling? Is this to be adopted into ext3?
>
>
> Well there was a discussion about this on linux-k
I think the question was whether there was a way to successfully mirror
the MBR and boot kernel onto a second drive for redundancy...
--
Jeremy Stanley Trend CMHS
Network Engineer http://www.trendcmhs.org
The opinions expressed herein do not necessarily
represent those
>From: Robert Purdy <[EMAIL PROTECTED]>
>Does anyone know how far ext3 is off? Also I heard SGI had released thier
>code for journaling? Is this to be adopted into ext3?
Well there was a discussion about this on linux-kernel about a month ago.
AFAICT, there's work being done by Stephen Tweedie
There is no need for all this complication. At the start of the first disk create a
small
partition /boot
which contains the kernel and lilo files (chain loader etc) i.e what is normally in
/boot.
Create a
small linux installation (which can also be used as a rescue from a non bootable raid).
Cr
You're right. LILO doesn't like to install itself to a root raid1 partition
(LILO: "Sorry, don't know how to handle device 0x0900"). On the other hand,
the kernel image MUST be loaded from ONE of the mirrored devices. My way to
solve this chicken-and-egg problem is described as followed:
- cre
10 matches
Mail list logo
