The Disk & Filemanager module isnt working for some reason, when it does work I have to manually enable the 2nd partition and mount it.
I was googling around and I came up with the /etc/fstab file, this is what mine says:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda2
UUID=1faa78ed-c4ea-4a65-be86-8b4315e41cc9 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# /dev/hda6
UUID=551bb472-1e23-467a-9f7c-1acaba84370b none swap sw 0 0
/dev/hdc /media/cdrom0 auto user,atime,auto,rw,dev,exec,suid 0 0
/dev/hdc /media/cdrom0 auto users,atime,auto,rw,dev,exec,suid 0 0
/dev/hda1 /partition2 auto users,noauto,atime,rw,nodev,noexec,nosuid 0 0

Is everything right? Should I change anything? :/

Help

Example:

/dev/xxxx /mnt/xxxx auto user,async,auto,rw,dev,exec,suid 0 0

Replace the xxxx by the name of the device.
You will be able to use it as a regular user (not root), if you don't want it to be accessible by regular users, use nouser instead of user.
For a better understanding of /etc/fstab see:
http://tinyurl.com/fzhoj
I recommend you learn more about /etc/fstab.

Note: Don't forget to create the /mnt/xxxx directory, if not already present. You can use another path than /mnt/xxxx though. I use /home/user/myfiles for /dev/hda2.

Thanks alot dude. Im going to read up on fstab.

See the manual pages for fstab and mount also.

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

Too late, I touched god know what and when I restarted it didnt want to boot up. Backed everything up, partitioned my hard drive and made /home a seperate partition. I installed an old copy of ubuntu and it doesn't want to upgrade :/

Meh, Im going to download a new copy of Kubuntu and format the OS partition...

Thanks guy, btw.

I know this problem is solved but if anyone ever runs into this again, contrast the UUID against the hdparams file, althougth most of the time the fstab will contain the /dev/[h,s]d[0-9], sometimes it will be id by the UUID, and it will actually work. This kind of mirrors Solaris use of WWN when using Fcal drives in some of the newer system (v240, 490s)

UUID is only used by LVM.
If there is no LVM being used, a UUID will not work, in any case.
Maybe you are confusing an Ext2/3 disk label with UUID.

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you

you can use a universally unique identifier in order to specify which device to mount in an fstab for some linux distros.

I am not sure where you get this certainity from, it was actually listed in the original fstab that was post, it was commented out, but I bet the system generated it when it was building the system.

Yes, the system did generate it I am sure also.
The /dev/device specifier is the PV (Physical Volume).
The UUID is the LV (Logical Volume).

__________________
[autopsy@localhost ~]$ cat you >>/dev/null && rm -rf you