From: manio <manio@skyboo.net>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: GPT partition table + RAID: kernel could not load init while root filesystem is mounted
Date: Sat, 18 Sep 2010 02:52:44 +0200 [thread overview]
Message-ID: <4C940D5C.4090408@skyboo.net> (raw)
Hello
I am trying to migrate from old root filesystem (linux raid1 on disks
with msdos partition table) to new (4K sector) disks with GPT partition
table (also raid1). I am using raid autodetection (i have superblock
v0.90 on all raid devices) and i am passing /dev/mdX as a root device to
the kernel. When i am passing root=/dev/md10 (old disks with msdos
partition tables) booting process is fine (i am pasting relevant info):
[ 6.695241] raid1: raid set md10 active with 2 out of 2 mirrors
[ 6.695280] md10: detected capacity change from 0 to 6999572480
[ 6.695332] md: ... autorun DONE.
[ 6.695407] md10: unknown partition table
[ 6.696236] EXT3-fs (md10): error: couldn't mount because of
unsupported optional features (240)
[ 6.696508] EXT2-fs (md10): error: couldn't mount because of
unsupported optional features (240)
[ 6.743086] EXT4-fs (md10): mounted filesystem with ordered data mode
[ 6.743185] VFS: Mounted root (ext4 filesystem) readonly on device 9:10.
[ 6.743227] Freeing unused kernel memory: 424k freed
..... now comes INIT - and it boots correctly
BUT (!) the problem is when i am trying to pass root=/dev/md0 (raid1 on
new disks with GPT partition tables). Then it seems like kernel cannot
run /sbin/init from my ext4 root partition. The root filesystem seems to
be mounted OK:
md: ... autorun DONE.
md0: unknown partition table
EXT3-fs (md0): error: couldn't mount because of unsupported optional
features (240)
EXT2-fs (md0): error: couldn't mount because of unsupported optional
features (240)
EXT4-fs (md0): mounted filesystem with ordered data mode
VFS: Mounted root (ext4 filesystem) readonly on device 9:0.
Freeing unused kernel memory: 424k freed
..... now there is some USB init debug info and it stop :(
/sbin/init is not launched and it seems like the kernel hung :(
i was waiting several minutes then - and nothing happend.
If you would like to see how the boot process look like from the grub to
the kernel hung (filmed with my digital camera) then download this:
http://manio.skyboo.net/kernel-gpt-init-problem.avi
please help me - any tips are welcome
best regards,
--
Mariusz Bialonczyk
jabber/e-mail: manio@skyboo.net
http://manio.skyboo.net
next reply other threads:[~2010-09-18 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 0:52 manio [this message]
2010-09-18 22:17 ` Mariusz Bialonczyk
2010-09-25 0:03 ` Mariusz Bialonczyk
2010-09-27 12:05 ` [SOLVED] " Mariusz Bialonczyk
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=4C940D5C.4090408@skyboo.net \
--to=manio@skyboo.net \
--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
all inboxes | Powered by JetHome®