Search Discussions:
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Advanced Search...
Welcome to Nokia Support Discussions! Here you can share advice and tips with thousands of other Nokia users around the world in English. Many Nokia employees also follow and participate in the discussions, see our guidelines for more information. Everyone can search and read the discussions, but to post your own question or reply to others, simply sign in with your Nokia account. If this is your first time here, you can choose an alias to represent you. And if you don't have a Nokia account yet, please register.
Reply
Topic Options

Re: n900 - memory unaccessible, unable to save con...

cuatanic
Advisor
cuatanic
Posts: 11

n900 - memory unaccessible, unable to save content

Options

‎2013-02-12 17:22

i wanted to take a photo but a messge that states memory unaccessible, unable to save content shows.

i have typed dmesg in the x terminal and these are the logs.

[ 3.123321] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[ 3.160308] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.160369] UBIFS: file system size: 254822400 bytes (248850 KiB, 243 MiB, 1975 LEBs)
[ 3.160430] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 3.160491] UBIFS: media format: 4 (latest is 4)
[ 3.160522] UBIFS: default compressor: lzo
[ 3.160552] UBIFS: reserved for root: 4384586 bytes (4281 KiB)
[ 3.161163] VFS: Mounted root (ubifs filesystem).
[ 3.161346] Freeing init memory: 144K
[ 4.915618] tsl2563 2-0029: model 7, rev. 0
[ 5.055847] lp5523 2-0032: LP5523 Programmable led chip found
[ 5.056579] Linux video capture interface: v2.00
[ 5.171020] Registered led device: twl4030:vibrator
[ 5.188293] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
[ 5.212005] I2C driver for Si4713 FM Radio Transmitter
[ 5.458068] isp_mod: Unknown symbol iommu_restore_ctx
[ 5.458526] isp_mod: Unknown symbol iommu_vfree
[ 5.459259] isp_mod: Unknown symbol iommu_put
[ 5.459747] isp_mod: Unknown symbol iommu_save_ctx
[ 5.460174] isp_mod: Unknown symbol iommu_vunmap
[ 5.460693] isp_mod: Unknown symbol iommu_vmalloc
[ 5.462127] isp_mod: Unknown symbol iommu_get
[ 5.462768] isp_mod: Unknown symbol iommu_kmap
[ 5.463256] isp_mod: Unknown symbol da_to_va
[ 5.463836] isp_mod: Unknown symbol iommu_vmap
[ 5.464172] isp_mod: Unknown symbol iommu_kunmap
[ 5.464538] isp_mod: Unknown symbol videobuf_to_dma
[ 5.573822] isp_mod: disagrees about version of symbol struct_module
[ 6.055816] i2c_omap i2c_omap.2: controller timed out
[ 6.112884] lp5523 2-0032: got interrupt from led chip
[ 6.113433] lp5523 2-0032: interrupt from led chip 4f
[ 6.113464] lp5523 2-0032: all engines configured
[ 6.113525] lp5523 2-0032: disabling engines
[ 6.114105] Registered led device: lp5523:kb1
[ 6.114257] Registered led device: lp5523:kb2
[ 6.114440] Registered led device: lp5523:kb3
[ 6.114562] Registered led device: lp5523:kb4
[ 6.114715] Registered led device: lp5523:b
[ 6.114837] Registered led device: lp5523:g
[ 6.114990] Registered led device: lp5523:r
[ 6.115142] Registered led device: lp5523:kb5
[ 6.115264] Registered led device: lp5523:kb6
[ 6.181121] nokia-av nokia-av: accessory detect module initialized
[ 6.197662] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[ 6.205352] Bluetooth: Core ver 2.15
[ 6.227783] NET: Registered protocol family 31
[ 6.227844] Bluetooth: HCI device and connection manager initialized
[ 6.227874] Bluetooth: HCI socket layer initialized
[ 6.282379] TSC2005 driver initializing
[ 6.283081] input: TSC2005 touchscreen as /class/input/input3
[ 6.436981] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[ 6.507202] hci_h4p hci_h4p: Registering HCI H4P device
[ 6.507507] SSI DRIVER Version 1.1-rc2
[ 6.542846] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[ 6.550292] smc91x: not found (-19).
[ 6.740478] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[ 6.761077] phy0: Selected rate control algorithm 'minstrel'
[ 6.814056] CMT speech driver v0.2.0
[ 6.836364] wl1251: loaded
[ 6.837158] wl1251: initialized
[ 6.839508] NET: Registered protocol family 35
[ 6.853271] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[ 6.888793] SSI McSAAB PROTOCOL Version: 2.0-rc1
[ 7.034667] dspbridge_init: 412800 bytes @ 80600000
[ 7.141845] omap-iommu omap-iommu.1: isp registered
[ 7.322631] omap-iommu omap-iommu.1: isp: version 1.1
[ 7.360534] mmc1: new high speed MMC card at address 0001
[ 7.376678] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[ 7.377014] mmcblk0: p1 p2 p3
[ 7.628753] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[ 7.648498] smia_reglist_import: meta_reglist version 2009-07-27
[ 7.648590] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/1502 ptr d0d072a0
[ 7.648590] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/3003 ptr d0d07228
[ 7.648620] smia_reglist_import: type 1 w 0 h 0fmt 30314142 ival 100/0 ptr d0d07090
[ 7.648651] smia_reglist_import: type 0 w 0 h 0fmt 30314142 ival 100/0 ptr d0d07038
[ 7.666625] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[ 7.685699] smia_reglist_import: meta_reglist version V4 alma 10.10.10
[ 7.685791] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314142 ival 100/399 ptr d0d0a464
[ 7.685791] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314442 ival 100/1292 ptr d0d0a204
[ 7.685821] smia_reglist_import: type 10 w 1728 h 1312 fmt 30314142 ival 100/11792 ptr d0d0a884
[ 7.685852] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/13000 ptr d0d0a7ec
[ 7.685852] smia_reglist_import: type 10 w 1296 h 984 fmt 30314142 ival 100/501 ptr d0d0a58c
[ 7.685882] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/3000 ptr d0d0a29c
[ 7.685913] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/2500 ptr d0d0a624
[ 7.685913] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/13584 ptr d0d0a754
[ 7.685943] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/2988 ptr d0d0a334
[ 7.685943] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/499 ptr d0d0a4f4
[ 7.685974] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/14779 ptr d0d0a6bc
[ 7.686004] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/2993 ptr d0d0a3cc
[ 7.686004] smia_reglist_import: type 1 w 2592 h 1968 fmt 30314142 ival 100/1207 ptr d0d0a05c
[ 7.786865] isp_mod: disagrees about version of symbol struct_module
[ 8.208740] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[ 8.208801] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[ 8.208862] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 8.211181] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 8.211669] usb usb1: configuration #1 chosen from 1 choice
[ 8.211883] hub 1-0:1.0: USB hub found
[ 8.212097] hub 1-0:1.0: 1 port detected
[ 10.505401] Adding 786424k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:786424k
[ 11.843017] kjournald starting. Commit interval 1 seconds
[ 11.855926] EXT3 FS on mmcblk0p2, internal journal
[ 11.855957] EXT3-fs: mounted filesystem with writeback data mode.
[ 16.241027] Bluetooth: L2CAP ver 2.13
[ 16.241058] Bluetooth: L2CAP socket layer initialized
[ 16.403869] Bluetooth: SCO (Voice Link) ver 0.6
[ 16.403900] Bluetooth: SCO socket layer initialized
[ 16.433258] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[ 16.659149] McSAAB: ACWAKE DOWN
[ 16.659210] McSAAB: ACWAKE UP
[ 16.659271] McSAAB: WAKELINES TEST OK
[ 17.013793] Bluetooth: RFCOMM socket layer initialized
[ 17.013854] Bluetooth: RFCOMM TTY layer initialized
[ 17.013885] Bluetooth: RFCOMM ver 1.11
[ 20.696441] misc iphb: Module registered in 2.6.28-omap1, built Aug 6 2010 11:50:55
[ 54.450164] cfg80211: Regulatory domain changed to country: EU
[ 54.450195] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 54.450225] (2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 54.450225] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 54.450256] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 54.450256] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 54.450286] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 54.450286] (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 61.387878] SCSI subsystem initialized
[ 61.611236] Driver 'sd' needs updating - please use bus_type methods
[ 87.399627] kb_lock (GPIO 113) is now closed
[ 88.009002] kb_lock (GPIO 113) is now open
[ 88.509033] kb_lock (GPIO 113) is now closed
[ 88.829284] kb_lock (GPIO 113) is now open
[ 115.415802] FAT: Filesystem error (dev mmcblk0p1)
[ 115.415832] invalid access to FAT (entry 0xeb192073)
[ 115.415863] File system has been set read-only
[ 4163.524963] kb_lock (GPIO 113) is now closed
[ 4163.696502] kb_lock (GPIO 113) is now open
[ 4225.485687] kb_lock (GPIO 113) is now closed
[ 4225.891784] kb_lock (GPIO 113) is now open
[ 4571.806182] kb_lock (GPIO 113) is now closed
[ 4572.259155] kb_lock (GPIO 113) is now open
[ 4576.493377] kb_lock (GPIO 113) is now closed
[ 4576.883972] kb_lock (GPIO 113) is now open
[ 5086.720123] kb_lock (GPIO 113) is now closed
[ 5087.337280] kb_lock (GPIO 113) is now open
[ 5228.103118] slide (GPIO 71) is now open
~ $ dmesg

