From: Igor Gueths <igueths@attbi.com>
To: "Ralph W. Reid" <rreid@sunset.net>
Cc: speakup@braille.uwo.ca
Subject: Re: bad inodes on initrd
Date: Tue, 5 Nov 2002 20:22:21 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0211052018510.387-100000@igueths> (raw)
In-Reply-To: <200211060037.gA60bUH12420@sunset.net>
Hi Ralph. I tried running fsck on the filesystem in question, and
immediately it found that the fs had a bad superblock. However, it didn't
seem to check before reporting that. A bit strange in my opinion.
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Tue, 5 Nov 2002, Ralph W. Reid wrote:
> Igor Gueths staggered into view and mumbled:
> >
> >Hi all. When attempting to create a bootable Woody Cd, I get so far as to
> >boot the kernel and getting it up talking. After it mounts the root_fs on
> >the ramdisk, I start getting errors about bad inodes starting at about
> >number
> >2945 and going up to 2949. I would paste the messages I get in this post,
> >however I am unable to capture them because they eventually scroll offf
> >the screen. The reason being that after the inode errors sease displaying,
> >dbootstrap attempts to start and open /dev/tty1, and /dev/tty2. This
> >doesn't work because the root filesystem was not properly mounted. As a
> >result, the console devices are deamed nonexistant by the kernel. I tried
> >re-creating the filesystem and copying all the files from the root.bin of
> >the original iso into the newly created ext2_fs. This didn't work. I also
> >tried changing linuxrc to a different executable (init). Anyone have any
> >other ideas I should try? Thanks!
>
> I guess you are doing this on a CD, so I do not know if it is much
> different from setting things up on a hard drive. The Slackware
> setup utility includes selections for formatting a drive partition,
> including an error checking option--error checking is much, much
> slower than the fast format option, but it does actually check the
> hard drive for errors. Maybe you need to do something on the CD?
>
> I hope this helps.
>
>
> --
> Ralph. N6BNO. Wisdom comes from central processing, not from I/O.
> rreid@sunset.net http://personalweb.sunset.net/~rreid
> Opinions herein are either mine or they are flame bait.
> 1 = x^0
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Ralph W. Reid
` Igor Gueths [this message]
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=Pine.LNX.4.44.0211052018510.387-100000@igueths \
--to=igueths@attbi.com \
--cc=rreid@sunset.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).