Official XBian 1.0 Beta 1.1 thread

[kraleksandr]

Since b1 I dont see my USB-HDD in the Video - Files menu.
With a5 it looks like "236.6Gb" in the Files menu.
fstab entry:

Terminal

UUID=839aea66-ad3d-4c3a-9d10-7f8f4d91ec9f /media/hdd ext4 defaults,noatime 0 0

P.S. Where is the TERM bb-code?

[0xFF]

Hello,
Before upgrading to Beta 1.1 I have issue with beta 1.0 and lirc_rpi module.
lirc_rpi module was loaded at boot time but ignoring /etc/modprobe.d/lirc_rpi.conf settings (options lirc_rpi gpio_in_pin=25).

I tried to remove lirc_rpi from /etc/modules or add to lirc_rpi to blacklisted modules, but no luck.

To force lirc_rpi module to use GPIO 25 PIN I had manually rmmod lirc_rpi and modprobe lirc_rpi again.

Now this odd issue gone. Lirc_rpi module is not loaded by default. I had to add lirc_rpi to /etc/modules. And now it is loaded with proper options (gpio_in_pin=25).

Thanks for upgrade

[belese]

mk01>wasn't the key copy of sdcard in any kind?

more or less, i think it is my test with a raid0 between usk key end sd card,
i've just reflash sd card, and have to remove usb before booting. but not at home now, could confirm later on content of sdcard.

[mk01]

(15th Jul, 2013 09:20 PM)belese Wrote:  mk01>wasn't the key copy of sdcard in any kind?

more or less, i think it is my test with a raid0 between usk key end sd card,
i've just reflash sd card, and have to remove usb before booting. but not at home now, could confirm later on content of sdcard.

I was thinking about maybe the same UUID or LABEL on both partitions.

---

(15th Jul, 2013 09:08 PM)0xFF Wrote:  Now this odd issue gone. Lirc_rpi module is not loaded by default. I had to add lirc_rpi to /etc/modules. And now it is loaded with proper options (gpio_in_pin=25).

Thanks for upgrade

between 1.0 and 1.1 we changed the busybox modprobe for native kmod package. seems that busybox's modprobe is not honoring MODPROBE_OPTIONS env settings.

anyhow, what is in /etc/modules is copied to initramfs and loaded upon "init starting", before real root exists, but not all files from /etc/modprobe.d

going to fix this.

mk

[googl1]

(15th Jul, 2013 08:52 PM)mk01 Wrote:  

(15th Jul, 2013 07:36 PM)googl1 Wrote:  The green LED on the pi is blinking.
I didn't unplug or poweroff it yet.

Does it convert the fs do btrfs or something like that or can I just unplug it to restart it?

but this one looks like the "reboot -f" wasn't performed and is stuck still before reboot.

I would unplug & replug it.

allready did this, didn't change anything...
please read my post above

[mk01]

(15th Jul, 2013 08:49 PM)googl1 Wrote:  

Code:

# fsck -y /dev/mmcblk0p1
fsck from util-linux 2.20.1
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
/start.elf
  Renamed to FSCK0000.000
/fixup.dat
  Renamed to FSCK0000.001
/cmdline.txt
  Renamed to FSCK0000.002

But even after that, the pi doesn't start up.

from this one /dev/mmcblk0p1 nothing will boot. and this also is answer to question why _nothing_ appeared.

[googl1]

(15th Jul, 2013 11:24 PM)mk01 Wrote:  

(15th Jul, 2013 08:49 PM)googl1 Wrote:  

Code:

# fsck -y /dev/mmcblk0p1
fsck from util-linux 2.20.1
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
/start.elf
  Renamed to FSCK0000.000
/fixup.dat
  Renamed to FSCK0000.001
/cmdline.txt
  Renamed to FSCK0000.002

But even after that, the pi doesn't start up.

from this one /dev/mmcblk0p1 nothing will boot. and this also is answer to question why _nothing_ appeared.

So whats the source of the problem, how can i avoid the corruption of mmcblk0p1?
I already tried it a second time, and the same happened.

When I flash my Alpha 5 backup, everything works fine, until I try to update.

[mk01]

(15th Jul, 2013 08:49 PM)googl1 Wrote:  But even after that, the pi doesn't start up.
Any suggestions? Or do I have to do a fresh install?
I have a full (dd) backup of my Alpha 5 installation for any reattempts.

it can not boot, because the needed files are not there (renamed).

reformat the /boot partition only and restore files from alpha5. let's see, what is the condition of rootfs.

btw: did you checked the ext4 also before the updating? and also, for manual check use -f option, not only replaying the journal.

is this card you updated original filesystem, or dd-ed copy?

[JeHaLi]

(15th Jul, 2013 08:34 PM)mk01 Wrote:  

