maemo.org - Talk - Problem in filesystem /home/user [SOLVED]

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)

- - Problem in filesystem /home/user [SOLVED] (https://talk.maemo.org/showthread.php?t=88153)

Problem in filesystem /home/user [SOLVED]

Hi! I have a serious problem with my N9, since 2 weeks some applications don't work correctly like camera, wazapp, mail, rss, and others; then I decided reflashed the firmware PR1.3 (no erros and zero problems) but now I have the same problem, i don't understand why:

Quote:

$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 3.9G 1.2G 2.5G 32% /
devtmpfs 10.0M 248.0K 9.8M 2% /dev
tmpfs 4.0M 96.0K 3.9M 2% /tmp
tmpfs 512.0K 152.0K 360.0K 30% /var/run
none 10.0M 248.0K 9.8M 2% /dev
tmpfs 64.0M 376.0K 63.6M 1% /dev/shm
/dev/mmcblk0p3 2.0G 1.2G 703.2M 63% /home
/dev/mmcblk0p1 8.8G 4.4G 4.4G 50% /home/user/MyDocs
aegisfs 3.9G 1.2G 2.5G 32% /var/run/applauncherd
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.odnp-fpcd/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.odnp/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.facebook/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.mms/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.positioningd/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/private
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.slpgwd/layer
aegisfs 3.9G 1.2G 2.5G 32% /home/user/.signon/private
aegisfs 3.9G 1.2G 2.5G 32% /var/cache/timed/aegis
aegisfs 3.9G 1.2G 2.5G 32% /etc/ssl/certs
/dev/mapper/signonfs 6.8M 41.0K 6.4M 1% /home/user/.signon/signonfs-mnt

/dev/mmcblk0p3 2.0G 1.2G 703.2M 63% /home

but if i try do this:

Quote:

~ $ pwd
/home/user
~ $ touch test
touch: test: No space left on device

in MyDocs i don't have any problem:

Quote:

~/MyDocs $ pwd
/home/user/MyDocs
~/MyDocs $ touch test

Here a example of the portion of log that creates the n9 when i try open the camera http://pastebin.com/ggwMUKjU

regards and thank you very much

Re: Problem in filesystem /home/user

type "mount" and post the exact output.

Could be that /home is mounted read-only?

Re: Problem in filesystem /home/user

thanks for answering reinob:

Quote:

~ $ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=504248k,nr_inodes=126062,mode=75 5)
none on /proc type proc (rw,nosuid,nodev,noexec,relatime)
none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,noatime,size=4096k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=512k)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
/dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,uid=299 99,fmask=0133,dmask=0000,allow_utime=0022,codepage =cp437,iocharset=iso8859-1,shortname=mixed,utf8,rodir,errors=remount-ro)
none on /sys/kernel/debug type debugfs (rw,relatime)
aegisfs on /var/run/applauncherd type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.odnp-fpcd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.odnp/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.facebook/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.mms/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.positioningd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.slpgwd/layer type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.signon/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /var/cache/timed/aegis type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /etc/ssl/certs type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
cgroup on /syspart type cgroup (rw,relatime,freezer,memory,cpu)
/dev/mapper/signonfs on /home/user/.signon/signonfs-mnt type ext2 (rw,sync,noexec,relatime,errors=continue)

regards

Re: Problem in filesystem /home/user

Quote:

Originally Posted by danito (Post 1302180)

/dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered

Taking a wild guess, errors while mounting /home resulted in it being mounted read-only?

I am far from an expert, so this is what I would do. Become a root, then

Code:

cd /

umount /dev/mmcblk0p3

fsck /dev/mmcblk0p3

Preferably do a backup first. I have had cases in the past when fsck, in an attempt to fix the file system, broke it even more.

Re: Problem in filesystem /home/user

Quote:

~ # cd /
/ # umount /dev/mmcblk0p3
umount: can't umount /home: Operation not permitted

and i don have fsck :'(

Re: Problem in filesystem /home/user

Well, try to boot the device to maintanance mode.
There are at least 2 ways to do that.

1. http://wiki.meego.com/N950/Fixing_MALF_state With this you can boot the device in such a mode that it will offer the mouns for mmcblk0p* partitions to an external computer and examine possible problems
2. https://toosa.swagman.org/svn/sillykbd/TRUNK/moslo With this you can boot the device in single-user mode where you can telnet into it and manually mount/examine the filesystems quite freely

Re: Problem in filesystem /home/user

Hi juiceme,

i try to do that explain in the first link:

flashed the phone all OK zero error

