First make sure that the partition is not mounted. Then as root run "fsck.ext3 /dev/hdd9". Please read the manpage for "fsck.ext3". There are some additional options that you may want to use. Especially the one to set how much space to reserve for the root user. Since this partition isn't a system partition, you could set that to 0 percent.
You can also use the YaST2 partitioner. YaST2 -> System -> Partitioner. Doing it this way you can enable additional features like "user xattr" in a drop down list, or change the ownership & permissions of the mounted directory. The YaST2 partitioner will also create the fstab entry for you. I'd recommend using it, even more if you were to create a win32 partition on a dual booting computer. It will include options such as file name encoding and for memory sticks options like noatime & flush that you may forget about.
If this will be a publicly writeable share, make sure that you set the "sticky" bit on the directory. E.G. "sudo chmod ugo=rwxt /srv/samba/share".
Since the name "fat" probably wouldn't be a very good name, you might as well create the directory (i.e the mount-point) in a more standard place. For SuSE that would be under /srv/samba/. Perhaps use your hosts name or something descriptive such as "podcasts" or "music" if that is what they will be used for.
If a public share is what you want, I had already set up a test share on my laptop, tested it and recommend it in a previous post.
In the [General] section of smb.conf you could use this setting:
map to guest = Bad User
Then the definition for the share could look like this:
comment = File Sharing on WildSwede
path = /srv/samba
read only = No
guest ok = Yes
You would use change the name, comment and mount point of course. This simple share will allow authenticated uses to save files which retain their permissions, and public users (who don't have Linux accounts & entries in smbpasswd) to save files without having to enter a password. The files for these users will be saved as using the the Linux user "nobody" as the owner. This is a very handy share if you have both Linux users and windows users. Linux users can mount the share with the cifs filesystem and even use acls and file attribs as if this were a local filesystem. Windows users entered with smbpasswd will have files retain ownership and some permissions. Someone not authenticated can save files as well, but in Samba, the owner will be displayed as the "Guest" windows user which is mapped to the "nobody" Linux user. guest & nobody are the standard aliases for "anybody" or anonymous in the respective OSes.
I would also recommend using "security = user". "Security = share" is obsolete. It was used for win95.
I would not recommemd "force user" and "force group". That is what "Map to Guest = Bad User" is for. Allowing authenticated users to retain the permissions on their own files is more flexible and the configuration I gave is a lot easier.