From owner-freebsd-bugs  Thu Jun 29 08:35:57 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA28214
          for bugs-outgoing; Thu, 29 Jun 1995 08:35:57 -0700
Received: from hpanalog.mdc.com (HPANALOG.MDC.COM [130.38.16.213])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA28203
          for <freebsd-bugs@FreeBSD.org>; Thu, 29 Jun 1995 08:35:54 -0700
Message-Id: <199506291535.IAA28203@freefall.cdrom.com>
Received: by hpanalog.mdc.com
	(1.37.109.4/16.2) id AA04403; Thu, 29 Jun 95 10:36:01 -0500
From: Mike Heitmann <mike@hpanalog.mdc.com>
Subject: OnTrack Disk Manager Problems.
To: freebsd-bugs@FreeBSD.org
Date: Thu, 29 Jun 95 10:36:00 CDT
Mailer: Elm [revision: 70.85]
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

Hello,

If this has already been reported, sorry for wasting the space.

I installed 2.0.5-RELEASE on my home system, a Gateway2000 486DX250
with a Maxtor 1.26Gb EIDE drive as wd0 and a Western Digital 340Mb
EIDE drive as wd1.  The Maxtor drive is using the OnTrack Disk Manager
to allow DOS/Windows access.  BSD is installed on wd1, but I allocated
a small BSD slice on wd0 so I could access the dos filespace. 

All appears well until I access the dos file system OR the BSD slice on wd0
(the Maxtor drive using the OnTrack manager). BSD sees the files and trys to
access them, and then the system re-boots.

I don't have a pressing need to access the dos files, and I've removed the
entries to mount the wd0 slices from my /etc/fstab for now, but I thought
I'd report the problem since the release notes state 2.0.5 will work with
the OnTrack DM.  2.0.5 *does* recognize the slices created by the DM, but
it appears 2.0.5 has a problem accessing the files.

Let me know if you need more details.

Thanks,

Mike Heitmann
Internet: mike@hpanalog.mdc.com