---Reply to mail from Stephen about "RAID Error":
> I am setting up raid and gert the error
>
> /dev/md0: invalid argumnet
I am not sure if that applies to you, however I have seen some
RedHat-distributions without a /dev/md0 device node. Check if it's there...
Tho
I am setting up raid and gert the error
/dev/md0: invalid argumnet
can you point me in the right direction ???
[EMAIL PROTECTED]
Hi there!
A great 'thank you' to all who destroyed my fear.
Regards
Hans-Günter
On Thu, Apr 27, 2000 at 05:30:15PM +0200, Hans-G=FCnter?= Lütke Uphues wrote:
>
> Hi!
>
> md: serializing resync, md0 has overlapping physical with md2!
> md: serializing resync, md1 has overlapping physical with md2!
dont worry it says that md0 md1 and md2 are on the same physical disk(s)
so i
Hi!
I just booted my Linux box running kernel 2.2.14 using raid-2.2.14-B1
and raidtools-19990824-0.90. Because this was the first boot after
the system crashed yesterday evening, a lot of resync and filesystem
check had to be done. Within these resync procedures for the raid0
and raid5 volumes 2
Hi,
I feel stupid. Trying to fsck a drive in readonly mode could cause
problems... duh.
It's too late. I'll be getting some sleep now. Sorry for the bother,
everyone.
- David Harris
Principal Engineer, DRH Internet Services
David Harris
Principal Engineer, DRH Internet Services
-Original Message-
From: David Harris [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 21, 1998 1:01 AM
To: MOLNAR Ingo [[EMAIL PROTECTED]]; [EMAIL PROTECTED]
Subject:Raid error?
Hi,
Somehow my server ended up re
Ingo [[EMAIL PROTECTED]]; [EMAIL PROTECTED]
Subject:Raid error?
Hi,
Somehow my server ended up rebooting (how I don't know) and failed when
trying to fsck the filesystem on one of my raid devices. Have _no_ idea why
the system failed, but it did.
The error message on the fsck see
Hi,
Somehow my server ended up rebooting (how I don't know) and failed when
trying to fsck the filesystem on one of my raid devices. Have _no_ idea why
the system failed, but it did.
The error message on the fsck seems to indicate a problem reading the
underlying block device, /dev/md2. (It says
