Subject: Re: mount trouble / missing extutil.h / software not available
To: None <netbsd-help@netbsd.org>
From: None <polzer02@stud.uni-passau.de>
List: netbsd-help
Date: 03/18/2004 10:26:06
Quoting Manuel Bouyer <bouyer@antioche.eu.org>:
> On Wed, Mar 17, 2004 at 09:52:12PM +0100, polzer02@stud.uni-passau.de wrote:
> > 1. I have two FAT32 partitions, one primary, one logical in a extended
> > partition, and am not able to mount them. When I'm trying to mount
> > the primary, I get 'invalid superblock', when trying this with the
> > logical, it's 'device not configured'. What's wrong?
>
> For the first one: I guess you didn't use '-t msdos' for mount.
> For the second: you're probably using the wrong device. What do
> fdisk and disklabel say about this disk ?
# ---------- #
dreadnought# fdisk
Disk: /dev/rwd0d
NetBSD disklabel disk geometry:
cylinders: 16383 heads: 16 sectors/track: 63 (1008 sectors/cylinder)
BIOS disk geometry:
cylinders: 1023 heads: 255 sectors/track: 63 (16065 sectors/cylinder)
Partition table:
0: sysid 12 (Primary DOS with 32 bit FAT - LBA)
start 63, size 16723602 (8165 MB), flag 0x0
beg: cylinder 0, head 1, sector 1
end: cylinder 1022, head 254, sector 63
1: sysid 15 (Ext. partition - LBA)
start 16723665, size 11020590 (5381 MB), flag 0x0
beg: cylinder 1022, head 254, sector 63
end: cylinder 1022, head 254, sector 63
Extended partition table:
0: sysid 12 (Primary DOS with 32 bit FAT - LBA)
start 16723728, size 10490382 (5122 MB), flag 0x0
beg: cylinder 1023, head 254, sector 63
end: cylinder 1023, head 254, sector 63
1: sysid 5 (Extended partition)
start 27214110, size 530145 (258 MB), flag 0x0
beg: cylinder 1023, head 254, sector 63
end: cylinder 1023, head 254, sector 63
Extended partition table:
0: sysid 130 (Linux swap or Prime or Solaris)
start 27214173, size 530082 (258 MB), flag 0x0
beg: cylinder 1023, head 254, sector 63
end: cylinder 1023, head 254, sector 63
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>
2: <UNUSED>
3: <UNUSED>
2: <UNUSED>
3: sysid 169 (NetBSD)
start 27744255, size 50411970 (24615 MB), flag 0x80
beg: cylinder 1022, head 254, sector 63
end: cylinder 1022, head 254, sector 63
# ---------- #
dreadnought# disklabel /dev/wd0
# /dev/wd0d:
type: unknown
disk: storage_deck
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 78165360
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 829521 27744255 4.2BSD 1024 8192 87 # (Cyl. 27524*- 28346)
b: 1575504 28573776 swap # (Cyl. 28347 - 29909)
c: 50411970 27744255 unused 0 0 # (Cyl. 27524*- 77535*)
d: 78165360 0 unused 0 0 # (Cyl. 0 - 77544)
e: 48006945 30149280 4.2BSD 1024 8192 86 # (Cyl. 29910 - 77535*)
# ---------- #
# d is the primary, c is the logical.
# Miscellaneous linux kernels and userlands do not have problems with them.
# Yet:
dreadnought# mount_msdos /dev/wd0c /mnt/win
mount_msdos: /dev/wd0c on /mnt/win: Device not configured
dreadnought# mount_msdos /dev/wd0d /mnt/win
mount_msdos: /dev/wd0d on /mnt/win: Invalid argument
Note: it says 'invalid argument' here, but I got 'invalid superblock' once,
too - maybe that was my first try without _msdos or -t.
Oh, and btw: Why does fdisk use /dev/rwd0d ? Does (Net-)BSD differentiate
between partitioned and raw device access?
Leslie