Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed, sed: -e expression #1, char 1: unterminated address regex, procmail + change subject, w2ksp4.exe download

Links

XODOX
Impressum

#1: Fedora 2.0 - raid1 not working

Posted on 2004-11-09 20:08:22 by Jesse Burkhardt

I am new to raid installations. I have installed Fedora 2.0 onto a
system with two identical drives that I configured to be a raid1 mirror
through the disk druid interface. I created partition mirrors for both
the /boot partition (md0) and the / partition (md1). Then I created same
sized, non-mirrored swap partitions on each of the identical drives.
After the installation process, I found that I could boot with both
physical drives online and only one of the two physical drives when
booting in a single drive (failure simulation) mode.

I am wondering if there is a required kernel module that is not loaded
or compiled into the default Fedora 2.6 kernel.

When I look into the process list I see processes called md0_raid and
md1_raid. I did not run the raidstart command but assume that it
probably has been run.

Also here are a few raid file listings:

/etc/raidtab

raiddev /dev/md1
raid-level 1
nr-raid-disks 2
chunk-size 256
persistent-superblock 1
nr-spare-disks 0
device /dev/hda3
raid-disk 0
device /dev/hdd3
raid-disk 1
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
chunk-size 256
persistent-superblock 1
nr-spare-disks 0
device /dev/hda1
raid-disk 0
device /dev/hdd1
raid-disk 1

And /proc/mdstat

Personalities : [raid1]
md1 : active raid1 hda3[0]
242958848 blocks [2/1] [U_]

md0 : active raid1 hda1[0]
104192 blocks [2/1] [U_]

unused devices: <none>


Thanks for any help.
--

Jesse Burkhardt, Cambridge MA
jesse@skybuilders.com (w) 617-876-5680
aerogoose.com (h) 617-354-5523
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#2: Re: Fedora 2.0 - raid1 not working

Posted on 2004-11-09 20:22:19 by Jurriaan

From: Jesse Burkhardt <jesse@skybuilders.com>
Date: Tue, Nov 09, 2004 at 02:08:22PM -0500
> After the installation process, I found that I could boot with both
> physical drives online and only one of the two physical drives when
> booting in a single drive (failure simulation) mode.
>

I take it this is your question? And do I read correctly you mean that
you cannot boot if you disconnect drive A, but can boot if you
disconnect drive B?

In that case, could you please give some more details on 'could boot'.
Is this a problem with your bootloader (lilo, grub or other?) or with
the kernel?

For the record: here's my /boot/grub/menu.lst, which allows me to boot
from both drives of my mirrored raid-1 root partition.

timeout 15
default 0
color white/blue white/red
fallback 1

title GNU/Linux (Debian working 2.6.9-mm1 kernel /dev/hda (part of raid-1 system))
root (hd0,0)
kernel /boot/vmlinuz-269mm1 root=/dev/md3 video=radeonfb:1600x1200-32@85 softrepeat=1

title GNU/Linux (Debian working 2.6.9-mm1 kernel /dev/hdb (part of raid-1 system))
root (hd5,0)
kernel /boot/vmlinuz-269mm1 root=/dev/md3 video=radeonfb:1600x1200-32@85 softrepeat=1 floppy=no_acpi

title Memtest86
root (hd0,0)
kernel /boot/memtest86.bin

title Floppy
root (fd0)
chainloader +1

Good luck,
Jurriaan
--
"Evayne told you this."
"Evayne," he said softly, "has forced me to bear witness to much in my life."
Michelle West - Sea of Sorrows
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 0.34
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#3: Re: Fedora 2.0 - raid1 not working

Posted on 2004-11-09 20:41:27 by Jurriaan

From: Jesse Burkhardt <jesse@skybuilders.com>
Date: Tue, Nov 09, 2004 at 02:30:19PM -0500
> Hi Jurriaan,
>
> Your interpretation of my scenerio is correct. Boot is successful when
> both drives A and B are present; also when just drive B is present, but
> not when just drive A is present.
>
> I am using a grub loader which ennumerates thusly:
>
> /boot/grub/menu.lst
>
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title Fedora Core (2.6.5-1.358)
> root (hd0,0)
> kernel /vmlinuz-2.6.5-1.358 ro root=/dev/md1 rhgb quiet
> initrd /initrd-2.6.5-1.358.img
>
I'm still not clear on what happens when boot isn't succesful. Do you
get error messages from grub? If so, what do they say?