(15th Jul, 2013 04:35 PM)JeHaLi Wrote:  Setting up nfs-common (1:1.2.6-4) ...
insserv: Service rpcbind has to be enabled to start service nfs-common
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing nfs-common (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@xbian:/home/xbian#

just do "sudo "insserv -f rpcbind", then "apt-get -f install", then continue with update.

---

(15th Jul, 2013 07:36 PM)googl1 Wrote:  The tv screen said something like "rebooting now"

After that the screen stayed black, ssh didn't answer and my harddrives stayed in standby.
The green LED on the pi is blinking.
I didn't unplug or poweroff it yet.

rebooting now appears on the screen when xbian-update finishes setting up under dpkg. then it waits for apt-get and dpkg processes to finish. because system changed init (sysvinit -> upstart), runlevels are not working and reboot / shutdown either.

so we wait cca 30s, do sync and reboot -f.

then splash screen should disappear and rpi reboots. the black screen is where RPi is starting. so far so good.

during kernel loading, blinking cursor should be visible in upper left corner. as soon as kernel loads, splash should be started, first with "init process..." and in few seconds it should jump into "sd card resize" and "sd card convert".

this can take minutes, but also an hour (even more). text under progress bar is changing through the process steps. this is how it SHOULD run. you can compare your situation.

here on forum were reported cases with upgrade via remote ssh with frustration first (it rebooted, now i can't connect, even ping ...). and hour - two later rpi booted after convert.

during conversion, xbian system is not started - so no network, ping, nothing.

---

(15th Jul, 2013 07:36 PM)googl1 Wrote:  The green LED on the pi is blinking.
I didn't unplug or poweroff it yet.

Does it convert the fs do btrfs or something like that or can I just unplug it to restart it?

but this one looks like the "reboot -f" wasn't performed and is stuck still before reboot.

I would unplug & replug it.

I did it, but:
xbian@xbian ~ $ sudo "insserv -f rpcbind"
sudo: insserv -f rpcbind: command not found

[mk01]

(16th Jul, 2013 12:23 AM)JeHaLi Wrote:  xbian@xbian ~ $ sudo "insserv -f rpcbind"
sudo: insserv -f rpcbind: command not found

without quotes. if you quote this, sudo wants to start ONE command named insserv\ \-f\ rpcbind

Code:

sudo insserv -f rpcbind

[dlysnes]

Hey
Just a quick question. I'm on the first beta (fresh).
I ran apt-get update, but the apt-get install xbian-update -y only returns "xbian-update is already the newest version."

Do I need to update sources / mirrors? The xbian-config mirros update don't work, so guess I need to add sth manually?
This is my /etc/apt/sources.list:

deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb mirror://apt.xbian.org/mirror.txt wheezy main
#deb-src http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi

[googl1]

(16th Jul, 2013 12:04 AM)mk01 Wrote:  

(15th Jul, 2013 08:49 PM)googl1 Wrote:  But even after that, the pi doesn't start up.
Any suggestions? Or do I have to do a fresh install?
I have a full (dd) backup of my Alpha 5 installation for any reattempts.

it can not boot, because the needed files are not there (renamed).

reformat the /boot partition only and restore files from alpha5. let's see, what is the condition of rootfs.

btw: did you checked the ext4 also before the updating? and also, for manual check use -f option, not only replaying the journal.

is this card you updated original filesystem, or dd-ed copy?

it was a dd-ed copy

I dd-ed the backup on the card again and checked the filesystems before update to beta:

Code:

# fsck -f -y /dev/mmcblk0p1
fsck from util-linux 2.20.1
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
/dev/mmcblk0p1: 19 files, 22483/34662 clusters

Code:

# fsck -f -y /dev/mmcblk0p2
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
Durchgang 1: Prüfe Inodes, Blocks, und Größen
Durchgang 2: Prüfe Verzeichnis Struktur
Durchgang 3: Prüfe Verzeichnis Verknüpfungen
Durchgang 4: Überprüfe die Referenzzähler
Durchgang 5: Überprüfe Gruppe Zusammenfassung
Block Bitmap differieren:  -(987278--987286)
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #2 ist falsch (21764, gezählt=21763).
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #17 ist falsch (65510, gezählt=19).
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #22 ist falsch (55, gezählt=76).
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #28 ist falsch (218, gezählt=224).
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #29 ist falsch (3201, gezählt=3196).
Repariere? ja

Die Anzahl freier Blöcke in Gruppe #30 ist falsch (28180, gezählt=28117).
Repariere? ja

Die Anzahl freier Blöcke ist falsch (1074340, gezählt=1074343).
Repariere? ja

Die Anzahl freier Inodes ist falsch für Gruppe #18 (106, gezählt=105).
Repariere? ja

Die Anzahl freier Inodes ist falsch (420788, gezählt=420787).
Repariere? ja


/dev/mmcblk0p2: ***** DATEISYSTEM WURDE VERÄNDERT *****
/dev/mmcblk0p2: 62541/483328 Dateien (0.4% nicht zusammenhängend), 857177/1931520 Blöcke

[mk01]

(16th Jul, 2013 01:18 AM)dlysnes Wrote:  Hey
Just a quick question. I'm on the first beta (fresh).
I ran apt-get update, but the apt-get install xbian-update -y only returns "xbian-update is already the newest version."

do a "apt-cache policy xbian-update". if really just 1.0-1.0 then do

apt-get clean
apt-get update
apt-get upgrade

[brantje]

Thanks, beta 1.1 running fine!

[JeHaLi]

(16th Jul, 2013 12:30 AM)mk01 Wrote:  

(16th Jul, 2013 12:23 AM)JeHaLi Wrote:  xbian@xbian ~ $ sudo "insserv -f rpcbind"
sudo: insserv -f rpcbind: command not found

without quotes. if you quote this, sudo wants to start ONE command named insserv\ \-f\ rpcbind

Code:

sudo insserv -f rpcbind

.........
Generation complete.
root@xbian:/home/xbian#

That helps, Thanks a lot !!!