Raspberry Pi

From Holyheads Wiki
Revision as of 15:13, 8 February 2015 by Holyhead (Talk | contribs)

Jump to: navigation, search

Contents

Cookbook

My collection of hints, tips and tricks (supporting my memory and maybe also helping others).

External USB drives

  • Install ntfs-3g if you need write access to ntfs file systems
  • How to increase performance?

udevil

  • example for manual mounting: 
udevil mount /dev/sda1
  • my build-steps (maybe there's a simpler way, but this worked...):
    • download 0.4.3/udevil_0.4.3-1_all.deb from https://github.com/IgnorantGuru/udevil/tree/pkg, e.g. using wget
    • extract deb-package via ar vx udevil_0.4.3-1_all.deb
    • extract data archive tar xzvf data.tar.gz
    • change to tar usr/share/devil/src
    • untar tar xvfJ udevil-current.tar.xz
    • cd udevil-0.4.3
    • mv distros/debian
    • execute dpkg-buildpackage
    • If all required packages are installed, this results in udevil_0.4.3-1_armhf.deb. If the build fails due to missing packages, install the missing packages, and re-do the dpkg-buildpackage step
    • Install via sudo dpkg -i udevil_0.4.3-1_armhf.deb

Samba server / NAS

  • Slow disc performance?
    • see 'Slow USB drives' above
    • use Raspbian, etc without GUI to get as much CPU power for file-transfer as possible (OpenELEC or RaspBMC constantly use about 10-20% CPU load when idle, use top to check!)
  • I don't need sound: 
root@pi ~ # cat /etc/modprobe.d/snd-blacklist.conf 
# I don't need sound
blacklist snd
blacklist snd_pcm
blacklist snd_soc_core
blacklist snd_soc_bcm2708_i2s

Trying to reduce number of disk writes (SD card)

I'm using RRD with a cron job (currently observing pi's temperature and frequency). I hope that my SD card has proper wear-leveling (and currently my 8 GB card is less than half full), so that the frequent writing should not be a problem. But still, I want to reduce the number of writes to the SD card (in order to not bust it's lifetime).

Here's what I've done:

  • Edit /etc/default/cron and set EXTRA_OPTS="-L 0" to disable logging (I don't need these)
  • Avoid entries like pam_unix(cron:session): session closed for user pi in /var/log/auth.log
    • Edit /etc/pam.d/cron and comment the line @include common-session-noninteractive ([1])
or 
$local_fs_orig  +mountall +mountall-bootclean +mountoverflowtmp +umountfs
# we need the sym-link data in /var/log and /var/spool to be available
$local_fs       $local_fs_orig +persist-ramdisk
/etc/init.d/persist-ramdisk depends on $local_fs_orig, and the other init-scripts keep their dependency to $local_fs. This ensures that /var/log and /var/spool are ok when starting & stopping other init scripts.
  • set RAMTMP to yes in /etc/default/tmpfs to get tempfs based /tmp

Before changing /tmp:

But still, iostat shows quite some data written to the SD card, according to iotop its jbd2, the ::journaling part of ext4 (pi is 'idle', only some services run, and the ext4 partition is mounted with noatime).
I need to do more digging...

After changing /tmp:

It looks like the unwanted writes to SD are gone. I'll watch it for some time...

Useful stuff and Q&A

  • Q: Does Raspberry support WOL?
A: No: the Ethernet chip is connected via USB (http://www.raspberrypi.org/forum/viewtopic.php?f=53&t=39714)
  • Q: The new password is to short, or too simple
A: Try adjusting the PAM settings in /etc/pam.d/common-password:
  • remove the 'obscure' setting for pam_unix.so, and add your desired minimum length (e.g. minlen=2) 
 password        [success=1 default=ignore]      pam_unix.so sha512 minlen=2
!! This is not recommended if your box is connected to the internet or if it contains private data noone should know !!
But it's nice for testing (if you cannot or do not want to use auto-login.)
  • Q: How to configure static IP?
A: In /etc/network/interfaces: 
 iface eth0 inet static
   address 192.168.0.31
   netmask 255.255.255.0
   gateway 192.168.0.1
  • Q: How to read core temperature, etc?
A: vcgencmd: 
 vcgencmd measure_temp
 vcgencmd measure_clock arm
  • External USB HDD spin down
    • hdparm does not work with my WD Elements (SG_IO: bad host status: 0x7)
    • hd-idle works: 
hd-idle -a sda -i 600
for details, see for example http://blog.is-a-geek.org/festplatten-in-den-standby-modus-versetzen-unter-ubuntu-desktopserver-mit-hd-idle (German)
  • Q: How to avoid update of a certain package?
A: Put package on hold ([2] (German)): 
echo <packagename> "hold" | dpkg --set-selections
  • Q: How many bytes are written to my (SD) disc?
A: Use iostat http://www.mybinarylife.net/2012/08/linux-iostat-command.html
A: Use iotop http://guichaz.free.fr/iotop/
A: Raw data of the kernel can be found in files /proc/diskstats and /sys/block/DEVNAME/stat https://www.kernel.org/doc/Documentation/iostats.txt

Overclocking

  • I only set overclocking via raspi-config
Luckily, I could recover all my data, see below.
  • Medium: Raspberry is stable. I've observed two file system corruption which might be related to overclocking (see [3] and its links).
  • Underclocking to 600 MHz
echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Raspberry was stable for some hours, but it got frozen later on. I don't now if really related to underclocking. As the temperature did not drop significantly (stayed around 45°C), and the Raspberry CPU has no sleep modes either (for power saving), I did not retry.

Stress test and benchmarks

SD card issues

After my (Turbo-overclocked) Raspberry fried my 8 GB SD card, I had not hoped to to be able to recover any data, but I tried anyway. The card was only 1 week old, I have not written that much data too it (<4 GB, mainly the Raspbian image). I could still use this card for some time (see below), but finally I got a corrupted file system and could no longer repair it. That's when I re-installed Raspbian on a new SD card.

Maybe I should try running from USB sometime?

Recovery

  • Creating a binary image of the SD card with my PC using Win32 Disk Imager resulted in IO errors at about 17%.
  • The partition table of my SD card was still ok. I hoped to at least recover some text data of my ext4 partition, and thus I created an image using dd conv=sync,noerror if=/dev/sdb2 of=rasp-image.img bs=1M on my Linux machine (option conv=noerror ignores any errors, sync pads read-errors with zeros). The resulting image could not be mounted using a loop device.
  • Fortunately, fsck.ext4 raspberry-image.bin was able to repair the image, which I then could successfully mount on my Linux machine using mount -o loop rasp-image.img /mnt, and at a first glance, everything looked ok. So, I was at least able to get to my data.
  • On a later 'event', I dd-ed the repaired image back to the Raspberry, and could boot again.
  • On another a later 'event', I just fsck-ed the /dev/sdb2 using Linux, and could boot again... but I did not have luck this time - some files were gone.
  • I was just about to return the SD card, but for curiosity, I tried what happens if I re-install the (original) Raspbian image. To my surprise, Win32 Disk Imager did not report any error. And even more surprising, after writing the image, I was able to create an image of the whole disk without error. It looks like the card remapped some spare sectors.
  • My Raspberry successfully booted from this new image. I then used raspi-config to expand the root-fs (I've done this on my first installation as well). With Linux I was able to dd my repaired image to the repaired SD. The card booted as if nothing had happened...
  • But after some weeks, my Raspberry fried the SD card again, and some weeks later again ... And finally I could not get my pi to boot with this card. However, I can still read the data linux. Moving data to a new card... (easier said than done if the new card is slightly smaller... but, see below for resizing... and sometimes a fresh install is even less painful).

Reminders: dd, dd_rescue, losetup, mount and others

  • Example partition table printed by fdisk: 

/dev/sdb: 7861 MB, 7861174272 bytes, 15353856 sectors
Units = Sektoren of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Gerät  boot.     Anfang        Ende     Blöcke   Id  System
[...]
/dev/sdb3        15288320    15353855       32768   83  Linux

Byte-offset of sdb3: 7827619840 = 15288320 * 512

  • Mount partition to /dev/loopN partition for repair, etc.

losetup -o 7827619840 --find --show /dev/sdb --show prints the used /dev/loopN device

  • Directly mount partition using loop device:

mount -o loop,offset=7827619840 /dev/sdb /mnt

Some 1-Wire Stuff

Temperature Sensor DS1820

  • I have two DS18B20 and log temperatures using rrdtool.
  • When copying data via samba, I frequently get read-errors (CRC errors), or device-disconnects (/sys/bus/w1/devices/<id>/w1_slave temporarily not available).
    • Q: Is this due to overclocking with using dynamic governor?
    • A: No - also occurs without overclocking (but less frequent?)
    • Q: Or is this due to voltage-problems?
    • A: No - also occurs without over-voltage
    • Q: Or something else?
    • A: I have the impression that this is connected to electrical problems (e.g. timing, voltage) on my 1-wire when there's a lot of IO (USB, ethernet). Using 3 sensors works almost all the time (without overclocking), but using 4 or more sensors (2 connected star topologies, very bad for 1-wire GUIDELINES FOR RELIABLE LONG LINE 1-WIRE NETWORKS), almost always fails to read values on most of the sensors.
    • A:Implement multiple 1-wire interfaces (see below), using 1 for each star-topology solved the problem. Reading 2x3 works perfect!

Multiple 1-wire buses

  • Note: With kernel version, device tree were introduced, see for example http://www.raspberrypi.org/documentation/configuration/device-tree.md
    But somehow 1-wire works for my 3.18.5+ without specifying any dtoverlays... And all tries to configure w1-gpio-overlay.dtb via config.txt resulted in my Raspberry not booting (I also tried a modified w1.dtb which should also handle my second w1-bus).

Some 1-wire internals

Compiling own kernel

  • Some hints on cross-compiling:
  • extract kernel config from image:
scripts/extract-ikconfig kernel-image
(extract-ikconfig is part of the kernel sources)

Device Trees

What about updates?

As I always forget this

  • apt-get update - update package lists
  • apt-get upgrade - upgrade installed packages
  • rpi-update - update kernel and modules
use SKIP_KERNEL=1 rpi-update to update the RPi firmware, but keep the current kernel
set SKIP_REPODELETE=1 to keep downloaded files (by default: /root/.rpi-firmware)

Kernel Sources

LCD

Attach a LCD display

Controlling the display

LCDProc hints


Todo and Miscellaneous

Collection of stuff to check - things I might) try sometime

  • NAS/Samba
  • try adjusting 'socket options' in (/etc/samba/smb.conf) to increase NAS performance: some websites recommend to disable the 'socket options', some recommend to set: 
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

Things done

Some links (aka bookmark lists)

Project sites

Blogs, forums, etc

Miscellaneous

Manuals

Retrieved from "https://holyhead.de/index.php?title=Raspberry_Pi&oldid=202"
Personal tools