* bad inodes on initrd
@ Igor Gueths
` Ralph W. Reid
0 siblings, 1 reply; 3+ messages in thread
From: Igor Gueths @ UTC (permalink / raw)
To: speakup
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!
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bad inodes on initrd
bad inodes on initrd Igor Gueths
@ ` Ralph W. Reid
` Igor Gueths
0 siblings, 1 reply; 3+ messages in thread
From: Ralph W. Reid @ UTC (permalink / raw)
To: speakup
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: bad inodes on initrd
` Ralph W. Reid
@ ` Igor Gueths
0 siblings, 0 replies; 3+ messages in thread
From: Igor Gueths @ UTC (permalink / raw)
To: Ralph W. Reid; +Cc: speakup
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
bad inodes on initrd Igor Gueths
` Ralph W. Reid
` Igor Gueths
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).