Re: NetBSD 7.2, 8.2 and 9.0 on SparcStation IPC

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi Martin!

sorry for the delay - In all this NetBSD install and update I am doing,
this was left a bit behind.
The IPC is more a small toy and test tool I keep because of "pride" and
cuteness... but has no primary functions. And, of course, it will get
packages only compiled from other systems.

Martin Husemann wrote:
> On Wed, May 06, 2020 at 01:10:01PM +0200, Riccardo Mottola wrote:
>> What now?
> Let's see if we can debug it further.
> With the new kernel, can you access the disk you tried to boot from?

Yes. I just tried, once the NetBSD 8.2 kernel is booted it is fully
functional. I boot into multi, user hard disk is mounted:

meriadoc$ mount
/dev/sd0a on / type ffs (log, local)
/dev/sd0d on /home type ffs (log, local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)

I also did:



Now, in the root of the disk, I found this:

meriadoc$ ls -l /boot*
-r--r--r--  1 root  wheel  66296 Sep 29  2014 /boot
-rw-r--r--  1 root  wheel  64096 Dec  3  2014 /boot.388000-2005-02-26
-rw-r--r--  1 root  wheel  64192 Dec  3  2014 /boot.388000-2005-04-28
-rw-r--r--  1 root  wheel  64224 Dec  3  2014 /boot.388000-2005-06-21
-rw-r--r--  1 root  wheel  64728 Dec  3  2014 /boot.388000-2005-07-11
-rw-r--r--  1 root  wheel  64968 Dec  3  2014 /boot.388000-2005-08-15
-rw-r--r--  1 root  wheel  75520 Dec  3  2014 /boot.388000-2006-01-26
-rw-r--r--  1 root  wheel  67624 Dec  3  2014 /boot.388000-2006-11-17

I think to remember (but as we see from the dates, time passed quickly)
that this is an attempt to fix boot blocks
I think I installed very old ones, from 2005/2006 and did so in 2014
(the date I installed NetBSD 6) because probably I had a similar issue!

I found it, I discussed with you. I still have it in my Mail folder
"SparcStation IPC: Data Access Exception"


This PR was mentioned (not by me) http://gnats.netbsd.org/42186

Is this fix present in the 8.2 ? or did it get lost? Or it was not the
right fix for me....


>> PS: in case, is jumping from 6.x to 8.x supported by an upgrade or is
>> 6->7->8 the only safe way?
> You can directly update to the target version.

Oh! good to know, Thanks.

Riccardo