Hi again,
don't forget, what I have written the mail before, but this day I got the same
failure after the attempt to initialize two disks as a raidarray which were
accessed by mdutils-0.41 before (SuSE 6.0).
As I see now (as I am involved myself) the output of mkraid shows two different
superblo
Hi,
On Wed, 17 Mar 1999, Piete Brooks wrote:
> > - fdisk your disks to remove the partitions that will be in the raid.
> > Completely remove them, don't just change the partition type.
> > - reboot.
> > - fdisk your partitions into existence, with type 'fd' as advertised in
> > the doc. Do not r
> I then reverted back to the old raidtools package that came with redhat 5.2
> (raidtools 0.50beta1 or something) and then insmoded the raid1 module..
> ...
> this shows the raid1 module has been loaded and registered, i now seem to
> have all i need to mke2fs the /dev/md0 device, yet when i do t
At 11:11 AM 3/17/99 +0100, you wrote:
>
> I've been playing with raid-1 too, with 0.90-0399 on RH 5.2. I have been
>creating/destroying raid partitions quite a lot and have had this error a
>few times. I now have what I believe to be a recipe for success:
>
ok, i give up, what did you do to get t
At 11:11 AM 3/17/99 +0100, Tony Wildish, exts 77103 / 71207 wrote:
> If anyone out there has any long-term experience with Linux-RAID in a
>production environment would they please let me know (either directly or
>via this list).
We've been testing 0.90 with Linux 2.0.36 (a system upgraded from R
>> [root@xx raidtools-0.90]# mkraid --force /dev/md0
>> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
>> handling MD device /dev/md0
>> analyzing super-block
>> disk 0: /dev/sdb1, 4188937kB, raid superblock at 4188864kB
>> disk 1: /dev/sdc1, 4188937kB, raid superblock at
you asked for experiences:
pfeiffer university uses linux for nfs, smb, mail and web services. we wanted
security of our data, but could not afford raid controllers. so,
we have been using a redhat 5.0 box with 2.0.35 or 36 kernel and the ancient
raid tools (.40) on three different boxes. combine
Hi Steve,
as I recognized so far, you haven't patched the kernel yet. Am I right?
If so,
you have to patch the kernel with the patch for the new raidtools. You
will
get it from www.de.kernel.org for example. There is one for kernel
2.0.36 and
2.2.3. Add the patch to the kernel, recompile it and r
Hello,
> [root@xx raidtools-0.90]# mkraid --force /dev/md0
> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/sdb1, 4188937kB, raid superblock at 4188864kB
> disk 1: /dev/sdc1, 4188937kB, raid superblock a
> originally, i followed all the docs, and suceeded in mirroring the two
> drives, but the problems started when i went to format the partition
> (/dev/md0) with mke2fs, i got an error along the lines of "the file system
> returned an unsupported library function call" or something, i no longer
>
Hiyas All,
Have been trying for the past few day to setup RAID-1 on a
redhat linux system and came across some weirdnesses..
firstly, this is the system its running on..
RedHat Linux 5.2
raidtools 0.90 (the rpm from the redhat contrib site - originally started
out with the 0.5 versi
11 matches
Mail list logo
