OK, calling all Unix people... See the other post on the status of the Tek Unix system - I got that going with another disk and it booted to single-user mode, complaining about filesystem errors. I ran fsck and it worked this time on the new disk (I vaguely remember before that it used to give up halfway with the old failing drive) Lots of errors, to which I just answered 'y' to each one (if that was the wrong thing to do then say - I still have an image of the old, corrupted drive). I now have a clean filesystem, and lots of stuff in /lost+found Any ideas what the next step is? Do I just have to look at the contents of files and directories in /lost+found (they're all numbered rather than named - by inode or something?) and try to figure out what everything in there is? (there's a lot of files there - I suppose I'm quite lucky the system even booted) That's going to be painful (and probably impossible for some of the data) - presumably the original filenames have been lost in the corruption? I'm only used to fsck on linux where it always seems to sort itself out - I've not had to rebuild a filesystem like this before! cheers Jules --