Well, I've outdone myself again. I think that last message went to the
list, since I'd forgotten about all the config options that listservers
can have. Again, sorry for that being totally out of place. Now, if
you're not all furious at me, I need some help getting software (R)AID
working on my
Hmm, well i took your advice and it has seemed to work.
I havent done a thourough check for corruption, but there doesnt seem to be
any major problems.
I had a linear raid partition over 4 drives (1 raid partition on each
drive).
I used ext2resize to resize the partition to below the last disk, t
I answered my own question below..
> I have a production system with raid5 0.42 tool set. Disk A of a 3
> disk set failed a couple of days ago on a power cycle. The array was
> downed successfully PRIOR to the failure, the drive simply did not
> spin up and appears totally dead. I've replaced the
>
>Assuming this is yet again the cause of problems, is anyone else getting
>sick of
>stupid distros like Suse and Mandrake that include raidtools-0.90 without
>including support in the kernel?
I keep replying to these emails, all the users are thankful, but yeah, i
think we're all getting
kin
> Sorry, the cause of the fault is obviously NOT the (latest?) version of
> the raid tools. I just downloaded raidtools-19990824-0.90.tar.gz
> which seems to be the latest one on ftp.de.kernel.org and comiled it
> on my machine. Same result as before.
>
> Are there general problems this way with 2
> But: I have not succeeded in installing a valid LILO bootblock in the second
> disks MBR,
> which would allow me to trash the bootfloppy.
If your first disk fails so comprehensively that you have to boot from the
second disk, the second disk will more than likely be recognized by the BIOS as
th
Surge + Martin,
many thanks for your fast response.
Sorry, the cause of the fault is obviously NOT the (latest?) version of
the raid tools. I just downloaded raidtools-19990824-0.90.tar.gz
which seems to be the latest one on ftp.de.kernel.org and comiled it
on my machine. Same result as before.
this is a re-post, but i thought it might be of interest under a
different title...
Stephen Waters wrote:
>
> so to clarify, the solution for removing, adding, and spinning up a
> scsi disk drive is:
>
> echo "scsi remove-single-device a b c d" >/proc/scsi/scsi
> echo "scsi add-single-device a
Hi,
thanks for your help
I ordered to make a try a
P III 450/384RAM/SCSI 2940U2W with 2x Ultrastar ES9
in raid-1 running on redhat6.1
hope to get it in 4 days and make the practice :)
> You should take measures that you WILL notice the first disk failure by
> monitoring /proc/mdstat - or you wil
I have a production system with raid5 0.42 tool set. Disk A of a 3
disk set failed a couple of days ago on a power cycle. The array was
downed successfully PRIOR to the failure, the drive simply did not
spin up and appears totally dead. I've replaced the drive and done a
ckraid /etc/raid5.conf
> But: I have not succeeded in installing a valid LILO bootblock in the second
> disks MBR, which would allow me to trash the bootfloppy.
I usually fdisk only one of the disks and then "dd" the MBR to the other
disks - so the MBR and partitioning is really identical.
After setting up the array a
On Mon, 3 Jan 2000, Jim Ford wrote:
>
> Luca Berra wrote on 2/1/00 13:20:
>
> >ok, your only chance is to
> >recreate the disk array.
> >
> >make a conf file specifying
> >as failed-disk the drive you
> >cut the power to, then
> >mkraid, data should be
> >there.
>
> Thanks Luca - but I
Hi,
this is only vaguely connected to Raid, but here goes anyways.
I have a machine with two identical disks set up as RAID 1, including the root
partition,
but not the /boot where vmlinux resides. /boot is mirrored with a script when
it changes.
I can unplug the second disk and the machine comes
I try to set up a RAID 1 mirror made up of 2 SCSI drives 4MB each.
The drives are connected to te system via an AIC78xx controller that
works just fine with single disks. Each disk has one singe partition
that covers the whole disk. According to the Software-RAID HOWTO,
i changed the patition ty
On Sun, Jan 02, 2000 at 06:22:05PM -0800, Andrew Biddle wrote:
> Actually, I'm having the same problem as the original poster, so I'll
> provide some details...
>
> Patching the 2.2.13 kernel to pre-2.2.14-18 compiles properly, yielding
> the expected kernel. Then I apply the raid0145-19990824-2
Luca Berra wrote on 2/1/00 13:20:
>ok, your only chance is to
>recreate the disk array.
>
>make a conf file specifying
>as failed-disk the drive you
>cut the power to, then
>mkraid, data should be
>there.
Thanks Luca - but I can't get past a kernel panic whilst booting. I might make a
res
On Sun, 2 Jan 2000, Thomas Waldmann wrote:
> > - for my use (web/email/cgi) why should I choise RAID 5 and not RAID 1 ?
> Always assuming that CPU power and SCSI bus bandwidth is NOT a limiting
> factor:
>
> RAID1, READ: with mutliple parallel reads, you get better values than with
> single d
On Sun, 2 Jan 2000, Raid wrote:
> Has anyone set up Software RAID 1 to allow disk mirroring under Linux?
>
Yep, there are plenty of us.
-- Mika
On Fri, 31 Dec 1999, Jim Ford wrote:
> I've been experimenting with my 4 disk Raid5 setup for a few weeks now and been
>impressed - so far.
>
> Today, I sucumbed to the temptation of of simulating a disk failure (or more
>accurately a power supply failure to a disk), by 'hot' unplugging its
19 matches
Mail list logo