Quote:

flasher --load -k vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 007, device address 017.
Device identifier: 357923041044712 (SN: N/A)
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending kernel image (2497 kB)...
100% (2497 of 2497 kB, avg. 32024 kB/s)
Sending initfs image (1920 kB)...
100% (1920 of 1920 kB, avg. 31475 kB/s)
Success

but when i type fdisk -l:

Quote:

......
Disco /dev/sdc: 9453 MB, 9453436928 bytes
64 heads, 32 sectors/track, 9015 cylinders, 18463744 sectores en total
Units = sectores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificador del disco: 0x00000000

Disposit. Inicio Comienzo Fin Bloques Id Sistema

no appear partitions

in this link apper the same solution: http://wiki.maemo.org/N9QTweak#Mount..._MALF_State.5D

the second link don't work :(

Re: Problem in filesystem /home/user

Quote:

Originally Posted by danito (Post 1302216)

Hi juiceme,

i try to do that explain in the first link:

flashed the phone all OK zero error

but when i type fdisk -l:

no appear partitions

Oookay, then there is something indeed awry in your partition setup. So you actually get no offered mounts of partitions? That is pretty strange.

What linux are you using? Can you do a "dmesg" to see if there is anything offered on the USB?

Quote:

Originally Posted by danito (Post 1302216)

the second link don't work :(

? Works for me atleast now, tried it 3 minutes ago.

Send me your email by PM and I can send them as a tarfile to you.
it's about 6megs of size.

Re: Problem in filesystem /home/user

i used debian SID 64,

flasher version: flasher 3.12.1 (Oct 5 2011) Harmattan

when i boot the phone show the message warning about loss of warranty

my dmesg

Quote:

[31358.816258] usb 7-1.2: new high-speed USB device number 30 using ehci_hcd
[31358.864514] hub 7-1:1.0: unable to enumerate USB device on port 2
[31430.408151] usb 7-1.2: new high-speed USB device number 31 using ehci_hcd
[31430.501028] usb 7-1.2: unable to get BOS descriptor
[31430.502368] usb 7-1.2: New USB device found, idVendor=0421, idProduct=0106
[31430.502375] usb 7-1.2: New USB device strings: Mfr=34, Product=38, SerialNumber=0
[31430.502379] usb 7-1.2: Product: Nokia USB ROM
[31430.502382] usb 7-1.2: Manufacturer: Nokia
[31432.289018] usb 7-1.2: USB disconnect, device number 31
[31965.956254] usb 7-1.2: new high-speed USB device number 32 using ehci_hcd
[31966.049004] usb 7-1.2: unable to get BOS descriptor
[31966.050100] usb 7-1.2: New USB device found, idVendor=0421, idProduct=0106
[31966.050106] usb 7-1.2: New USB device strings: Mfr=34, Product=38, SerialNumber=0
[31966.050110] usb 7-1.2: Product: Nokia USB ROM
[31966.050113] usb 7-1.2: Manufacturer: Nokia
[31969.085884] usb 7-1.2: USB disconnect, device number 32
[31970.820255] usb 7-1.2: new high-speed USB device number 33 using ehci_hcd
[31970.919255] usb 7-1.2: New USB device found, idVendor=0421, idProduct=0105
[31970.919261] usb 7-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[31970.919266] usb 7-1.2: Product: N9 (Update mode)
[31970.919269] usb 7-1.2: Manufacturer: Nokia
[31970.919272] usb 7-1.2: SerialNumber: 357923041044712
[31971.389752] usb 7-1.2: USB disconnect, device number 33
[31992.804260] usb 7-1.2: new high-speed USB device number 34 using ehci_hcd
[32007.876256] usb 7-1.2: device descriptor read/64, error -110
[32023.052266] usb 7-1.2: device descriptor read/64, error -110
[32023.228150] usb 7-1.2: new high-speed USB device number 35 using ehci_hcd
[32038.300267] usb 7-1.2: device descriptor read/64, error -110
[32053.476273] usb 7-1.2: device descriptor read/64, error -110
[32053.652272] usb 7-1.2: new high-speed USB device number 36 using ehci_hcd
[32064.060077] usb 7-1.2: device not accepting address 36, error -110
[32064.132276] usb 7-1.2: new high-speed USB device number 37 using ehci_hcd
[32074.540078] usb 7-1.2: device not accepting address 37, error -110
[32074.540294] hub 7-1:1.0: unable to enumerate USB device on port 2

thanks!!

Re: Problem in filesystem /home/user

