Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 7 hrs, 3 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 11 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 23 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 23 hrs ago - more...
|
2013-03-04
, 14:24
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Mar 2013
|
#2
|
Hi,
Same thing happens to me yesterday.
Do you find what is wrong? And how to solve the problem?
Peace.
Same thing happens to me yesterday.
Do you find what is wrong? And how to solve the problem?
Peace.
|
|
2013-12-09
, 11:27
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Sep 2013
|
#3
|
The same thing happened to me this morning, plus...:
The n900 was on and charging for the night. This morning, I found it charged (green led) but was unable to unlock it. It looked halted, but I'm not sure. I powered it on and found the all my 3 desktops empty of any of my applet icons & widgets.
Moreover, the desktop menu bar (to repopulate the desktop) is completely unresponsive. I rebooted the n900, still the same.
I can no longer populate my desktops! Crazy thing.
The n900 was on and charging for the night. This morning, I found it charged (green led) but was unable to unlock it. It looked halted, but I'm not sure. I powered it on and found the all my 3 desktops empty of any of my applet icons & widgets.
Moreover, the desktop menu bar (to repopulate the desktop) is completely unresponsive. I rebooted the n900, still the same.
I can no longer populate my desktops! Crazy thing.
 |
|
2013-12-09
, 11:49
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#4
|
This kind of thing tends to happen when your optfs is corrupt. Did you by any chance force power-off in the past few weeks? Long power button press, pull the battery out, battery ran out in the middle of doing something...
Your chances of recovery range from easy as pie to nigh impossible and it is hard to tell which. If you have BackupMenu or at least SSH installed then you might have a fighting chance but if not, then you are stuffed. Reflash might be your only option. Hope you have a backup. Sorry.
Your chances of recovery range from easy as pie to nigh impossible and it is hard to tell which. If you have BackupMenu or at least SSH installed then you might have a fighting chance but if not, then you are stuffed. Reflash might be your only option. Hope you have a backup. Sorry.
| The Following User Says Thank You to pichlo For This Useful Post: | ||
|
|
2013-12-09
, 17:52
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Sep 2013
|
#5
|
Originally Posted by pichlo
OK. Thank you for your answer!
This kind of thing tends to happen when your optfs is corrupt. Did you by any chance force power-off in the past few weeks? Long power button press, pull the battery out, battery ran out in the middle of doing something...
Your chances of recovery range from easy as pie to nigh impossible and it is hard to tell which. If you have BackupMenu or at least SSH installed then you might have a fighting chance but if not, then you are stuffed. Reflash might be your only option. Hope you have a backup. Sorry.
I think I will investigate (using dpkg & aptitude) and check/reinstall every installed packages. I already quickly tried to reinstall some osso-hildon packages without success (but it was over expensive 3G). But I think I will reinstall all of the installed packages! I'm home with wifi... unlimited.
|
|
2013-12-09
, 18:08
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#6
|
Careful with that - writing ANYTHING to a corrupt file system may corrupt it even more, beyond any chance of repair. I think your best bet is a full backup and reflash. Do you have any file manager installed other than the stock one? Can you open the terminal? The reason for asking is that you need to access files and directories above MyDocs, where the stock file manager can't reach.
If I were you, then depending on the extent of the damage, the only thing I would install - if not installed already - is the SSH server. Then connect to the phone from a PC via SSH and do a backup. Once done, you can try running fsck from BackupMenu but in my experience that is not going to go far, unless the damage is absolutely trivial. A better option is to connect the phone to a PC in BackupMenu mass storage mode (note this is different from "normal" mass storage mode as it exports two more partitions) and try to fsck your partitions. Or just back it up that way. You will need a Linux PC (at least a virtual one) for that.
If I were you, then depending on the extent of the damage, the only thing I would install - if not installed already - is the SSH server. Then connect to the phone from a PC via SSH and do a backup. Once done, you can try running fsck from BackupMenu but in my experience that is not going to go far, unless the damage is absolutely trivial. A better option is to connect the phone to a PC in BackupMenu mass storage mode (note this is different from "normal" mass storage mode as it exports two more partitions) and try to fsck your partitions. Or just back it up that way. You will need a Linux PC (at least a virtual one) for that.
|
|
2013-12-11
, 08:53
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Sep 2013
|
#7
|
Well... talking about dpkg should have been enough for you to understand I know ssh! ;-)
(And a corrupted filesystem doesn't scare me, I have nightly backups of my n900 on my server, through ssh/rsync and then rdiff-backup. At least, I prefer fixing broken systems instead of reinstalling everything from scratch.)
Two days ago, I run a script of my own on the n900 that uses debsums (from Debian Squeeze armel repo, not installable as is, but I unpacked and grabbed the executables only).
Basically, debsums just checks the presence & checksums (weak MD5...) of installed packages files. So it's only a read-only process.
But during the script execution, desktop icons reappeared and the phone & messaging notifications went back to life.
So, I can't really explain how this happened, but things are fixed now.
As a (useless?) reference, this is what I did (I'm a sudoer on the n900, if you're not, just install rootsh and type "sudo su -" it will ask for your own password):
Enable squeeze/armel Debien repo:
Then extracted and "installed" debsums binaries in ~/bin (which is also a member of my $PATH env. variable):
Run the following little script that scans every installed package and keep a log of things that are wrong:
Note that since nearly every packages are optyfied under the n900 (i.e., files moved from <their_initial_path> to /opt<their_initial_path>), debsums complained about every single installed file!
What I think in the end is that my /home[/opt] volume might have some electrical issue fixed by the fact it was extensively scanned. Can't imagine any other explanation. But more on this would be welcome.
(And a corrupted filesystem doesn't scare me, I have nightly backups of my n900 on my server, through ssh/rsync and then rdiff-backup. At least, I prefer fixing broken systems instead of reinstalling everything from scratch.)
Two days ago, I run a script of my own on the n900 that uses debsums (from Debian Squeeze armel repo, not installable as is, but I unpacked and grabbed the executables only).
Basically, debsums just checks the presence & checksums (weak MD5...) of installed packages files. So it's only a read-only process.
But during the script execution, desktop icons reappeared and the phone & messaging notifications went back to life.
So, I can't really explain how this happened, but things are fixed now.
As a (useless?) reference, this is what I did (I'm a sudoer on the n900, if you're not, just install rootsh and type "sudo su -" it will ask for your own password):
Enable squeeze/armel Debien repo:
Code:
sudo echo "deb http://ftp.fr.debian.org/debian/ squeeze main contrib non-free" >/etc/apt/sources.list.d/squeeze.list sudo aptitude update
Code:
cd ~/tmp && aptitude download debsums # got debsums_2.0.48+nmu3_all.deb mkdir debsums && dpkg-deb -x debsums_2.0.48+nmu3_all.deb debsums/ && cp debsums/usr/bin/*debsums ~/bin/
Code:
#!/bin/bash
mypath="$(basename "${0}")"
log_file=~/"$(date +"%Y-%m-%d")-${mypath}".log
debsums -s 2>${log_file}
What I think in the end is that my /home[/opt] volume might have some electrical issue fixed by the fact it was extensively scanned. Can't imagine any other explanation. But more on this would be welcome.
|
|
2013-12-11
, 09:36
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#8
|
Originally Posted by NicoLarve
Right you are! Sorry, didn't think straight, did I?
Well... talking about dpkg should have been enough for you to understand I know ssh! ;-)
What I think in the end is that my /home[/opt] volume might have some electrical issue fixed by the fact it was extensively scanned. Can't imagine any other explanation. But more on this would be welcome.
|
|
2013-12-11
, 10:05
|
|
Posts: 20 |
Thanked: 10 times |
Joined on Sep 2013
|
#9
|
Originally Posted by pichlo
OK, never heard about this option. Thanks.
or export the partitions in mass storage mode from BackupMenu (key 'w') and fsck from a Linux machine.
On think I also tried was
Code:
sudo echo "y" >/home/forcefsck
Also note that I couldn't find any mention to this in man fsck* pages... only on forums, etc.
| The Following User Says Thank You to NicoLarve For This Useful Post: | ||
|
|
2013-12-11
, 11:16
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#10
|
Force fsck on boot was either added or removed in CSSU, don't remember which. Anyway, it is functionally the same (as it runs the same binary) as running fsck from BackupMenu. The fsck we have on our N900s is ancient and, in my experience at least, tends to break more things in an attempt to fix them, which is why I wouldn't recommend it. YMMV.
| The Following 3 Users Say Thank You to pichlo For This Useful Post: | ||
My N900 seems to have a serious issue. As every night, I left it on my bed table charging (alarm was set).
Today morning I wasn't able to unlock it, then it rebooted automatically.
After the reboot all four desktop pages were completely empty, only my page with internet bookmarks showed up and disappeared continuously (as well as the carrier info). The clock/online/wifi status etc. worked, as well as all other programs (tested contacts, conky, xterminal).
After approx. 3 minutes the device crashes and reboots.
Iirc PR1.3 is installed with custom kernel settings, the device was overclocked to 950 MHz manually using kernel-power settings (it reboots with standard power settings).
Could this be a SW or a HW failure?
I think I have to flash the device, unfortunately the time it's acutally usable is too short to make a backup.
However, the flash should not affect the MyDocs-folder, right? There are still some backups in this folder.