gt; > Sent: May 2, 2000 4:09 PM
> > To: [EMAIL PROTECTED]
> > Subject:ANNOUNCE - Boot Root Raid + LILO howto has been sent to LDP
> >
> > Boot Root Raid + LILO howto has been sent to LDP and move to it's
> > local permanent directory here as well
Boot Root Raid + LILO howto has been sent to LDP and move to it's
local permanent directory here as well.
See
ftp://ftp.bizsystems.net/pub/raid
Michael
[EMAIL PROTECTED]
ete
> answer with examples config files + explainations tomorrow. Please
> be patient and I will get you the info.
as promised, here is the complete description for bootable root raid
and upgrade of a conventional system to raid.
Those of you who use this, be advised that while I have proofed
Theo Van Dinter writes:
> On Wed, 27 Oct 1999, Bruno Prior wrote:
>
> BP> (a) Getting the latest patched lilo from RedHat or applying the lilo.raid1 patch
> BP> and rebuilding it yourself (if /dev/md0 is RAID-1)
> BP> (b) Providing lilo with the geometry of one of the devices in the array (a
On Wed, Nov 03, 1999 at 09:28:54AM +0100, Martin Schulze wrote:
> > syslogd 378 root5w REG9,18548 192396
> > /var/log/boot.log
> > klogd 389 root2r REG8,1 191102 12
> > /boot/System.map-2.2.12-20
> >
> > Is it safe to kill these?
>
> Better add
Marcos Lopez wrote:
> I am attempting to get my system to run RAID 1 for /, /usr, /var, /home
>
> I have moved over all except for / and it works fine.
>
> After reading the howto "Root file system on RAID. by - Jakob
> OEstergaard" I have decided to take the first approach, unfortunately I
>
On Sun, Oct 31, 1999 at 11:50:26PM -0200, Christian Robottom Reis wrote:
> On Wed, 27 Oct 1999, Jakob Østergaard wrote:
>
> > Because LILO doesn't understand RAID, and thus cannot (yet) load the kernel
> > of it.
>
> Doesn't the lilo.raid1 patch included in RH6.1 permit booting off a raid1
> arr
On Wed, 27 Oct 1999, Admin Mailing Lists wrote:
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1). Of course you can put
> this bootable partition on a seper
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1).
You can mirror that partition manually by using 2 dd commands - see one of my
earlier messages here (if ne
the kernel
> of it.
Actually, I think Tony has a point. He isn't suggesting booting from RAID-1. He
is suggesting booting from a floppy to a root RAID-1 system. This would be one
way of doing it. However, it still doesn't give you any redundancy if you have a
problem with the flopp
On Wed, 27 Oct 1999, [iso-8859-1] Jakob Østergaard wrote:
>
> True. That's why you put identical /boot partitions on all the drives
> in your array if you want to be really safe.
>
i c
> > Wouldn't it be easier to stick the kernel, lilo config, relevant boot info
> > on a floppy and boot ra
On Wed, Oct 27, 1999 at 11:19:38AM -0400, Admin Mailing Lists wrote:
>
...
> The thing I TOTALLY don't get is if the first drive dies, how can
> you boot the 2nd drive (mirror) when you're still losing the small
> bootable partition (as it's still part of drive 1). Of course you can put
> this bo
ke My home page
FAX 407-676-2355
- Original Message -
From: Jakob Østergaard <[EMAIL PROTECTED]>
To: Linux-Raid <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 1999 12:31 PM
Subject: Re: Root RAID and unmounting /boot
On Wed, Oct 27, 1999 at 11:19:38AM -0400, Admin Mailing
ve forever, live as if you'll die today"
http://cygnus.ncohafmuta.comhttp://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
On Wed, 27 Oct 1999, Bruno Prior wrote:
> There seems to be quite a lot of confusion about root-
and partitions (see Harald
>Nordgård-Hansen's message to the list of 22 August on the "Booting Root RAID 1
>Directly _Is_ Possible" thread). You may need this section in your
>lilo.conf to
>enable booting, but it has nothing to do with RAID, nor should it be a
>cure for
On Wed, 27 Oct 1999, Bruno Prior wrote:
BP> (a) Getting the latest patched lilo from RedHat or applying the lilo.raid1 patch
BP> and rebuilding it yourself (if /dev/md0 is RAID-1)
BP> (b) Providing lilo with the geometry of one of the devices in the array (again
BP> if /dev/md0 is RAID-1)
BP> (c)
There seems to be quite a lot of confusion about root-RAID out there.
> > to /mnt/newroot/boot. Then after running "lilo -r /mnt/newroot" I get
> > the following error:
> > "Sorry, don't know how to handle device 0x0900"
> >
> > What do
you suggest.
But you presumably have this running for a reason. So if you don't want to do
this, the other alternative would be to leave /dev/sda1 on /boot for now. Edit
/mnt/newroot/etc/lilo.conf so that you have an image section which selects your
root-RAID array as root (e.g. root=/dev/md?)
ase, the disk= and partition= lines would
point to RAID arrays, not normal disks and partitions (see Harald
Nordgård-Hansen's message to the list of 22 August on the "Booting Root RAID 1
Directly _Is_ Possible" thread). You may need this section in your lilo.conf to
enable bootin
On Tue, Oct 26, 1999 at 09:07:34AM -0600, Marcos Lopez wrote:
> Egon Eckert wrote:
> >
> > > syslogd 378 root5w REG9,18548 192396
> > > /var/log/boot.log
> > > klogd 389 root2r REG8,1 191102 12
> > > /boot/System.map-2.2.12-20
> > >
> > > Is it s
> to /mnt/newroot/boot. Then after running "lilo -r /mnt/newroot" I get
> the following error:
> "Sorry, don't know how to handle device 0x0900"
>
> What does the above mean and how to i fix it?
It does mean that lilo doesn't know anything about md device. Change the
line containing "root=" i
At 09:07 26/10/99 -0600, Marcos Lopez wrote:
>Egon Eckert wrote:
> >
> > > syslogd 378 root5w REG9,18548 192396
> > > /var/log/boot.log
> > > klogd 389 root2r REG8,1 191102 12
> > > /boot/System.map-2.2.12-20
> > >
> > > Is it safe to kill these?
Egon Eckert wrote:
>
> > syslogd 378 root5w REG9,18548 192396
> > /var/log/boot.log
> > klogd 389 root2r REG8,1 191102 12
> > /boot/System.map-2.2.12-20
> >
> > Is it safe to kill these?
>
> These are loggers, so I guess nothing terrible would h
> syslogd 378 root5w REG9,18548 192396
> /var/log/boot.log
> klogd 389 root2r REG8,1 191102 12
> /boot/System.map-2.2.12-20
>
> Is it safe to kill these?
These are loggers, so I guess nothing terrible would happen. But I
wouldn't kill them anyw
I am attempting to get my system to run RAID 1 for /, /usr, /var, /home
I have moved over all except for / and it works fine.
After reading the howto "Root file system on RAID. by - Jakob
OEstergaard" I have decided to take the first approach, unfortunately I
can not umount \boot. even after
self into
the future." --Kraftwerk, 1981
> --
> From: David Cooley[SMTP:[EMAIL PROTECTED]]
> Sent: Monday, September 27, 1999 12:21 PM
> To: Stanley, Jeremy; Linux-Raid
> Subject: Re: Boot Linear/RAID-1 [was: Root Raid Questions]
>
At 12:00 PM 9/27/1999 -0400, Stanley, Jeremy wrote:
>If we don't already have a HOWTO section on this issue, we probably
>should add one. We've seen more and more questions on this topic of
>late... Just my half-nybble.
>
>On a similar note, wouldn't it be possible to boot from RAID-1/5 using a
> --
> From: Stanley, Jeremy
> Sent: Monday, September 27, 1999 12:00 PM
> To: Linux-Raid
> Subject: Boot Linear/RAID-1 [was: Root Raid Questions]
>
[clip]
> On a similar note, wouldn't it be possible to boot from RAID-1/5 using
>
If we don't already have a HOWTO section on this issue, we probably
should add one. We've seen more and more questions on this topic of
late... Just my half-nybble.
On a similar note, wouldn't it be possible to boot from RAID-1/5 using a
similar method if the chunk size was greater than the ker
>
> You don't have to put lilo on the boot partitions. It can go on the MBR. Lilo
> needs to point to files on a non-raided partition, not necessarily be on that
> partition itself.
Sorry, on the MBR is what I meant...
>
> The following /etc/lilo.conf should work for /dev/sda (substituting app
On Mon, Sep 27, 1999 at 09:29:51AM -0400, Luca Pescatore wrote:
> Sep 27 15:26:36 test kernel: kmod: failed to exec /sbin/modprobe -s -k md-
> personality-3, errno = 2
either compile raid1 in the kernel or add
alias md-personality-3 raid1
to /etc/conf.modules
if you are using a redhat initrd you
Hi,
this is my /var/log/messages it doesn't start MD0, Why ?
At this moment 'm using kernel 2.2.13ac12 with last raidtools, what's wrong ?
Best Regards,
Luca Pescatore
Sep 27 15:26:36 test kernel: Detected scsi disk sdb at scsi0, channel 0, id
1, l
un 0
Sep 27 15:26:36 test kernel: SCSI dev
MAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bo Kersey
> Sent: 24 September 1999 23:19
> To: [EMAIL PROTECTED]
> Subject: Root Raid Questions
>
>
> Hi,
> I've successfully gotten my box up with root software raid1 and I
> have created
> md's for
[ Sunday, September 26, 1999 ] Luca Pescatore wrote:
> Do you know if is it possible to mkraid when a partition is mounted ?
Much like the answer to the perl FAQ "what happens if I add or remove
keys from a hash while iterating over it" "Don't do that." :)
http://language.perl.com/newdocs/po
>try to download the newest raidtools and the newest kernel patch
>ftp.xx.kernel.org/pub/linux/daemons/raid/alpha where xx is a country
code. the raidtools also have an >up to date faq :)
Do you know if is it possible to mkraid when a partition is mounted ?
Best Regards,
Luca Pescator
Check out http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/
On Sun, 26 Sep 1999, Luca Pescatore wrote:
> Hi Guys,
> i think that is a very newbie quesion, but i have tryed to find out with
> Howto in LDP but i think that explain only old Raid Tools, someone can help
> me or point me to ne
Hi Guys,
i think that is a very newbie quesion, but i have tryed to find out with
Howto in LDP but i think that explain only old Raid Tools, someone can help
me or point me to new HowTo or can give me an help in private ?
Best Regards,
Luca Pescatore
Hi,
I've successfully gotten my box up with root software raid1 and I have created
md's for all but the boot partition...
I had hell getting lilo to put its magic in the right place and ended up using
brute force and awkwardness to get it on both boot partitions...
I did the raid1 using the 's
On Mon, 20 Sep 1999, Glenn McGrath wrote:
> Does anyone know how GRUB would go as an alternative to lilo for booting
> root raid partitions?
>
> Ive heard its fairly flexible, but seems pretty complex to me, i tried
> getting it working, but never really understood it. Sta
Does anyone know how GRUB would go as an alternative to lilo for booting
root raid partitions?
Ive heard its fairly flexible, but seems pretty complex to me, i tried
getting it working, but never really understood it. Stage 1, 1.5 2 etc...
But if this complexity makes it flexible it may be worth
an [mailto:[EMAIL PROTECTED]]
> Sent: 17 September 1999 18:59
> To: [EMAIL PROTECTED]; Bruno Prior
> Cc: [EMAIL PROTECTED]
> Subject: RE: root raid problems
>
>
> hello,
>
> i was probably unclear in my previous post. i had not been able to make
> any raid devices (/dev/m
Leandro et al,
THANKS!! normally i don't type in caps, but this was so amazingly helpful
that i can't help it.
i followed your instructions nearly step for step and i now have
Personalities : [linear] [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md3 : active raid1 sda7[1] sdb7[0] 530048 blo
> > read-only
>
> Lilo can't see raid devices. So if /boot is on /dev/md1, as it is in this case,
> lilo can't find any of the files in /boot, such as the kernel image, the system
> map etc. The traditional solution is to have /boot on its own little non-raided
>
v/md1, as it is in this case,
lilo can't find any of the files in /boot, such as the kernel image, the system
map etc. The traditional solution is to have /boot on its own little non-raided
partition.
You don't have /boot on a non-raided partition, and you haven't taken any of the
measur
hello,
i'm trying to set up root raid on a new system. it's an adaptec aaa-131u2
(which linux doesn't like for hardware-based raid) with two 9gb disks.
the biggest problem, i think, is that i can't get the system to boot off a
hard disk at all. during the (redhat 6.0) i
am my homecomputer; beam myself into
the future." --Kraftwerk, 1981
> --
> From: Schackel, Fa. Integrata, ZRZ
> DA[SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, August 24, 1999 3:54 PM
> To: Stanley, Jeremy
> Subject: Abwesenheitsnotiz: Booti
On Wed, Aug 25, 1999 at 10:12:18AM -0400, Stanley, Jeremy wrote:
> Shouldn't be too hard to throw together a bash script that reruns LILO
> for each MBR, with different parameters, I wouldn't think... Anyone
> disagree?
If anyone has the time to do that (eh, takes the time to do that), then
why
> Shouldn't be too hard to throw together a bash script that reruns LILO
> for each MBR, with different parameters, I wouldn't think... Anyone
> disagree?
Hmmm here's a question...
If you run the raid on the whole drives instead of creating partitions,
do you even need to re-run lilo for all dev
OTECTED]
> Subject: Re: Booting Root RAID 1 Directly _Is_ Possible
>
> > This does open RAID-5 systems up for a full-redundancy solution with
> > little loss in capacity... Allocate the first 5 or 10MB on each
> drive
> > in your array for /boot as an n-way RAID-1 mir
anley, Jeremy
> Subject: RE: Booting Root RAID 1 Directly _Is_ Possible
>
> On Tue, 24 Aug 1999, Stanley, Jeremy wrote:
> > This does open RAID-5 systems up for a full-redundancy solution with
> > little loss in capacity... Allocate the first 5 or 10MB on each
> dri
Ferrell
> Cc: Harald Nordgård-Hansen; James Manning; Linux RAID Mailing List
> Subject: Re: Booting Root RAID 1 Directly _Is_ Possible
>
> On Tue, 24 Aug 1999, Mark Ferrell wrote:
>
[clip]
> Don't forget, though, that we're only talking about booting RAID 1
> here...
>
[snip]
On Tue, 24 Aug 1999, Mark Ferrell wrote:
> Maybe you two could work together and make a RaidRoot-HOWTO that covers both lilo
> and grub??
I think that's an excellent idea - one stop shopping.
Don't forget, though, that we're only talking about booting RAID 1 here...
not RAID booting in general.
Maybe you two could work together and make a RaidRoot-HOWTO that covers both lilo
and grub??
--
Mark Ferrell : [EMAIL PROTECTED]
Andy Poling wrote:
> On 23 Aug 1999, Harald Nordgård-Hansen wrote:
> > James Manning <[EMAIL PROTECTED]> writes:
> > > > How come I've been running this for about a
On Sun, Aug 22, 1999 at 01:28:32PM +0200, Harald Nordgård-Hansen wrote:
> disk=/dev/md1
> bios=0x80
> sectors=32
> heads=64
> cylinders=4341
> partition = /dev/md0
> start = 32
Gosh, you are a genius,
or pheraps i am just a dumbass
i spent a lot of time trying
On Mon, 23 Aug 1999, Tim Walberg wrote:
> One method I've seen on another platform (Solaris/Veritas)
> is as follows:
>
> 1) boot loader knows about a list of the various components
>of the boot RAID device (accomplished via eeprom on SPARC)
>and will attempt to boot from the first of the
On 23 Aug 1999, Harald Nordgård-Hansen wrote:
> James Manning <[EMAIL PROTECTED]> writes:
> > > How come I've been running this for about a year and a half, then?
> >
> > I believe he's talking about not having to do *any* non-raid partitions
> > (ie your /boot I believe, reading your lilo.conf)
One method I've seen on another platform (Solaris/Veritas)
is as follows:
1) boot loader knows about a list of the various components
of the boot RAID device (accomplished via eeprom on SPARC)
and will attempt to boot from the first of these it can
talk to
2) first component is accessed
James Manning <[EMAIL PROTECTED]> writes:
> > How come I've been running this for about a year and a half, then?
>
> I believe he's talking about not having to do *any* non-raid partitions
> (ie your /boot I believe, reading your lilo.conf)
> (...)
>
> Please enlighten if I missed the point in hi
> How come I've been running this for about a year and a half, then?
I believe he's talking about not having to do *any* non-raid partitions
(ie your /boot I believe, reading your lilo.conf) I have to admit, his
success with GRUB has been good to hear about. Adding in the code
to handle raid wi
Andy Poling <[EMAIL PROTECTED]> writes:
> LILO is just not going to let me boot my RAID 1 root.
>
> This is not a slam on LILO. Heck, I've happily used it for years to boot my
> Linux systems, and probably will continue to on my non-root-raid systems
> just because it
Andy Poling wrote:
>
>
> I'm willing to put together a cookbook description, of sorts, to patch and set
> up GRUB to boot RAID 1, and post it to the list. I guess my question is
> whether there's any interest in such a thing. It's entirely possible that
> most people are smarter than me, and
RAID 1 root.
This is not a slam on LILO. Heck, I've happily used it for years to boot my
Linux systems, and probably will continue to on my non-root-raid systems
just because it works out of the box.
GRUB
I've seen GRUB mentioned a few times as an alternative bootloader. I decide
[EMAIL PROTECTED] writes:
> Hi, have you read the manual???
>
> I now talk about version 0.90, previous versions don't have autodetection.
>
> 1. activate Autodetection in Kernel
> 2. make the raid with a correct /etc/raidtab
> 3. change the partition-id to 0xfd
>
> I haven't got the manual he
A while back I was also looking into ways to umount the root partition
(raid5 in my case). I was poking around with the kernel to see how
real_root_dev etc works, and the way initrd (which I was using) moved the
real root device around.. I figured a syscall of some sort could be called
at shutdown
Hi, have you read the manual???
I now talk about version 0.90, previous versions don't have autodetection.
1. activate Autodetection in Kernel
2. make the raid with a correct /etc/raidtab
3. change the partition-id to 0xfd
I haven't got the manual here right now, but these 3 should be the right
Hi.
I'm having problems using raid with kernel 2.2.10. I actually don't know
whether the kernel is the problem.
The problem is that my kernel doesn't mount my /dev/md0 raid1 device at
startup. I added it to fstab and mdtab, but it refuses to mount. when i
mount it manually it works fine. Did i f
I got the root raid working (using James Lewis recipie [sic]) and am able to reboot fine. I must confess to a very limited understanding of lilo, so I followed that part of the instruction rather blindly.
When I reboot, it always looses the "original" root partition. I have att
> I have read the root-raid howto v1.07 mar '98, and I have read the
> software raid howto v 0.90.2 feb '99. Unfortunately, the root-raid
> howto seems to be very out of date - it refers to raidtools 0.42 and
> almost all the info does not seem to apply. For example, it
Hello!
I am attempting to build a fileserver running redhat-6.0 and raidtools
0.90 which has two 9gb scsi disks. I would like to make the system boot
off the raid.
So, my question is: Where can I go or what do I need to know to make root
raid level 1 work? I have unsucessfully tried to make
Hello,
I'd like to install a redhat 6.0 on a raid array. But I don't know how
to set the persistant superblock in the /etc/raidtab file. What is the
correct option to add to my config file ?
I have also another question, do the raidtools shipped with the redhat
6.0 are enough stab
ss. Plus, it leaves me with a small but annoying
> original boot partition. I want the whole drive used in one big root raid
> partition.
Lilo has to read the kernel from a specified position on a particular drive. If
you have the kernel on a RAID-5 array, it will be spread across all the drives
want the whole drive used in one big root raid
partition.
--
This message contains a minimum of 63% recycled electrons.
> I tested this some time ago ( dd if=/dev/hda1 of=/dev/hdc1 in single user
> mode) but did not shrink the ext2fs, but it worked.
That is not a surprise -- the PSB is onlt one 4K block at the very end ...
> Will the superblock get corrupted when I use up my last 4k of space on the
> ext2fs ?
As
> (I'm aware of the failed-disk patches and have used them
> successfully. Is there another way?)
(resize2fs from PartitopnMagic, and of course dump/restore ...)
> If you ask me, mke2fs should be modified to reserve that 4k in the end
> of the volume by default..
Yup -- I too suggested that whe
yes, you can reduce the size of blocks by one in ext2fs, as long as the
blocks are 4k or greater, then mkraid will copy disk one onto disk 2, etc.
and the raid SB will takeup its space at the end of the disk.
this only works for raid1 though, cause under raid5 your fs will be larger
than a single
Luca Berra wrote:
>
>
> > Third, (naive questions) if raid1 supports on-the-fly disk
> > "reconstruction" why can't I simply add another identical disk alongside
> > my present one, activate raid1 non-destructively and have disk2 be
> > "reconstructed" as the mirror image of disk1?
> because linu
Luca Berra <[EMAIL PROTECTED]> writes:
> because linux-raid keeps a 4K raid superblock at the end of the partition
> so if you already created the filesystem you have no room for the superblock.
This reminds me.. mke2fs has a blocks-count argument that, if you omit
it, defaults to the size of th
you have no room for the superblock.
i have not yet tested this, but you could get resize2fs (you need a partition
magic license for that, shrink the filesystem by 4K, dd one disk over the
other, then create a new raid.
> Finally, I read that the way to install root-raid is to use the to-
read that root raid (meaning
boot-on-raid, is it the same?) is the most desirable solution, although
not the best supported especially when using raid1.
First, kernel-2.2.7's documentation states that booting on raid1 is not
supported yet, but looking at the alpha raidtools-0.90 package it seem
In article <[EMAIL PROTECTED]>,
Martin Bene <[EMAIL PROTECTED]> wrote:
> 1) do a normal installation onto one of the disks you intend to use for
> your root raid array. If your disks are not the same size, DON'T use the
> smallest one.
> 2) install raid tools + rai
Hi Stephen,
At 22:24 09.03.99 -0600, you wrote:
>Here's my situation.
>
>I made a nice raid 5 with only two drives naively expecting to
>add the third non-raided disk later. Unfortunately I have no
>clue how to do that since I did the mkraid with nr-raid-disks set
>to 2.
Nope, you can't change
Here's my situation.
I have linux 2.2.1 with raid0145-19990128-2.2.0 and
raidtools-19990128-0.90.tar.gz.
I have three disks.
I made a nice raid 5 with only two drives naively expecting to
add the third non-raided disk later. Unfortunately I have no
clue how to do that since I did the mkraid
>
> On Fri, 5 Feb 1999, m. allan noah wrote:
>
> > what you mention is not possible for the reasons i outlined on non-raid1.
This is the whole purpose behind the root raid HOWTO.
The scripts were only required because the 0.42 raid tools do not
have a means to cleanly stop/dismount a
now we are talking about the same thing, black sabbath albums aside
yes, under raid1, all the partitions would be identical in the area where
the kernels are. however, you still have to update the MBR which is
outside the raid space. this would require copying that block from the
first disk a
I think we're talking cross purposes!
I was trying to say that if lilo could do RAID( 1 ) then you could have a
5(say) way mirror for the 10meg /boot partition... then lilo would be on
all the disks... then you could use all 5 disks in a raid5 for /
On Fri, 5 Feb 1999, m. allan noah wrote:
> w
what you mention is not possible for the reasons i outlined on non-raid1.
under raid 5- the /boot directory inside the root partition does not exist
on everydisk. it is striped across multiple disks with a parity stripe on
one. lilo would have to pull blocks from different disks, and if one was
m
> From: steve rader
> Am I following this correctly: in this senario, are /boot and
> /boot1 non-raid "stub root" filesystems with kernel(s) for
> launching the "real" root-raid1 system with one or the other of
> the root-raid1 disks offline? That would be pretty sweet eh.
> If so, what doe
The production systems I'm adminin' have very static root
filesystems so, for now, I'm converging on the conclusion
that having two bootable roots and mirrored non-roots is
the cleanest setup.
I'm using 2.0.36 + latest aic7xxx + raidtools 0.42. I assume
I should also apply raid0145-19990128-2.0
> > From: Michael
> > The Root Raid HOWTO is seriously out of date and is based on the 0.42
> > raid tool set. The current .9x tool set is different in it's setup
> > and configuration. Raid is still alpha but seems to be pretty stable now
> > with a r
Lilo being raid1 capable would be cool, it would be simple enough to have
a 10 meg mirror to have /boot on then / could be mounted from a raid5
or somthing... might even be cool to have the mirror across each disk in
the raid5 then you could guarantee it would find one and boot no matter
whic
On Fri, 5 Feb 1999, Osma Ahvenlampi wrote:
> steve rader wrote:
> > Is it safe to assume 2.0.36 is more stable with 0.9x than
> > with 0.42?
>
> Well, I've run a busy file server with 2.0.3x and 0.9x RAID patches from
> november/december in uninterrupted production use without a single
> problem
steve rader wrote:
> Is it safe to assume 2.0.36 is more stable with 0.9x than
> with 0.42?
Well, I've run a busy file server with 2.0.3x and 0.9x RAID patches from
november/december in uninterrupted production use without a single
problem (at RAID-5). I don't know about the stability of 0.42, bu
ok- the main point with booting is thus- with the new raid code, you can
start raid from the kernel without any utils on the disk. meaning, all you
have to do is get the kernel into ram, and jump to its starting address.
this is what lilo is for, along with loadlin, etc.
they are needed cause the
> From: Michael
> The Root Raid HOWTO is seriously out of date and is based on the 0.42
> raid tool set. The current .9x tool set is different in it's setup
> and configuration. Raid is still alpha but seems to be pretty stable now
> with a real nice feature set. I w
The Root Raid HOWTO is seriously out of date and is based on the 0.42
raid tool set. The current .9x tool set is different in it's setup
and configuration. Raid is still alpha but seems to be pretty stable now
with a real nice feature set. I will update the HOWTO, hopefully in the
n
Does anyone know of other root-raid howtos? For example,
for those of us who have only a basic understanding of linux
booting and ramdisks?!
I spent the morning looking at the Root-RAID-HOWTO [1]
and have come to the conclusion that doing a root-raid is
seriously non-trivial unless you have a
-0.90 but it still needs a little work.
Root raid(1) works with MILO for booting since MILO only reads the disk
on boot and since with RAID1 the disk image is unaltered from what a
normal disk all is ok. This by the way is what Sun supports with there
own software raid solution.
System booting
Someone wrote me a note about bench marks etc
after reading my Root Raid Howto
I have managed to misplace the e-mail message...
Drop me a note if you get this message.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
98 matches
Mail list logo
