*BSD News Article 36970


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!hpg30a.csc.cuhk.hk!news.hk.net!howland.reston.ans.net!news.sprintlink.net!sunserver.insinc.net!cato.Direct.CA!vanbc.wimsey.com!scipio.cyberstore.ca!nntp.cs.ubc.ca!cs.ubc.ca!anvil.ugrad.cs.ubc.ca!not-for-mail
From: h5h1@ugrad.cs.ubc.ca (Markus Meister)
Newsgroups: comp.os.386bsd.questions
Subject: Help! Can't access my D: drive
Date: 15 Oct 1994 10:36:10 -0700
Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
Lines: 34
Message-ID: <37p3uaINNhok@anvil.ugrad.cs.ubc.ca>
NNTP-Posting-Host: anvil.ugrad.cs.ubc.ca

Ok, here's the scoop. When I booted up I got this:
Invalid media type reading drive D
Abort, Retry, Fail?

That's booting under DOS of course. The thing is I have DOS on drive C:, and
DOS on most of drive D:, and the root partition for my FreeBSD 1.5.1.1 on
the rest of drive D:, and the bulk of FreeBSD on a SCSI drive. Now whenever
I try to access drive D: from DOS, I get the above error. I can still boot 
FreeBSD from it, though. Note that drive D: used to work fine under DOS
until now.
The DOS FDISK tells me correctly about my Extended DOS partition (88%) and
'Non-DOS' partition (12%). But then the 'logical drive information' tells
me about that another 285 meg parition (the same as the previously mentioned
88% ext-dos one), and 'usage:100%' and, get this, 'System: UNKNOWN'. That
looks to my unskilled eye like the problem.
The reason I'm posting all this stuff here is that I assume that FreeBSD
is somehow responsible for this mess (note that indirectly means I'm
responsible for it, since I doubt my very honorable FreeBSD would do
something like that without the user screwing up). However, I can't
remember doing anything, shall we say, 'fancy' in FreeBSD immediately
prior to this happening.
Now I'm of course wondering if there is any way to fix the drive up without
losing the data on it. I hope there's a way... maybe using some dirty hacking
tricks that someone knows about? After all, the information should still be
there, if I could just get DOS to access it. I hope the FAT is still around.
sigh.

Please respond my e-mail.. actually please respond at all! I would really
appreciate it!

- Markus ("That guy again!! Him and his $(*^! problems!")