I have an Ultra 60 /w/ an IBM DDRS39130SUN9.0G as the boot disk and an 
unused IBM DNES30917SUN9.0G as a currently unused second drive.

The controller is esiop0 (Symbios Logic 53c875)

It is currently running 2.0.2 but will probably change to 2.1 before it 
goes into production.

Since the machine is currently not in production it could be used to test 
various builds.

I plan on running 2.1 (plus today's security updates) soon and will let you 
know if I have any odd problems with the disks.


At 07:50 PM 11/8/2005 +0100, Manuel Bouyer wrote:
>On Tue, Nov 08, 2005 at 09:45:44AM +0100, edwin wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> >
> > After installing NetBSD 2.1 on an Ultra 60, some strange things happend.
> > When I do an ls -al /etc , no files seems to exist in this dir.
> > However, when I do an vi /etc/rc.conf  There's no problem in edditing
> > the file.
> >
> > If I boot into single user mode, and do again an ls -al /etc/ all the
> > files get listed.
> >
> > So I tried to make a tar file of /etc in single user mode, and
> > untarred this in multi usermode.
> > Next thing I know, all files and dir in / are not listed with ls -al /
> > But cd /usr works. and an ls -al /usr also.
> >
> > This machine is running NetBSD 2.0 for more then 4 months now without
> > any problem.
> > So I figured, maybe its just my disk , this seems a filesystem problem.
> > Instead of an upgrade, I tried a fresh install of NetBSD 2.1.
> > Hopefully I recieve  errors when the filesystem are created, and to go
> > from there.
> > So I downloaded the NetBSD 2.1 iso, and checked the MD5SUM which is ok.
> > The install starts without any problem, and after saying yes to the
> > partition scheme, I entered a name for the disk.
> > But by writing the disklabel to disk , I recieved the error: disklabel
> > command not found.
> >
> > After this advanture, I switched back to NetBSD 2.0.
> > dmesg and other information is lost with the reinstall.
> > But when needed, I can reproduce the errors and willing to do tests.
> >
> > Hopefully someone could help, or give me a direction.
>
>You have a scsi drive connected to a esiop adapter ?
>There seems to be changes between 2.0 and 2.1 in the esiop driver which cause
>issues with some disks. I still need to setup a box to try to reproduce this
>(the model of drive you're using would help me).
>
>--
>Manuel Bouyer <bouyer@antioche.eu.org>
>      NetBSD: 26 ans d'experience feront toujours la difference
>--



------------------------------------------------------------------
"Unix is user friendly, it's just | Steven Grunza
particular about with whom it     | voice:  (856) 787 - 2759
makes friends."                   | fax:    (856) 866 - 2033
  - Unknown                        | mailto:steven_grunza@ieee.org
-------------------------------------------------------------------