Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

BL2 stopped working on one computer, which led to try fixing it with BL3 
e2fsck, which does NOT work on BL2.

First, I installed qemu with the SW10.2 glibc 2.3.5 (on top of glibc 2.3.2 
and gcc 3.2.3 probably from SW9.1), then tried to downgrade it (following 
Steven's instructions to boot with BL3, delete the 2.3.5 (and 2.3.2) 
libraries and remake the links to 2.2.5 with ldconfig and I had to also 
remake one other link manually, ld-linux?).

Today I could boot to BL2, and copy a file, but then suddenly when I tried 
to install timidity_bl3.tgz, (which did not get installed) I got a message 
about 'GLIBC_2.3 not found (required by /lib/tls/libc.so.6)'.  Same 
message if I did ls or mv or rm or which.  (2.3 is the SW9.1 or 10.2 
glibc).

If I boot to BL3 and try to chroot to BL2 I get the same message.  There 
is now a /lib/tls with a copy of what looks like library files from glib 
2.3.5 dated 2005 (not found on my other BL2).

If I first rename tls to tls-bak, I can chroot and use BL2.
I will delete the directory.

So I have solved this one problem though I don't know what caused it.
I will try to remember never to upgrade glibc without keeping a full 
backup of relevant directories for uninstalling - do I need to keep only 
/lib?

 -----------------------------
I tried to fix it first by e2fsck from BL3:

If I boot to BL3 something goes by about a superblock and the BL2 
partition.

> From BL3, e2fsck on the BL2 partition tells me
esfsck:  Filesystem has unsupported feature(s) while trying to open 
/dev/hdb4.

The superblock could not be read......

It says to use -b 8193, and I do that and am told
e2fsck:  Bad magic number in super-block while trying to open...

Same for -b 16835.

Similarly to another computer where e2fsck keeps finding a bad inode 
count, BL2 appears to work anyway despite the bad magic number and bad 
superblock.

A google search found a suggestion to use a newer e2fsck.  The BL3 one is 
1997.

Without /lib/tls, BL2 now boots and 'was not cleanly unmounted, check 
forced' and it checks it without complaining about the superblock.  So 
this is my third computer where the BL3 e2fsck is not working correctly. 
This is a PIII with no known hardware problems, the others were older.

The e2fsck from BL2 hard disk works if I copy it and also libext2fs.so.2.4 
to RAMdisk BL2, but not with the e2fsckfs.so.2.4 that comes with RAMDISK 
BL2.

Could e2fsck and libext2.so.2.4 be compiled dynamically for libc5 or 
statically with uclibc for BL3 so that it will work on all computers to 
check BL2?  Using SW7.1 or later source code.

Sindi