maemo.org - Talk - View Single Post - N900 Desktop gone, reboot few minutes after start

NicoLarve	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:

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

Then extracted and "installed" debsums binaries in ~/bin (which is also a member of my $PATH env. variable):

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/

Run the following little script that scans every installed package and keep a log of things that are wrong:

Code:

#!/bin/bash
mypath="$(basename "${0}")"
log_file=~/"$(date +"%Y-%m-%d")-${mypath}".log
debsums -s 2>${log_file}

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.

Quote & Reply |

The Following 2 Users Say Thank You to NicoLarve For This Useful Post:
handaxe, pichlo