help: corrupt file system due to random reboots
hi all,
my n900 was functioning flawlessly, until i tried the settings to undercurrent the cpu. i have kernel power v49 and battery patch installed. i never had any problem due to overclocking, so i thought i would try to undercurrent using the kernel-config load lv command. the instructions should state this could cause some device to reboot. i didnt know, by the time i realised it was already too late. m n900 kept rebooting many times after i undercurrent the cpu. then i began to get many problems. initially i lost all contacts. then m n900 entered reboot loops. this random reboots happened for 4-5 hours and finally stopped after i set kernel-config load ideal. however by now, i have a barely functioning n900 with many issues: - missing images, broken theme - empty contacts - cant open dialling pad, call history shows incoming/outgoing/missed icons but neither names nor numbers - hildon-thumbnails using up almost 100 percent cpu - unable to access n900 on my pc, only can see the removable storage icons but cant open - status bar icons gone - microb works but without flash, and trying to download or save page will cause internal error - cant fsck from backupmenu or xterm, both rootfs and optfs - many more i,m really in a dire situation because this is my main phone, i'm away from home and i need to be always available this week. especially during this time due to getting a new job. this is just so frustrating. i havent try flashing it yet. it might solve the corrupted fs issue but i cant backup my files before flashing. i've spent a lot of time and money to get things working on this phone, now everything goes to **** due to a stupid tweak..... is there other ways to copy my files before i flash this bugger? |
Re: help: corrupt file system due to random reboots
idk where to start you overclocked and didnt read any of the warnings they are front and center in the wiki. You have backup menu but didnt use it to make a backup before f'n around with overclocking?
try to ssh or usb host mode and see what you can pull off the emmc. |
Re: help: corrupt file system due to random reboots
does under volting cpu can harm n900 ? i also under volted my n900 and its working fine. it been almost 2 months that i under volted my n900.
|
Re: help: corrupt file system due to random reboots
Please post your error messages here for further debugging. Do not only describe the errors you are getting.
Try to check for file system health of MyDocs: Code:
sudo gainroot Code:
df |
Re: help: corrupt file system due to random reboots
when using this new nitdroid-installer beta at x-terminal, an error came out asking me whether i want to remove previous nitdroid installed. if yes, i have to reboot the device after that. after reboot, my phone screen application name become weird.for example, calender has become cal_ap_name. what has occurred? HELP!!!!!
|
Re: help: corrupt file system due to random reboots
Quote:
|
Re: help: corrupt file system due to random reboots
Quote:
fsck of MyDocs didn't produce any error No error was produced when looking for free space, there were many lines of output, which one shows the free space? I didn't fsck from Linux-PC or LiveCD from rw-mode in BackupMenu, how do I do that? Edit: I found Vi_'s post in this thread, regarding using Gparted to repair optfs, is this how to do it? I'm a total newb to Linux. http://talk.maemo.org/showthread.php?t=43698&page=3 Btw fsck from just in BackupMenu didnt produce error with regard to mmcblk0p1, but produced this error when trying to fsck mmcblk0p2. Code:
Errors may have been encountered: code:4 /dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; The phone still can't access itself, every sms that I received went into the SIM card. After the SIM card is full I can't receive anymore sms, and Conversations produced error that it can't access my device. |
Re: help: corrupt file system due to random reboots
Here is a walkthrough for those steps
Quote:
Quote:
|
Re: help: corrupt file system due to random reboots
Quote:
When I rebooted my phone, the problem still remains, I also can't use Xterm due to "Internal error". Then I booted in BackupMenu and when I tried to fsck all partitions, I received these errors: Code:
Checking the OptFS... Code:
Checking MyDocs... Code:
Checking the OptFS... Code:
Checking MyDocs... I briefly took out the battery and rebooted in BackupMenu. This time fsck didn't produce errors about OptFS. |
Re: help: corrupt file system due to random reboots
First parts of your post:
That is bad! The only explanation i could offer is: The fsck did not repair the damage, so you may have to use a terminal application in some Linux-Live-CD (don't know, but may be Gparted-Live has it as well) to get better manual control of the fsck process with options like -af for automatic repair, or -r for repair everything, even if it is considered to be dangerous. Quote:
Quote:
|
All times are GMT. The time now is 08:12. |
vBulletin® Version 3.8.8