I'm not sure how to fix it, but I'm suspicious that some portion of the data
which LILO should have written to both mirrors is only being written to the
"first" drive in the mirror; which in your case is your second physical
drive. Note that LILO says its working on /dev/sdb1 first, then /dev/sda
Hi,
I've been trying to get Lilo to work with Linux software RAID-1. I'm
using the patches from Richard Bollinger's post from 5/4/2000, and
things almost work. I can use lilo to update the boot sector and
maps, but lilo will not boot unless I enter a valid kernel label at
the boot time lilo pro
I just solved my problem. This is what I posted to the RH-list
On Mon, 8 May 2000, Michael Ghens wrote:
>
> Date: Mon, 8 May 2000 12:25:56 -0700 (PDT)
> From: Michael Ghens <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: RH6.2 & RAID
>
> Well, I can answer my own question.
>
> I am
> >When the two devices are compared they are equal but I get error
> >messages like:
> >
> >analyzing super-block - invalid chunk-size (0 Kb)
> >mkraid aborted
> >md: invalid raid superblock magic on sdb1
> >sdb1 has invalid sb, not importing
> >could not import sdb1
> >autostart sd
"Luigi Gangitano" <[EMAIL PROTECTED]> writes:
> Now the problem is: how should I use lilo to write the boot code in MBR on
> both disks? or how can I easily write the MBR on both disks so that it loads
> boot informations from a partition superblock (/dev/sda1 for MBR on /dev/sda
> and /dev/sdb
Hi, seems like this is really a FAQ but even re-reading all previous posts I
can't get it working.
Maybe I'm missing something.
I'm using kernel 2.2.14, Mingo's patches, lilo 2.21.4.2 (latest). I can get it
writing the boot code on the RAID partition (actually it writes it twice, once
per p
Hi,
On (an another) server i have this:
EXT2-fs error (device md(9,0)): ext2_new_block: Free blocks count corrupted for block
group 1
EXT2-fs error (device md(9,0)): ext2_new_block: Free blocks count corrupted for block
group 1
EXT2-fs error (device md(9,0)): ext2_new_block: Free blocks count c
Hi,
> It looks like your hda died. Those hda: errors in the log aren't
> good. Back up your data, shutdown (nicely), and then replace hda with
> another drive of the same parition sizes (or bigger?). Maybe you can
> still use fdisk to display the partitioning of hda if you don't know?
>
> Aft
It looks like your hda died. Those hda: errors in the log aren't
good. Back up your data, shutdown (nicely), and then replace hda with
another drive of the same parition sizes (or bigger?). Maybe you can
still use fdisk to display the partitioning of hda if you don't know?
After you have a new
I have been using Linux 2.2.x and RAID 1 happily.
Because of netfilter, I must move to Linux 2.3.15 or higher. It seems that
RAID 1 was disabled from 2.3.15 and above. The only options available are
Raid 0 or Linear. Even in the kernels where RAID1 is an available option,
2.3.25 for example, it
2 questions
The address of the archives for this list.
Any advice on getting a RH6.2 to boot from rain. Lilo coughs. From what I
have read, it should be very possible as long as the boot partition is
raid1. This is currently proving untrue.
TIA
Michael
On Mon, 1 May 2000, Gregory Leblanc wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 01, 2000 11:07 AM
> > To: [EMAIL PROTECTED]
> > Subject: Fastest / Most stable way to get >2GB files in 2.2?
> >
> > I have a MySQL database, r
[Ian Morgan]
> I can raidhotremove the (simulated-)faulty disk, and then physically remove
> it. Next, I put the disk back in physically. I then want to run raidhotadd to
> add the disk back into the array and begin reconstruction.
>
> Problem is, when I run raidhotadd, the system totally locks u
13 matches
Mail list logo
