Re: help!

Try mkraid --really-force /dev/md0 Im sure it will work. Greetings, Dietmar - Ursprüngliche Nachricht - Absender: [EMAIL PROTECTED] Betreff: help! Empfänger: [EMAIL PROTECTED] Datum: 09. Apr 1999 05:41 Help! im lost, finaly have found the new howto on ftp.fi.kernel.org after days of

Re: help!

Chris Chabot wrote: Help! im lost, finaly have found the new howto on ftp.fi.kernel.org after days of dispair and old documentation... tried the new tools ... nada ... tried kernel patches ... busted kernel 2.2.5 ... My problem is this ... i created the /etc/raidtools (modified example

[off-topic] HELP! weird keyboard lockup problem

Hi guys, I'm sorry for the off-topic subject, but I'm having this weird problem that locks up the console's keyboard. What could conceivably lock out the keyboard upon boot-up? I have a Stampede Linux installation that works fine. Worked fine with 2.0.36 kernel. However, if I try to boot up

boot RAID-1

Hi, does somebody have a lilo.conf sample on how do this. I am having problems with mounting the root file system. - Alex

Re: /dev/md0 doesnt come up on boot

- Did you marked the raid partitions as type 'fd'? (stop the raid before doing that) I asked this question some time ago, but get no answer: how to mark them as type fd? Can you send the whole command line? Thanks, Dietmar

remaking raid from 4 drives to 3

Hello... I had a raid0 set where one of the drives started going bad. The raid is for a usenet feed. I took the raid down, took out the bad drive and remade it with the 3 remaining drives. I works but the autodetect still wants 4 drives. kernel 2.2.3 latest raid015 patches latest

Marking partitions as raid/fd

I asked this question some time ago, but get no answer: how to mark them as type fd? Can you send the whole command line? Thanks, Dietmar You need to use fdisk... the process is usually something like this: rootprompt# fdisk /dev/sda Then use the 't' command to change the partition's system

AW: /dev/md0 doesnt come up on boot

I asked this question some time ago, but get no answer: how to mark them as type fd? Just run fdisk and change the type to fd manually (it will complain that this is an unknown type). There is no "whole command line" (to run fdisk type "fdisk" Rgds, Till

Re: boot RAID-1

you cant boot off of a raid partition. lilo needs to find the kernel on the disk using bios routines. raid is not in bios. you need to create a ~20 meg partition to hold the kernel, etc. this works very well at redhat install time to create a /boot and /boot2 folder on the first and second

Sorry that I can't...

Tried using linux 2.2.5 w/o patches, mkraid aborts attempting to open /dev/md0 for read-only. Tried to patch with raid0145-1990309-2.2.3 -- OK, backed off to linux 2.2.3, and tried again, well, neither will build because there is no linux/md.h. Suggestions? I must be missing something really

Re: RAID1

Basically: to get improved Read performance because of mirrored-disks, DO I NEED 2 SCSI CARDS? Or will the command queueing/SCSI subsystem still give me a benefit? Right now I'm assuming 2 separate cards is better You can get increased read performance with both drives on one scsi

Re: Filesystem corruption (was: Re: Linux 2.2.4 RAID - success report)

On Wed, 31 Mar 1999, Tony Wildish wrote: Try booting with the 'mem=xxxM' option to limit yourself to a small amount of RAM. If you are lucky then the problem is high enough in the memory that you can limit yourself to a good region and it will work. There's also a memtest86 utility that