bad inodes on initrd

Ralph W. Reid rreid at sunset.net
Tue Nov 5 19:37:29 EST 2002


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 at sunset.net  http://personalweb.sunset.net/~rreid
Opinions herein are either mine or they are flame bait.
1 = x^0




More information about the Speakup mailing list