Date: Fri, 30 Jun 1995 11:51:38 +1000 From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org, mike@hpanalog.mdc.com Subject: Re: OnTrack Disk Manager Problems. Message-ID: <199506300151.LAA20667@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>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. 2.0.5 doesn't need a small BSD slice on a drive to access DOS or other slices on the drive. However, configuration of the bootstrap is easier if you have a BSD slice on the first drive. Otherwise you would need a boot selector program somewhere on the first drive, and sysinstall doesn't properly support installing one. >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. The following details should be included with all reports about slice/ partition problems: 1) Boot messages for booting with -v. These are in recorded near the end of /var/log/messages if the system booted far enough to give you a login prompt. Edit the file to remove old messages and messages about non-disks. 2) Contents of /etc/fstab. 3) Output from `fdisk /dev/rXXX' for all relevant drives XXX (e.g. wd0). 4) Output from `disklabel /dev/rXXX' for XXX as in 3). 5) Output from `disklabel XXXsY' for XXX as in 3) and all relevant BSD slices sY (e.g., wd0s2). Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506300151.LAA20667>