Forum

i shutdown on shutdown button....

is possible take scrrens shots of xbian??

thanks

Yes it's possible - just press "Prt Scr" and it should ask you for which folder, if not already setup.

I recently have issues with XBian Beta 1.1 and Beta 2. I constantly get this message (even after clean installs):
And then my system becomes hardly usable.

few days ago solved this by buing one card new and second reformated twice with some kind of software.

What software? This happens with both brand new SD cards and already used ones.

https://www.sdcard.org/downloads/formatter_4/

low level sector by sector rewrite - nothing special. i also cleaned the sd card slots on RPis from dust. did nothing else.

Didn't work

I'm wondering whether the "boom" like anounced solution in rpi firmware for SD-card corruption is this one ;-)

What firmware you run ?

Beta 2 – Latest upgrades + staging.

From 2G SD card boot, created an .img file via ssh xbian-config to an external NTFS drive. Image file creation ended normally. (Or so it said)

Used this image to flash a new 2G SD card with Win32diskimager.

Booted the RPi – all lights came on but wouldn’t boot. Flashing cursor in top left corner (Tried twice, same results).

cmdline.txt and config.txt look Ok, so removed the # from initram in config.txt, but all that happened was that it then wouldn’t boot at all – only red light.

Read the original SD card with Win32diskimager and created an image with that.

There was a difference in size. Xbian = 1665M Win32 = 1982M.

Couldn’t use the Win32 image as it was too large for the SD card.

Any idea what could be happening here?

The system is 69% full using df –h.

Retried with a fresh Xbian 2 no staging this time, upgraded. System 54% full. Wrote a .img as before. Rewrote the image to SD card and rebooted. Worked just fine.

So, tried again on the Staging SD card. Removed some files, space now 55% - wrote img as before and retried.

Same results. So looks like something is amiss in the staging repo

root@xbian:~# xbian-apt-show-versions -u
gnupg/wheezy 1.4.12-7+deb7u2 upgradeable to 1.4.12-7+deb7u3
gpgv/wheezy 1.4.12-7+deb7u2 upgradeable to 1.4.12-7+deb7u3
kpartx/wheezy 0.4.9+git0.4dfdaf2b-7~deb7u1 upgradeable to 0.4.9+git0.4dfdaf2b-7~deb7u2
libcurl3/wheezy 7.26.0-1+wheezy6 upgradeable to 7.26.0-1+wheezy7
libcurl3-gnutls/wheezy 7.26.0-1+wheezy6 upgradeable to 7.26.0-1+wheezy7
libexpat1/wheezy 2.1.0-1 upgradeable to 2.1.0-1+deb7u1
libmysqlclient18/wheezy 5.5.31+dfsg-0+wheezy1 upgradeable to 5.5.33+dfsg-0+wheezy1
mysql-common/wheezy 5.5.31+dfsg-0+wheezy1 upgradeable to 5.5.33+dfsg-0+wheezy1
tzdata/wheezy 2013d-0wheezy1 upgradeable to 2013h-0wheezy1
xbian-package-config-shell/stable 2.1.6-52g upgradeable to 2.1.6-52h
xbian-package-config-xbmc/stable 1.1.4-3a upgradeable to 1.1.4-4b
xbian-package-vnc-server/stable 1.0.0-3b upgradeable to 1.0.1

Any ideas?

My guess is VFAT didn't survive the dd-ing into img file. There is no magic while doing the clone - first partition (32mb) is copied with dd. If PCs would have been 100% reliable then it MUST boot. Apparently no so I will re-code this to proper mkfs.vfat and copy files (with -v).

Also initramfs should be uncommented as after reflash we need resize + swap creation. Will fix.

Size difference is ok as xbianclone is not doing block copy. It uses btrfs internal functions. And always makes .img as small as possible (to be able to restore to smaller SDs as well in case of emergency).

Any ideas to my problems?

@Curly

hardly specially if you saying that existing beta1 install is doing the same "suddenly". in few results from google reasons were wearing off PSU, wearing off SD, wearing off RPI.

btw: feel free to update firmware. you can update to -9 (Dec-1st) or -11 (Dec-9th). Dec1st was the one generally recommended with all the fixes.

Trying right know. The wierd thing is that it happens with two pi's, with two PSU, and with multiple SD cards, were i never had issues before.

@CurlyMo

I was reviewing some past changes on kernels and found at least two commits which are actually INTRODUCING outputs about errors on MMC.

So could be that those errors are happening (or were happening) all the time, only nobody took care with notifications.