Yes, it's a FAT system.

Yes, I'm using a duplicate of the line used for the other one, with the UUID and mount point changed for the drive in question.

Oh, and I added the lines ADA mentioned (replacing my previous versions of those lines where applicable, and adjusted, of course, for the hardware I'm using) but I still can't get it to recognize my second monitor.

What do you mean? If you have it installed, you should be able to just run "nvidia-settings" from a command-line as root and it will come up. If you don't have it, it should be included in the Nvidia driver package available here or from your distro's package repositories. In Ubuntu, for example, you can just apt-get install nvidia-settings.

Would you post the above results please?

I could've sworn I did already, but if not, here it is again:

I have ubuntu, but it claims not to have that package. Is there something I need to do to enable certain repositories, or do I just not have it?

Yeah, you will. The nvidia-settings package is in the restricted repository, so you'll have to enable that. Sorry, didn't think of that.

Alright, went to nvidia settings, but my command line showed the following errors:

You add a line like this to your /etc/apt/sources.list file.
You can probably also do it from withing Synaptic. Not sure exactly how, since I'm using Kubuntu, but I know Adept has a "manage repositories" feature with a checkbox to enable restricted software. Synaptic most likely has something similar.

Er. I figured it out, so I changed my reply to the next problem I encountered. Sorry for the confusion.

My mistake. Sorry.

This is mounted under your user name! So with these permissions, you should be able to do anything with it from your account.

So I am confused. Is this from manually mounting it, or was it automatically mounted via fstab? (You can certainly set up fstab to mount it this way, but I didn't think you had.) Could you post the output of

EDIT: Actually, what that looks like is what happens when the system automatically mounts a removable medium like a thumb drive and puts an icon on your desktop.

Ah. Well that's probably what's at the root of the problem. That command doesn't give me any output, errors or otherwise.

EDIT: After mounting the volume, that command gives me this output:
EDIT2: Oh, and to answer your first question, I have to manually mount it. If I put it on fstab, it claims I don't have permission to mount it anymore.

OK. I'd kind of lost my train of thought on this thread. I've re-read the whole thread and think I remember where I was going with this.
I wanted to see if you could manually mount it just to make sure it was doable. I.e. make sure there wasn't some kind of a problem with the filesystem that was preventing mounting. We've established that. So now, the mystery of why it won't mount automatically from an fstab entry at boot ...

Try adding (or replacing depending on the current state of the file) this line to fstab. Make sure the partition is unmounted first.

Of course, use the real UUID for the partition. The new options tell it not to automatically mount the partition at boot time and to let non-priviledged users mount it. After making the change, try to mount the partition as a normal user and see if you get any errors.

Wait, am I doing this with the NIFLHEIM partition, which already mounts automatically with no problem, or the MUSPELHEIM partition, the one I'm currently trying to get working?

I copied and edited that line from your earlier post about your sucessful mount and could have *sworn* I had edited it to reflect the partitiion that wasn't mounting correctly. So you are quite correct. It should be the MUSPELHEIM partition, the one you are currently trying to get working. Sorry about that.

I tried mounting it, and got this error:

Notably, this did not happen prior to adding the volume to FSTAB