Re: /dev/md* Device Files

On Wednesday 26 January 2005 07:28, Gordon Henderson wrote: On Tue, 25 Jan 2005, Steve Witt wrote: I'm installing a software raid system on a new server that I've just installed Debian 3.1 (sarge) on. It will be a raid5 on 5 IDE disks using mdadm. I'm trying to create the array with 'mdadm

RE: Fun with onboard raid in dell poweredge 2650

At 09:07 +0100 1/25/05, Bene Martin wrote: We have here a dell poweredge 2650 with the dell perc3/di onboard raid running suse enterprise linux 9. The install process went smoothly but we would like to have a way to check on the raid without having to physically see if a hard drive has

Re: Software RAID 0+1 with mdadm.

On Tue, Jan 25, 2005 at 02:28:21PM -0800, Brad Dameron wrote: Everything seems ok after boot. But again no /dev/md0 in /proc/mdstat. But then if I do a mdadm --assemble --scan it will then load /dev/md0. there is a bug in mdadm, see my mail patches for mdadm 1.8.0 or wait for 1.9.0 L. -- Luca

Re: /dev/md* Device Files

On Wed, 26 Jan 2005, Andrew Walrond wrote: On Wednesday 26 January 2005 07:28, Gordon Henderson wrote: On Tue, 25 Jan 2005, Steve Witt wrote: I'm installing a software raid system on a new server that I've just installed Debian 3.1 (sarge) on. It will be a raid5 on 5 IDE disks using mdadm. I'm

booting from a HW RAID volume

Hello, I'm using a 3Ware 9500 12 Hardware RAID controller that has 12 of 250GB S-ATA drives (total storage = 2.75TB). To my 64bit FC3 box, this looks like a single huge SCSI disk (/dev/sda). I used parted to create GPT partitions on it, (because nothing else would work on a volume that big).

Re: /dev/md* Device Files

On Wednesday January 26, [EMAIL PROTECTED] wrote: A useful trick I discovered yesterday: Add --auto to your mdadm commandline and it will create the device for you if it is missing :) Well, it seems that this machine is using the udev scheme for managing device files. I didn't realize

RE: booting from a HW RAID volume

Many hardware based RAID systems allow you to create more that 1 virtual disk. This is done with luns. If your hardware supports it, you could split your monster disk (2.75TB) into 2 or more virtual disks. The first would be very small, just for boot, or maybe the OS. Or you could split the

RE: Software RAID 0+1 with mdadm.

This bug that's fixed in 1.9.0, is in a bug when you create the array? ie do we need to use 1.9.0 to create the array. I'm looking to do the same but my bootdisk currently only has 1.7.soemthing on it. Do I need to make a custom bootcd with 1.9.0 on it? Thanks, -ryan -Original

RE: Software RAID 0+1 with mdadm.

On Tue, 2005-01-25 at 15:04, Guy wrote: For a more stable array, build a RAID0 out of 2 RAID1 arrays. Like this: mdadm --create /dev/md1 --level=1 --chunk=4 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create /dev/md2 --level=1 --chunk=4 --raid-devices=2 /dev/sdd1 /dev/sde1 mdadm

Re: megaraid mbox: critical hardware error on new dell poweredge 1850, suse 9.2, kernel 2.6.8

Hi Olivier, I'm trying to get a quite standard suse linux 9.2 setup working on a brand new dell poweredge 1850 with 2 scsi disks in raid1 setup. Installation went completely fine, everything is working. But now (and every time), after 2-3h of uptime and some high disk I/O load (rsync of

hda: irq timeout: status=0xd0 { Busy }

Hi I'm new to this list, but I have a lot of projects that involve RAID and Linux. And consequently, a lot of questions. (But maybe a few answers too :) I have a 3 disk RAID5 array, and one of the member was recently rejected, and I'm trying to get to the bottom of it. I reformatted the

RE: Software RAID 0+1 with mdadm.

On Wednesday January 26, [EMAIL PROTECTED] wrote: This bug that's fixed in 1.9.0, is in a bug when you create the array? ie do we need to use 1.9.0 to create the array. I'm looking to do the same but my bootdisk currently only has 1.7.soemthing on it. Do I need to make a custom bootcd with

Re: Software RAID 0+1 with mdadm.

On Tuesday January 25, [EMAIL PROTECTED] wrote: Been trying for days to get a software RAID 0+1 setup. This is on SuSe 9.2 with kernel 2.6.8-24.11-smp x86_64. I am trying to setup a RAID 0+1 with 4 250gb SATA drives. I do the following: mdadm --create /dev/md1 --level=0 --chunk=4

RE: Software RAID 0+1 with mdadm.

Sorry, I did not intend this to be the solution to your problem. Just a much more stable method for creating the 1+0 array. With this method, losing 1 disk only requires re-syncing 1 disk. With the array as a 0+1, if you lose 1 disk, you lose the whole RAID0 array, which then requires

RE: irq timeout: status=0xd0 { Busy }

Why would you fsck the failed member of a RAID5? You said format, please elaborate! You should verify the disk is readable. It looks like your disk is bad. But a read test would be reasonable. Try this: dd if=/dev/had of=/dev/null bs=64k It should complete without errors. It will do a full