From: "Maximilian Bräutigam" <max-braeu@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] * Boot (initramfs) .. does not continue
Date: Sat, 16 May 2009 16:01:10 +0200 [thread overview]
Message-ID: <1242482470.3832.9.camel@maxrechner> (raw)
In-Reply-To: <20090516180928.6fe429bb@coercion>
Am Samstag, den 16.05.2009, 18:09 +0600 schrieb Mike Kazantsev:
> On Sat, 16 May 2009 13:33:04 +0200
> Maximilian Bräutigam <max-braeu@gmx.de> wrote:
>
> > could you please tell me, where to find these options in menuconfig,
> > because if i'm compiling my kernel i use:
> > genkernel --menuconfig all
> >
> > if you are thinking of the options in
> > http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml
> > -- these are enabled.
>
> Yes, I mean these options as well, but in recent kernels there's one
> more flag in "Multi-dev" section that's missing in the guide:
> "Autodetect RAID arrays during kernel boot".
> Obviously, it should be set if you want to boot from mdraid.
>
> Device Drivers --->
> [*] Multiple devices driver support (RAID and LVM) --->
> <*> RAID support
> [*] Autodetect RAID arrays during kernel boot
> <*> RAID-1 (mirroring) mode
>
> But that's not all the prequesites, since you also need a device
> and fs driver compiled in.
>
> It might look like this (but the hardware and/or fs is probably
> different in your case):
>
> Device Drivers --->
>
> SCSI device support ---> (RAID settings here is not for sw raid)
> -*- SCSI device support
> <*> SCSI disk support
>
> <*> Serial ATA (prod) and Parallel ATA (experimental) drivers --->
> <*> AHCI SATA support
> [*] ATA SFF support
> <*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
>
> File systems --->
> <*> The Extended 4 (ext4) filesystem
>
>
> > by the way, if i'm booting w/o the initrd, i get a kernel panic because
> > he is not able to mount/find the raid system -- something with
> > "superblock not found".
>
Hi Mike and all other gentoos ;)
all of your mentioned options are enabled (since genkernel and me did
it).
i copied all data to another partition /dev/sdb9 and disabled initrd. by
the way, i think that initrd was running, because all the scans after
executing the initrd ran without problems. despite, i disabled it and
got a kernel panic, like:
"""
[md] scanned 0 and added 0
...
VFS: cannot open root device "sdb9" or unknown block(0,0)
please append correct "root="
...
Kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block(0,0)
"""
i don't know how to handel this error, since my grub entry is correct
(or not?):
"""
title Gentoo Linux x86_64-2.6.28-5 (no initrd) (on /dev/sdb9)
root (hd1,8)
kernel /boot/kernel-genkernel-x86_64-2.6.28-gentoo-r5 root=/dev/sdb9
"""
kind regards,
der Max
next prev parent reply other threads:[~2009-05-16 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 10:11 [gentoo-user] * Boot (initramfs) .. does not continue Maximilian Bräutigam
2009-05-16 10:21 ` Volker Armin Hemmann
2009-05-16 10:23 ` Mike Kazantsev
2009-05-16 11:33 ` Maximilian Bräutigam
2009-05-16 11:44 ` [gentoo-user] " Remy Blank
2009-05-16 12:06 ` Maximilian Bräutigam
2009-05-16 12:09 ` [gentoo-user] " Mike Kazantsev
2009-05-16 14:01 ` Maximilian Bräutigam [this message]
2009-05-16 16:43 ` Mike Kazantsev
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=1242482470.3832.9.camel@maxrechner \
--to=max-braeu@gmx.de \
--cc=gentoo-user@lists.gentoo.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