Subject: 200206150000/sparc64
To: None <port-sparc64@netbsd.org>
From: Simon Gerraty <sjg@juniper.net>
List: port-sparc64
Date: 06/17/2002 16:31:08
Sorry if any of this is old news.

I downloaded 200206150000/sparc64 and attempted an upgrade of my ultra1.
I booted via miniroot.  One of the first things it wanted to do is
upgrade inode format, but this failed:

     Status: Failed: command ended on signal
    Command: /sbin/fsck_ffs -c 3 /dev/rsd1a
     Press any key to continue
--------------------------------------------------------------------------------
** /dev/rsd1a
** File system is already clean

CONVERT TO NEW INODE FORMAT? [yn] y

** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
uid 0 comm fsck_ffs on /: file system full

/: write failed, file system is full
     
 It appears that sd1a is not a BSD file system or the fsck was not successful.
 The upgrade has been aborted.  (Error number 11.)

uid 0 comm fsck_ffs on /: file system full
                           lqqqqqqqqqqqqqqqqqqqqqqqk
/: write failed, file systex Hit enter to continue x
                           x                       x
                           x>a: ok                 x
                           mqqqqqqqqqqqqqqqqqqqqqqqj

So I tried again using "install" rather than "upgrade".

I kept getting write errors for / but all went well though I had to
give the IP addr of my nfs server rather than its hostname. 
I'd configured le0 via DHCP.

Hmmm there were no xsets but I asked it to continue and when finished
its says:

 There were problems unpacking distribution sets.  Your installation is
 incomplete.
 
 You selected 14 distribution sets.  6 sets couldn't be found and 0 were
 skipped after an error occurred.  Of the 8 that were attempted, 8 unpacked
 without errors and 0 with errors.

 The installation is aborted.  Please recheck your distribution source and
 consider reinstalling sets from the main menu.


                           lqqqqqqqqqqqqqqqqqqqqqqqk
                           x Hit enter to continue x
                           x                       x
                           x>a: ok                 x
                           mqqqqqqqqqqqqqqqqqqqqqqqj

So is my machine hosed - who knows.
Yep, disk1 isn't bootable.  Start again...
Fortunately the miniroot is on a nother disk
This time I let it stop doing sets as soon as it hit x*.tgz
same result!  So looks like you have to do a custom install and
deselect the X sets to get past this.

So I got to boot, logged in as root, fixed root's shell to be ksh
ran df - which spewed all output on the same line,
reset the xterm, ran df again - still spewed all output on the same
line, ran it again - box locked up.

Break to ddb, still getting everying on one line.  Weird.
Doesn't matter what I do to the xterm, I just get one
line of output overwriting itself.  Fortunately its a serial console
with logging!

db> trace
zstty_stint(2015cb0, 0, 129b1c0, 101f1, 3, 2e98) at zstty_stint+0x94
zsc_intr_hard(8, 0, 10ed260, 0, 187c000, 101f0) at zsc_intr_hard+0x64
zshard(2015c00, 1298b38, fffc7c18, bf9, ffff, 1805400) at zshard+0x1c
intr_list_handler(2013dc0, 0, e0017ed0, 0, 12b9498, 12b3c04) at intr_list_handler+0x18
sparc_intr_retry(0, 0, 13102b8, 0, ffffffffffffffff, 187f608) at sparc_intr_retry+0x48
ufsspec_read(e684b40, b46, 18987c8, 0, 1a, fffffffffffddd3a) at ufsspec_read+0x48
mi_switch(e684b40, 29a, e69e428, e684b40, 0, fffffffffff14c67) at mi_switch+0x158
ltsleep(0, 0, 1344d18, 64, 0, 0) at ltsleep+0x1d8
sched_sync(180fc00, 180cc00, 1808400, 1344c00, 180c400, 183bc00) at sched_sync+0x1ac
proc_trampoline(0, 0, 0, 0, 0, 0) at proc_trampoline+0x4
db> 

If anyone has any ideas - please let me know.

Thanks
--sjg