Problem creating mount point for FAT32 device after upgrade

[GoranTornqvist]

Hi,
I just upgraded from FreeNAS 7 (0.7.2) to 9.1.0.1 - Sandstorm (revision 573) by importing my freenas conf.
Works fine besides one thing.
After the upgrade I cannot mount my FAT32 USB disk which was working fine in FreeNAS.
The disk is ONLINE in disk management but in mounts the status is ERROR.
Tried deleting the mount point and recreating it.
Then I get:
"Wrong partition type or partition number."
I see the disk in dmesg:
da4: <Freecom Hard Drive XS 1.00> Fixed Direct Access SCSI-4 device
da4: 40.000MB/s transfers
da4: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)

And fdisk /dev/da4 gives me:
******* Working on device /dev/da4 *******
parameters extracted from in-core disklabel are:
cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
start 2048, size 976748544 (476928 Meg), flag 0
beg: cyl 0/ head 32/ sector 33;
end: cyl 1023/ head 254/ sector 63

Not sure how to troubleshoot - any suggestions?

I also get a lot of warnings at boot up in the console about my config is from the old version of freenas.
Should I worry or do anything about this?

Thanks...

[alexey123]

I also get a lot of warnings at boot up in the console about my config is from the old version of freenas.

Config need convert, better way make it by hand
About FAT32 I have troubles before. I think NAS4Free not work with FAT32, only FAT16

[GoranTornqvist]

Hmm, you may be right. Shite...

tellus:~# ls -l /dev/da4*
crw-r----- 1 root operator 0, 109 Mar 8 07:58 /dev/da4
crw-r----- 1 root operator 0, 115 Mar 9 10:14 /dev/da4p1

tellus:~# /sbin/mount_msdosfs /dev/da4p1 /mnt/usb1
mount_msdosfs: /dev/da4p1: Invalid argument

Not sure if this has something to do with it:
http://forums.freebsd.org/showthread.php?t=11154

Solve:
FreeBSD don't see slice's because they are not present on the flash.
1. Windows XP: fill flash with "zeros" (WinHex)
2. FreeBSD: create slice type 6 FAT (sysinstall)
3. Windows XP: format flash with FAT
----
after plug in FreeBSD in /dev created /dev/da1s1 ))

[shakky4711]

Hello,

As far as I can remember FAT32 formatted devices with a capacity above 128GB needed a special switch in the mount command, try "-o large"

Please consider ALL OTHER FILE SYSTEMS EXCEPT UFS2 and ZFS ARE NOT RECOMMENDED TO USE WITH WRITE ACCESS, if absolute necessary to connect only read-only. BSD is not Linux and third party file system support is not so wide and stable as in Linux. Furthermore FAT and NTFS are Windows file systems and the underlying attributes are not compatible with unix like file systems. Windows uses read-only, archive or hidden attribut, unix like systems user-group-other permission, user, group, sticky bit, etc. Using FAT you can run in problems which are annoying.

This is the first issue, the second is this:
/sbin/mount_msdosfs /dev/da4p1 /mnt/usb1

When I look at the name it is a USB connected drive? Generally I made lots of bad experience with the USB implementation at FreeBSD, I always avoid it and plug in these disks into my client PC with other operating systems and copy/sync the data by network.

The issue with mangling device names (ada0, ada1...) when you boot with a connected drive is the third issue.

So my strongest recommendation still remains, simply connect the disk to your client and sync/copy by network.

Shakky

[GoranTornqvist]

Thanks for your reply.
Yes, I decided to give up on my idea to use FAT32, I reformatted the drive with UFS instead and now its working fine.
Yepp, its a USB drive but direct attached in VMware ESXi (pass through). Not sure if nas4free see it as a usb device or normal hard drive...