Hey, I have an old server at the police dept that they want to pull some data off of. Unfortunately, anybody who might have known anything about it is long since resigned / retired / passed away. No documentation / records. It was, at our best guess, taken out of service ~10 - 11 years ago, but it does manage to boot.
1) I get a prompt of the form SERVER_NAME:, but I have no idea what it expects from me here. I've tried any number of commands, passwords, login names, etc., but it just pops up an error something like ??? Unknown Command ???. Any idea what I need to do to log in / start it up? I think I have a few good guesses as to what the admin password will be, but if those fail, are there any handy tricks / tools to reset or bypass that on NetWare?
2) It continually pops up errors about no connection, check cable, etc. Going off the connectors on the back of the machine and what I know about the network that was in place at the time, it's a safe bet it was coax at the time. I certainly don't have any of that gear, and if I did, no machines that could act as a client, so I'm hoping this isn't necessary. Anybody have any insight here?
3) At boot, I get warnings about inconsistency between mirrors, so this thing may be on it's last legs. Anybody have any advice on a way I could grab an image and run it as a VM or something?
Between NetWare and simply the age of the machine, I'm well out of my depth here, so any advice would be appreciated.
*ETA:
version = 3.12
modules = LNEPCI2.LA, ISADISK.DSK
Puts on dusty, well-used NetWare cap
Hooray legacy skills.
First of all, the command line you see is mostly useless for what you're trying to do. It isn't a command interpreter like bash or cmd.
The next step is seriously dependent upon what version it is. 10-11 years old could be anything from Netware 3.1x to NetWare 5.0. You can find this out by typing "version" at the command line.
The 'mirror' message is usually a good sign that one of the hard-drives is actually bad.
Edit I had a brain-wave. You may not be as screwed as you could be. You'll need to do the floppy-drive tango for this, but it can be done. If it isn't a NetWare 3.x server, you can use a command called 'toolbox', which allows copy operations. Once you've found where in the file-system the files are located, you can then copy them to the floppy drive. Obviously this is more suitable to a few files than a complete filesystem recovery.
You'll need something DOS formatted of course, and you'll probably need to download the TOOLBOX.NLM from the Novell site (Alt, or elsewhere on the Internet if you'd rather). Copy it to the floppy. Then...
Which should either load, or complain about not having a library loaded (very probably CLIBAUX). Try loading the specified module, then retry loading TOOLBOX.
Once you have that loaded, you can copy toolbox to the system.
That'll put it local so you don't need to keep loading it from floppy. Then you can use the DIR and COPY commands to move data to the floppy disk. You can find the local volumes with the 'volumes' command. (may look different than this)
Those are your mount-points, so start delving for the needed data there.
If it asks you to log in to DIR the volume, unload TOOLBOX, and reload it with the "/NL" option. You'll be limited to 8.3 names, but you may already be limited to that anyway so no loss.
What kind of hard drive(s) are in the server? you may be better off removing them and attempting to access the data by putting them into another system as secondary drives.
Most likely they\you will need a drive recover process, but you can start by doing the basics!
type modules at the server_name: prompt.
what modules are listed?
Even when it breaks, you can try to use PhotoRec to recover files from it, booting from a Linux Live CD for example