linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: J Dalessandro <joe@nan0.com>
To: linux-raid@vger.kernel.org
Subject: RAID1 problem, newbie to RAID
Date: Mon, 20 Jan 2003 16:38:44 -0700	[thread overview]
Message-ID: <3E2C8884.8040003@nan0.com> (raw)

I am trying to get RAID1 working on a Debian machine with a 2.4.20 
kernel. I hope I am close, but this is my first attempt at RAID on any 
platform.

I seem to get two out of three partitions. I think my problem is in that 
my "/" partition is mounted, but I'm new to RAID and I'm not sure how to 
fix this issue. Below is my: /proc/mdstat, raidtab, fdisk -l outputs. 
What am I missing here to solve my bungled configuration?

CM:~# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hda1[0]
       96256 blocks [2/1] [U_]

md1 : active raid1 hda2[0]
       9767424 blocks [2/1] [U_]

unused devices: <none>

CM:~# cat /etc/raidtab
raiddev /dev/md2
         raid-level              1
         nr-raid-disks           2
         nr-spare-disks          0
         chunk-size              32
         persistent-superblock   1
         device                  /dev/hda3
         raid-disk               0
         device                  /dev/hdc3
         failed-disk             1

raiddev /dev/md1
         raid-level              1
         nr-raid-disks           2
         nr-spare-disks          0
         chunk-size              32
         persistent-superblock   1
         device                  /dev/hda2
         raid-disk               0
         device                  /dev/hdc2
         failed-disk             1

raiddev /dev/md0
         raid-level              1
         nr-raid-disks           2
         nr-spare-disks          0
         chunk-size              32
         persistent-superblock   1
         device                  /dev/hda1
         raid-disk               0
         device                  /dev/hdc1
         failed-disk             1

CM:~# df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda3             86437648    480844  81565840   1% /

CM:~# fdisk -l

Disk /dev/hdc: 255 heads, 63 sectors, 12161 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             1        12     96358+  fd  Linux raid autodetect
/dev/hdc2            13      1228   9767520   fd  Linux raid autodetect
/dev/hdc3          1229     12161  87819322+  fd  Linux raid autodetect

Disk /dev/hda: 255 heads, 63 sectors, 12161 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1        12     96358+  83  Linux
/dev/hda2            13      1228   9767520   82  Linux swap
/dev/hda3          1229     12161  87819322+  83  Linux
CM:~#


             reply	other threads:[~2003-01-20 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 23:38 J Dalessandro [this message]
2003-01-21  1:03 ` RAID1 problem, newbie to RAID Scott Mcdermott
  -- strict thread matches above, loose matches on Subject: below --
2003-01-21 21:57 Cress, Andrew R

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E2C8884.8040003@nan0.com \
    --to=joe@nan0.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).