David Grimes wrote:
I'm sorry but I do not know how to apply this patch.. when I do #patch
raidreconf-0.0.2.patch
It just sits there... can u tell me how ya'll made did it? Thank you in
advance.
Did you type "patch raidreconf-0.0.2.patch" ?
---^^^
btw. what is this patch
Hi,
I'm sorry but I do not know how to apply this patch.. when I do #patch
raidreconf-0.0.2.patch
It just sits there... can u tell me how ya'll made did it? Thank you in
advance.
Did you type "patch raidreconf-0.0.2.patch" ?
---^^^
btw. what is this patch for and
I'm sorry but I do not know how to apply this patch.. when I do #patch
raidreconf-0.0.2.patch
It just sits there... can u tell me how ya'll made did it? Thank you in
advance.
Regards
David Grimes
Sr. Technical Engineer/Level II Check Point Software
Email: [EMAIL PROTECTED]2505 N.
can u send your raid configuration file(s)? maybe, I will be able to help
then...
-Original Message-
From: Sandro Dentella [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, July 06, 2000 2:23 AM
To: [EMAIL PROTECTED]
Subject: help: read-ahead not set: what is it???
Hi,
I'm
Hi,
I'm trying to configure raid1 w/ 2 disks /dev/hda7 /dev/hda8 but I get:
mkraid version 0.36.4
parsing configuration file
mkraid: aborted
cat /proc/mdstat:
personalities: [1 linear] [2 raid0] [3raid 1]
read_ahead not set
md0 : inctive
what does
we do now?
May we run fsck on the md devices???
PLAAASE Help
Regards and thanks in advance
Jochen
on our own...
Anyone had this problem with overlapping physical units??? How can
this happen? What can we do now?
May we run fsck on the md devices???
PLAAASE Help
Regards and thanks in advance
Jochen
To: "linux-raid" [EMAIL PROTECTED]
Sent: Tuesday, June 20, 2000 2:06 PM
Subject: Raid-Failure, please help
At the moment my colleague at the location is trying to get the
machine back to work, at present with an open chasi. But the Raid
does not recreate automatically... The problem m
On Tue, Jun 20, 2000 at 05:21:15PM -0400, Richard Bollinger wrote:
The message about overlaping physical units does not indicate failure...
Where there are multiple mirrors on the same physical disks, the Raid code
avoids recovering more than one at a time for performance reasons. It
[Jochen Haeberle]
does not recreate automatically... The problem mentioned striking me
most is "md0 has overlapping physical units with md2"... this does
not sound very good to me...
That's informative about resync operations. It is not an error.
May we run fsck on the md devices???
sure,
and many other things.
I need a work, please, help!.
I've been running 2.2.16 with the 2.2.15-A0 patch for about 18 hours now on
two boxes (one RAID1, one large RAID5).
It's working fine (the md.c rejects don't matter -- that was for old version
of md.c).
Well, I tried the "2.2.15, raid-2.2.15-A0 patch, 2.2.16 patch, build"
method.
Leblanc
Cc: [EMAIL PROTECTED]
Subject:Re: HELP with autodetection on booting
[Gregory Leblanc]
I started seeing this when I blew away my RAID0 arrays and put RAID1 arrays
on my home machine. I suspect that this is cause by RedHat putting
something in the initscripts to start the RAID
On Mon, 29 May 2000, James Manning wrote:
Sure makes it look like hdc3 has some major issues. It has a partition
type of fd, but invalid raid superblock. Makes me wonder if e2fsck
didn't get run on hdc3 itself and it "fixed" that last part (hope not
since it may have done some real
5:50 AM
Subject: Re: HELP!!! Broken raid0
On Mon, 29 May 2000, James Manning wrote:
Sure makes it look like hdc3 has some major issues. It has a partition
type of fd, but invalid raid superblock. Makes me wonder if e2fsck
didn't get run on hdc3 itself and it "fixed" th
: "Matthew Burke" [EMAIL PROTECTED]
To: "James Manning" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, May 29, 2000 5:50 AM
Subject: Re: HELP!!! Broken raid0
On Mon, 29 May 2000, James Manning wrote:
Sure makes it look like hdc3 has some m
I am running Redhat 6.0 with kernel 2.2.5-22. I have successfully created a
RAID1 disk and mount with no problem. However, when I reboot the machine,
it failed. Below is part of the message from running command dmesg:
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem).
(scsi0)
this. And since I just totaled my RH install, it may be a couple of weeks
before I get back to look some more.
Greg
-Original Message-
From: Jieming Wang [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 29, 2000 6:31 AM
To: [EMAIL PROTECTED]
Subject: HELP with autodetection
[Jieming Wang]
autorun ...
considering sdb1 ...
adding sdb1 ...
adding sda1 ...
created md0
bindsda1,1
bindsdb1,2
running: sdb1sda1
now!
sdb1's event counter: 000a
sda1's event counter: 000a
Looks like a couple of partitions with type fd, looking great for
autostart by the
[Gregory Leblanc]
I started seeing this when I blew away my RAID0 arrays and put RAID1 arrays
on my home machine. I suspect that this is cause by RedHat putting
something in the initscripts to start the RAID arrays AND the RAID slices
being set to type fd (RAID autodetect), but I haven't
Hi. I'm in URGENT need of some help.
After changing motherboards in one of my boxes to a Via VB601, I forgot to
disable the UDMA setting in the bios. This is needed because this mobo,
my Seagate 6.5Gb drives, and UDMA don't mix.
The result was the kernel segfaulted/panicked after fscking
[Matthew Burke]
e2fsck 1.18, 11-nov-1999 for EXT2 FS 0.5b, 95/08/09
e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/md1
Could this be a zero-length partition?
/dev/md1 is not mounted, but it is properly set up in /etc/raidtab
raidstart
[Matthew Burke]
On Sun, 28 May 2000, James Manning wrote:
[Matthew Burke]
e2fsck 1.18, 11-nov-1999 for EXT2 FS 0.5b, 95/08/09
e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/md1
Could this be a zero-length partition?
mdstat:
Hello,
I have all my backup on server with 8 EIDE disk in RAID5 array. This
server was cold rebooted and now RAID5 has unconsistent superblock. Is
there any posibility to get my data back from RAID ?
Thanks,
Pavel
This is what happens when I try to start raid (raidstart):
May 18 16:38:27
n with hdh2 included.
Good luck!
Rich B
- Original Message -
From: "Pavel Kucera" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 18, 2000 9:46 AM
Subject: Help with RAID5 damage please
Hello,
I have all my backup on server with 8 EIDE disk in RAID5 array.
Hi there,
On Thu, 18 May 2000, Richard Bollinger wrote:
May 18 16:38:27 backup kernel: hdh2's event counter: 000a
May 18 16:38:27 backup kernel: hdg2's event counter: 0008
May 18 16:38:27 backup kernel: hdf2's event counter: 0008
May 18 16:38:27 backup kernel: hde2's event
I get:
File Block Num Seq ReadRand Read Seq Write Rand
Write
DirSize Size Thr Rate (CPU%) Rate (CPU%) Rate (CPU%) Rate
(CPU%)
--- -- --- --- --- --- ---
---
. 20040961 21.57 12.0% 0.634 1.13% 19.67 24.0%
-Original Message-
From: Edward Schernau [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 17, 2000 11:19 AM
To: [EMAIL PROTECTED]
Subject: help interpret tiobench.pl results?
I get:
File Block Num Seq ReadRand Read Seq Write Rand
Write
DirSize Size
've tried to find an alternate superblock, but I didn't succeed so far.
Thank you in advance for any help!!
bye!
Volker Wysk wrote:
Hello!
RedHat 6.1's graphical install program has destroyed my RAID0 volume,
which is really bad for me.
I was going to install a second Linux, on a separate partition, and chose
"create RAID partition", and to *not* format it. After that, I couldn't
mount it any
Help me please
I am Korean and My English is poor
very...sorry
my name is jongyeob kim
I make Linux Server
this Server use DMA66 and Software Raid
one is 20 GiGa HDD ( DMA 33 )
two is 40 GiGa HDD ( DMA 33 )
three is CDROM
four is 40 GiGa HDD ( DMA 33 )
five is 40 GiGa HDD
Hello
I have installed a raid 1(mirror) partition.
/ = /dev/md0
/boot = /dev/hda1 and /dev/hdc1 (handmade mirror)
Here is my problem: I have destroyed my Bootblock. Now I can´t access
the root-Partition in order to make a new one. The only thing that I can
reach is the kernel i had put
Hello
I have installed a raid 1(mirror) partition.
/ = /dev/md0
/boot = /dev/hda1 and /dev/hdc1 (handmade mirror)
Here is my problem: I have destroyed my Bootblock. Now I can't
access the root-Partition in order to make a new one. The only thing
that I can reach is the kernel
controller (PDC20262) . I've also tried this with 4 and 8 Maxtor 40GB
drives (94098U8) and other PCI DMA66 controllers (HPT366 CMD648)
with much the same results.
Any help or suggestions will be much appreciated.
Also the latest raidtools and patches I have been able to find at
kernel.org are dated
]
Subject: PLEASE HELP: mkraid aborts!
I am trying to make a software raid5, and it seems no matter what I do
mkraid aborts.
My mkraid output looks like this:
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hde2, 5269320kB, raid superblock at 5269248kB
disk 1: /dev/hdf2
it to work? This last possibility would be unfortunate, because
it will be difficult to apply both a RAID patch and a Promise Ultra/66
patch.
Thanks for your help,
e
--
This message was my two cents worth. Please deposit two cents into my
e-gold account by following this link:
http
Erich wrote:
Any clues? I feel like I've done everything according to the
instructions, and I feel like I'm very close to getting it to work,
but it's still not working. Have I left out something important in
the kernel config? Or did I need a RAID patch to the 2.2.14 kernel to
get it
On Fri, 14 Apr 2000, Tony Grant wrote:
Erich wrote:
Any clues? I feel like I've done everything according to the
instructions, and I feel like I'm very close to getting it to work,
but it's still not working. Have I left out something important in
the kernel config? Or did I
I'm the one who originally posted the question, and now I may have an
answer (with help from the list):
I've tried doing that, 2.2.14 adding both patchs.
mostly they failed everywhere. then once I did it get it in, and compile,
it still never worked right, I change to 2.3 kernel, even tho
It's definitely possible to use 2.2.14 with the Software RAID patch
and with the Promise Ultra/66 patch at the same time. I'm doing it
right now. Download the plain-vanilla 2.2.14 kernel. Apply this
patch first:
http://www.kernel.org/pub/linux/kernel/people/hedrick/old/ide.2.2.14
Ok, here are the notes that I wrote to myself of how to get Software
RAID and the Promise Ultra/66 in the same kernel:
1. Don't use the RedHat version of the 2.2.14 kernel. It has
too many patches, so the other patches won't work.
2. Do unpack the linux-2.2.14.tar.gz file.
3. Apply the
wrote:
I'm the one who originally posted the question, and now I may have an
answer (with help from the list):
I've tried doing that, 2.2.14 adding both patchs.
mostly they failed everywhere. then once I did it get it in, and compile,
it still never worked right, I change to 2.3 kernel
On Tue, 11 Apr 2000, Darren Nickerson wrote:
On Tue, 11 Apr 2000, "Lance" == D. Lance Robinson wrote:
Lance So, if the md driver doesn't fail a drive that is because the lower
Lance levels have taken care of all the nitty details and have supposedly
Lance performed the requested
On Mon, 10 Apr 2000, "Darren" == Darren Nickerson wrote:
Darren 4. is there some way to mark this disk bad right now, so that
Darren reconstruction is carried out from the disks I trust? I do have a hot
Darren spare . . .
Things are more and more frightening:
EXT2-fs warning (device
I hope this helps. See below.
Lance.
my questions are:
2. the disk seems to be "cured" by re-enabling DMA . . . but what is the state
of my array likely to be after the errors above? Can I safely assume this was
harmless? I mean, they WERE write errors after all, yes? Is my array still
On Tue, 11 Apr 2000, "Lance" == D. Lance Robinson wrote:
Lance So, if the md driver doesn't fail a drive that is because the lower
Lance levels have taken care of all the nitty details and have supposedly
Lance performed the requested data transfer correctly. As long as the actual
Darren Nickerson wrote:
+ 4. is there some way to mark this disk bad right now, so that
+ reconstruction is carried out from the disks I trust? I do have a hot
+ spare . . .
Lance You can use the 'raidhotremove' utility.
This has never worked for me when the disk had not been
On Tue, 11 Apr 2000, "Lance" == D. Lance Robinson wrote:
Lance In that case, I would:
Lance 1) Do a normal shutdown of the machine
Lance 2) Disconnect the bad drive
Lance 3) Power up the system
*grin* now I'm sure I read somewhere that RAID was meant to lessen the number
of reboots
On Mon, 10 Apr 2000, "Darren" == Darren Nickerson wrote:
array.
Ack - too late:
Apr 11 09:58:24 osmin kernel: attempt to access beyond end of device
Apr 11 09:58:24 osmin kernel: 21:01: rw=0, want=318373889,
limit=33417184 Apr 11 09:58:24 osmin kernel: dev 09:01 blksize=4096
Folks,
I've been running four 37GB IBM drives in a Raid5 array for several months now.
They're driven by two Promise Ultra66 ide controllers, and I'm running
2.2.13ac2 with Andre Hedrick's ide.2.2.13.1999.patch (see another thread -
I'm considering upgrading but am not sure of the current
I've posted the following message in the newsgroups
and a couple other places, without much success. I
got this address as I was about to try the mkraid
--force option when I saw this address. Executing
the actual command frightened me away by saying it
was about to destroy the contents of
I am trying to get RAID-1 running with dual SCSI drives.
I read the Software-RAID HOWTO and followed the steps outlined
there. However.. when I get to the part to run mkraid,
it returns the following..
# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0:
-Original Message-
From: Pete Rossi [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 31, 2000 3:34 PM
To: [EMAIL PROTECTED]
Subject: Need help with software RAID-1
I am trying to get RAID-1 running with dual SCSI drives.
I read the Software-RAID HOWTO and followed the steps
hallo
I´m trying to get a RAID5 system running but i`ve got problems setting up the
/dev/md. I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc
version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Mon Nov 8 15:51:29 CET 1999 , and
raidtools v.0.90.2 -Alpha, 27th
[Wolfram Lassnig]
I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED])
is it the wrong kernel patch (SuSE does not respond on my queries)
SuSE doesn't patch their kernels
Excellent software raid howto:
http://linuxdoc.org/HOWTO/Software-RAID-HOWTO.html
kernel 2.2.14
Wolfram Lassnig wrote:
hallo
I´m trying to get a RAID5 system running but i`ve got problems setting up the
/dev/md. I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc
version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Mon Nov 8 15:51:29 CET 1999 , and
raidtools
Hi!
I was told several times now to use LILO with the Redhat patches.
But my favorite distribution was/is/will be Debian, and I didn't find these
patches anywhere on the net..
So please post them to the list or directly to me (if they're too large)..
THX!
Thomas
At 09:36 03.03.00, Thomas Rottler wrote:
I was told several times now to use LILO with the Redhat patches.
But my favorite distribution was/is/will be Debian, and I didn't find these
patches anywhere on the net..
You can get the patch from ftp://ftp.sime.com/pub/linux/lilo.raid1.gz
Bye, Martin
I'm trying to set up a Raid 1 configuration on my linux box, and I always
get the same error, whatever the kernel I'm using.
I first tried with a Mandrake 6.1 (kernel 2.2.13-15 updated to some
version > 2.2.13-22), then with a Mandrake 7 (kernel 2.2.14).
My configuration is : PII 450, 128Mo
ais wrote:
I'm trying to set up a Raid 1 configuration on my linux box, and I
always get the same error, whatever the kernel I'm using.
I first tried with a Mandrake 6.1 (kernel 2.2.13-15 updated to some
version 2.2.13-22), then with a Mandrake 7 (kernel 2.2.14).
My configuration is
At 19:14 29.02.00, Gregory Leblanc [EMAIL PROTECTED] wrote:
If you're running some
other distro, you need to be running RAID 0.90, and LILO with the redhat
patches.
Just a small warning about the lilo - rai1 patches:
1) The patch does NOT handle arrays in degraded mode correctly (check for
Hi!
I've another idea to run a RAID 1 '/' partition:
(I assume that CONFIG_AUTODETECT_RAID is available.)
Recently I found out that you can access the individual real devices of a RAID
array (if it's not active). This way I could tell the kernel to mount my RAID
1 device as rootdir
Dunno what all the fuzz is about... But i'm running 2 raid1 arrays. One
16mb /dev/md0
for boot, and one 15gb /dev/md1 as root. If u go into rh6.1's graphic
install u can choose
if u want an ext2 or a raid device. Go ahead and try it out. Worked
perfectly here, just
2day i janked out the
The solution is so simple after I got the RH 6.1 CDROM with new graphical
installer. I did finish it in so easy way. Thank you for your helps.
George
Kelina wrote:
Dunno what all the fuzz is about... But i'm running 2 raid1 arrays. One
16mb /dev/md0
for boot, and one 15gb /dev/md1 as root.
-Original Message-
From: Thomas Rottler [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 29, 2000 1:43 AM
To: Linux RAID
Subject: Re: ask help RAID1, 2 SCSI Drive, RedHat6.1
On Mon, Feb 28, 2000 at 05:40:11PM -0600, George Liu wrote:
This is a simple question
On Tue, Feb 29, 2000 at 10:14:35AM -0800, Gregory Leblanc wrote:
I think you've got them mixed up. It makes the most sense to be able to
boot from a RAID1 (mirror), next most to be able to boot from LINEAR, and
the least ammount of sense to be able to boot from a RAID0 or RAID5, because
of
-Original Message-
From: Thomas Rottler [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 29, 2000 2:44 PM
To: Linux RAID
Subject: Re: ask help RAID1, 2 SCSI Drive, RedHat6.1
On Tue, Feb 29, 2000 at 10:14:35AM -0800, Gregory Leblanc wrote:
I think you've got them mixed up
Hi
This is a simple question but is difficult for me. I want to install a
bootable-RAID 1 for 2 SCSI hard drive in the same controller. The kernel
is 2.2.12 accompanying OS Redhat 6.1. Here is my RAID plan
disk partition mount pt. sizedevice
1
Quoted mail:
Hi James,
[ Saturday, February 12, 2000 ] David Cooley wrote:
As the error message points out, you need to type "mkraid --[snip]
/dev/md0"
1) as the error message also points out, that option is NOT to be sent
in email :) privately? perhaps... a well-archived list? no :)
[ Monday, February 14, 2000 ] Jens Klaas wrote:
[ Saturday, February 12, 2000 ] David Cooley wrote:
As the error message points out, you need to type "mkraid --[snip]
/dev/md0"
1) as the error message also points out, that option is NOT to be sent
in email :) privately?
Hi ,
I have linux 2.2.13 (SuSE) and a problem with a raid1.
I included 2 new SCSI-HD, in my system, created 3 Partitions sda1..3,
sdb1..3 (3x3GB), and i will use only a part of this, so I created
/etc/raidtab
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
Please help me trouble shoot the RAID installation.
I am trying to concatenate 2 scsi drives of 50 GB each using software RAID
level 1 in Linux 6.1.
1. I created 2 raid partitions during installation on scsi drives a and
b. These are /dev/sda5 and /dev/sdb1 and of equal number of blocks
Title: RE: help, help, help
Here is the main clue as to what is wrong **
#cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
Any time you see a /proc/mdstat listing md0 through md3
[ Monday, January 17, 2000 ] Holger Kiehl wrote:
On Fri, 14 Jan 2000, James Manning wrote:
Just for clarification, the default (stock) RH 6.x *is* patched
for 0.90 RAID (the 6.1 installer even allows you to install to a
s/w raid1!)
And raid0 or raid5, only /boot needs to be raid1.
The
[ Tuesday, January 18, 2000 ] KS wrote:
We recently had an ups failure and some of our servers have crashed. When
reviewing the logs on the maschines I have spotted messages like:
kernel: md: serializing resync, md0 has overlapping physical units with md1!
..
kernel: md: serializing
Hi,
We recently had an ups failure and some of our servers have crashed. When
reviewing the logs on the maschines I have spotted messages like:
kernel: md: serializing resync, md0 has overlapping physical units with md1!
..
kernel: md: serializing resync, md2 has overlapping physical units with
On Fri, 14 Jan 2000, James Manning wrote:
[ Friday, January 14, 2000 ] jesse nelson wrote:
I had the same problem the default kernel is not patched on 6.0 or 6.1
installs although they include the 0.90 tools. I think the up2date RPM's are
though. I just moved to Mandrake 7.Beta and it
I haven't dealt with linear, but the stock RH kernel comes
with 0.90 raid so I'm not sure where the issue is here.
- Forwarded message from "Prof. Mad Crazy" [EMAIL PROTECTED] -
From: "Prof. Mad Crazy" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Raid Help
Date:
Many thanks to all who helped me with the RAID setup.
I had the 2.2.13 kernel patched successfull. Kernel build was also o.k.
But during boot a problem arises: When i construct a RAID1 from hdb1
and hdc1 including autodetection, the kernel panics when trying to
mount the root fs on hda1. I
. When you first asked for help you
were building the mirror on /dev/sda1 and /dev/sdb1. Now you're building it on
/dev/hdb1 and /dev/hdc1. This problem may be caused by an error in your new
configuration. We could do with knowing what your setup is (raidtab, fstab,
mdstat, output of df and dmesg etc
-Original Message-
From: Kelina
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
Bruno Prior wrote:
Have you patched the kernel with the appropriate raid-patch? Vanilla kernels
only support old-style RAID (i.e. raidtools-0.42 or earlier). You have to patch
and rebuild them with the raid-patch to enable support for raidtools-0.90. You
can apply the 2.2.11 patch to 2.2.13
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
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.2.13
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
kinda
attempting
to write beyond the end of the device?
Please help.
Thanks
--Drew
Dec 27 16:02:48 cwb-jumbo kernel: 929388176 sector=-436190944 size=1024 count=1
Dec 27 16:02:48 cwb-jumbo kernel: interrupting MD-thread pid 8
Dec 27 16:02:48 cwb-jumbo ker
of drives changes.
So, what would be the best way (other than full DAT backup) to replace
the disk and get system back as soon as possible? Can I move sdb to be
sda and install new disk as sdb, and the reconstruct RAID or does sdb
must stay as sdb? Howto does not help too much, it seems to refer to
(other than full DAT backup) to replace
the disk and get system back as soon as possible? Can I move sdb to be
sda and install new disk as sdb, and the reconstruct RAID or does sdb
must stay as sdb? Howto does not help too much, it seems to refer to
newer RAID than one on that computer.
I
failed ...
do_md_run() returned -22
unbindsdc5,0
export_rdev(sdc5)
md0 stopped.
... autorun DONE.
eth0: Auto-Negotiation unsuccessful, trying force link mode
eth0: Link has been forced up using internal transceiver at 10Mb/s, Half Duplex.
Can anyone help me? I think this is something easy, but I jus
lf
Duplex.
Can anyone help me? I think this is something easy, but I just
don't see what I'm doing wrong.
Thanks much,
-Robb
--
--- \*/ ---
Robert S. Dubinski, Computer Systems Technician, M
Thanks for the clear explanation. I gave it a try, but it didn't
work. It may be because I used the 'old' raid as compiled into the
standard 2.2.13 kernel.
That'll be exactly why. Don't use the old RAID code unless you have a good
reason to.
I've been very confused by the various raid
docs
On Thu, Dec 09, 1999 at 11:09:18PM +, Lyndon David wrote:
I am just setting up a system and have put in two identical disks as hda and hdc.
fdisk
sees hda as having 255 heads and 63 sectors but hdc as having 16 heads and 63
sectors !
in addition to what has been said try zeroing the
Hi,
i had the same problem and i found the following solution:
try to delete or set the "dos compatibility flag" on both drives.
You have to do this with fdisks c command.
For mee it looks as if one of your drives has this flag set and the another not.
I hope this helps
Bruno Prior wrote on 3/12/99 9:39:
This is a little unorthodox,
but try the following
Thanks for the clear explanation. I gave it a try, but it didn't work. It may be
because I used the 'old' raid as compiled into the standard 2.2.13 kernel. I've been
very confused by the various raid docs
make
the partitions the same. The bios (ami) says 16 heads so why does the kernel see them
as
different. They are definitely the same drive. They even have sequential serial
numbers.
Any help most appreciated.
--
Lyndon David Internet and Intranet development
Sentinet Ltd http
I had _exactly_ the same problem. The only way I found around it was to
go into the BIOS and manually set both disks to NORMAL instead of LBA.
Attempting to set both to LBA didn't work. This is with RedHat 6.0 with
the 2.2.5-22 kernel. Perhaps this is fixed in a later kernel?
--
Stephen
the same. The bios (ami) says 16 heads so why does the kernel see
them as
different. They are definitely the same drive. They even have sequential serial
numbers.
Any help most appreciated.
--
Lyndon David Internet and Intranet development
Sentinet Ltd http://www.sentinet.co.uk
I had exactly the same experience with 2.2.13ac3 kernel, only setting disks to
NORMAL made fdisk to see them as two identical disks.
Does this influence the speed of disks in any way ?
On pi±, 10 gru 1999, Stephen Walton wrote:
I had _exactly_ the same problem. The only way I found around it
Hi,
I am trying to configure a
raid1 on my Linux box.My system configuration is as follows:
Linux kernel: 2.0.36-07
two IDE disks: hda and hdc
etc/mdtab file: /dev/md0 /dev/hda2
/dev/hdc1
and the file /proc/mdstat looks fine.
But when I tried:
mdadd -a and I got the following error:
]]On Behalf Of David Cunningham
Sent: 03 December 1999 02:26
To: Jim Ford; linux-raid
Subject: Re: Help on root fs using raid-0
I've done this on raid-1. I assume the procedure for raid-0 will be the
same. Here is how I do it. I'm not guaranteeing this is the best way:
First I'll make
1 - 100 of 207 matches
Mail list logo
