Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Dec 2000 17:28:40 -0500 (EST)
From:      Tim McMillen <timcm@umich.edu>
To:        Mike Meyer <mwm@mired.org>
Cc:        questions@freebsd.org
Subject:   Re: vnconfig question
Message-ID:  <Pine.SOL.4.10.10012081711470.25259-100000@breakout.gpcc.itd.umich.edu>
In-Reply-To: <14897.23031.119975.387586@guru.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On Fri, 8 Dec 2000, Mike Meyer wrote:
> Tim McMillen <timcm@umich.edu> types:
> > Thank you, but it still doesn't work.
> 
> You didn't try what I meant, which was:
> 
> # vnconfig /dev/vn0 ./maxtorbackup2
> # mount -t msdos /dev/vn0s1 /mnt

	Yes, you're right, I did not understnd what you meant, but of
course what you're suggesting makes more sense now that I see it.  But:
tim# vnconfig /dev/vn0 ./maxtorbackup2
tim# mount -t msdos /dev/vn0s1 /mnt
msdos: /dev/vn0s1: Invalid argument

	Even though this and Ken's suggestion should accomplish the same
thing, Ken's works:
tim# dd if=/dev/ad1s1 of=maxtorbackup3
1031121+0 records in
1031121+0 records out
527933952 bytes transferred in 633.425457 secs (833459 bytes/sec)
tim# vnconfig /dev/vn0 ./maxtorbackup3
tim# mount -t msdos /dev/vn0 /mnt
tim# ls /mnt
CONFIG.SYS      IO.SYS          NANSI.SYS       QBASIC      AUTOEXEC.BAT

> Sorry I can't test it for you; I'd like to know if it works.

	Would you like remote root access to my system with ssh to try it
yourself?  Haha just kidding. :)
	Seriously, thanks to both of you, Mike and Ken.  Now I can wipe
that drive and not worry about being able to access the info that was on
it.

							Tim

> > On Fri, 8 Dec 2000, Mike Meyer wrote:
> > > Tim McMillen <timcm@umich.edu> types:
> > > > 	Hi, I am trying to access an image that I made of a small hard
> > > > drive.  I made it pretty simply with dd if=/dev/ad1 of=file
> > > > I can get vnconfig working fine with an iso, but I try somethig similiar
> > > > with my image and I get this output and error:
> > > > tim# ls
> > > > maxtorbackup
> > > > tim# vnconfig vn0c ./maxtorbackup
> > > > tim# mount_msdos /dev/vn0c /mnt
> > > > mount_msdos: /dev/vn0c: Invalid argument
> > > > 
> > > > 	The disk was msdos ver 6 and mounting it worked correctly so I
> > > > figured this would too.  I read the manpage and can't see where I am going
> > > > wrong.  Did I need certain options to dd when I made the image to get this
> > > > to work?  Help would be greatly appreciated.
> > > 
> > > At a wild guess, you're running into problems with the slice
> > > table. Without knowing how you mounted it as a disk and how you
> > > created the image, it's hard to say. You might try using the
> > > appropriate sliced vn device (vn0s1, say).
> > 
> > Ok I mount it like this:  (I included the wrong ways in case that tells
> > somebody something)
> > tim# mount -t msdos /dev/ad1 /mnt
> > msdos: /dev/ad1: Invalid argument
> > tim# mount -t msdos /dev/ad1c /mnt
> > msdos: /dev/ad1c: Invalid argument
> > tim# mount -t msdos /dev/ad1s1 /mnt
> > tim# ls /mnt
> > CONFIG.SYS      IO.SYS          NANSI.SYS       QBASIC      AUTOEXEC.BAT
> > etc.
> > 
> > 	I created the image exactly as above in my message,
> > tim# dd if=/dev/ad1 of=maxtorbackup2
> > 
> > 	But I still get: 
> > tim# vnconfig /dev/vn0s1 ./maxtorbackup2
> > tim# mount_msdos /dev/vn0s1 /mnt
> > mount_msdos: /dev/vn0s1: Invalid argument
> > 
> > tim# vnconfig vn1s1 ./maxtorbackup2
> > vnconfig: /dev/vn1s1: No such file or directory
> > 
> > 	The problem may be:  (which I had forgotten about.)
> > tim# disklabel ad1
> > disklabel: ioctl DIOCGDINFO: Invalid argument
> > 
> > 	Do I need to put a valid disklabel on the drive first?  Or redo
> > the MBR?  And if I do either of these will the drive still boot into DOS?
> > It is used usually as the primary drive on an old 486 for my mom.
> > 	I thought that if I could mount the drive then I could do the same
> > with the image using vnconfig.  But I guess I didn't understand much of
> > the manpage.  Any idea what is wrong?  If you need any other info, let me
> > know.
> > 
> > 						Tim



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.4.10.10012081711470.25259-100000>