On Saturday 26 May 2001 17:22, you wrote:
> On Sat, 26 May 2001, Murray Armfield wrote:
> > > What does "fdisk wd0" and "disklabel wd0" show?
> >
> > no probs...
>
> And "disklabel wd0"??

# /dev/rwd0d:
type: ESDI
disk: ST313032A
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
total sectors: 25434228
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0
 
8 partitions:
#        size   offset     fstype   [fsize bsize cpg/sgs]
  a: 25434165       63      MSDOS                        # (Cyl.    0*- 
25232*)
  c: 25434228        0     unused        0     0         # (Cyl.    0 - 
25232*)
  d: 25434228        0     unused        0     0         # (Cyl.    0 - 
25232*)
  e: 25434165       63      MSDOS                        # (Cyl.    0*- 
25232*)

>
> Also, make sure your kernel has "file-system MSDOSFS" (which is default
> with GENERIC).

It does.

I gave up with that disk after using an new partition or an extended 
partition freshly created in NT. Found out after experimentation that 
wd0{a,b,c,d,e,f,g,....} refer only to the active partition. Is there any way 
of bypassing this instead of fdisk -a? If you'd like the disklabel for 
partition 1 just email... I'll have to recreate the partition but thats no 
prob.

I then chucked in a spare drive and used the whole thing rather than trying 
to hit the second partition, and formatted as fresh FAT from NT.

From NetBSD-current, the FAT drive would no load at all. An fdisk revealed 
the active partition was partition 4; changed this to 0 and saved data. Then 
looked at disklabel. This showed nonsense (its gone now but easy to recreate) 
so I hacked the partition definitons appropriately and the drive now happily 
mounts as msdos and everything is fine.

However, NT obviously is responsible for this disk info or there are some 
probs in the code. I suggest this is reviewed as every time I have used FAT 
disks, I have had to hack disklabel stuff........may not be NetBSD issue, 
rather inconsistant DOS,Win,NT,ME formatting,fdisking I don't know.

Regards,
	Murray Armfield