Yep.

Oh.....

empeg:/empeg/bin# ro

mount: /drive0 not mounted already, or bad option



empeg:/empeg/bin# umount /dev/hda4

umount: /dev/hda4: not found



empeg:/empeg/bin# swapon /swapfile

Adding Swap: 16028k swap-space (priority -1)



empeg:/empeg/bin# fsck -fay /

Parallelizing fsck version 1.19 (13-Jul-2000)

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

ext2fs_check_if_mount: No such file or directory while determining whether /dev/

hda5 is mounted.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

/dev/hda5: 1514/4096 files (0.5% non-contiguous), 9457/16384 blocks



empeg:/empeg/bin# fsck -b 32768 -fay /dev/hda4

Parallelizing fsck version 1.19 (13-Jul-2000)

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

ext2fs_check_if_mount: No such file or directory while determining whether /dev/

hda4 is mounted.

fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4



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>

No good ?

Steve.

No good ?

No, not good. Try each of these alternate numbers:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

These are from the new recommended format scheme, though; the scheme used by the builder might not have put the superblocks in the same place.

Still no good. Every time, I get:

Parallelizing fsck version 1.19 (13-Jul-2000)

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

ext2fs_check_if_mount: No such file or directory while determining whether /dev/

hda4 is mounted.

fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4



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>

Steve.

Doubleplusungood.

I think it's time for mke2fs with the -S flag as a last ditch effort. Roger, will mke2fs -S /dev/hda4 do it or does he need other flags?

Before the -S, it might be worth it to try the dry run -n. It might be that the superblocks from the default builder are in different locations.

So a "mke2fs -n -m 0 -b 1024 -i 131072" ?

FWIW I'm now not too worried about losing the stuff on there, a lot of it was badly ripped anyway !

Steve.

Yes. You might want to capture this to a log file and post the results here.

Looks like it doesn't recognise the -n flag:

empeg:/empeg/bin# mke2fs -n -m 0 -b 1024 -i 131072



mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

Usage: mke2fs [-c|-t|-l filename] [-b block-size] [-f fragment-size]

        [-i bytes-per-inode]  [-N number-of-inodes]

        [-m reserved-blocks-percentage] [-o creator-os] [-g blocks-per-group]

        [-L volume-label] [-M last-mounted-directory] [-O feature[,...]]

        [-r fs-revision] [-R raid_opts] [-s sparse-super-flag]

        [-qvSV] device [blocks-count]

Steve.

Worth a shot. Given that there does not appear to be a non-destructive way to find superblock locations, I do not know what else to tell you. It might be time for that -S switch.

Does anyone else have any ideas???

Does anyone else have any ideas?

Might be worth trying a newer version of fsck. There is a more recent version on my ext3 page.

Just grab the e2fsck binary and ftp it to your player and then follow step 1 (and only step 1) on that page. Then try the fsck again.

-Mike

OK, I tried doing mcomb's suggestion, but I'm not quite sure what happened. I then did the -s whatsit and got this:

empeg:/empeg/bin# mke2fs -S /dev/hda4

mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

ext2fs_check_if_mount: No such file or directory while determining whether /dev/

hda4 is mounted.

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

4872896 inodes, 9741414 blocks

487070 blocks (5.00%) reserved for the super user

First data block=0

298 block groups

32768 blocks per group, 32768 fragments per group

16352 inodes per group

Superblock backups stored on blocks:

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

        4096000, 7962624

Those last two numbers are new, so I tried the fsck command again with the first of the new numbers but get

fsck: fsck.ext2: not found

I think I've screwed something up.

Steve.

No, I think that error is because you copied the new fsck across.

Can you do ls -l /sbin/e2* and ls -l /sbin/fsck*

empeg:/empeg/bin# ls -l /sbin/e2* and ls -l /sbin/fsck*

ls: and: No such file or directory

ls: ls: No such file or directory

lrwxrwxrwx    1 0        0              11 Jun 10 17:24 /sbin/e2fsck -> /bin/e2f

sck

lrwxrwxrwx    1 0        0              16 Jun 10 17:25 /sbin/e2fsck.ext2 -> /bi

n/e2fsck.ext2

-rwxr-xr-x    1 0        0           66301 Apr  1  2003 /sbin/fsck

lrwxrwxrwx    1 0        0              11 Jun 10 16:40 /sbin/fsck.ext2 -> /bin/

e2fsck

So what's that doing ?

Steve.

Checking what is where...

ls -l /bin/e2*
ls -l /bin/fsck*


Note the path change, bin not sbin this time.

empeg:/empeg/bin# ls -l /bin/e2*

lrwxrwxrwx    1 0        0              11 Jun 10 17:24 /bin/e2fsck -> /bin/e2fsck

lrwxrwxrwx    1 0        0              16 Jun 10 17:25 /bin/e2fsck.ext2 -> /bin/e2fsck.ext2



empeg:/empeg/bin# ls -l /bin/fsck*

-rwxr-xr-x    1 0        0           66301 Apr  1  2003 /bin/fsck

lrwxrwxrwx    1 0        0              11 Jun 10 16:40 /bin/fsck.ext2 -> /bin/e2fsck

There's your problem. Somehow in putting the newer e2fsck tools on the player something got screwed up.

fsck is trying to call fsck.ext2 which symlinks to /bin/e2fsck which in turn symlinks to ... itself. You're missing the e2fsck binary.

Erk. I knew I shouldn't have got up this week. I'm in way over my head now so I think I'll cut my losses and rebuild the drive.

Many thanks to everyone for the help :-)

Steve.