Well, when I received the file .tar I proceed to follow the instructions and with the links I could connect to my mobile:

https://wiki.merproject.org/wiki/Nemo
https://wiki.merproject.org/wiki/Nemo/USBNetworking

Quote:

/ # fdisk -l

Disk /dev/mmcblk0: 15.8 GB, 15896412160 bytes
4 heads, 16 sectors/track, 485120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 17 288512 9231872 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 288513 419584 4194304 83 Linux
/dev/mmcblk0p3 419585 485120 2097152 83 Linux

And use mkfs.ext4 for checking the three volumes:
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3
I get the same result in the three cases (paste only one)

Quote:

mkfs.ext4 /dev/mmcblk0p1
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
577088 inodes, 2307968 blocks
115398 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2365587456
71 block groups
32768 blocks per group, 32768 fragments per group
8128 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

when i tried reboot the mobile don't boot correctly and then reflashing with the original firmware 1.3, active the developper mode and check in the shell again:

Quote:

~ $ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=504248k,nr_inodes=126062,mode=75 5)
none on /proc type proc (rw,nosuid,nodev,noexec,relatime)
none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,noatime,size=4096k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=512k)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
/dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,data=ordered)
tmpfs on /home/user/MyDocs type tmpfs (ro,relatime,size=512k)
none on /sys/kernel/debug type debugfs (rw,relatime)
aegisfs on /var/run/applauncherd type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.odnp-fpcd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.mms/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.odnp/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.positioningd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /var/cache/timed/aegis type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.slpgwd/layer type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/.signon/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /home/user/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
aegisfs on /etc/ssl/certs type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)
cgroup on /syspart type cgroup (rw,relatime,freezer,memory,cpu)
/dev/mapper/signonfs on /home/user/.signon/signonfs-mnt type ext2 (rw,sync,noexec,relatime,errors=continue)
aegisfs on /home/user/.facebook/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=3 0010,allow_other)

The situation not change but there are very strange:

Quote:

~ $ pwd
/home/user
~ $ echo "why works?" > test.txt
~ $ ls
MyDocs private test.txt
~ $ cat test.txt
why works?

I think that when i reflashed the las week the situation it's the same
is it my memory flash broken?

thanks you very much @juiceme and regards :(:(:(:(

Re: Problem in filesystem /home/user

One thing I see is different on my N9, with the home partition:

I have:
/dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)

You have:
dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,data=ordered)

The option "stripe=8" is missing on your mmcblk0p3, but it does exist on your root device mount. I am not sure if it is significant but at least it is a difference.

Re: Problem in filesystem /home/user

Some go wrong in the mobile, now the camera error it's different, i will go to nokia care :S

Thanks for the lessons i learn a lot off internals things about the nokia n9

Re: Problem in filesystem /home/user

Quote:

Originally Posted by danito (Post 1302343)

And use *mkfs.ext4* for checking the three volumes:
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3

You use fsck for checking. You use mkfs.ext4 for creating a filesystem! (i.e. formatting, wiping the whole partition).

So you basically reformatted your three partititions (rootfs, /home and MyDocs, I guess).

Quote:

when i tried reboot the mobile don't boot correctly

.. because there was nothing to boot. Only the bootloader and a lone kernel.

Quote:

and then reflashing with the original firmware 1.3, active the developper mode and check in the shell again:

The situation not change but there are very strange:

Well, the situation *did* change as you now had a completely reflashed system. I bet your previous flashing didn't involve wiping the whole N9.

Now we'll never know what the problem was. But at least it's solved for you :)

Re: Problem in filesystem /home/user

But i have the problem in /home, who can i fixed this? Beacause reinstall the firmware not fixed this..

Regards

Re: Problem in filesystem /home/user

If you had a problem in /home try to use following command instead of mkfs.ext4
fsck.ext4 -f /dev/mmcblk0p1
fsck.ext4 -f /dev/mmcblk0p2
fsck.ext4 -f /dev/mmcblk0p3

Re: Problem in filesystem /home/user [SOLVED]

Finally i solved the issue:

I flashed the eMMC and the firmware but the server to download the firmware is Nokia Care:

Quote:

flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.13-7.IBERIA_EMMC_IBERIA.bin -f -R
.........
.........
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3447 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1913 kB/s]
[x] rootfs [finished 100 % 1170282 / 1170282 kB 11000 kB/s]
[x] mmc [finished 100 % 1379731 / 1379731 kB 19741 kB/s]
Updating SW release
Success

them i resolved the problem :)

i find the solution when i search in google all the error in /var/log/syslog

thanks to all