Although i remember giving all the code in a couple of threads to sort things, i don't know which exact errors you are facing. There are is a way to get around the shortage of internet access from the N900 itself.
Try to redirect the output of the commands to a text file, copy this file to your pc, then paste its content here.This would give you root rights, then unmounts the MyDocs partition, redirects (>) the output of the fsck commant to the output.txt file and finally append (>>) the output of the mount command to output.txt file also.
Accordingly the codeblock for those debugging commands would be

If the backup has folders and files in it then copy the backup over the first and hopfully you will get your (some) contacts back. I have never tried this so I cannot say how successful it wil be. Fingers crossed.

Can you give me some help how to get it to txt file?

The first one is short so I'll type it quickly

# fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT 32, LFN
/dev/mmcblk0p1: 6020 files, 384378/442377 clusters
#

# mount /dev/mmcblk0p1 /home/user/MyDocs
#

no problems.

Why are there no first file? What should I copy it over, since there are no file, or should I copy and then rename it? I have copied everything I could from the n900 to my Laptop, so I should have everything safe. All my docs and pics and all are there. Just can't get the n900 to see them.

Just add the sign for 'larger as' > to the command and specify the name of the file. That will give you no response in the terminal, because it redirects the terminal output into the file.
This indicates that the MyDocs partition is clean, there is no corrupt file system here.
The 'mount' command without any further argument will list any partitions and directories which are mounted on the device. There could be some indication that important stuff is missing right now.

rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,noatime,size=1024k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
/dev/mmcblk0p2 on /home type ext3 (rw,noatime,errors=continue,commit=1,data=writebac k)
/home/opt on /opt type none (bind)
nodev on /sys/kernel/debug type debugfs (0)
/opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind)
/opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind)
/opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind)
/opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind)
/opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind)
/dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (0)
Filesystem Size Used Available Use% Mounted on
rootfs 227.9M 148.7M 75.0M 66% /
ubi0:rootfs 227.9M 148.7M 75.0M 66% /
tmpfs 1.0M 76.0k 948.0k 7% /tmp
tmpfs 256.0k 72.0k 184.0k 28% /var/run
none 10.0M 76.0k 9.9M 1% /dev
tmpfs 64.0M 100.0k 63.9M 0% /dev/shm
/dev/mmcblk0p2 2.0G 601.1M 1.3G 31% /home
/home/opt 2.0G 601.1M 1.3G 31% /opt
/opt/pymaemo/usr/lib/python2.5
2.0G 601.1M 1.3G 31% /usr/lib/python2.5
/opt/pymaemo/usr/share/pyshared
2.0G 601.1M 1.3G 31% /usr/share/pyshared
/opt/pymaemo/usr/lib/pyshared
2.0G 601.1M 1.3G 31% /usr/lib/pyshared
/opt/pymaemo/usr/share/python-support
2.0G 601.1M 1.3G 31% /usr/share/python-support
/opt/pymaemo/usr/lib/python-support
2.0G 601.1M 1.3G 31% /usr/lib/python-support
/dev/mmcblk1p1 3.7G 32.0k 3.7G 0% /media/mmc1
/dev/mmcblk0p1 27.0G 23.5G 3.5G 87% /home/user/MyDocs
drwxr-xr-x 49 user users 4096 Dec 3 11:25 .
drwxr-xr-x 25 root root 1632 Dec 3 09:34 ..
drwxr-xr-x 3 root root 4096 Dec 3 11:28 .apt-archive-cache
drwx------ 26 root root 16384 Jan 1 1970 lost+found
drwxr-xr-x 44 root root 4096 May 8 19:57 opt
drwxr-xr-x 3 user users 4096 Nov 27 20:01 temp
drwxr-xr-x 58 user users 4096 May 8 22:35 user

Disk /dev/mmcblk1: 121008 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk1p1 0+ 121007 121008- 3872248 b W95 FAT32
/dev/mmcblk1p2 0 - 0 0 0 Empty
/dev/mmcblk1p3 0 - 0 0 0 Empty
/dev/mmcblk1p4 0 - 0 0 0 Empty

Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 1 884864 884864 28315648 c W95 FAT32 (LBA)
/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux
/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris
/dev/mmcblk0p4 0 - 0 0 0 Empty

Something to do with your crash, you have lost your contacts, so copying the backup should restore them.

Make sure "Contacts" is closed, then type in XTerm.
If we can find your contacts again then you can back them up and then reflash.

JonWW I'm not too concerned with my Contacts, since I know they are safe at home, further I have my old phone with me, and most of my contacts are still on there, the problem is even if I do copy the 2'nd file to the first, the n900 will still not see it, and the backup utility is not working either. I did copy my previous backups to my laptop aswell. So I think the data is safe. I'm a bit scared of flashing, so I'll stick with any other options until it's the only option left. Wanna get behind why it happened.

I doubt you'll be able to find out why it happened. I would reflash because everything will be back to factory deflaults and if it crashes again then it could indicate you have a hardware problem.

Also, it's good to know how to reflash, there's nothing to worry about and it will format the corrupted drive.

Ok JonWW, how do I go about it? I know it's somewhere in the wiki, but how do I get there?