From: Maciej Grela <maciej.grela@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Booting Gentoo from USB stick
Date: Fri, 10 Sep 2010 09:27:25 +0200 [thread overview]
Message-ID: <AANLkTi=ZqOTH+0NVYS30e6vYHgT=3vVNXEqu8JCstDzy@mail.gmail.com> (raw)
In-Reply-To: <4C89BD8B.4020306@gmail.com>
2010/9/10 Jake Moe <jakesaddress@gmail.com>:
> Hello all,
>
> I've been thinking about creating a Gentoo USB stick for install and rescue
> purposes (and, of course, just to see if I could). I've mostly followed the
> Gentoo handbook (I used a single 4GB partition for the whole system, and no
> swap). I've used genkernel for the kernel (so I can have a multi-system
> capable kernel). I've gotten GRUB installed and working. My problem comes
> in after what I believe is the init process:
>
>
> Gentoo Linux; http://www.gentoo.org
> Copyright 1999-2009 Gentoo Foundation; Distributed under the GPLv2
>
> Press I to enter interactive boot mode
>
> * Mounting proc at /proc ... [
> ok ]
> * Mounting sysfs at /sys ... [
> ok ]
> * Mounting /dev ... [
> ok ]
> * Starting udevd ... [
> ok ]
> * Populating /dev with existing devices through uevents ... [
> ok ]
> * Waiting for uevents to be processed ... [
> ok ]
> * Mounting devpts at /dev/pts ... [
> ok ]
> * Checking root filesystem ...
> fsck.ext2: No such file or directory while trying to open /dev/sda1
> /dev/sda1:
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
>
> * Filesystem couldn't be fixed :( [
> !! ]
> Give root password for maintenance
> (or type Control-D to continue):
>
>
> If I give the root password, I can find no /dev/sda1. However, mount shows
> /dev/sda1 on /, and there *is* a /sys/block/sda folders, with a sda1 folder
> in that as well. It's almost like it had /dev/sda1, but then lost it
> somehow.
>
> Does anyone have any idea what's going on here? Any help would be
> appreciated.
>
Have you seen http://www.sysresccd.org/Main_Page ? It's based on
Gentoo, you could check what they did to boot from a usb stick.
Br,
Maciej Grela
next prev parent reply other threads:[~2010-09-10 7:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 5:09 [gentoo-user] Booting Gentoo from USB stick Jake Moe
2010-09-10 7:27 ` Maciej Grela [this message]
2010-09-10 8:43 ` Jake Moe
2010-09-10 9:05 ` J. Roeleveld
2010-09-10 11:29 ` David Relson
2010-09-14 18:28 ` YoYo Siska
2010-09-14 22:34 ` Jake Moe
2010-09-15 10:10 ` YoYo Siska
2010-09-15 22:03 ` Jake Moe
2010-09-15 22:18 ` Al
2010-09-15 22:43 ` Jake Moe
2010-09-15 23:04 ` Al
2010-09-16 0:21 ` Jake Moe
2010-09-16 11:08 ` Al
2010-09-15 22:26 ` Dale
2010-09-15 22:34 ` Jake Moe
2010-09-16 6:22 ` J. Roeleveld
2010-09-16 10:01 ` Jake Moe
2010-09-16 11:30 ` J. Roeleveld
2010-09-21 5:35 ` Jake Moe
2010-09-21 7:26 ` J. Roeleveld
2010-09-22 4:36 ` Jake Moe
2010-09-22 7:02 ` Al
2010-09-22 8:57 ` Jake Moe
2010-09-22 7:16 ` J. Roeleveld
2010-09-22 9:13 ` Jake Moe
2010-09-22 11:23 ` J. Roeleveld
2010-09-10 10:51 ` Al
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='AANLkTi=ZqOTH+0NVYS30e6vYHgT=3vVNXEqu8JCstDzy@mail.gmail.com' \
--to=maciej.grela@gmail.com \
--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