paul@eye.com (Paul B. Booth) (06/27/91)
Any ideas?
I've got a dn3000 with a 70Mb micropolis disk. It's running 9.7 because 10.x
won't really fit on the little guy. The folks who've loaned me this machine
want to upgrade it to 10.2, so they send a 360Mb micropolis, supposedly with
10.2 already installed on it. I install the new disk and driver board (the
note with the board says that all the jumpers are ok) and fire it up.
It goes through self tests ok (but complains that configuration table is
corrupt. Not surprising, since the battery in the box is dead)
It starts to bring up 10.2 and asks me if I want to reset the calendar (which
is way off because of the dead battery). I say ok and ex calendar.
I change the date. Calendar drops me back to the > prompt, and I ex domain_os
Now I get the message "domain_os unreadable". In fact, now calendar is not
readable, nor is dex. I can still ld and ex config, but not much else.
salvol won't do much either.
What do I do now? I guess I can install 10.2 from tape, but I'd really rather
not if I can get the disk to boot. Any tricks to this or am I hosed?
Thanks for _any_ wisdom!
--
Paul B. Booth (paul@eye.com) (...!hplabs!hpfcla!eye!paul)
-------------------------------------------------------------------------------
3D/EYE, Inc., 2359 N. Triphammer Rd., Ithaca, NY 14850 voice: (607)257-1381
fax: (607)257-7335krowitz@RICHTER.MIT.EDU (David Krowitz) (06/27/91)
The dead battery should not affect your config table, only the date/time calendar (I know, I had a dead battery in my DN4000 before I finally sold the poor little beast). My guess is that since the disk was loaded on another machine, all of the disk objects have UID's which have the node-ID of the other machine encoded into the UID. Try running "chuvol" (ie. EX CHUVOL) to change the UID's on the disk to your machines UID encoding. Also run "config" to make certain you've got the machine configuration correct. -- David Krowitz krowitz@richter.mit.edu (18.83.0.109) krowitz%richter.mit.edu@eddie.mit.edu krowitz%richter.mit.edu@mitvma.bitnet (in order of decreasing preference)
thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) (06/27/91)
> I've got a dn3000 with a 70Mb micropolis disk. It's running 9.7 because 10.x > won't really fit on the little guy. The folks who've loaned me this machine > want to upgrade it to 10.2, so they send a 360Mb micropolis, supposedly with > 10.2 already installed on it. I install the new disk and driver board (the > note with the board says that all the jumpers are ok) and fire it up. > ... > Now I get the message "domain_os unreadable". In fact, now calendar is not > readable, nor is dex. I can still ld and ex config, but not much else. > salvol won't do much either. > > What do I do now? I guess I can install 10.2 from tape, but I'd really rather > not if I can get the disk to boot. Any tricks to this or am I hosed? Well, the first thing that comes to mind is CHUVOL. The disk UIDs (unique-IDs, not Unix-IDs) will be for the wrong node. I don't know if the system will boot up or not with the wrong node's UID on domain_os. However, since CHUVOL is yet another one of those things in your /sau8 directory, I don't know if it'll let you EX that any better. Can you boot diskless off of somebody, and run CHUVOL? If not, you might boot off of tape, and try running CHUVOL from there. ('DI C' 'EX CHUVOL') I can't remember the exact questions that CHUVOL asks, but it'll basically be like salvol -- it'll ask the disk to do, and it'll ask the volume. Then it asks for original and new nodeIDs -- I think it prompts with what it believes are the correct ones. Hope this helps. If it doesn't, I hope it doesn't waste too much time. -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com Avoid the rush -- Procrastinate Now!