I get the following, and I think it might be bad news....

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 -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: Filesystem revision too high while trying to open /dev/hda4

The filesystem revision is apparently too high for this version of e2fsck.

(Or the filesystem superblock is corrupt)



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>

I don't have backups of a lot of the stuff here so it'd be nice to recover whatever I can, but it's not the end of the world if I lose it.

Steve.