beta2 ongoing development

[IriDium]

(17th Jul, 2013 05:47 AM)nsviper Wrote:  Identical error to Iridium i'm afraid mk01

(edit) trying yout fix now...

---

ok great snapshot created now:

btrfs-auto-snapshot snapshot --name pre-beta2-snapshot root
Create a snapshot of '/tmp/btrfs-snap/root/@' in '/tmp/btrfs-snap/root/@pre-beta2-snapshot'
@pre-beta2-snapshot, 1 created snapshots, 0 destroyed snapshots, 0 warnings.

Ditto for me:
root@xbian:/home/xbian# btrfs-auto-snapshot snapshot --name pre-beta2-snapshot root
Create a snapshot of '/tmp/btrfs-snap/root/@' in '/tmp/btrfs-snap/root/@pre-beta2-snapshot'
@pre-beta2-snapshot, 1 created snapshots, 0 destroyed snapshots, 0 warnings.
root@xbian:/home/xbian# btrfs-auto-snapshot listhome/@
home/@safe
root/@
root/@pre-beta2-snapshot
root/@safe

[mk01]

perfect. so now you can work with the updates as it would be normal life time of xbian, with the difference you have direct access to my development.

you also already have a solid point to return if issues.

what is currently available are general fixes as were reported / solved on the forums (not config xbmc, not my cup of tea).

but xbian-update version 1.0-1.2 is complete rewrite of all system service scripts. after installing, all should go through parallel events from /etc/init/, rcS.d should be empty, rc2.d with few not core scripts.

there is lot of dependencies (even cross dependencies between events and services statuses and even more debug logging to files /run/upstart*, /run/mountall*).

at http://ivka57.dyndns-ip.com/a.sh is script, which is gathering this info together with relevant directories from /etc/, so if you hit a strange things going on, run the script and send /tmp/setup.xbian.tar.gz directly to my email matuskral @ me. com.

for myself, once see that files is what I need and what is relevant. I was developing the scripts and logging for almost two weeks - and 1.5 week it wanted work at all - until I started with the debugging.

have a nice evening and thanks for help.

