Re: boot/startup help

"moot" <cowan@xxxxxxx> wrote in
news:1156714680.720064.308270@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

I'm having some trouble with a little used os9 mvme system we once
again need to use a little.

A couple days ago it was booting and I could get into the shell over
the serial console,
and run basic commands (dir, help, etc.) now it's balking with:

----------------------------------------------------------------------
...<normal looking eeprom stuff, complete log appended at end>...
Checking for OS-9 RBF filesystem

Booting -
A valid OS-9 bootfile was found.
ioman: can't chgdir to system device: Error $00DD
shell: can't execute "mbinstall" -
$ dir
dir: can't open ".". Error #000:215

$ procs
shell: can't execute "devs" - Error #000:215

$
----------------------------------------------------------------------
And basically any command spits out the same 215 error.

from http://www.roug.org/soren/6809/os9sysprog/errorcodes.html
215 seems to be
BAD PATH NAME - syntax error in pathlist (illegal character, etc.).
and DD is
MODULE NOT FOUND - request for link to module not found in directory.

I'm completely new to os9, but a very experienced unix guy.
My first worry was a disk (it's scsi) problem, but it checks out fine
with badblocks (even
non-destructive read-write) under linux (fdisk and parted both show
the disk as unpartitioned), and having found that the "host" system (
at the other end of the mvme serial console line where I'm running
minicom) had a bootp
setup for the crate, I booted it via bootp and end up at the same
state. I guess it
could be a filesystem corruption issue? I'm hoping it's something
that just got screwed up
in the system startup or shell environment, but not knowing os9
uh?.?.?

The vme board is a MEN A 10.
http://www.menmicro.com/download/default.asp?lv=support&prod_dl=20A008-
00&lid=o_3mzlnzxks_4&op=1 or support->docs->discontinued
hardware->a9/10 if the above link doesn't work

Not sure of the os9 version :(

any help is greatly appreciated!
woohoo! just found docs at http://www.icdia.co.uk/microware/index.html
could certainly still use help though
thanks!

full disk boot log -- this is with the front panel hex dial set to
0 (as per the board
docs for setting up a board) instead of 7 (what it normally is). with
it set to 0 you get the interactive menmon->rombug->boot menu
interface, with it set to 7 it autoboots following the boot order
(scsi disk first) and ends up in the same state. I had a sniffer
running during bootup to see if it's looking for an nfs root device or
something... no net traffic when disk
booting.
-----------------------------------------------------------------------
----------


=====[ MENMON for A8/A9/A10 Version 1.5 ]=====



Board Rev 3.07, Ver 1.02, Serial No. <snipped>, Ethernet Addr
<snipped>

DRAM detected: Onboard RAM=4M, SIMM module=32M (SIMM-ID:D)

SRAM detected: 2048K

System reset caused by External Reset

Init VMEbus controller...



-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

| MenMon - 68k Debugger |

| Kernel Version 2.8 |

| (c) men 1994 |

| |

| Press 'H' for help-screen |

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

CPU-Type : 68060

Vector Base : 00000400

MENMON Globals : 00FFE400..00FFE56C

MENMON Stacktop: 00FFE400



MenMon> BO

Calling bootstrap PC=$000104A4 SP=$28108900



OS-9/68K System Bootstrap



<Called>

dn: 00000000 00002000 00000002 00000000 00000002 00000001 FFFFE000
28108900
an: 00010992 00010478 00000000 00000000 28109900 28100400 00000000
28108900
pc: 00010894 sr:2700 (--S--7-----) usp:00000000
^ssp^
0x00010894 >43FAFC0E lea.l 0x104A4(pc),a1

RomBug: g

---------------------------------------------------------

| MEN OS-9/68k Boot (c) 1996 A8/A9/A10 ROM Version 2.1 |

---------------------------------------------------------



CPU type = 68060



BOOTING PROCEDURES AVAILABLE ----- <INPUT>



Boot from SCSI (CCS) hard drive -- <hs>

Boot from onboard FLASH ROM ------ <fl>

Boot from Ethernet - BOOTP ------- <le>

Boot from Teac SCSI floppy drive - <fs>

Boot from shared RAM ------------- <sr>

Boot from PCMCIA card ------------ <pc>

Transfer PCMCIA -> FLASH --------- <pf>

Reconfigure the boot system ------ <rc>

Restart the system --------------- <q>



Select a boot method from the above menu: hs



Checking for OS-9 RBF filesystem



Booting -

A valid OS-9 bootfile was found.

ioman: can't chgdir to system device: Error $00DD

shell: can't execute "mbinstall" -

$ dir

dir: can't open ".". Error #000:215



$

-----------------------------------------------------------------------
-----------------------

net boot log -- note that the boot file name suggests it's going to
use nfs and
there are a few additional mount/rpc/network related output
lines/errors, but
I had a sniffer running and it doesn't get to the point of looking for
anything on the
network; the only network traffic is the bootp bootup, tftp download,
and related arp traffic.
-----------------------------------------------------------------------
-----------------------

=====[ MENMON for A8/A9/A10 Version 1.5 ]=====

Board Rev 3.07, Ver 1.02, Serial No. <snipped>, Ethernet Addr
<snipped> DRAM detected: Onboard RAM=4M, SIMM module=32M (SIMM-ID:D)
SRAM detected: 2048K
System reset caused by External Reset
Init VMEbus controller...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| MenMon - 68k Debugger |
| Kernel Version 2.8 |
| (c) men 1994 |
| |
| Press 'H' for help-screen |
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
CPU-Type : 68060
Vector Base : 00000400
MENMON Globals : 00FFE400..00FFE56C
MENMON Stacktop: 00FFE400

MenMon> BO
Calling bootstrap PC=$000104A4 SP=$28108900

OS-9/68K System Bootstrap

<Called>
dn: 00000000 00002000 00000002 00000000 00000002 00000001 FFFFE000
28108900
an: 00010992 00010478 00000000 00000000 28109900 28100400 00000000
28108900
pc: 00010894 sr:2700 (--S--7-----) usp:00000000
^ssp^
0x00010894 >43FAFC0E lea.l 0x104A4(pc),a1
RomBug: g
---------------------------------------------------------
| MEN OS-9/68k Boot (c) 1996 A8/A9/A10 ROM Version 2.1 |
---------------------------------------------------------

CPU type = 68060

BOOTING PROCEDURES AVAILABLE ----- <INPUT>

Boot from SCSI (CCS) hard drive -- <hs>
Boot from onboard FLASH ROM ------ <fl>
Boot from Ethernet - BOOTP ------- <le>
Boot from Teac SCSI floppy drive - <fs>
Boot from shared RAM ------------- <sr>
Boot from PCMCIA card ------------ <pc>
Transfer PCMCIA -> FLASH --------- <pf>
Reconfigure the boot system ------ <rc>
Restart the system --------------- <q>

Select a boot method from the above menu: le

inetboot: using QUICC Ethernet @ 0xFFEC00 MTU=1500
bootp: <mac snipped> broadcasting for server
bootp: recv waiting 50 ticks
GOT BOOTP RESPONSE from server <srv ip snipped>!
My IP address will be: <snipped>
My tftp bootfile is: /tftp/bootp/OS9Boot.nfs
My bootfile size is: 1522 (512-byte) blocks
My subnet mask is: <snipped>
Network time offset is: 4294945696
tftp: fetch 1522 blocks
tftp: server response <snipped> port 1359
<snipped network traffic related "rewaiting" messages>
tftp: expected 1522: received 1521:266 blocks (761Kb)
A valid OS-9 bootfile was found.
ioman: can't chgdir to system device: Error $00DD
+5
ee_hostname: setting hostname to <hostname snipped>
mounting /dd
hp: RPC: Unknown host
mount: cannot contact server.

$ dir

dir: can't open ".". Error #000:215


$
-----------------------------------------------------------------------
----------------------

The error $00dd is an error 000:221 module not found. You need to see
what the system device is in the init module. Something is missing in
the boot or the load that haapens in the startup.

Allan R. Batteiger

.

Relevant Pages

  • boot/startup help
    ... A couple days ago it was booting and I could get into the shell over ... I'm completely new to os9, but a very experienced unix guy. ... I booted it via bootp and end up at the same ... with it set to 7 it autoboots following the boot order (scsi ...
    (comp.os.os9)
  • Re: loader problem?
    ... >> OK boot ... > Are you sure it isn't booting using the serial console instead? ... when no device hints were present (easily verifiable with the ...
    (freebsd-current)
  • Re: serial console installation of 6.1-BETA4
    ... unplugging the keyboard does nothing, booting with 'boot -h' gives me all the ... kernel's device probing messages on both the serial console and the normal console, ...
    (freebsd-stable)
  • Re: (was Re: HEADS UP! MAJOR change to FreeBSD/sparc64) Boot failure on rebuild
    ... I'm having trouble figuring out why the old kernel won't boot. ... booting on serial console. ...
    (freebsd-current)
  • Re: WinXP doesnt start
    ... > My computer stopped booting properly. ... > driver updates. ... > - When normal boot is chosen it starts boot process then reboots. ... and replacing or swapping its flat ribbon cable, ...
    (microsoft.public.windowsxp.help_and_support)