Reply
Thread Tools
Posts: 6 | Thanked: 1 time | Joined on Dec 2011
#1
I few months that I have problems with the phone's internal memory
I flash a different way!
But it still remains difficult
I am faced with the following message after flash
Please help me solve this problem would be quite

 
Posts: 115 | Thanked: 342 times | Joined on Dec 2010
#2
Did you flash EMMC ? What does the filemanager say when you chose the internal storage (if you see an entry for that)?
 

The Following 2 Users Say Thank You to NIN101 For This Useful Post:
Posts: 6 | Thanked: 1 time | Joined on Dec 2011
#3
Originally Posted by NIN101 View Post
Did you flash EMMC ? What does the filemanager say when you chose the internal storage (if you see an entry for that)?
File Manager opens, but nothing inside it
 
Posts: 110 | Thanked: 31 times | Joined on Jan 2011
#4
hardware Problem
 

The Following User Says Thank You to maemo55 For This Useful Post:
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#5
To get this working in X-Terminal application you need rootsh installed:
Code:
sudo gainroot
umount /dev/mmcblk0p1
There might be an neglectable error here
Code:
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
If any errors occur, please post them here.
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Posts: 6 | Thanked: 1 time | Joined on Dec 2011
#6
Originally Posted by michaaa62 View Post
To get this working in X-Terminal application you need rootsh installed:
Code:
sudo gainroot
umount /dev/mmcblk0p1
There might be an neglectable error here
Code:
fsck -af /dev/mmcblk0p1
mount /dev/mmcblk0p1 /home/user/MyDocs
If any errors occur, please post them here.

Code:
BusyBox v1.19.3 (Debian 1.19.3power1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ sudo gainroot
Root shell enabled


BusyBox v1.19.3 (Debian 1.19.3power1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # umount /dev/mmcblk0p1
umount: can't umount /dev/mmcblk0p1: Invalid argument
/home/user # umount /dev/mmcblk0p1
umount: can't umount /dev/mmcblk0p1: Invalid argument
/home/user # fsck -af /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/mmcblk0p1: 1026 files, 3857/393231 clusters
/home/user # mount /dev/mmcblk0p1 /home/user/MyDocs
/home/user #
The drive will mount the file management

But do not drive after restart
 
Posts: 2,102 | Thanked: 1,937 times | Joined on Sep 2008 @ Berlin, Germany
#7
Did you reboot for some purpose?
Did you get access to the files?

The commands seem to have succeeded, no unexpected errors in the X-Terminal output!
 

The Following User Says Thank You to michaaa62 For This Useful Post:
Mike Fila's Avatar
Posts: 412 | Thanked: 480 times | Joined on Feb 2011 @ Bronx, NY
#8
You could try to format the drive since you can see it in the file manager.

Open file manager press and hold nokia N900 until the menu pops up and choose format.
 

The Following User Says Thank You to Mike Fila For This Useful Post:
Posts: 6 | Thanked: 1 time | Joined on Dec 2011
#9
Originally Posted by michaaa62 View Post
Did you reboot for some purpose?
Did you get access to the files?

The commands seem to have succeeded, no unexpected errors in the X-Terminal output!
After the restart file manager is empty
But you can mount the drive and the drive is the default file

I unbutu - flasher - Phoenix, I flash the phone with both file

(Ate this problem when the image of the device installed on megoo)

So how can I solve this problem?

I formatted the drive via the phone still the same
 
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#10
Definitely it is not a hardware problem - that's good. IMO, some of Your initial scripts (executed on boot) aren't working properly, thus Your vfat isn't mounted as MyDocs on boot.

You can:

a) Check init scripts related to MyDocs mounting - use search for list of them. You can also think for a while, what action that You did could affect boot scripts.

b) flash FIASCO (see reflashing in wiki). If problem still persist, flash whole vanilla eMMC image + fiasco. It's no way for it to persist after that. This solution is best to take *if* (and only if) You've created some mess on Your device, that You don't know how to roll back, or can't identify.

c) If You don't care after tracking down origins of problem, or cleaning whole thing from scratch, You can just create a text file in Your /etc/event.d/ (for example, /etc/event.d/mydocson), and paste following content into it:
Code:
description "MyDocs on"
start on started hildon-desktop
stop on starting shutdown
console none
service

script

# umounting /dev/mmcblk0p1, just in case something was screwed up bizzarely, and it get mounted somewhere else by boot scripts
umount /dev/mmcblk0p1

#mounting MyDocs exactly the way it should be mounted on boot
mount -t vfat /dev/mmcblk0p1 /home/user/MyDocs -o noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir

end script
This way, after every boot You'll have MyDocs mounted. Be aware of some untraced bug, that, in some cases, makes MyDocs to stay unmounted after using mass storage mode (even if one use "safe device removal") - if this affect You as well, You may want to create a script of any name You fancy in /usr/local/sbin/, and paste this inside:
Code:
#!/bin/sh

# Mounting eMMC partition 1
mount -t vfat /dev/mmcblk0p1 /home/user/MyDocs -o noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir

# Printing info
dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint string:"eMMC vFAT mounted, MyDocs is available"
... the (as root) chmod +x it. Ñow, every time Your MyDocs is unmounted after mass storage (or any unknown disaster) You may mount it by just executing this script as root - it will ever give Your fancy popup message upon completion (As with every script located in correct place, You don't need to type full path to execute it - name alone in root terminal is sufficient, and tab auto-completion works like with every program).

Hope it helps.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 3 Users Say Thank You to Estel For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 01:59.