Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Nov 1997 16:04:31 -0800 (PST)
From:      Steven Kehlet <kehlet@dt.wdc.com>
To:        Julian Elischer <julian@whistle.com>
Cc:        hackers@freebsd.org
Subject:   Re: diskless freebsd, can't mount local msdos disk
Message-ID:  <Pine.NEB.3.96.971113155942.3347E-100000@mockingbird.dt.wdc.com>
In-Reply-To: <346B9081.15FB7483@whistle.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hmm, "mount -t msdos" doesn't work.  I thought "mount" was just a
wrapper for "mount_<fstype>" anyway..

  # mount -t msdos /dev/wd0s1 /mnt
  msdos: /dev/wd0s1: Invalid argument

Oops, yeah, I forgot about fdisk being weird (I suppose this definitely
shows there's a problem... ;-)):

  # fdisk
  fdisk: Can't get disk parameters on /dev/rwd0; supplying dummy ones
  ******* Working on device /dev/rwd0 *******
  parameters extracted from in-core disklabel are:
  cylinders=1 heads=1 sectors/track=1 (1 blks/cyl)
  
  parameters to be used for BIOS calculations are:
  cylinders=1 heads=1 sectors/track=1 (1 blks/cyl)
  
  fdisk: Invalid fdisk partition table found
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 0 is:
  <UNUSED>
  The data for partition 1 is:
  <UNUSED>
  The data for partition 2 is:
  <UNUSED>
  The data for partition 3 is:
  sysid 165,(FreeBSD/NetBSD/386BSD)
      start 1, size 0 (0 Meg), flag 80
          beg: cyl 1/ sector 1/ head 0;
          end: cyl 0/ sector 0/ head 0


Hmm, now why wouldn't it be able to get the disk parameters? (these
are wrong, of course--there is one DOS partition on this disk).

Steve



On Thu, 13 Nov 1997, Julian Elischer wrote:

> Date: Thu, 13 Nov 1997 15:42:57 -0800
> From: Julian Elischer <julian@whistle.com>
> To: Steven Kehlet <kehlet@dt.wdc.com>
> Cc: hackers@freebsd.org
> Subject: Re: diskless freebsd, can't mount local msdos disk
> 
> Steven Kehlet wrote:
> > 
> > I'm booting FreeBSD 2.2.5 diskless with the kernel's BOOTP features.
> > It detects the local hardware just fine (e.g. ethernet (obviously),
> > hard drive, floppy, etc), but if I try to mount the local msdos disk
> > like I would on a non-diskless station, it doesn't work.  Floppy
> > operations (mounting, hexdumping, fdwriting) seem to work, however.
> > Anyone know what's wrong, or have any suggestions what I could do?  If
> > I can give any more information, please let me know.
> > 
> > wdc0 at 0x1f0-0x1f7 irq 14 on isa
> > wdc0: unit 0 (wd0): <WDC AC33200L>
> > wd0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S
> > 
> > # foreach i (1 2 3 4)
> > ? mount_msdos /dev/wd0s$i /mnt
> 
> use mount -t msdos
> 
> does wd0 have 4 DOS slices on it?
> what does '/sbin/fdisk' have to say about it?
> do those partitions appear in /dev?
> 
> 
> > ? end
> > mount_msdos: /dev/wd0s1: Invalid argument
> > mount_msdos: /dev/wd0s2: Invalid argument
> > mount_msdos: /dev/wd0s3: Invalid argument
> > mount_msdos: /dev/wd0s4: Invalid argument
> > #
> > 
> > The msdos module loaded okay:
> > 
> > mockingbird:/home/kehlet-> modstat
> > Type     Id Off Loadaddr Size Info     Rev Module Name
> > MISC      0   0 f43ea000 0008 f43eb000   1 blank_saver_mod
> > VFS       1   4 f442f000 001c f4435090   1 msdos
> > 
> > Weird, too, if I try to hexdump the raw disk, nothing comes up:
> > 
> > # hd -v /dev/rwd0 |more
> > #
> > 
> > Thanks a ton,
> > 
> > Steve Kehlet
> >
> 




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