what format are you going to use?
I run v12 and ntfs as far as I know is a read only format, so it might still be the the same with v11.2. NTFS = read only.
You will need to look into that. especially if you're going to use it for storage for FreeBSD exclusively then you might really want to change its format to UFS, or another format that FreeBSD can read and write to.
For which ever one you do pick.
look into how to mount it using your terminal. Whence you get it to mount via a terminal then add that to your fstab in a slightly modified form.
just follow the headings to know where to put what.
Code:
# Device Mountpoint FStype Options Dump Pass#
/dev/ada1s1a / ufs rw 1 1
For example on my laptop I have a ext4 partition. to mount this via cli ( in lue of automount, which I use). taking if off automount. (that part just requires I open a file manager and click on that arrow to unmount it.)
to find my (partitons) slices.
Code:
$ ls /dev/ada*
/dev/ada0 /dev/ada0s2 /dev/ada1s1 /dev/ada1s2
/dev/ada0s1 /dev/ada1 /dev/ada1s1a
now using the terminal (cli) to find the correct mount command.
Code:
mount -t ext2fs /dev/ada1s2 /mnt
well, that worked, so now unmount it, then make preps to add it to the fstab
create a mount point if one does not exist.
Code:
$ mkdir -p /home/userx/myextdrive
in /etc/fstab add the formula to now mount the slice to the mount point.
Code:
# Device Mountpoint FStype Options Dump Pass#
/dev/ada1s1a / ufs rw 1 1
#added by me
/dev/ada1s2 /home/userx/myextdrive ext2fs rw 1 0
now mount it via fstab
it is now mounted
Code:
$ ls /home/userx/myextdrive
bin etc lib64 mnt root srv usr
boot home lost+found opt run sys var
dev lib media proc sbin tmp
If anything goes wrong the system will definitely notify you of the infraction .
NOTE:
ada0 is the device notation, you may need to add a slice into it in order to actually use it. Which the '0' (zero) indicates first drive, if you have two then you should look for ada1.
That being another BIG Point, Make sure you have the right drive and slice before modifying it in anyway whatsoever. The drive notation is zero based.
0 = 1
1 = 2
2 = 3
so on and so forth. Whereas the slice notation is not. 1s, s2, or s1a s2a etc.