From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Cc: "Richard B. Pyne" <rpyne@kinfolk.org>
Subject: Re: system startup hangs
Date: Thu, 8 Dec 2011 12:21:54 +0000 [thread overview]
Message-ID: <20111208122154.GA12445@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <4EDFEACD.3010806@kinfolk.org>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
On Wed Dec 07, 2011 at 03:38:05PM -0700, Richard B. Pyne wrote:
> Please forgive me if I ask stupid questions, I am fairly new to linux
> raid and most of the documentation I can find is severely outdated
> and/or written for someone who already understands linux raid.
>
> I have successfully built a set raid 6 array with 4 drives and have
> copied my system partitions onto the raid drives. I then reboot with
> root=/dev/md0.
>
> Everything looks like it is working right up through:
>
> md/raid:md0 raid level 6 active with 4 out of 4 devices, algorithm 2
> md0: detected capacity change from 0 to 1000131788
> md: autorun DONE.
> md0: unknown partition table
> EXT3-fs (md0): error: couldn't mount because of unsupported optional
> features
> EXT2-fs (md0): error: couldn't mount because of unsupported optional
> features
> EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
> VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
> freeing unused kernel memory: 472k freed
>
>
> at which point it just hangs. No more disk access, no more messages.
>
>
> The system has 5 WD Caviar Black 500GB drives. I did the linux install
> on the first drive and built the other 4 drives into the raid system,
> planning to move everything (except the /boot partition) on to the raid
> array and then repartition everything except the /boot partition on the
> first drive and add it to the raid.
>
> I currently have md0 for / md1 for /home md2 for /usr md3 for /var and
> md4 on which I plan on running lvm to allocate to other system needs.
>
> Any advice, insights and/or direction will be greatly appreciated.
>
>
I've been bitten by this one myself recently. I suspect you've failed to
copy over the required underlying /dev entries. You need at least
/dev/console and /dev/null on the rootfs - at this stage the tmpfs
hasn't been mounted on /dev and udev hasn't created all the dev nodes.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-08 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 22:38 system startup hangs Richard B. Pyne
2011-12-07 23:00 ` NeilBrown
2011-12-07 23:24 ` Richard B. Pyne
2011-12-07 23:01 ` Mathias Burén
2011-12-07 23:19 ` Richard B. Pyne
2011-12-08 12:21 ` Robin Hill [this message]
2011-12-08 16:16 ` Richard B. Pyne
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=20111208122154.GA12445@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rpyne@kinfolk.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).