Hey guys, well i dont know where to ask and get support.. I just thought that you guys can give me an advice to solve this problem of mine using terminal or any method...

My memory card isnt showing anything while i have more than 1 GB of data on it!! I dont remember sending any file using an unapropriate way...

I checked the memory card details and it was writen things that mean 1 GB is used and such things... So please guys tell me what to do to solve this problem!!!

I had problem in my phone's memory some time back but i got support from the maemo team and it is now fine, now i hope u help me to solve this as well!!

Thanks in advance for your help!!

Try to check the file system of the internal memory card. You need rootsh installed for this procedure:There might be anerror in the umount comand, if the partition is not mounted, what would be alright.
Good luck!

hey thanks but it is not working!!
I tried it and it just did somethings on my phone memory not the memory card... What i am asking is how can i let my memory card's contents show up using the n900's x terminal.??
Anyway thanks for ur help but please try to help me solve themain problem

This is an external card,okay! I totally missed that!
If the built-in file manager application does not show, try to mount the card as rootIf that does not help, please show the output of

It's alright!
I tried the commands u wrote but they were not working...

This is the output:

/home/user # mount /dev/mmcblk1p1 /home/user/MyDocs/externalcard
mount: mounting /dev/mmcblk1p1 on /home/user/MyDocs/externalcard failed: Device or resource busy
/home/user #

but i restarted my phone and i re_wrote the command again and it gave no output.. So i tried the second one

and it gave the following:


/home/user # sfdisk -i
sfdisk version 3.08 (aeb@cwi.nl, 040824) from util-linux-2.12r
Usage: sfdisk [options] device ...
device: something like /dev/hda or /dev/sda
useful options:
-s [or --show-size]: list size of a partition
-c [or --id]: print or change partition Id
-l [or --list]: list partitions of each device
-d [or --dump]: idem, but in a format suitable for later input
-i [or --increment]: number cylinders etc. from 1 instead of from 0
-uS, -uB, -uC, -uM: accept/report in units of sectors/blocks/cylinders/MB
-T [or --list-types]:list the known partition types
-D [or --DOS]: for DOS-compatibility: waste a little space
-R [or --re-read]: make kernel reread partition table
-N# : change only the partition with number #
-n : do not actually write to disk
-O file : save the sectors that will be overwritten to file
-I file : restore these sectors again
-v [or --version]: print version
-? [or --help]: print this message
dangerous options:
-g [or --show-geometry]: print the kernel's idea of the geometry
-G [or --show-pt-geometry]: print geometry guessed from the partition table
-x [or --show-extended]: also list extended partitions on output
or expect descriptors for them on input
-L [or --Linux]: do not complain about things irrelevant for Linux
-q [or --quiet]: suppress warning messages
You can override the detected geometry using:
-C# [or --cylinders #]:set the number of cylinders to use
-H# [or --heads #]: set the number of heads to use
-S# [or --sectors #]: set the number of sectors to use
You can disable all consistency checking with:
-f [or --force]: do what I say, even if it is stupid
/home/user # sfdisk --list

Disk /dev/mmcblk1: 60352 cylinders, 4 heads, 16 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/62/61 (instead of 60352/4/16).
For this listing I'll assume that geometry.
Units = cylinders of 1936384 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk1p1 2+ 1021- 1020- 1927164+ 6 FAT16
start: (c,h,s) expected (2,10,26) found (2,2,10)
end: (c,h,s) expected (1021,18,8) found (957,61,61)
/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

so what can i do??

Fat16, really Fat16, which application did formate that!
Well try the file system check on that partitionEither mount with the above command or reboot.

Hey!!
I tried the commands the first line gave not output but the second line gave the following:


the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0869.jpg".
(Short name FSCK0000.049 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0871.jpg".
(Short name FSCK0000.050 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0873.jpg".
(Short name FSCK0000.051 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0882.jpg".
(Short name FSCK0000.052 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0885.jpg".
(Short name FSCK0000.053 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0886.jpg".
(Short name FSCK0000.054 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0890.jpg".
(Short name FSCK0000.055 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0891.jpg".
(Short name FSCK0000.056 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0896.jpg".
(Short name FSCK0000.057 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0897.jpg".
(Short name FSCK0000.058 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0970.jpg".
(Short name FSCK0000.059 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0934.jpg".
(Short name FSCK0000.060 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0907.jpg".
(Short name FSCK0000.061 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0939.jpg".
(Short name FSCK0000.062 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0910.jpg".
(Short name FSCK0000.064 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0911.jpg".
(Short name FSCK0000.065 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0912.jpg".
(Short name FSCK0000.066 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0913.jpg".
(Short name FSCK0000.067 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0914.jpg".
(Short name FSCK0000.068 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0915.jpg".
(Short name FSCK0000.069 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0971.jpg".
(Short name FSCK0000.070 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0944.jpg".
(Short name FSCK0000.071 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0945.jpg".
(Short name FSCK0000.072 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0920.jpg".
(Short name FSCK0000.073 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0921.jpg".
(Short name FSCK0000.074 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0922.jpg".
(Short name FSCK0000.075 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0946.jpg".
(Short name FSCK0000.076 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0924.jpg".
(Short name FSCK0000.077 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0925.jpg".
(Short name FSCK0000.078 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0947.jpg".
(Short name FSCK0000.079 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0927.jpg".
(Short name FSCK0000.080 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0928.jpg".
(Short name FSCK0000.081 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0950.jpg".
(Short name FSCK0000.083 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0951.jpg".
(Short name FSCK0000.084 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0952.jpg".
(Short name FSCK0000.085 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0972.jpg".
(Short name FSCK0000.086 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0973.jpg".
(Short name FSCK0000.087 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0975.jpg".
(Short name FSCK0000.088 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0980.jpg".
(Short name FSCK0000.089 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0981.jpg".
(Short name FSCK0000.090 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0982.jpg".
(Short name FSCK0000.091 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0983.jpg".
(Short name FSCK0000.092 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0984.jpg".
(Short name FSCK0000.093 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0986.jpg".
(Short name FSCK0000.094 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0987.jpg".
(Short name FSCK0000.095 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0988.jpg".
(Short name FSCK0000.096 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0989.jpg".
(Short name FSCK0000.097 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0995.jpg".
(Short name FSCK0000.098 may have changed without updating the long name)
Not auto-correcting this.
Wrong checksum for long file name "Image0998.jpg".
(Short name FSCK0000.099 may have changed without updating the long name)
Not auto-correcting this.
/dev/mmcblk1p1: 616 files, 41202/60216 clusters
/home/user #

so what should i do?? This is part of the output.. The other part i guess the xterminal couldnt view all the outputs...

So what should i do??

something a bit more basic first.

if you run the built in file manager, do you see MMC1 listed as one of the storage when you first start the app?

if you plug the micro-sd into a PC - can it be read?

did you remove your SIM card or battery etc lately? i had this problem and it was due to a lose micro-sd. i removed it, and remounted it back into its slot and it worked again.