kakalos
|
2010-03-09
, 12:21
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#11
|
|
2010-03-09
, 12:34
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#12
|
i had a similar problem with backup.it was getting stuck and i couldn`t backup anything.a reflash did solve the problem, then i`ve installed something from extras/testing and the problem came back!....so i would suggest a clean reflash and no applications from extras!....if it doesn`t solve it, then i`m afraid is a hardware problem.
It`s strange that all the greeks have a backup problem!it`s probably due to the economy collapsing.....ax ellada
|
2010-03-09
, 17:02
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#13
|
|
2010-03-09
, 17:08
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#14
|
I did reinstall the os and eyrething ok!I even restored the latest backup and still ok!After the reboot though the problem showed up.
Cannot backup on the built in memory because it is not an option on the backup app and worst it cannot read maps on ovi map app.
I unistalled a bunch of applications but nothing.
anapospastos can you send me a list of your installed app in order to compare it with mine?
debugging for dummies
Any idea someone...
sudo gainroot umount /home/user/MyDocs fsck -a /dev/mmcblk0p1 mount /home/user/MyDocs
|
2010-03-09
, 18:47
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#15
|
Try checking the filesystem? If you connect to a PC in mass storage mode, you should be able to run a disk check over the filesystem. Alternately, install rootsh then run (in X Terminal):
Code:sudo gainroot umount /home/user/MyDocs fsck -a /dev/mmcbl0p1 mount /home/user/MyDocs
/home/user # umount /home/user/MyDocs /home/user # fsck -a /dev/nncb10p1 fsck 1.41.3.maemo0 (12-Oct-2008) fsck.ext2: No such file or directory while trying to open /dev/nncb10p1 /dev/nncb10p1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
|
2010-03-09
, 18:55
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#16
|
Code:/home/user # umount /home/user/MyDocs /home/user # fsck -a /dev/nncb10p1 fsck 1.41.3.maemo0 (12-Oct-2008) fsck.ext2: No such file or directory while trying to open /dev/nncb10p1 /dev/nncb10p1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
|
2010-03-09
, 19:33
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#17
|
Sorry, I'd mistyped the path name (though you seem to also have misread it anyway). It should be "/dev/mmcblk0p1"
/home/user # umount /home/user/MyDocs /home/user # fsck -a /dev/mmcblk0p1 fsck 1.41.3.maemo0 (12-Oct-2008) dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN alleged total clusters: 442377 4424 8848 13272 17696 22120 26544 30968 35392 checked clusters: 36432 /dev/mmcblk0p1: 2288 files, 36432/442377 clusters /home/user # mount /home/user/MyDocs
|
2010-03-09
, 19:41
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#18
|
and after a reboot still nothingCode:/home/user # umount /home/user/MyDocs /home/user # fsck -a /dev/mmcblk0p1 fsck 1.41.3.maemo0 (12-Oct-2008) dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN alleged total clusters: 442377 4424 8848 13272 17696 22120 26544 30968 35392 checked clusters: 36432 /dev/mmcblk0p1: 2288 files, 36432/442377 clusters /home/user # mount /home/user/MyDocs
|
2010-03-09
, 20:57
|
Posts: 7 |
Thanked: 0 times |
Joined on Mar 2010
|
#19
|
|
2010-03-09
, 21:11
|
|
Posts: 552 |
Thanked: 183 times |
Joined on Oct 2009
@ Not decided
|
#20
|