@ichbindasauge: That... has nothing to do with a failed update, sorry... ^^
@kilikini: That's... weird. Here are the relevant part:
Code:
100722:021022 system: I K85dbus:def:stopping system message bus
100722:021022 system: I S50updater:def:updater started
100722:021022 system: I S50updater:def:Waiting for wand to shutdown
100722:021023 rmmod: ERROR: Module ehci_hcd does not exist in /proc/modules
100722:021023 rmmod: ERROR: Module usbcore does not exist in /proc/modules
100722:021023 wand[14388]: I lipc:evts:name=powerStateChanged, origin=com.lab126.wan, fparam=0:Event sent
100722:021023 wand[14388]: I def:wpstate:state=powerStateDown:wan power state changed
100722:021027 system: I S50updater:def:wand shutdown complete
100722:021029 system: I S50updater:def:read bundle line [/mnt/us/Update_501100064_501108064.bin]
100722:021029 system: I S50updater:def:Applying update /mnt/us/Update_501100064_501108064.bin
100722:021029 system: I S50updater:def:Size of update: 57188 bytes
100722:021029 system: I S50updater:def:Version before update: 064-TN2.0.4-050110
100722:021029 system: I _otaupexec:def:processing update /mnt/us/Update_501100064_501108064.bin
100722:021029 system: I _otaupexec:def:version is "FC02"
100722:021029 system: I _otaupexec:def:update image checksum OK
100722:021030 system: I mntroot:def:Making root filesystem writeable
100722:021030 EXT3 FS on mmcblk0p1, internal journal
100722:021030 ota_install: I def:patch:patchinfo="/etc/prettyversion.txt":patching file
100722:021030 ota_install: I def:patch:patchinfo="/etc/version.txt":patching file
100722:021030 ota_install: I def:update::updating device with patches
100722:021030 ota_install: I def:update::updating device with symlink deletes
100722:021031 ota_install: I def:update::updating device with symlink changes
100722:021031 ota_install: I def:update::updating device with new rootfs_md5_list
100722:021031 ota_install: I def:done:id=501100064-501108064,version=8064-TN2.0.5-050110:update complete
100722:021031 journaling: I def:journal_start:journalfile=Journal-update.jar:journal start
100722:021031 cvm[16282]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused)
100722:021031 cvm[16282]: C def:dbusi::Failed to init dbus
100722:091031 java: I UpdateJournal:Start:
100722:091031 java: I UpdateJournal:Information:availSpace=1018mb:
100722:091032 java: I UpdateJournal:Information:asin=B001CBBTJM, type=mobi, numAnnots=3:
100722:091034 java: I UpdateJournal:Information:asin=B001GIPJ2Y, type=mobi, numAnnots=1:
100722:091034 java: I UpdateJournal:Information:asin=B0011XW1E8, type=mobi, numAnnots=1:
100722:091035 java: I UpdateJournal:Information:journalSize=5380:
100722:021035 journaling: I def:tar_start:tarfile=700000000-journal.tar.gz:tar start
100722:021035 journaling: I def:tar_end:tarfile=700000000-journal.tar.gz:tar end
100722:021035 journaling: I def:patch:patchinfo="/etc/prettyversion.txt":patching file back
100722:021035 journaling: I def:patch:patchinfo="/etc/version.txt":patching file back
100722:021035 journaling: I def:update::updating device with patches
100722:021035 journaling: C def:journal_failed:exitcode=1:journaling failed
100722:021038 system: E _otaupexec:def:image update failed
100722:021039 system: I mntroot:def:Making root filesystem read-only
100722:021040 system: E S50updater:def:OTA update failed (1)
100722:021040 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/Update_501100064_501108064.bin"
I'm assuming the dbus error is meaningless, since it's part of the usual update system to stop it, so... Not sure why the journaling thingy fails. I'd have to take a look at a successful install log to compare. (Or, in case that thing is more verbose at higher debug levels, try one update after having switched to debug level 2 via ;debugOn).
One other theory might be to try to delete the 3 books whose ASIN numbers are mentionned...
Since I don't really now what this Journal-update thing does (and can't easily take a look at what it does, since it's a part of the java framework, and java + me = fail.), that's pretty much a shot in the dark, sorry. (The somewhat 'good' news seems to be that this doesn't seem to have anything to do with the hacks causing trouble...).
To recap:
#0: I'm pretty sure the hacks are not the root of the issue.
#1: I'd very much like a log of a successful install to have a baseline.
#2: Try once more after having switched to debug log level (;debugOn in the search box).
#3: Try deleting those 3 books (ASIN #): B001CBBTJM, B001GIPJ2Y, B0011XW1E8