Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Paul Aviles" <paul.aviles@palei.com>
To: linux-raid@vger.kernel.org
Subject: Diff between 2.4 and 2.6 kernels for raid
Date: Mon, 17 Oct 2005 00:08:05 -0400	[thread overview]
Message-ID: <003b01c5d2d0$63601940$3224050a@avilespaxp> (raw)

I have a setup script that has worked great for configuring servers in the 
2.4 kernels. The scripts works from a pxe load, mounts a bunch of nfs drives 
and then partitions and formats the drives and later installs a rpms in a 
chroot mode. This works great for my Fedora Core 1 distribution, but when I 
changed the rpms for the CentOS it creates the partitions as needed, but 
when is time to boot the newly created server is gives the following error 
right after it starts checking the root filesystem

fsck.ext3 /dev/md1
invalid argument while trying to open /dev/md1

and it drops you to a shell to run maintenance on the drive. It passes all 
the test so I know the partition and formats are ok.  Are there differences 
between the way the 2.4 and 2.6 kernels handled this or anything else to 
look for?

Here is my configuration.

Thanks

Paul

/etc/fstab
/dev/md1              /         ext3    defaults                          1 
1
/dev/md2              /var      ext3    defaults,nosuid                   3 
3
/dev/md3              swap      swap    defaults                          0 
0
/dev/md4              /home     ext3    defaults,usrquota,grpquota        4 
4
none                  /proc     proc    defaults                          0 
0
none                  /dev/pts  devpts  gid=5,mode=0620                   0 
0
none                  /dev/shm  tmpfs   defaults                          0 
0

/etc/raidtab
raiddev               /dev/md1
raid-level            0
nr-raid-disks               1
nr-spare-disks        0
persistent-superblock 1
chunk-size      64
device  /dev/hda1
raid-disk       0

raiddev               /dev/md2
raid-level            0
nr-raid-disks               1
nr-spare-disks        0
persistent-superblock 1
chunk-size      64
device  /dev/hda2
raid-disk       0

raiddev               /dev/md3
raid-level            0
nr-raid-disks               1
nr-spare-disks        0
persistent-superblock 1
chunk-size      64
device  /dev/hda3
raid-disk       0

raiddev               /dev/md4
raid-level            0
nr-raid-disks               1
nr-spare-disks        0
persistent-superblock 1
chunk-size      64
device  /dev/hda4
raid-disk       0

/boot/grub/grub.conf
default=0
timeout=10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title CentOS (2.6.9-11.EL)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.9-11.EL ro root=/dev/hda1 acpi=on
        initrd /boot/initrd-2.6.9-11.EL.img



                 reply	other threads:[~2005-10-17  4:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='003b01c5d2d0$63601940$3224050a@avilespaxp' \
    --to=paul.aviles@palei.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