Frans Pop <[EMAIL PROTECTED]> writes:
> I've seen the same error on my Sparc Ultra 10. The problem is in klibc
> which is used by initramfs-tools; merging the bug reports.
>
> Try installing yaird and using that to generate your initrd.
That gets it further, but then it fails as follows (where sda1 is
/boot). If I then get in single-user, I see /dev/sda1 mounted on /,
but there is no /dev/sd*, i.e. no sd devices, which looks odd.
...
Waiting for /dev to be fully populated...done.
Activating swap.
Checking root file system...
fsck 1.37 (21-Mar-2005)
/: clean,EXT3 FS on sda2, 55400/641280 fiinternal journal
les, 485138/1280188 blocks
System time was Thu Jan 26 10:08:17 UTC 2006.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Thu Jan 26 10:08:19 UTC 2006.
Cleaning up ifupdown...done.
Calculating module dependencies...done.
Loading modules...
sd_mod
All modules loaded.
Checking all file systems...
fsck 1.37 (21-Mar-2005)
fsck.ext3: 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>
fsck failed. Please repair manually.
By the way, the trouble with reassigning bugs like this is that anyone
who checks for existing reports against the kernel (like I did)
doesn't see them. It guess it would be helpful if there was some way
to leave a pointer in the original place (assuming it's a likely
package against which to report the bug). Is it possible to operate
the tracker so that it does that?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
