SUMMARY: Module in slot 4 has bad ROM format, can't configure it

From: Karl Amrhein <ksa_at_ucolick.org>
Date: Tue, 10 Nov 1998 09:59:14 -0800 (PST)

Thanks for the responses.


************ Original question:

My system cannot boot, I get this message at startup time:

        Module in slot 4 has bad ROM format, can't configure it
        Module in slot 5 has bad ROM format, can't configure it

then

        panic (cpu0): vfs_mountroot: cannot mount root.

o Does this mean my firmware update to v7.0 failed?

o What are the modules in slot 4 and slot 5 and how can I fix
  the bad ROM format?

But, it does say during startup that I'm at 'Firmware revision: 7.0'.
And 'PALcode: Digital UNIX version 1.45'.

Please help! I'm going to try reloading the firmware now, because
it seems likely that the update failed at least partially
according to the above message.


************ Summary:

Problem fixed by reloading firmware AND reinstalling OS.
After reloading the firmware, the system still would not
boot. But, after reinstalling the OS, the system booted
up fine.

===> Key information point I failed to mention:
The OS was installed on the boot disk on *another system*
(by another sysadmin) then the boot disk was put back into
this system, and that's when the boot failed. Maybe the problem
stems from the fact that: the OS was installed on disk1 when inside
in hardwareA, then when disk1 was placed in hardwareB, it did
not boot. hardwareA and hardwareB appear to be almost identical
DEC 3000 systems, but apparently they are not. However, I did not
do the initial install or firmware upgrade, so I can not really be
sure what was done or not done the first time around.

Is the post kernel build specific to the system hardware? It
seems that the likely problem is that the automatic post-install
kernel build was not done on the hardware which the system was
eventually run on.

A very good suggestion was to boot genvmunix. I didn't try this
before reinstalling the OS, but is sounds like it would have
worked:

  1 - >>>boot -fi "/genvmunix" -fl 1 (boot genvmunix single user)
  2- #doconfig -C "nodename" (recreate your kernel (if you boot OK)
  3- move the new kernel into "/" and try booting again

************

Thanks very much for the following responses to my questions:

Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
Robert Otterson <Robert.Otterson_at_digital.com>
mjwatson_at_snafu.livenet.net (MJ Watson)
alan_at_nabeth.cxo.dec.com
Chris Glenister <C.Glenister_at_cranfield.ac.uk>


-- 
      Karl
-----------------------------------------------------------------
Karl Amrhein                                ksa_at_ucolick.org
UNIX Systems Administrator                  Voice: (831) 459-2303
NICS, UCO/Lick Observatory                  Fax:   (831) 426-3115
-- 
      Karl
-----------------------------------------------------------------
Karl Amrhein                                ksa_at_ucolick.org
UNIX Systems Administrator                  Voice: (831) 459-2303
NICS, UCO/Lick Observatory                  Fax:   (831) 426-3115
Received on Tue Nov 10 1998 - 18:00:46 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT