maemo.org Bugzilla – Bug 6014
apt-get upgrade can result in non-bootable device
Last modified: 2010-03-10 20:22:58 UTC
You need to log in before you can comment on or make changes to this bug.
from ssh: Nokia-N900-41-10:~# apt-get update .. Nokia-N900-41-10:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: policy-settings-rx51 The following packages will be upgraded: alsa-policy-enforcement bme-rx-51 browser-neteal camelisync dsme gstreamer-tools gstreamer0.10-tools hermes hildon-desktop kernel kernel-flasher kernel-modules libbmeipc0 libclutter-0.8-0 libdres0 libgles2-sgx-img libhildon1 libhildonmm libohm-plugin-core0 libpurple0 liqflow liqtorch maemo-launcher mce mirror modest-nokiamessaging-plugin modest-nokiamessaging-plugin-l10n-cscz modest-nokiamessaging-plugin-l10n-dadk modest-nokiamessaging-plugin-l10n-dede modest-nokiamessaging-plugin-l10n-engb modest-nokiamessaging-plugin-l10n-enus modest-nokiamessaging-plugin-l10n-eses modest-nokiamessaging-plugin-l10n-esmx modest-nokiamessaging-plugin-l10n-fifi modest-nokiamessaging-plugin-l10n-frca modest-nokiamessaging-plugin-l10n-frfr modest-nokiamessaging-plugin-l10n-itit modest-nokiamessaging-plugin-l10n-nlnl modest-nokiamessaging-plugin-l10n-nono modest-nokiamessaging-plugin-l10n-plpl modest-nokiamessaging-plugin-l10n-ptpt modest-nokiamessaging-plugin-l10n-ruru modest-nokiamessaging-plugin-l10n-svse nokiamessaging obexd ohm ohm-plugin-resolver ohm-plugins-misc opengles-sgx-img-common operator-wizard-settings osso-abook-home-applet osso-mission-control pulseaudio-policy-enforcement purple-protocol-sametime python-glade2 python-gobject python-gtk2 python-pkg-resources python-setuptools python-xml rootsh rtcom-notification-ui rtcom-presence-ui softupd tablet-bookmark-manager tablet-browser-controls tablet-browser-ui tablet-browser-widgets xserver-xomap xserver-xorg-core xserver-xorg-video-fbdev 71 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 13,6MB of archives. After this operation, 418kB of additional disk space will be used. Do you want to continue [Y/n]? ... Fetched 5571kB in 18s (307kB/s) (Reading database ... 26884 files and directories currently installed.) Preparing to replace kernel 2.6.28-20094102+0m5 (using .../kernel_2.6.28-20094102.3+0m5_armel.deb) ... Unpacking replacement kernel ... Setting up kernel (2.6.28-20094102.3+0m5) ... (Reading database ... 26884 files and directories currently installed.) Preparing to replace kernel-flasher 2.6.28-20094102+0m5 (using .../kernel-flasher_2.6.28-20094102.3+0m5_armel.deb) ... Unpacking replacement kernel-flasher ... Preparing to replace alsa-policy-enforcement 0.24+0m5 (using .../alsa-policy-enforcement_0.25.1+0m5_armel.deb) ... Unpacking replacement alsa-policy-enforcement ... Preparing to replace bme-rx-51 0.8.46+0m5 (using .../bme-rx-51_0.8.47+0m5_armel.deb) ... Unpacking replacement bme-rx-51 ... Preparing to replace browser-neteal 0.6.9.1+0m5 (using .../browser-neteal_0.6.10.1.1+0m5_armel.deb) ... Unpacking replacement browser-neteal ... Preparing to replace libbmeipc0 0.8.46+0m5 (using .../libbmeipc0_0.8.47+0m5_armel.deb) ... Unpacking replacement libbmeipc0 ... Preparing to replace dsme 0.60.32+0m5 (using .../dsme_0.60.34+0m5_armel.deb) ... Unpacking replacement dsme ... Preparing to replace gstreamer0.10-tools 0.10.23-0maemo5+0m5 (using .../gstreamer0.10-tools_0.10.23-git305-0maemo5+0m5_armel.deb) ... Unpacking replacement gstreamer0.10-tools ... Preparing to replace gstreamer-tools 0.10.23-0maemo5+0m5 (using .../gstreamer-tools_0.10.23-git305-0maemo5+0m5_armel.deb) ... Unpacking replacement gstreamer-tools ... Preparing to replace libgles2-sgx-img 0.20090218.55.1+0m5 (using .../libgles2-sgx-img_0.20090218.55.9+0m5_armel.deb) ... Unpacking replacement libgles2-sgx-img ... Preparing to replace opengles-sgx-img-common 0.20090218.55.1+0m5 (using .../opengles-sgx-img-common_0.20090218.55.9+0m5_armel.deb) ... Unpacking replacement opengles-sgx-img-common ... Preparing to replace libclutter-0.8-0 0.8.2-0maemo53+0m5 (using .../libclutter-0.8-0_0.8.2-0maemo56+0m5_armel.deb) ... Unpacking replacement libclutter-0.8-0 ... Preparing to replace libhildon1 2.2.0-2+0m5 (using .../libhildon1_2.2.0-2+ultrastable1+0m5_armel.deb) ... Unpacking replacement libhildon1 ... Preparing to replace hildon-desktop 1:2.2.100-28+0m5 (using .../hildon-desktop_1%3a2.2.100-31+0m5_armel.deb) ... ... Unpacking replacement modest-nokiamessaging-plugin-l10n-svse ... Preparing to replace obexd 0.15-0maemo1+0m5 (using .../obexd_0.15-0maemo2+0m5_armel.deb) ... Unpacking replacement obexd ... Preparing to replace ohm 0.1.2-0maemo28+0m5 (using .../ohm_0.1.2-0maemo30.1+0m5_armel.deb) ... Unpacking replacement ohm ... Preparing to replace ohm-plugin-resolver 0.1.13+0m5 (using .../ohm-plugin-resolver_0.1.14.1+0m5_armel.deb) ... Unpacking replacement ohm-plugin-resolver ... Preparing to replace osso-mission-control 5.10+0m5 (using .../osso-mission-control_5.10.1+0m5_armel.deb) ... Unpacking replacement osso-mission-control ... Preparing to replace ohm-plugins-misc 0.6.61+0m5 (using .../ohm-plugins-misc_0.6.62.1+0m5_armel.deb) ... Unpacking replacement ohm-plugins-misc ... Preparing to replace operator-wizard-settings 2.0.32+0m5 (using .../operator-wizard-settings_2.0.34+0m5_all.deb) ... Unpacking replacement operator-wizard-settings ... Preparing to replace osso-abook-home-applet 4.20090806+0m5 (using .../osso-abook-home-applet_4.20090806.2+0m5_armel.deb) ... Unpacking replacement osso-abook-home-applet ... Preparing to replace pulseaudio-policy-enforcement 0.5.32+0m5 (using .../pulseaudio-policy-enforcement_0.5.33.1+0m5_armel.deb) ... Unpacking replacement pulseaudio-policy-enforcement ... Preparing to replace purple-protocol-sametime 2.6.3-0nix2~fremantle (using .../purple-protocol-sametime_2.6.3-1nix0_armel.deb) ... Unpacking replacement purple-protocol-sametime ... Preparing to replace python-gobject 2.14.2-1maemo5 (using .../python-gobject_2.16.1-1maemo1_armel.deb) ... Unpacking replacement python-gobject ... Preparing to replace python-glade2 2.12.1-6maemo8 (using .../python-glade2_2.12.1-6maemo9_armel.deb) ... Unpacking replacement python-glade2 ... Preparing to replace python-gtk2 2.12.1-6maemo8 (using .../python-gtk2_2.12.1-6maemo9_armel.deb) ... Unpacking replacement python-gtk2 ... Preparing to replace python-setuptools 0.6c9-1maemo1 (using .../python-setuptools_0.6c9-1maemo2_all.deb) ... Unpacking replacement python-setuptools ... Preparing to replace python-pkg-resources 0.6c9-1maemo1 (using .../python-pkg-resources_0.6c9-1maemo2_all.deb) ... Unpacking replacement python-pkg-resources ... Preparing to replace python-xml 0.8.4-10.1maemo3 (using .../python-xml_0.8.4-10.1maemo4_armel.deb) ... Unpacking replacement python-xml ... Preparing to replace rootsh 1.5 (using .../archives/rootsh_1.7_all.deb) ... /var/lib/dpkg/info/rootsh.prerm: line 5: syntax error: "fi" unexpected (expecting "then") dpkg: warning - old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement rootsh ... Preparing to replace rtcom-notification-ui 0.0.39-1+0m5 (using .../rtcom-notification-ui_0.0.40-2+0m5_armel.deb) ... Unpacking replacement rtcom-notification-ui ... Preparing to replace rtcom-presence-ui 0.43.3-1+0m5 (using .../rtcom-presence-ui_0.43.4-1+0m5_armel.deb) ... Unpacking replacement rtcom-presence-ui ... Preparing to replace tablet-bookmark-manager 0.0.17.1-1+0m5 (using .../tablet-bookmark-manager_0.0.17.2-2+0m5_armel.deb) ... Unpacking replacement tablet-bookmark-manager ... Preparing to replace tablet-browser-controls 1.4.1.15-1+0m5 (using .../tablet-browser-controls_1.4.1.21-1+0m5_armel.deb) ... Unpacking replacement tablet-browser-controls ... Preparing to replace tablet-browser-widgets 1.1.1-1+0m5 (using .../tablet-browser-widgets_1.1.1.1-2+0m5_armel.deb) ... Unpacking replacement tablet-browser-widgets ... Preparing to replace tablet-browser-ui 1.6.3.20-1+0m5 (using .../tablet-browser-ui_1.6.3.26-2+0m5_armel.deb) ... Unpacking replacement tablet-browser-ui ... Preparing to replace xserver-xorg-video-fbdev 1:0.4.0-173+0m5 (using .../xserver-xorg-video-fbdev_1%3a0.4.0-175+0m5_armel.deb) ... Unpacking replacement xserver-xorg-video-fbdev ... Preparing to replace xserver-xomap 2:1.6.99.1-0osso20090208.100.1+0m5 (using .../xserver-xomap_2%3a1.6.99.1-0osso20090208.102.3+0m5_armel.deb) ... Unpacking replacement xserver-xomap ... Preparing to replace xserver-xorg-core 2:1.6.99.1-0osso20090208.100.1+0m5 (using .../xserver-xorg-core_2%3a1.6.99.1-0osso20090208.102.3+0m5_armel.deb) ... Unpacking replacement xserver-xorg-core ... Now I feel I was just asking for it after posting https://bugs.maemo.org/show_bug.cgi?id=6012 and https://bugs.maemo.org/show_bug.cgi?id=6013 :/
Here's what happens: * I turn on my device, * The led turns white * Blue Nokia appears * Screen goes dark * Both led and screen turn off
I think it's related to USB. The apt-get upgrade was when I had USB plugged in. The above steps are when USB is not plugged in. When it's off and I plug in the USB cable to my laptop, without turning the device on, the following loop starts: 1. A little vibration 2. Blue Nokia, but on a very dark screen 3. A bit brighter black 4. Some pause. 5. Back to 1.
I also tried taking out the battery out a couple of times, tried both USB and power cable. Before the apt-get upgrade I had 22,9M free on / and I had already put apt/cache/archives on another filesystem. Nokia-N900-41-10:~# df -h Filesystem Size Used Available Use% Mounted on rootfs 227.9M 200.8M 22.9M 90% / ubi0:rootfs 227.9M 200.8M 22.9M 90% / tmpfs 1.0M 80.0k 944.0k 8% /tmp tmpfs 256.0k 84.0k 172.0k 33% /var/run none 10.0M 80.0k 9.9M 1% /dev tmpfs 64.0M 4.0k 64.0M 0% /dev/shm /dev/mmcblk0p2 2.0G 195.1M 1.7G 10% /home /dev/mmcblk0p1 27.0G 9.6G 17.4G 36% /home/user/MyDocs /dev/mmcblk1p1 3.7G 2.1G 1.6G 57% /media/mmc1
The apt-get upgrade was fetching packages from: https://downloads.maemo.nokia.com ./ http://repository.maemo.org fremantle/free On #maemo I learned that I was not supposed to apt-get upgrade my device, which is a bit odd if I'm also supposed to be a beta tester of the device. And well, I hadn't mentioned yet that I've been using the N900 as my primary phone since the Maemo conference. (In fact, I haven't touched my old phone since.)
I sympathise, but I don't think there's anything you can do until official firmware is released. More generally, apt-get upgrade has been known to brick maemo devices since the 770. It's just something we learned to avoid but perhaps it's time we had a bug about it, adjusting accordingly and confirming.
(In reply to comment #5) > More generally, apt-get upgrade has been known to brick maemo devices since the > 770. I've been apt-get upgrading since the 770, never bricked my 770 or my N810...
(In reply to comment #6) > I've been apt-get upgrading since the 770, never bricked my 770 or my N810... You've just been lucky I guess. The mailing lists and forums contain many threads where people found out the hard way that this is not a safe thing to do.
1) Have rootsh installed 2) Connect via USB from laptop to N900 - choose "Charging only" 3) open Terminal 4) sudo gainroot 4) apt-get upgrade It finished successfully. I turned the device off, still having the USB cable plugged in. After pressing the power-up button twice for three seconds it boots correctly. Running 45-7 here. Now I wonder which steps are the important combination here - using ssh? The remaining free space? "Use%" for rootfs here was only 66%... As written before it is recommended to use the Application Manager for updating stuff.
So did this ever happen again? Once the next update (internally called PR1.1) is out, updating this report is highly welcome.
(In reply to comment #9) > So did this ever happen again? > Once the next update (internally called PR1.1) is out, updating this report is > highly welcome. > I remember having a problem upgrading OTA to PR1.1 as it asks me to connect to a PC to perform the upgrade but I wanted to do it OTA. So what I did was use 'apt-get upgrade' After a while it failed mid-way due to lack of space. I had to reboot the device. The device loaded fine but still on the old firmware. I then open Application Manager and continue the update through that. It completed without any further errors, the phone rebooted with PR1.1 Hence I would close this as WORKSFORME Feel free to reopen if you can reproduce it when upgrading to the upcoming PR1.2
It has been working for me as well