i don't know what to do next. how can this be resolved?

thank you for your help
Message 1 of 12 (764 Views)
Reply
0
Please use plain text.
 
Mobile Sensei
Mobile Sensei
scoobyman
Posts: 8,317

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-12 20:26

Have you thought pf connecting to PC in mass storage mode and use chkdsk upon Windows as possibly /home/user/MyDocs corrupted?

 

You could also try in X-Terminal:-

 

sudo gainroot

umount /dev/mmcblk0p1

fsck -af /dev/mmcblk0p1

mount /dev/mmcblk0p1 /home/user/MyDocs

If I've helped in any way, a click upon the white kudos star would always be appreciated.

Message 2 of 12 (751 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

[ Edited ]
Options

‎2013-02-13 19:10 - edited ‎2013-02-13 19:20

after i have typed umount /dev/mmcblk0p1, message cannot unmount /home/user/MyDocs: Operation not permitted is displayed

Message 3 of 12 (716 Views)
Reply
0
Please use plain text.
 
Mobile Sensei
Mobile Sensei
scoobyman
Posts: 8,317

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-13 19:52

cuatanic wrote:

after i have typed umount /dev/mmcblk0p1, message cannot unmount /home/user/MyDocs: Operation not permitted is displayed

Install rootsh from the repositories then try again.

If I've helped in any way, a click upon the white kudos star would always be appreciated.

Message 4 of 12 (706 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-18 16:24

how do i install the rootsh? where can i get the installer and file?

Message 5 of 12 (496 Views)
Reply
0
Please use plain text.
 
Mobile Sensei
Mobile Sensei
scoobyman
Posts: 8,317

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-18 16:38

You may need to set up one of these "mirrors" but think that "rootsh" in in "Extras":

http://talk.maemo.org/showthread.php?t=88707

If I've helped in any way, a click upon the white kudos star would always be appreciated.

Message 6 of 12 (491 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-19 15:51

the second step here says that there will be catalogues that have a red sign with exclamation mark, but there is none in my n900.

what do i do?
Message 7 of 12 (472 Views)
Reply
0
Please use plain text.
 
Mobile Sensei
Mobile Sensei
scoobyman
Posts: 8,317

Re: n900 - memory unaccessible, unable to save content

[ Edited ]
Options

‎2013-02-19 16:37 - edited ‎2013-02-19 16:39

You don't need to use the mirrors if these have a green dot beside them and are refreshing correctly:

http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Top-12-Maemo-N900-Issues-amp-Fixes/m-p/75359...

If I've helped in any way, a click upon the white kudos star would always be appreciated.

Message 8 of 12 (457 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

[ Edited ]
Options

‎2013-02-19 16:43 - edited ‎2013-02-19 16:44

i have installed the rootsh.

i have typed sudo gainroot
umount /dev/mmcblk0p1

after typing umount /dev/mmcblk0p1 - canno unmount hiome/user/MyDocs: Device or resource busy shows

Message 9 of 12 (452 Views)
Reply
0
Please use plain text.
 
Mobile Sensei
Mobile Sensei
scoobyman
Posts: 8,317

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-19 20:14

Your N900 is not connected to a PC in mass storage mode when you get this result?

If I've helped in any way, a click upon the white kudos star would always be appreciated.

Message 10 of 12 (434 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-20 18:10

yes, it is not connected in the PC

Message 11 of 12 (399 Views)
Reply
0
Please use plain text.
 
cuatanic
Advisor
cuatanic
Posts: 11

Re: n900 - memory unaccessible, unable to save content

Options

‎2013-02-24 15:46

i can now access my memory, thank you :smileyhappy:
Message 12 of 12 (278 Views)
Reply
0
Please use plain text.