I suggest mondo-archive by Hugo Rabson.
http://www.microwerks.net/~hugo/
We use it.
Great piece of reliable software.
//OLAS
Ed Wilts wrote:
> Or you can use dd for free... Do a quick google search for "linux duplicate
> drive" and you'll find a bunch of responses. Add "dd" to the search lis
t; steve
>
> -Original Message-
> From: OLA SAMUELSON [mailto:[EMAIL PROTECTED]]
> Sent: 22 January 2002 11:55
> To: [EMAIL PROTECTED]
> Subject: SV: Which Red Hat distro for 2.2.x?
>
>
> We are using updated 6.2 with 2.2.20 which works superbly.
> If it's for
We are using updated 6.2 with 2.2.20 which works superbly.
If it's for a server I would stick with 6.2, a desktop user
might want the newer UI stuff etc that comes with 7.2.
- Original Message -
From: David Krovich <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 22, 2
Try
Mondo
or
mkcdrec
or
partedimage(or something similar)
I found mondo easy to install/use.
Rhugga wrote:
We
have several Linux clusters that we want to upgrade from 6.2 to 7.2 using
an image system like Ghost. We have tried System Imager but it hangs during
imaging and we believe it is relat
You're right Chuckunless You want to upgrade to 2.2.13 kernel
and still boot on raid 1 which I can not figure out how to do.
mkinitrd as You suggested did not work so I am probably
going to raid ONLY the mounts i have data on. This means
that in case of disk failure I will have to reinstall b
>
Generally speaking , I prefer hardware raid.
Does not put "any" load on cpu and hides the
disk "arrangement" from the os which
makes it easier to manage. Also, rebuilding
is run by i960 cpu on card and the system
is almost unaffected by such operations.
Rebuild with software raid has more impac
>
>
> Essentially if you can get the raid driver loaded and the image exploded
> into RAM the system should be able to read the rest from disk. Try it and
> see what happens (just be sure you preserve your 2.2.12 kernel which runs).
>
Thinking maybe there is another way to solve this which may be
Hi!
Thanks for your time.
It appears to work without /boot since
all diskspace is raid:ed and it boots perfectly with
the rh6.1(2.2.12)kernel. The problem
appears when i build a NEW kernel.
THAT kernel won't boot from raid
but the "original" will.
the ramdisk appears to be the solution since it
>
> Yup... this sounds like you need mkinitrd!
>
>
> "mkinitrd /boot/initrd-2.2.13.img 2.2.13" would probably help but you might
> need/have to include "--with=raid1.o". Give it a shot and see what happens.
>
>
Thanks!
Don't I need to include startup/raidboot scripts and raid tools to start the r
Hi!
> On Fri, 5 Nov 1999, Ola Samuelson said:
>
> OS>Most greatful for assistance.
> OS> I need rh 6.1 for raid1 but 2.2.13 kernel for improved smp and
> OS> fix of eepro100 drivers in system with 4 cards.
> OS>
> OS> 1. Installed rh6.1 on
)
a high availability net site. I would like to reward
anybody that can help me with this. Nothing serious but I have
some hardware we will be tossing out soon. Maybe there is something
You would like to have?
Thanks & regards!
//OLA SAMUELSON
--
To unsubscribe:
11 matches
Mail list logo