(don't forget to remove the # from snapshot trigger in /etc/apt/.....)

[IriDium]

(17th Jul, 2013 06:04 AM)mk01 Wrote:  perfect. so now you can work with the updates as it would be normal life time of xbian, with the difference you have direct access to my development.

you also already have a solid point to return if issues.

what is currently available are general fixes as were reported / solved on the forums (not config xbmc, not my cup of tea).

but xbian-update version 1.0-1.2 is complete rewrite of all system service scripts. after installing, all should go through parallel events from /etc/init/, rcS.d should be empty, rc2.d with few not core scripts.

there is lot of dependencies (even cross dependencies between events and services statuses and even more debug logging to files /run/upstart*, /run/mountall*).

at http://ivka57.dyndns-ip.com/a.sh is script, which is gathering this info together with relevant directories from /etc/, so if you hit a strange things going on, run the script and send /tmp/setup.xbian.tar.gz directly to my email matuskral @ me. com.

for myself, once see that files is what I need and what is relevant. I was developing the scripts and logging for almost two weeks - and 1.5 week it wanted work at all - until I started with the debugging.

have a nice evening and thanks for help.

(don't forget to remove the # from snapshot trigger in /etc/apt/.....)

Performed the upgrade and all seemed to go well. Rebooted - and alas - Nothing. Just a cursor on the top left of the screen. RPi shows only steady RED light. Oh well. Will give it another go later.

[mk01]

(17th Jul, 2013 06:25 AM)IriDium Wrote:  Performed the upgrade and all seemed to go well. Rebooted - and alas - Nothing. Just a cursor on the top left of the screen. RPi shows only steady RED light. Oh well. Will give it another go later.

iridium, don't complicate things for yourself if you see like this, you don't have waste time with ref-lashing starting from scratch.

the probable reason for that is
- kernel is loaded
- initramfs is not

recently I changed initramfs to be compressed with gzip instead of xz. older version of kernel could decompress xz only.

did you upgrade all packages, including initramfs package & kernel ? or you upgraded initramfs, it recreated initramfs at boot with older kernel, not able to decompress gzip?

there is always one backup copy of initreamfs at /boot, ju try rename initramfs.gz.old to initramfs.gz

worst case, just take http://ivka57.dyndns-ip.com/boot.tar.gz and unpack to /boot. it should boot and provide usual tasks.

if not yet, install the kernel package. corresponding initramfs will be created automatically.

---

(17th Jul, 2013 06:47 AM)mk01 Wrote:  

(17th Jul, 2013 06:25 AM)IriDium Wrote:  Performed the upgrade and all seemed to go well. Rebooted - and alas - Nothing. Just a cursor on the top left of the screen. RPi shows only steady RED light. Oh well. Will give it another go later.

iridium, don't complicate things for yourself if you see like this, you don't have waste time with ref-lashing starting from scratch.

the probable reason for that is
- kernel is loaded
- initramfs is not

recently I changed initramfs to be compressed with gzip instead of xz. older version of kernel could decompress xz only.

did you upgrade all packages, including initramfs package & kernel ? or you upgraded initramfs, it recreated initramfs at boot with older kernel, not able to decompress gzip?

there is always one backup copy of initreamfs at /boot, ju try rename initramfs.gz.old to initramfs.gz

worst case, just take http://ivka57.dyndns-ip.com/boot.tar.gz and unpack to /boot. it should boot and provide usual tasks.

if not yet, install the kernel package. corresponding initramfs will be created automatically.

anyhow you inspired me to check dynamically against /boot/system.map for kernel compress/decompression routines. and do it according this.

[mk01]

nsviper

still yesterday I put dependency into initramfs package to require the appropriate kernel package, so after apt-get update, even apt-get should know the right combo and this was happened to iridium should not happen to you

[nsviper]

yep, will test tonight when back from work I'm at the same stage as Iridium (cursor top left after reboot), so will SSH in and redo apt-get's...

(edit) actually, no - its bricked.

Can't SSH in, there's no IP, and no way to to login prompt, so will reimage and reupgrade later.

[mk01]

(17th Jul, 2013 11:47 PM)nsviper Wrote:  yep, will test tonight when back from work I'm at the same stage as Iridium (cursor top left after reboot), so will SSH in and redo apt-get's...

(edit) actually, no - its bricked.

Can't SSH in, there's no IP, and no way to to login prompt, so will reimage and reupgrade later.

hmm. and you also just upgraded what was available, so kernel installed as well with the initramfs-package ?

I would like to find the reason, grab kernel.img, initramfs.gz, system.* from /boot and /etc/xbian-initramfs/update-initramfs.sh archive it into file and send it to my email ? (before you try the kernel.img and initramfs.gz from package for booting into RPI I provided or re-imaging. but mostly (if no filesystem corruption) re-imaging makes no sense, takes too long comparing to change two files in /boot). but it is up to you.

and if you boot with the images i provided, please send me "dpkg --get-selections xbian\* | awk '{print $1}' | xargs -L1 apt-cache policy"

i would appretiate.

[nsviper]

(18th Jul, 2013 04:21 AM)mk01 Wrote:  

(17th Jul, 2013 11:47 PM)nsviper Wrote:  yep, will test tonight when back from work I'm at the same stage as Iridium (cursor top left after reboot), so will SSH in and redo apt-get's...

(edit) actually, no - its bricked.

Can't SSH in, there's no IP, and no way to to login prompt, so will reimage and reupgrade later.

hmm. and you also just upgraded what was available, so kernel installed as well with the initramfs-package ?

I would like to find the reason, grab kernel.img, initramfs.gz, system.* from /boot and /etc/xbian-initramfs/update-initramfs.sh archive it into file and send it to my email ? (before you try the kernel.img and initramfs.gz from package for booting into RPI I provided or re-imaging. but mostly (if no filesystem corruption) re-imaging makes no sense, takes too long comparing to change two files in /boot). but it is up to you.

and if you boot with the images i provided, please send me "dpkg --get-selections xbian\* | awk '{print $1}' | xargs -L1 apt-cache policy"

i would appretiate.

Thats the problem. there was no way to get onto the Pi at all - no network connectivity, couldnt do anything with keyboard in (via USB hub) - no activity at all

I've reset SD card to a5 install and upgraded - will see how that goes.

[mk01]

(18th Jul, 2013 04:51 AM)nsviper Wrote:  Thats the problem. there was no way to get onto the Pi at all - no network connectivity, couldnt do anything with keyboard in (via USB hub) - no activity at all

I've reset SD card to a5 install and upgraded - will see how that goes.

yes, I got that, that's why I posted the kernel.img and initramfs.gz link to start it up - so instead of reflash, just replacing the two files should have helped.

[IriDium]

This was on the existing Beta 1.1 upgrade as started in the first thread.

Still no joy. Tried the new boot http://ivka57.dyndns-ip.com/boot.tar.gz and just the same.

Removed those files and renamed initramfs.gz.old to initramfs.gz

Still the same problem.

Tried a fresh install Beta 1.1 did the fixes and upgraded.

Failed to fetch http://ivka57.dyndns-ip.com/pool/main/x/xbian-package-xbmc/xbian-package-xbmc_2.3-0.7_armhf.deb Size mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Ran apt-get update
apt-get upgrade

Seemed to upgrade Ok this time

Partial success.
xbian loading screen - finished bar movement. Then started again. Stuck in that position. Can ssh into the Pi.

Tried to start via xbian-config - error xbmc is alreay running. Tried stopping - Ok, tried to restart. Error already running.

from shell sudo start xbmc -> Job failed to start
dmesg shows a list of
init: xbmc pre-start process (19145) terminated with status 1 and just loops.

sudo stop xbmc
stop: Job failed while stopping

[mk01]

(18th Jul, 2013 11:00 PM)IriDium Wrote:  Failed to fetch http://ivka57.dyndns-ip.com/pool/main/x/xbian-package-xbmc/xbian-package-xbmc_2.3-0.7_armhf.deb Size mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

the last days I was doing many changes and repo updates itself automatically.

so if you run "update", it fetches the md5 sums and file lists. if in between your "upgrade" command I'm posting new files to apt repo, you will download new file, but the "lists" you have still from a minute ago, so it won't match.

in that case just run (as you did) update and upgrade again.

I changed the opening post with new instructions how to make testing as easy and revertible as possible, please check it.

also, again, last two days were busy and few packages went to the repo not in much functional version. but since today should be ok. can you update/upgrade ?

[IriDium]

Ok, I'll do a fresh install following the new instructions and see where I get. It won't be for a couple of days, so maybe NsViper will pip me to the post.

[5ft24]

I've followed everything, copy/paste etc, and I get:

root@xbian:~# btrfs-auto-snapshot snapshot -name 'beta2' root
getopt: invalid option -- 'a'

---

(20th Jul, 2013 11:00 AM)5ft24 Wrote:  I've followed everything, copy/paste etc, and I get:

root@xbian:~# btrfs-auto-snapshot snapshot -name 'beta2' root
getopt: invalid option -- 'a'

figured it out...
The original code only shows as "-name" it needs to be "--name"

[5ft24]

Preparing to replace xbian-update 1.0-1.1 (using .../xbian-update_1.0-1.2_armhf.deb) ...
1) Stopping XBMC
2) Installing new files
dpkg: error processing /var/cache/apt/archives/xbian-update_1.0-1.2_armhf.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/xbian-update_1.0-1.2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[nsviper]

Sorry not had a chance yet over weekend to retry this - weather too good - hopefully tomorrow