Also note that while my menu.lst works fine and lets me boot from both
drives, I haven't tested disconnecting one. I know where my data is, and
my backup, and in case of trouble, I can (and have tested that I can)
boot from a Knoppix-cd.

Kind regards,
Jurriaan
--
and even as Pug spoke, he knew the answer to his question.
"Whom must I seek?"
The girl's eyes seemed to pierce his soul. Calmly she said,
"You must find Macros the Black."
Raymond E Feist - A Darkess at Sethanon
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 0.32
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#4: Re: Fedora 2.0 - raid1 not working

Posted on 2004-11-09 20:57:06 by Jurriaan

From: Jesse Burkhardt <jesse@skybuilders.com>
Date: Tue, Nov 09, 2004 at 02:48:25PM -0500
> What happens in failure mode is that the computer succeeds in completing
> its POST (power on self test) cycle but never goes on to load the OS.
>
> PS - Another user, [1]olchansk@sam.triumf.ca, says that kernel 2.6 is
> broken as to raid1, but it has been patched, but not yet in the Fedora
> version.
>
I'm not sure if current BIOS code still requires a single 'active'
partition on a single drive to boot. If it still does, that would
explain what happens to you.

As for the kernel being at fault - perhaps, I never noticed anything,
but if even grub doesn't come on, it surely isn't the kernel's fault.

Good luck,
Jurriaan
--
REAL LIFE MANAGEMENT 'DILBERT QUOTATIONS':
5: Doing it right is no excuse for not meeting the schedule. No one will
believe you solved this problem in one day! We've been working on it
for months. Now, go act busy for a few weeks and I'll let you know
when it's time to tell them. (R&D supervisor, Minnesota Mining and
Manufacturing/3M Corp.)
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 1.17
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message

#5: More: Fedora 2.0 - raid1 not working

Posted on 2004-11-09 23:14:25 by Jesse Burkhardt

A little more info - this is excerpted from dmesg:

md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdd3 ...
md: adding hdd3 ...
md: hdd1 has different UUID to hdd3
md: adding hda3 ...
md: hda1 has different UUID to hdd3
md: created md1
md: bind<hda3>
md: bind<hdd3>
md: running: <hdd3><hda3>
md: kicking non-fresh hdd3 from array!
md: unbind<hdd3>
md: export_rdev(hdd3)
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md1 stopped.
md: unbind<hda3>
md: export_rdev(hda3)
md: considering hdd1 ...
md: adding hdd1 ...
md: adding hda1 ...
md: created md0
md: bind<hda1>
md: bind<hdd1>
md: running: <hdd1><hda1>
md: kicking non-fresh hdd1 from array!
md: unbind<hdd1>
md: export_rdev(hdd1)
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<hda1>
md: export_rdev(hda1)
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
md: raid1 personality registered as nr 3
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hda1 ...
md: adding hda1 ...
md: adding hdd1 ...
md: hda3 has different UUID to hda1
md: hdd3 has different UUID to hda1
md: created md0
md: bind<hdd1>
md: bind<hda1>
md: running: <hda1><hdd1>
md: kicking non-fresh hdd1 from array!
md: unbind<hdd1>
md: export_rdev(hdd1)
raid1: raid set md0 active with 1 out of 2 mirrors
md: considering hda3 ...
md: adding hda3 ...
md: adding hdd3 ...
md: created md1
md: bind<hdd3>
md: bind<hda3>
md: running: <hda3><hdd3>
md: kicking non-fresh hdd3 from array!
md: unbind<hdd3>
md: export_rdev(hdd3)
raid1: raid set md1 active with 1 out of 2 mirrors
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdd3 ...
md: adding hdd3 ...
md: hdd1 has different UUID to hdd3
md: md1 already running, cannot run hdd3
md: export_rdev(hdd3)
md: considering hdd1 ...
md: adding hdd1 ...
md: md0 already running, cannot run hdd1
md: export_rdev(hdd1)
md: ... autorun DONE.

Thanks again.


--

Jesse Burkhardt, Cambridge MA
jesse@skybuilders.com (w) 617-876-5680
aerogoose.com (h) 617-354-5523

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Report this message