From: Jurriaan <thunder7@xs4all.nl>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: [SOLVED!] Re: raid-0/reiserfs problem; file system not recognized after reboot
Date: Thu, 30 Jan 2003 16:00:47 +0100 [thread overview]
Message-ID: <20030130150047.GA1017@middle.of.nowhere> (raw)
In-Reply-To: <20030130130041.GA21637@codemonkey.org.uk>
From: Dave Jones <davej@codemonkey.org.uk>
Date: Thu, Jan 30, 2003 at 01:00:41PM +0000
> On Thu, Jan 30, 2003 at 01:42:24PM +0100, Jurriaan wrote:
>
> > umount /dev/md0
> > umount /dev/md1
> > raidstop /dev/md0
> > raidstop /dev/md1
> > dd if=/dev/zero of=/dev/hdi bs=512 count=1
> > dd if=/dev/zero of=/dev/hdk bs=512 count=1
> > fdisk /dev/hdi < /root/fdisk.in
> > fdisk /dev/hdk < /root/fdisk.in
> > mkraid --really-force /dev/md0
> > mkraid --really-force /dev/md1
>
It turned out the kernel I did this with was compiled like this:
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=m
# CONFIG_MD_RAID1 is not set
CONFIG_MD_RAID5=m
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
# CONFIG_BLK_DEV_DM is not set
and those modules weren't loaded. After recompiling the kernel with all
raid-options on and in the kernel, it works.
It's strange, however, that you can create a raid partition without raid
support until you reboot.
You'd expect to have 'mkraid' say:
'no RAID support in kernel - aborting'
or something like that.
Kind regards,
Jurriaan
--
"Witness the strategy of silence - while the intended victims unravel each
other in pointless, divisive discourse. Oh yes, I have learned much from
Tremorlor."
Steven Erikson - Deadhouse Gates
GNU/Linux 2.4.21-pre3-ac5 SMP/ReiserFS 1x2824 bogomips load av: 0.09 0.13 0.07
prev parent reply other threads:[~2003-01-30 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 12:42 raid-0/reiserfs problem; file system not recognized after reboot Jurriaan
[not found] ` <20030130130041.GA21637@codemonkey.org.uk>
2003-01-30 13:30 ` Jurriaan
2003-01-30 15:00 ` Jurriaan [this message]
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=20030130150047.GA1017@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@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