public inbox for gentoo-ppc-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: <nova@macintoshclub.com>
To: <gentoo-ppc-user@lists.gentoo.org>
Subject: Re: [gentoo-ppc-user] Problems booting...still
Date: Fri, 28 Oct 2005 08:04:00 -0700 (PDT)	[thread overview]
Message-ID: <50742.216.204.100.226.1130511840.squirrel@webmail.macintoshclub.com> (raw)
In-Reply-To: <435E8190.1020003@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

I have attached fstab. It has the paritions configured with root =
/dev/dha7 ext3, which is correct. I ran the e2fsck (because it said that
is had been over 12000 days since the last test, due to not resetting the
clock), and it reported no problems, 1.1% fragmentation.
What should I be using instead of devfs?
> nova@macintoshclub.com wrote:
>> OK, I didn't have the devfs loaded into the kernel, so the new version
>> boots past that point. However, the boot stops when it tries to load
>> the root filesystem.
>
> You shouldn't use devfs.  It's obsolete.  Which liveCD / stage are you
> installing from?  Which profile are you using?
>
>> warning, no fsck.ext3 found.
>> Error: mounting an ext2 partition failed on /dev/hda7 (a little
>> different wording), Bad superblock, etc
>> type cntrl-D to cancel, or enter root passwd to fix:
>> and it is frozen (no keyboard recognised)
>> There is a copy of fsck.ext3 on /sbin/, so I think that it is not in
>> the initrd. Any ideas on how to fix this?
>
> Is /dev/hda7 an ext2 partition?  Are you sure you have your partition
> numbering right and that your fstab reflects your partition layout?
>
> -Joe
> --
> gentoo-ppc-user@gentoo.org mailing list
could this be caused by my PRAM battery being DEAD (is says the year is 1904)
thanks,
nick
Also, I configured in both EXT2 and EXT3 kernel support...


[-- Attachment #2: fstab --]
[-- Type: text/plain, Size: 1112 bytes --]

# /etc/fstab: static file system information.
# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.18.4.1 2005/01/31 23:05:14 vapier Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't 
# needed; notail increases performance of ReiserFS (at the expense of storage 
# efficiency).  It's safe to drop the noatime options if you want and to 
# switch between notail / tail freely.
#
# See the manpage fstab(5) for more information.

# <fs>			<mountpoint>	<type>		<opts>		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda7		/		ext3		noatime		0 1
/dev/hda6		none		swap		sw		0 0
/dev/cdroms/cdrom0	/mnt/cdrom	iso9660		noauto,ro	0 0
#/dev/fd0		/mnt/floppy	auto		noauto		0 0

# NOTE: The next line is critical for boot!
proc			/proc		proc		defaults	0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for 
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
shm			/dev/shm	tmpfs		nodev,nosuid,noexec	0 0


  parent reply	other threads:[~2005-10-28 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 18:50 [gentoo-ppc-user] Problems booting...still nova
2005-10-25 19:03 ` Joseph Jezak
2005-10-25 20:20   ` Nicholas S-A
2005-10-28 15:04   ` nova [this message]
2005-10-28 15:45     ` Rod Furey

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=50742.216.204.100.226.1130511840.squirrel@webmail.macintoshclub.com \
    --to=nova@macintoshclub.com \
    --cc=gentoo-ppc-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