All of lore.kernel.org
 help / color / mirror / Atom feed
From: markus reichelt <ml@bitfalle.org>
To: linux-admin@vger.kernel.org
Subject: FWD: [slackware] Boot kernel from CD & root fs on ext disc
Date: Mon, 4 Oct 2004 13:17:48 +0000	[thread overview]
Message-ID: <20041004131748.GA8913@dantooine> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,


I'm trying to boot a recent kernel (2.4.27 or 2.6.7) from CD with the
root fs on external disc (usb). Can't boot off of external devices
because of old bios. All needed drivers are compiled in and working,
only thing I can't get to work is my prob with initrd described
below.

Looking desperately for help on this one.

- ----- Forwarded message from markus reichelt <ml@bitfalle.org> -----

Date: Mon, 4 Oct 2004 12:25:12 +0000
From: markus reichelt <ml@bitfalle.org>
To: slackware@mailman.lug.org.uk
Subject: Re: [slackware] Boot kernel from CD & root fs on ext disc

John Briggs <john@johneb47.id.au> wrote:
> I would first check and see if the scsi module you are using belongs in the
> second group and if so do an internet search for anyone who may have solved
> a similar problem.

I managed to create an initrd from scratch, this is what I use as
init-script:

#!/bin/bash
mount -t proc /proc /proc
mount -t sysfs none /sys
mount -r -n -t reiserfs /dev/sda10 /mnt
while [ $? -ne 0 ]
do
    /bin/mount -r -n -t reiserfs /dev/sda10 /mnt
done
cd /mnt
sleep 1
pivot_root /mnt /loader
umount -f /loader
exec chroot . /sbin/init


This works to some extend;  after some seconds /dev/sda10 is
available and can be mounted without any further errors. But now I'm
stuck again because pivot_root complains about "device or resource
busy". Next the kernel panics again ("attempted to kill init!"). I'm
lost here, an intensive google search went not as expected, not at
all.


Then I tried a different approach and patched a 2.6.7 vanilla kernel
with a blkdev_wakeup.patch, that basically repeats the mounting
operation after the kernel booted until the provided root=/dev is
available. I used the /sbin/makebootdisk script to create a bootdisk
with that kernel but unfortunately the code is immature and produces
a segfault late in the boot process.

This is killing me...

- -- 
Bastard Administrator in $hell


- ----- End forwarded message -----

- -- 
Bastard Administrator in $hell

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBYU18LMyTO8Kj/uQRAjt7AJ9GyrISp8efkcaqhY4OiewEWsy9lwCffqD3
FTUNrt/vTENi0Qk86ldlJZM=
=6WXU
-----END PGP SIGNATURE-----

             reply	other threads:[~2004-10-04 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 13:17 markus reichelt [this message]
2004-10-07 13:55 ` FWD: [slackware] Boot kernel from CD & root fs on ext disc markus reichelt

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=20041004131748.GA8913@dantooine \
    --to=ml@bitfalle.org \
    --cc=linux-admin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.