(solved) messed up Filebox
 

hello,

after shutting down the phone,becuase it was slow and Filebox wouldn't close down, it's messed up.

another program was taking up all cpu power,even after it was closed

anyway...
now all icons are gone in Filebox,and also some buttons are missing.
starting it from termninal doesn't give an error...

i removed it, dpkg purge, installed it again an --reinstall
neither of these things work...

so,to sum it up...HELP!! ;)

Re: messed up Filebox
 

Is only Filebox suffering? I suspect you may have a file system corruption. I would install BackupMenu if you have not yet, boot to mass storage mode and fsck all your partitions.

Another possibility is that not Filebox itself but some theme it uses is corrupt. In that case you may need to find which one. The first step, apt-get purge filebox, apt-get autoremove --purge.

Re: messed up Filebox
 

everyting else works great...
remove/purge and install again won't work,tried that already.

i'll try a different theme, and a reboot...

Re: messed up Filebox
 

changing the theme didn't work
backupmenu fsck gives me an error:
"unknown error code 1 couldn't change name"

maye something is read-only...?

just reminds me, i downloaded a huge file to /home, wich ended up full
that gave some errors installing/uninstalling apps
but i removed that after the reboot i mentiond in my first post.

Re: messed up Filebox
 

Have you also tried autoremove? The idea is that Filebox itself is OK but one of its dependencies was screwed up. apt-get autoremove --purge should clear that, provided nothing else used it. After that, reinstalling Filebox should pull it back again.

You may have ended up with some partial installation due to full /home. Try dpkg -l | grep -v ^ii.

Re: messed up Filebox
 

I think it is fs corruption. Coincidentally the same happened to me last night but with cutetube and a ca. 100 mb file downloads to home. 2 files ok, 3rd failed. Now cannot download new stuff and cannot remove cutetube folder with partial downloads. Device otherwise operative.

A fsck via backupmenu produces same error as given above. A fsck from root shell reveals 2 fats. Following request by fsck to select one of the fats does not complete (I forgot error as it was late...). That's as far as I got.

Re: messed up Filebox
 

I'd recommend NOT doing fsck from BackupMenu. More often than not its attempts to fix errors will lead to more problems. Instead, I'd recommend booting to BackupMenu and selecting mass storage mode (the "w" key). That will export all partitions via USB, including rootfs and optfs. Then you can fsck them from a desktop Linux PC with a more up-to-date fsck. Even better, dd the entire partition to the PC, fsck it offline, and if and only if it turns out OK, dd it back.

Re: messed up Filebox
 

can't remove any files from /MyDocs
it's all read-only...
think thats part of the problem

Re: messed up Filebox
 

if i run fsck -a it start complaining about a couple of files i dowloaded

home/user # fsck -a /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
FATs differ but appear to be intact. Using first FAT.
/.documents/iGO Navteq 2012.Q3 EUROPE/map/Ukraine_R3_NQ_2012.Q3(AP).fpa
Contains a free cluster (33821). Assuming EOF.
/.documents/iGO Navteq 2012.Q3 EUROPE/map/Ukraine_R3_NQ_2012.Q3(AP).fpa
File size is 15883280 bytes, cluster chain length is 0 bytes.

/edit/
fixed that..
now I get this:
/home/user # fsck /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Reclaimed 2364 unused clusters (154927104 bytes).
Free cluster summary wrong (425760 vs. really 431028)
1) Correct
2) Don't correct

Re: messed up Filebox
 

I would go the route advised by pichlo. Pref use dd and fsck....

The corruption is the real issue as that is truly limiting if it happens regularly with large writes. Have yet to search that issue on tmo but recall there are concerns (kp or was it cssu?).

Re: messed up file system (was Filebox)
 

so..I maneged to fix all errors fsck was giving me...

now, Filebox still looks weird, no icons
the icons,however, are in the Filebox directory.

but the weirdest thing is, I mis a whole directory...!
in /MyDocs I have a directory Documents.
its only shown in the default filemanager, but nowhere else.
not in hamsterfile,not i xterminal LS...

any ideas left...?

Re: messed up file system (was Filebox)
 

This 'Documents' you are finding in the default application is really /home/user/MyDocs/.documents in the file system hierachy. You should find that folder in filebox at that place.

Re: messed up file system (was Filebox)
 

bit ashamed, but everyting is back to normal....
.documents is a hidden folder,as i found out :/

the only real problem stil,was filebox acting weird.
changing some settings back and fort fixed it to....

thanks for all the hints in this threath, so i got the read/write thing sorted out also...

Re: (solved) messed up Filebox
 

I followed pichlo's advice and fsck'd a dd copy. Takes a while that dd copy so because fsck repaired the dd copy just fine I kept it as a backup and then fsck'd the exported n900 partition directly. Worked as well. But why the corruption. Will test large downloads.

Re: (solved) messed up Filebox
 

Glad you got it working.

As to why the corruption - you said you switched it off for being unresponsive, didn't you? Powering down or rebooting a device while writing to a storage medium is taking place is pretty much a guarantee for FS corruption. Some file systems are more robust than others, but this kind of treatment will be a challenge to all of them. Which is by the way the main reason for having to "safely remove" a USB memory stick, for example. To get the OS a chance to finish all writes and make sure the FS is consistent.

Re: (solved) messed up Filebox
 

I wish it were so simple :) - I did no such thing. The weirdness became evident when cutetube no longer could save a download after 2 successful large files.... The cutetube folder was screwy thereafter.