Search the Community

@guidol - no, while this may seem weird it's perfectly normal - this is a "bind mount", and this is how bind mounts appear in "mount". You can create one of these yourself, for example: root@nanopi:~# mkdir foo bar root@nanopi:~# mount --bind foo bar root@nanopi:~# mount | grep bar /dev/mmcblk1p2 on /root/bar type f2fs (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2) root@nanopi:~# (The "log.hdd" bind mount is created via "/usr/lib/armbian/armbian-ramlog".) Hope this helps!

@Adrian Cable - I made the changes for sunxi-current and pushed to the repo: https://github.com/armbian/build/commit/b2adb2935b4dcee57c982a1447de8cf75760dd2a. This change adds a new boot overlay for the sun8i-h3 that enables a maximum of 1.3GHz at a CPU core voltage of 1.3v. If you use this overlay, I strongly recommend you try driving the board hard to ensure stability (e.g., "stress --cpu 4", etc.) Historically on most of my boards the maximum I could push to was 1.2GHz at 1.3v, which is why I added a 1.2GHz overlay for the H5 (and I could only get to 1.368GHz w/a 1.4v core voltage). I can do the same for the H3, but am short on time atm. I'll also add this overlay to sunxi-legacy as well, but I won't be able to get to this later. I tested this on one of my H3 boards w/a max CPU voltage of 1.3v: /boot/armbianEnv.txt (note the addition of "cpu-clock-1.3GHz-1.3v" to the "overlays=" line): verbosity=7 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost0 usbhost1 usbhost2 uart1 cpu-clock-1.3GHz-1.3v rootdev=UUID=3ad712a7-75cb-4ac1-8cfa-dbb67df8f239 rootfstype=f2fs extraargs=net.ifnames=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u After booting with this overlay, from "cpufreq-info", w/everything else at the defaults, maximum clock rate is now 1.30GHz: analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.30 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 1.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:96.94%, 648 MHz:0.35%, 816 MHz:0.04%, 960 MHz:0.03%, 1.01 GHz:0.03%, 1.06 GHz:0.02%, 1.10 GHz:0.02%, 1.15 GHz:0.03%, 1.20 GHz:0.02%, 1.22 GHz:0.01%, 1.25 GHz:0.01%, 1.30 GHz:2.50% (253) Please give this a try and let me know how it goes If 1.3GHz is unstable, I'll try to expedite adding the 1.2GHz overlay as well.

Suggested changes to general.sh 796 export LC_ALL="en_US.UTF-8" 797 798 # packages list for host 799 # NOTE: please sync any changes here with the Dockerfile and Vagrantfile 800 local hostdeps="wget ca-certificates device-tree-compiler pv bc lzop zip binfmt-support build-essential ccache debootstrap ntpdate \ 801 gawk gcc-arm-linux-gnueabihf qemu-user-static u-boot-tools uuid-dev zlib1g-dev unzip libusb-1.0-0-dev fakeroot \ 802 parted pkg-config libncurses5-dev whiptail debian-keyring debian-archive-keyring f2fs-tools libfile-fcntllock-perl rsync libssl-dev \ 803 nfs-kernel-server btrfs-progs ncurses-term p7zip-full kmod dosfstools libc6-dev-armhf-cross \ 804 curl patchutils liblz4-tool libpython2.7-dev linux-base swig aptly acl python3-dev \ 805 locales ncurses-base pixz dialog systemd-container udev lib32stdc++6 libc6-i386 lib32ncurses5 lib32tinfo5 \ 806 bison libbison-dev flex libfl-dev cryptsetup gpgv1 gnupg1 cpio aria2 pigz dirmngr python3-distutils \ 807 ccache aria2 libusb-1.0-0-dev" 808 809 local codename=$(lsb_release -sc) 810 When I get my build environment working, and can adequately test, I'll submit this as a pull request. Harry

I doubt it can be done easily : U-Boot is not aware of F2FS, so it requires that at least the /boot folder to be located in EXT4 or FAT partition. What you can do is to manually shrink the ROOTFS partition and then add a new partition that you will format as F2FS. Then, you can transfer ROOTFS contain to new F2FS partition using tools such "rsync" or "tar|tar", and leave the /boot folder, adjust both /boot/armbianEnv.txt and /etc/fstab to point ROOTFS to the new F2FS.

I have never tried it. I am running it from SD card. That way it is much easier to manage. microSD cards cost so little these days. Just make sure you pick up a good one, like Sandisk Extreme (Pro), Samsung Pro or something like that. Samsung Evo+ is not too bad either. Generic cards, like cheap Kingston ones, are extremely slow. Specially when dealing with lot of small files. If you try to extract something like linux source or headers, which contain lot of small files, it takes ages. Goods cards have much higher IOPS and work quite well. Class 10, UHS-I and other markings are quite useless. The most important number is IOPS. Higher IOPS means much better performance when running OS on it. You can not find official IOPS specification for any cards. But internet is full of benchmarks and for some cards that information can be found unofficially. When booting kernel looks for partition labeled ROOTFS to mount as "/" and it can be on any storage device visible to kernel. So you can put it on USB stick or external HDD or any other device kernel recognizes, including emmc. I am not sure if it works but in theory you could partition mmcblk2 (I think it is emmc on our box), make one ext4 (or maybe f2fs) partition on it and label it ROOTFS (or anything else but then you need to update boot files accordingly). Copy entire SDcard contents there (except /boot, /sys, /proc, /dev - just make empty directories). If you labeled your partition ROOTFS then relabel your SD partition to something else. So you have only one partition labeled ROOTFS. After reboot you should boot from emmc. Then your boot partition remains on SD card but everything else is on emmc. You still need SD card to boot but entire system except kernel (which is only read once when booting) will be on emmc. And that SD card can be any old slow card. I think I would try something like that. I do not know if emmc contains something important for booting. If you completely erase it and re-partition you might make your box unbootable/(soft)bricked. So in theory it will work. But if emmc contains something important for booting, it will not. You will not see Android partitions on emmc because Android does not use partition table. Android uses partition definition file or something like that. That is essentially external partition table stored somewhere else. So linux kernel and partition tools know nothing about existing partitions because emmc has no partition table and looks like empty - but it is not. About DTB... I think I tried meson-g12a-x96-max.dtb and meson-g12a-x96-max-rmii.dtb but I do not think either one worked. If I remember correctly I tried all g12a DTB files but only one worked. Do you have BT and/or WiFi working? I do not care much about WiFi (I use cable anyway) but BT would be good - I could use keyboard/mouse without external dongle. EDIT: meson-g12a-x96-max.dtb and meson-g12a-x96-max-rmii.dtb do not work on my box. Tried both. Mecool KM9, 4GB RAM, 32GB ROM, 1Gb ethernet, S905x2 CPU

@tkaiser From what I have seen performance is similar to ext4 and not sure if it still suffers the level of performance degradation over time that it once had. Just wondering if you Armbian guys ever did any tests on block wear vs ext4 as just wondering as never really seen many real world examples. In a way f2fs should take a dumb old cheap sd card and use the boards cpu to provide a high level wear levelling algs & process with over-provision. Not really sure aside from the perf tests how you can capture the block wear as a comparison however.

I got a similar issue, but i got solved by trying different things. Before we got this issue, I was installing the armbian to emmc with the fs f2fs. When I installed with f2fs sometimes I had to rebooted the several times to boot or sometimes it is not boot. Then I tried with ext3 and it works perfect. I hope I help you.

Greetings to all, Preamble: Thanks to all that have worked to make the Armbian project what it is today. It is greatly appreciated! I have done numerous hours of reading and searching (due diligence). I know I could run a benchmarks and all but that means even more delay reaching the objective. Some brief guidance from those who have gone before would save a lot of time and would be greatly appreciated. Looking at the datasheets wasn't real helpful in guesstimating optimum performance configuration - especially since there are so many other factors that have an impact. Background: My objective is to achieve a reliable, long life system and avoid big performance hits along the way. The host is for home automation so the most of the storage activity will be logging and playing back canned sounds and serving up web pages consistent with HMI functions by my estimation. Other activity will be from Node-Red, MQTT broker, The automation web server, etc. I also maintain a NAS in the house so logs backups and databases associated with the HA system will be copied or backed up there. I have done so much reading and a fair bit of testing that I am a bit unsure as I write if Armbian supports logging to ramdisk or some such. If so, this would also be part of the picture for me. I would either sense the UPS power state or come up with a supercap or other power storage scheme and sense power loss and push ramdisk to NV storage... This is a little off topic but is relevant to the extent that I don't want to loose data that has been collected and the safest place for it is not in ram but in flash. I am guessing that for this context with a limited number (15?) of devices connected to via browser such as tablets, phones, and PCs alongside a few dozen other devices that are I/O nodes, not a lot of disk I/O will be needed. Room for growth is important (I hope) as well as avoiding performance degradation as a consequence of it. It is troublesome to have to deal with 'users' noticing slowdowns! Though of course I wouldn't consider hobbling the system now and loosening the reins later to deal with extra load... As I see it, if I use eMMC at all, I need to be using some kind of wear leveling (f2fs), minimize writes to it, and don’t fill it too full. A better option if performance will allow is to use sda1 instead for the root file system. I assume the M.2 device will have wear leveling and other features which along with much larger capacity (largely empty) in concert with brtfs file system is the best I can do to get performance and reliable operation over the M.2 /USB interface. Since M.2 is replaceable it is reasonable to expect that the system will not become permanently unusable due to flash wear failures in the near and mid term - I can simply restore to new M.2 device if it fails. Long term fiscal and technology issues are another matter. Question 1: Which would yield a more responsive system? The os residing on the eMMC or M.2? I see that the eMMC is using an 8 bit parallel interface (data and address must be using same path) vs the M.2 slot which is connected via a JMS567-LGBB1A chip. I read here https://forum.armbian.com/topic/1925-some-storage-benchmarks-on-sbcs/?do=findComment&comment=51350 that it at least has the potential to be a good performer. The context there was USB3 which is not used on the FA shield. The shield uses USB2 so there is still some question about how it will perform (there are other factors as well of course). Question 2: If I end up using eMMC for root, and assuming logs are being written to m.2, what recommendations to monitor and make sure writes to eMMC are minimized? I would probably want to do some monitoring anyway later on for lots of reasons. Pointers on how to set up brtfs (f2fs as well actually) for root to maintain speed and health in this context would also be appreciated. Regards and thanks again to all that have and will contribute, Q

Preamble: I have done numerous hours of reading and searching (due diligence). See end. I have a FA NanoPi NEO Core-2 LTS with shield and 64G M.2 (This shield uses JMS567-LGBB1A chip USB to sata for M.2 access). I have successfully installed Armbian from SD to and booted from the eMMC. Armbian Stretch mainline kernel 4.14.y - This image https://dl.armbian.com/nanopineocore2/Debian_stretch_next.7z armbianmonitor -u results http://ix.io/1xAA Logs indicate formatting did occur correctly as far as I can tell. The volumes are formatted as I selected - along with an 'extra' ext4 volume that looks like it is just for boot. NOTE: Since I could not boot, I re-tried using default ext4 for both which works. System now boots Armbian without TF. ATM OS resides on sda1. Console output: INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) DRAM: 1024 MiB Trying to boot from MMC2 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):c9f55c0 NOTICE: BL3-1: Built : 08:32:12, Oct 27 2018 NOTICE: DT: sun50i-h5-nanopi-neo-core2 NOTICE: SCPI: dummy stub handler, implementation level: 000000 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2018.05-armbian (Oct 27 2018 - 08:32:18 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO Core 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: serial Err: serial Net: No ethernet found. MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3090 bytes read in 4 ms (753.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 208 bytes read in 2 ms (101.6 KiB/s) MMC: no card present ** Bad device mmc 0 ** 30102 bytes read in 11 ms (2.6 MiB/s) 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo 504 bytes read in 14 ms (35.2 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo 4179 bytes read in 13 ms (313.5 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 4923549 bytes read in 247 ms (19 MiB/s) 13148168 bytes read in 649 ms (19.3 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4923485 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49b4d000, end 49fff05d ... OK reserving fdt memory region: addr=4fa00000 size=6d000 Loading Device Tree to 0000000049add000, end 0000000049b4cfff ... OK Starting kernel ... Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.29.2 done. mount: Invalid argument done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: invalid option -- done. mount: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 No init found. Try passing init= bootarg. Rebooting automatically due to panic= boot argument To elaborate on the process, after writing TF card and booting, I ran armbian-config selecting option "eMMC boot | USB/SATA/NVMe root install" and selected format of btrfs for sda1. Also, "Select filesystem type for eMMC /dev/mmcblk2" ... "Formating /dev/mmcblk2 to f2fs ... please wait". The utility responded with the appropriate warnings (about erasing/formatting) and appeared to execute correctly, returning no errors and prompting for reboot at end of process. I shutdown, removed card, powered up and system did not come up properly. I saw no special advisories about additional manual steps etc. Question: Did I miss a step when using the alternative disk format options on this platform? Are they a WIP? Should I file a bug report? 'Bibliography:' https://docs.armbian.com/User-Guide_Getting-Started/ https://docs.armbian.com/User-Guide_Armbian-Config/ Nearly all NanoPi NEO2 forum posts here Many others...

vm.swappiness=100 https://ghostbin.com/paste/vrt5t With vm.swappiness=30: system work fine With wm.swappiness=100: system work fine for a random time (3-12 h), then hang with ssh unreachable, yellow ethernet led fixed on, pihole/motioneye/rpi monitor web pages unreachables. Hardware: OrangePI Zero v1.4 - Sandisk uSD 16GB U1 A1 (checked, good healt) EXT4 - Toshiba USB Stick 32GB (checked, good healt) F2FS, USB PSU FriendlyARM 5V/3A (checked, good healt).

These are two different questions. The media makes no difference whatsoever if it's about booting times, even most crappy SD cards perform the same: https://forum.armbian.com/topic/4167-f2fs-revisited/?do=findComment&amp;comment=30835 If you for whatever reasons need short boot times Armbian is not for you. We optimize constantly but never for short boot times but for better operation once the board has finished booting If you need short boot times you need to become an expert to learn how to eliminate the various bottlenecks (see https://forum.armbian.com/topic/1089-usbootpi/ for example) If you're interested in times relevant for your use case you need to measure the time until the respective service is usable (and not until a login prompt appears somewhere).

Hi, I tried the release upgrade from xenial to bionic on the orange pi pc. Commands: sudo apt install update-manager-core sudo do-release-upgrade But the upgrade failed: orange@orangepipc:~$ sudo apt install -f Reading package lists... Done Building aml-0-2 lp-solve python3-lxml python3-pycurl Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 512 not upgraded. orange@orangepipc:~$ sudo apt update && sudo apt dist-upgrade && sudo apt autoremove && sudo apt autoclean Hit:1 http://ports.ubuntu.com bionic InRelease Hit:2 http://ports.ubuntu.com bionic-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:5 http://ports.ubuntu.com bionic-updates InRelease Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Hit:7 http://ports.ubuntu.com bionic-backports InRelease Fetched 74,6 kB in 4s (17,3 kB/s) Error: Timeout was reached Reading package lists... Done Building dependency tree Reading state information... Done 512 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: alsa-base breeze-icon-theme docbook-xml docbook-xsl evolution-data-server-common fonts-freefont-ttf g++-5 gcj-5-jre-lib gdebi-core gir1.2-gnomekeyring-1.0 gir1.2-javascriptcoregtk-3.0 gir1.2-soup-2.4 gir1.2-webkit-3.0 gnome-icon-theme-symbolic gsettings-ubuntu-schemas gtk3-engines-unico imagemagick-common indicator-common indicator-sound indicator-sound-gtk2 inputattach kate-data katepart kde-runtime kde-runtime-data kde-style-breeze kde-style-breeze-qt4 kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools kwayland-data libasprintf0v5 libass5 libattica0.4 libaudio2 libavcodec-ffmpeg56 libavdevice-ffmpeg56 libavfilter-ffmpeg5 libavformat-ffmpeg56 libavresample-ffmpeg2 libavutil-ffmpeg54 libbind9-140 libbluray1 libboost-date-time1.58.0 libboost-iostreams1.58.0 libboost-python1.58.0 libcamel-1.2-54 libcamel-1.2-61 libcapnp-0.5.3 libcapnp-0.6.1 libcdio-cdda1 libcdio-paranoia1 libcdio13 libck-connector0 libcolamd2 libcolamd2.9.1 libdbusmenu-qt2 libdlrestrictions1 libdns162 libebackend-1.2-10 libebook-1.2-16 libebook-contacts-1.2-2 libedata-book-1.2-25 libedataserver-1.2-21 libedataserver-1.2-23 libenca0 libevent-2.0-5 libgcj-common libgcj16 libgdbm3 libgee-0.8-2 libgeoclue0 libglew1.13 libgnome2-0 libgnome2-bin libgpgme++2v5 libguess1 libhunspell-1.3-0 libical1a libicu55 libido-0.1-0 libido3-0.1-0 libilmbase12 libindicator7 libisc160 libisccc140 libisccfg140 libjasper1 libjavascriptcoregtk-3.0-0 libkactivities6 libkatepartinterfaces4 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkexiv2-11v5 libkexiv2-data libkf5style5 libkf5waylandclient5 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkprintutils4 libkpty4 libkrosscore4 libktexteditor4 libkxmlrpcclient4 liblwres141 libmate-menu2 libmirclient9 libmircommon7 libmircore1 libmirprotobuf3 libmng2 libmodplug1 libmpfr4 libnm-glib-vpn1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 libnma-common libntrack-qt4-1 libntrack0 libokularcore7 libopencv-core2.4v5 libopencv-imgproc2.4v5 libopenexr22 libopenjpeg5 libpackagekit-glib2-16 libpcre16-3 libphonenumber7 libphonon4 libplasma3 libpolkit-qt-1-1 libpoppler-qt4-4 libpoppler58 libpostproc-ffmpeg53 libprotobuf-lite9v5 libprotobuf10 libpython3.5 libqca2 libqimageblitz4 libqmobipocket1 libqt4-dbus libqt4-declarative libqt4-designer libqt4-network libqt4-opengl libqt4-qt3support libqt4-script libqt4-sql libqt4-svg libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4 libqtgui4 libqtwebkit4 libraw15 libschroedinger-1.0-0 libsodium18 libsolid4 libstdc++-5-dev libstreamanalyzer0v5 libstreams0v5 libsuitesparseconfig4.4.6 libsuitesparseconfig5 libswresample-ffmpeg1 libswscale-ffmpeg3 libthreadweaver4 liburl-dispatcher1 libva-wayland1 libva-x11-1 libva1 libvpx3 libwebkitgtk-3.0-0 libwebp5 libwebpdemux1 libwebrtc-audio-processing-0 libx264-148 libx265-79 libxapian22v5 libxfont1 libxml2-utils linux-sound-base lp-solve lubuntu-artwork-16-04 mate-menus ntrack-module-libnl-0 oxygen5-icon-theme phonon phonon-backend-gstreamer phonon-backend-gstreamer-common plasma-scriptengine-javascript printer-driver-pnm2ppa python-mate-menu python3-debian python3-lxml python3-packagekit python3-polib python3-pycurl python3-xkit qdbus qtchooser qtcore4-l10n sgml-base sgml-data ubuntu-drivers-common xml-core zlib1g-dev Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: packagekit-backend-aptcc The following NEW packages will be installed: apport apport-gtk brasero-common btrfs-progs cpp-7 dvd+rw-tools fonts-ubuntu g++-7 gcc-7 gcc-7-base gdisk gir1.2-wnck-3.0 gnome-desktop3-data growisofs indicator-common kinit kio kpackagetool5 kwayland-data liba52-0.7.4 libaa1 libaccounts-glib0 libaccounts-qt5-1 libaio1 libaribb24-0 libasan4 libbasicusageenvironment1 libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2 libboost-python1.65.1 libbrasero-media3-1 libburn4 libcamel-1.2-61 libcapnp-0.6.1 libcddb2 libcilkrts5 libcolamd2 libdbusmenu-qt5-2 libdca0 libdee-1.0-4 libdvbpsi10 libebml4v5 libedataserver-1.2-23 libevent-2.1-6 libexo-2-0 libfaad2 libfastjson4 libgcc-7-dev libgmime-3.0-0 libgnome-desktop-3-17 libgnomekbd-common libgnomekbd8 libgpgme++2v5 libgroupsock8 libgtop-2.0-11 libip6tc0 libiptc0 libirs160 libisl19 libisofs6 libjte1 libkaccounts1 libkate1 libkf5activities5 libkf5archive5 libkf5attica5 libkf5bookmarks-data libkf5bookmarks5 libkf5completion-data libkf5completion5 libkf5crash5 libkf5dbusaddons-data libkf5dbusaddons5 libkf5declarative-data libkf5declarative5 libkf5doctools5 libkf5globalaccel-data libkf5globalaccel5 libkf5jobwidgets-data libkf5jobwidgets5 libkf5js5 libkf5jsapi5 libkf5kexiv2-15.0.0 libkf5kiocore5 libkf5kiontlm5 libkf5kiowidgets5 libkf5notifications-data libkf5notifications5 libkf5package-data libkf5package5 libkf5parts-data libkf5parts5 libkf5pty-data libkf5pty5 libkf5purpose-bin libkf5purpose5 libkf5quickaddons5 libkf5service-bin libkf5service-data libkf5service5 libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5textwidgets-data libkf5textwidgets5 libkf5threadweaver5 libkf5wallet-bin libkf5wallet-data libkf5wallet5 libkf5waylandclient5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5 libkwalletbackend5-5 liblirc-client0 liblivemedia62 libluajit-5.1-2 libluajit-5.1-common libmad0 libmagic-mgc libmarkdown2 libmatroska6v5 libmicrodns0 libmpcdec6 libmpeg2-4 libmpfr6 libnautilus-extension1a libnfs11 libntfs-3g88 libokular5core8 libopenmpt-modplug1 libparted-fs-resize0 libphonenumber7 libphonon4qt5-4 libplacebo4 libpoppler-qt5-1 libpq5 libprotobuf-lite10 libprotobuf10 libqca-qt5-2 libqmobipocket2 libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5texttospeech5 libraw16 libresid-builder0c2a libsdl-image1.2 libshout3 libsidplay2 libsignon-qt5-1 libssh2-1 libstdc++-7-dev libsuitesparseconfig5 libteamdctl0 libtotem-plparser-common libtotem-plparser18 libunique-1.0-0 libunity-protocol-private0 libunity-scopes-json-def-desktop libunity9 libupnp6 libusageenvironment3 libvlc5 libvlccore9 libvulkan1 libwnck-3-0 libwnck-3-common libxapp1 libxcb-xv0 libxtables12 lubuntu-artwork-18-04 lxhotkey-core lxhotkey-gtk mate-polkit mate-polkit-common netplan.io nplan openbox-lxde-session phonon4qt5 phonon4qt5-backend-vlc powermgmt-base python-mate-menu python3-apport python3-asn1crypto python3-cffi-backend python3-cryptography python3-distro-info python3-httplib2 python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-oauth python3-problem-report python3-requests-unixsocket python3-secretstorage python3-simplejson python3-wadllib python3-yaml python3-zope.interface qml-module-org-kde-kquickcontrolsaddons qml-module-qtquick-dialogs qml-module-qtquick-privatewidgets qml-module-qtquick2 qml-module-ubuntu-onlineaccounts qtdeclarative5-qtquick2-plugin ubuntu-advantage-tools vlc-data vlc-plugin-base vlc-plugin-video-output xapps-common xserver-xorg-input-libinput xserver-xorg-video-qxl xxd The following packages will be upgraded: accountsservice alsa-utils anacron autoconf automake autotools-dev avahi-autoipd binfmt-support bluez-tools breeze-icon-theme bridge-utils btrfs-tools build-essential chromium-browser chromium-codecs-ffmpeg-extra cinnamon-desktop-data command-not-found command-not-found-data cpp cpp-5 cpufrequtils crda cups-pk-helper desktop-file-utils device-tree-compiler dialog dnsmasq-base dnsutils docbook-xml docbook-xsl dosfstools eject ethtool evince evince-common evolution-data-server-common evtest exo-utils expect f2fs-tools f3 fake-hwclock fbi fbset figlet file firefox fonts-freefont-ttf fping fuse g++ g++-5 galculator gawk gcc gcc-5 gcc-5-base gcc-6-base gdebi-core geany geany-common genisoimage gettext-base gir1.2-javascriptcoregtk-3.0 gir1.2-soup-2.4 gir1.2-webkit-3.0 gnome-keyring gpicview groff-base gsettings-ubuntu-schemas gsfonts gstreamer1.0-plugins-base gstreamer1.0-pulseaudio gthumb gthumb-data gtk2-engines gtk2-engines-murrine gtk2-engines-xfce gvfs gvfs-backends gvfs-common gvfs-daemons gvfs-fuse gvfs-libs haveged hddtemp hdparm hexchat hexchat-common hostapd html2text htop ifenslave im-config indicator-sound indicator-sound-gtk2 inputattach inxi iotop iozone3 iperf3 iptables iputils-arping iputils-ping isc-dhcp-common iw kate-data katepart kde-runtime kde-runtime-data kde-style-breeze kde-style-breeze-qt4 kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools keyutils language-pack-de language-pack-de-base language-selector-common language-selector-gnome laptop-detect leafpad less libaccountsservice0 libarchive13 libasan2 libasprintf0v5 libatasmart4 libatkmm-1.6-1v5 libatm1 libatomic1 libcairomm-1.0-1v5 libcanberra-gtk0 libcanberra-gtk3-0 libcc1-0 libcdparanoia0 libcinnamon-desktop4 libclutter-1.0-0 libclutter-gtk-1.0-0 libcogl-pango20 libcogl-path20 libcpufreq0 libdbusmenu-gtk4 libdbusmenu-qt2 libdjvulibre-text libdjvulibre21 libdlrestrictions1 libebackend-1.2-10 libebook-contacts-1.2-2 libedata-book-1.2-25 libenca0 libestr0 libevdocument3-4 libevview3-3 libexempi3 libexiv2-14 libexo-1-0 libexo-common libexo-helpers libf2fs0 libfam0 libfftw3-single3 libfm-data libfm-extra4 libfm-gtk-data libfm-gtk4 libfm-modules libfm4 libfuse2 libgarcon-1-0 libgarcon-common libgcc-5-dev libgconfmm-2.6-1v5 libgdata-common libgdata22 libgee-0.8-2 libgeoclue0 libgimp2.0 libglibmm-2.4-1v5 libgoa-1.0-0b libgoa-1.0-common libgpm2 libgtkmm-2.4-1v5 libgtkmm-3.0-1v5 libgtop2-common libgxps2 libhavege1 libido3-0.1-0 libimobiledevice6 libindicator7 libiperf0 libisl15 libiw30 libjpeg-turbo8 libkactivities6 libkatepartinterfaces4 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkeybinder-3.0-0 libkf5auth-data libkf5auth5 libkf5codecs-data libkf5codecs5 libkf5config-data libkf5configcore5 libkf5configgui5 libkf5configwidgets-data libkf5configwidgets5 libkf5coreaddons-data libkf5coreaddons5 libkf5guiaddons5 libkf5i18n-data libkf5i18n5 libkf5iconthemes-data libkf5iconthemes5 libkf5itemviews-data libkf5itemviews5 libkf5style5 libkf5widgetsaddons-data libkf5widgetsaddons5 libkf5windowsystem-data libkf5windowsystem5 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpathsea6 libkprintutils4 libkpty4 libkrosscore4 libktexteditor4 libkxmlrpcclient4 libleveldb1v5 liblightdm-gobject-1-0 libmagic1 libmate-desktop-2-17 libmate-menu2 libmate-panel-applet-4-1 libmatedict6 libmatekbd-common libmatekbd4 libmatemixer-common libmatemixer0 libmenu-cache-bin libmenu-cache3 libmirclient9 libmircommon7 libmircore1 libmirprotobuf3 libmm-glib0 libmodplug1 libmpc3 libmtp-common libmtp9 libmysqlclient20 libndp0 libnemo-extension1 libnetfilter-conntrack3 libnewt0.52 libnfsidmap2 libnih1 libnl-3-200 libnl-3-dev libnl-genl-3-200 libnl-genl-3-dev libnl-route-3-200 libnm-glib-vpn1 libnm-glib4 libnm-gtk0 libnm-util2 libnm0 libnma0 libnotify-bin liboauth0 libopenexr22 libopts25 libpam-gnome-keyring libpangomm-1.4-1v5 libparted2 libpci3 libpcre16-3 libpcsclite1 libphonon4 libpipeline1 libpkcs11-helper1 libplasma3 libplist3 libplymouth4 libpolkit-qt-1-1 libpolkit-qt5-1-1 libpoppler-glib8 libqca2 libqimageblitz4 libqtwebkit4 libsasl2-modules libsdl1.2debian libsigsegv2 libsolid4 libspectre1 libss2 libssl-dev libssl1.0.0 libstdc++-5-dev libstreamanalyzer0v5 libstreams0v5 libsysfs2 libtag1v5 libtag1v5-vanilla libtcl8.6 libthreadweaver4 libthunarx-2-0 libtirpc1 libubsan0 libudisks2-0 libunity-api0 libupower-glib3 liburl-dispatcher1 libusb-0.1-4 libusbmuxd4 libustr-1.0-1 libvisual-0.4-0 libvte-common libvte9 libwnck-common libwnck22 libxfce4ui-1-0 libxfce4ui-utils libxklavier16 libxml2-utils libxres1 lightdm lightdm-gtk-greeter linux-firmware linux-libc-dev logrotate lp-solve lubuntu-artwork lubuntu-artwork-16-04 lubuntu-core lubuntu-default-settings lubuntu-lxpanel-icons lxappearance lxde lxde-common lxde-core lxde-icon-theme lxdm lxmenu-data lxpanel lxpanel-data lxsession lxsession-data lxsession-edit lxsession-logout lxtask lxterminal m4 man-db mate-desktop-common mate-menus mate-settings-daemon mate-settings-daemon-common mate-utils mate-utils-common mawk multiarch-support mysql-common nano ncurses-term nemo nemo-data net-tools netcat-openbsd network-manager network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome nfs-common nodm ntfs-3g ntp okular openssh-client openssh-server openssh-sftp-server openvpn orage oxygen-icon-theme oxygen5-icon-theme p11-kit packagekit paprefs parted pasystray pavucontrol pavumeter pciutils pcmanfm phonon phonon-backend-gstreamer phonon-backend-gstreamer-common plasma-scriptengine-javascript plymouth plymouth-label plymouth-theme-lubuntu-logo plymouth-theme-lubuntu-text plymouth-theme-ubuntu-text policykit-1 policykit-1-gnome printer-driver-pnm2ppa profile-sync-daemon pv python-cairo python-gi python-gobject python-gobject-2 python-gtk2 python-pyexiv2 python3-commandnotfound python3-debian python3-distupgrade python3-polib python3-update-manager qemu-user resolvconf rfkill rpcbind rsync rsyslog screen sgml-base stress sudo sysbench sysfsutils sysstat tcl-expect thunar thunar-data thunderbird toilet toilet-fonts ttf-ubuntu-font-family u-boot-tools ubuntu-drivers-common ubuntu-mate-welcome ubuntu-minimal ubuntu-release-upgrader-core udisks2 unattended-upgrades unicode-data unzip update-manager-core ureadahead usbutils vim vim-common vim-runtime vim-tiny vlan wget whiptail wireless-regdb wireless-tools wpasupplicant x11-apps x11-session-utils x11-xserver-utils xarchiver xauth xbacklight xdg-utils xfce4 xfce4-appfinder xfce4-panel xfce4-pulseaudio-plugin xfce4-session xfce4-settings xfce4-terminal xfdesktop4 xfdesktop4-data xfonts-utils xfwm4 xinetd xinit xinput xml-core xorg xorg-docs-core xournal xsane xsane-common xserver-xorg xserver-xorg-input-all xserver-xorg-video-all zenity zenity-common zip 512 upgraded, 222 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B/441 MB of archives. After this operation, 200 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 126306 files and directories currently installed.) Preparing to unpack .../policykit-1_0.105-20ubuntu0.18.04.1_armhf.deb ... Failed to get properties: Connection timed out dpkg: error processing archive /var/cache/apt/archives/policykit-1_0.105-20ubuntu0.18.04.1_armhf.deb (--unpack): new policykit-1 package pre-installation script subprocess returned error exit status 1 Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Errors were encountered while processing: /var/cache/apt/archives/policykit-1_0.105-20ubuntu0.18.04.1_armhf.deb Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) orange@orangepipc:~$ sudo systemctl restart systemd-logind Failed to restart systemd-logind.service: Connection timed out See system logs and 'systemctl status systemd-logind.service' for details. orange@orangepipc:~$ The apt upgrade returned an error ... orange@orangepipc:~$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: alsa-base breeze-icon-theme docbook-xml docbook-xsl evolution-data-server-common fonts-freefont-ttf g++-5 gcj-5-jre-lib gir1.2-gnomekeyring-1.0 gir1.2-javascriptcoregtk-3.0 gir1.2-soup-2.4 gir1.2-webkit-3.0 gnome-icon-theme-symbolic gsettings-ubuntu-schemas gtk3-engines-unico imagemagick-common indicator-common indicator-sound indicator-sound-gtk2 inputattach kate-data katepart kde-runtime kde-runtime-data kde-style-breeze kde-style-breeze-qt4 kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools kwayland-data libappstream4 libasprintf0v5 libass5 libattica0.4 libaudio2 libavcodec-ffmpeg56 libavdevice-ffmpeg56 libavfilter-ffmpeg5 libavformat-ffmpeg56 libavresample-ffmpeg2 libavutil-ffmpeg54 libbind9-140 libbluray1 libboost-date-time1.58.0 libboost-iostreams1.58.0 libboost-python1.58.0 libcamel-1.2-54 libcamel-1.2-61 libcapnp-0.5.3 libcapnp-0.6.1 libcdio-cdda1 libcdio-paranoia1 libcdio13 libck-connector0 libcolamd2 libcolamd2.9.1 libdbusmenu-qt2 libdlrestrictions1 libdns162 libebackend-1.2-10 libebook-1.2-16 libebook-contacts-1.2-2 libedata-book-1.2-25 libedataserver-1.2-21 libedataserver-1.2-23 libenca0 libevent-2.0-5 libgcj-common libgcj16 libgdbm3 libgee-0.8-2 libgeoclue0 libglew1.13 libgnome2-0 libgnome2-bin libgpgme++2v5 libguess1 libhunspell-1.3-0 libical1a libicu55 libido-0.1-0 libido3-0.1-0 libilmbase12 libindicator7 libisc160 libisccc140 libisccfg140 libjasper1 libjavascriptcoregtk-3.0-0 libkactivities6 libkatepartinterfaces4 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkexiv2-11v5 libkexiv2-data libkf5style5 libkf5waylandclient5 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkprintutils4 libkpty4 libkrosscore4 libktexteditor4 libkxmlrpcclient4 liblwres141 libmate-menu2 libmirclient9 libmircommon7 libmircore1 libmirprotobuf3 libmng2 libmodplug1 libmpfr4 libnm-glib-vpn1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 libnma-common libntrack-qt4-1 libntrack0 libokularcore7 libopencv-core2.4v5 libopencv-imgproc2.4v5 libopenexr22 libopenjpeg5 libpcre16-3 libphonenumber7 libphonon4 libplasma3 libpolkit-qt-1-1 libpoppler-qt4-4 libpoppler58 libpostproc-ffmpeg53 libprotobuf-lite9v5 libprotobuf10 libpython3.5 libqca2 libqimageblitz4 libqmobipocket1 libqt4-dbus libqt4-declarative libqt4-designer libqt4-network libqt4-opengl libqt4-qt3support libqt4-script libqt4-sql libqt4-svg libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4 libqtgui4 libqtwebkit4 libraw15 libschroedinger-1.0-0 libsodium18 libsolid4 libstdc++-5-dev libstemmer0d libstreamanalyzer0v5 libstreams0v5 libsuitesparseconfig4.4.6 libsuitesparseconfig5 libswresample-ffmpeg1 libswscale-ffmpeg3 libthreadweaver4 liburl-dispatcher1 libva-wayland1 libva-x11-1 libva1 libvpx3 libwebkitgtk-3.0-0 libwebp5 libwebpdemux1 libwebrtc-audio-processing-0 libx264-148 libx265-79 libxapian22v5 libxfont1 libxml2-utils linux-sound-base lp-solve lubuntu-artwork-16-04 mate-menus ntrack-module-libnl-0 oxygen5-icon-theme phonon phonon-backend-gstreamer phonon-backend-gstreamer-common plasma-scriptengine-javascript printer-driver-pnm2ppa python-mate-menu python3-lxml python3-polib python3-pycurl python3-xkit qdbus qtchooser qtcore4-l10n sgml-base sgml-data ubuntu-drivers-common xml-core zlib1g-dev Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: haveged rpcbind sysfsutils Suggested packages: apparmor The following packages will be upgraded: haveged rpcbind sysfsutils 3 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 729 not fully installed or removed. Need to get 0 B/76,7 kB of archives. After this operation, 22,5 kB disk space will be freed. Do you want to continue? [Y/n] Y Setting up libfuse2:armhf (2.9.7-1ubuntu1) ... Setting up fuse (2.9.7-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up libsigsegv2:armhf (2.12-1) ... Setting up multiarch-support (2.27-3ubuntu1) ... (Reading database ... 141691 files and directories currently installed.) Preparing to unpack .../rpcbind_0.2.3-0.6_armhf.deb ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop rpcbind.service: Connection timed out See system logs and 'systemctl status rpcbind.service' for details. Failed to get load state of rpcbind.service: Connection timed out invoke-rc.d: initscript rpcbind, action "stop" failed. dpkg: warning: old rpcbind package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop rpcbind.service: Connection timed out See system logs and 'systemctl status rpcbind.service' for details. Failed to get load state of rpcbind.service: Failed to activate service 'org.freedesktop.systemd1': timed out invoke-rc.d: initscript rpcbind, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/rpcbind_0.2.3-0.6_armhf.deb (--unpack): new rpcbind package pre-removal script subprocess returned error exit status 1 Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to start rpcbind.service: Connection timed out See system logs and 'systemctl status rpcbind.service' for details. invoke-rc.d: initscript rpcbind, action "start" failed. Failed to get properties: Connection timed out dpkg: error while cleaning up: installed rpcbind package post-installation script subprocess returned error exit status 1 Preparing to unpack .../haveged_1.9.1-6_armhf.deb ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop haveged.service: Connection timed out See system logs and 'systemctl status haveged.service' for details. Failed to get load state of haveged.service: Connection timed out invoke-rc.d: initscript haveged, action "stop" failed. dpkg: warning: old haveged package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop haveged.service: Connection timed out See system logs and 'systemctl status haveged.service' for details. Failed to get load state of haveged.service: Connection timed out invoke-rc.d: initscript haveged, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/haveged_1.9.1-6_armhf.deb (--unpack): new haveged package pre-removal script subprocess returned error exit status 1 Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to start haveged.service: Connection timed out See system logs and 'systemctl status haveged.service' for details. invoke-rc.d: initscript haveged, action "start" failed. Failed to get properties: Connection timed out dpkg: error while cleaning up: installed haveged package post-installation script subprocess returned error exit status 1 Preparing to unpack .../sysfsutils_2.1.0+repack-4build1_armhf.deb ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop sysfsutils.service: Connection timed out See system logs and 'systemctl status sysfsutils.service' for details. Failed to get load state of sysfsutils.service: Connection timed out invoke-rc.d: initscript sysfsutils, action "stop" failed. dpkg: warning: old sysfsutils package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to stop sysfsutils.service: Connection timed out See system logs and 'systemctl status sysfsutils.service' for details. Failed to get load state of sysfsutils.service: Connection timed out invoke-rc.d: initscript sysfsutils, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/sysfsutils_2.1.0+repack-4build1_armhf.deb (--unpack): new sysfsutils package pre-removal script subprocess returned error exit status 1 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out Failed to retrieve unit state: Connection timed out Failed to start sysfsutils.service: Connection timed out See system logs and 'systemctl status sysfsutils.service' for details. invoke-rc.d: initscript sysfsutils, action "start" failed. Failed to get properties: Connection timed out dpkg: error while cleaning up: installed sysfsutils package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/rpcbind_0.2.3-0.6_armhf.deb /var/cache/apt/archives/haveged_1.9.1-6_armhf.deb /var/cache/apt/archives/sysfsutils_2.1.0+repack-4build1_armhf.deb Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) How can I solve this? ... otherwise I need to reinstall. Regards

Thanks @Igor, yes the problem is with script.bin. When using h3disp a script.bin with current date/time is placed in /boot which results in blank page. when I copy /boot/bin/orangepipcplus from Sep 2 2017, with 36568 bytes from the *not updated* opipcplus over it, then I have a correct image. However there is another problems, independent of script.bin: There is an empty /etc/resolv.conf so that no names are resolved on internet. I have to call dhclient by hand, which produces a valid resolv.conf Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.0.253 search fritz.box Here is my armbianmonitor -u http://ix.io/1deC and here is something very strange: the update went through without errors but: root@JagOpi:/var/lib/rpimonitor# armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you may have corrupt packages. This is usually a symptom of filesystem corruption caused by SD cards or eMMC dying or burning the OS image to the installation media went wrong. The following changes from packaged state files were detected: /var/lib/rpimonitor/updatestatus.txt root@JagOpi:/var/lib/rpimonitor# cat updatestatus.txt autoconf bash-completion blueman btrfs-tools cups cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common device-tree-compiler dh-python dmidecode e2fslibs e2fsprogs f2fs-tools fonts-opensymbol git git-man htop ifupdown libassuan0 libblas-common libblas3 libbluray1 libcomerr2 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdrm-freedreno1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libfftw3-double3 libfftw3-single3 libgbm1 libgcrypt20 libgeoip1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libglib2.0-0 libgpg-error0 libgphoto2-6 libhpmud0 libksba8 liblapack3 libldap-2.4-2 libllvm3.5 libmtp-common libmtp9 libnss-myhostname libpam-systemd libpcap0.8 libpulse-mainloop-glib0 libpulse0 libpulsedsp libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gtk libreoffice-impress libreoffice-style-tango libreoffice-writer libsqlite3-0 libss2 libssl-dev libssl1.0.0 libsystemd0 libudev1 libva-glx1 libva-x11-1 libva1 libwayland-egl1-mesa linux-base linux-libc-dev manpages openssl printer-driver-hpcups pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-utils python-numpy python-pyudev rsyslog shared-mime-info smartmontools stress systemd systemd-sysv tar udev unicode-data uno-libs3 ure 103 upgradable(s) root@JagOpi:/var/lib/rpimonitor# Thanks, gnasch

Hi nachoparker, I tried building the docker image on Armbian Jessie with XU4 hardware but some packages are not fetched : /nextcloudpi# ./build-SD-armbian.sh odroidxu4 remote: Counting objects: 5, done. remote: Compressing objects: 100% (5/5), done. remote: Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (5/5), done. From https://github.com/armbian/build a22156e..8f47d7f master -> origin/master Updating a22156e..8f47d7f Fast-forward config/boards/tinkerboard.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --2018-06-10 19:32:41-- https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/armbian.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.0.133, 151.101.64.133, 151.101.128.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1545 (1.5K) [text/plain] Saving to: ‘armbian/userpatches/customize-image.sh’ armbian/userpatches/customize-image.sh 100%[===========================================================================================================================================>] 1.51K --.-KB/s in 0s 2018-06-10 19:32:41 (14.5 MB/s) - ‘armbian/userpatches/customize-image.sh’ saved [1545/1545] [ o.k. ] Using config file [ config-docker.conf ] [ .... ] Building a Docker container Sending build context to Docker daemon 1.712GB Step 1/8 : FROM ubuntu:16.04 ---> 0d6bd8934d0f Step 2/8 : RUN dpkg --add-architecture i386 ---> Using cache ---> a31c4ea9194e Step 3/8 : RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y dist-upgrade && DEBIAN_FRONTEND=noninteractive apt-get install -y git dialog lsb-release binutils wget ca-certificates device-tree-compiler pv bc lzop zip binfmt-support build-essential ccache debootstrap ntpdate gawk gcc-arm-linux-gnueabihf qemu-user-static u-boot-tools uuid-dev zlib1g-dev unzip libusb-1.0-0-dev parted pkg-config libncurses5-dev whiptail debian-keyring debian-archive-keyring f2fs-tools libfile-fcntllock-perl rsync libssl-dev nfs-kernel-server btrfs-tools ncurses-term p7zip-full kmod dosfstools libc6-dev-armhf-cross fakeroot curl patchutils python liblz4-tool libpython2.7-dev linux-base swig libpython-dev systemd-container udev g++-5-arm-linux-gnueabihf lib32stdc++6 libc6-i386 lib32ncurses5 lib32tinfo5 locales ncurses-base zlib1g:i386 pixz bison libbison-dev flex libfl-dev ---> Running in d24a2ae405cd Get:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease [247 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease [109 kB] ........................ Fetched 24.4 MB in 13s (1747 kB/s) Reading package lists... E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/binary-i386/Packages 404 Not Found E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/binary-i386/Packages 404 Not Found E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/xenial-backports/main/binary-i386/Packages 404 Not Found E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/xenial-security/main/binary-i386/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. .......................................... The command '/bin/sh -c apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y dist-upgrade && DEBIAN_FRONTEND=noninteractive apt-get install -y git dialog lsb-release binutils wget ca-certificates device-tree-compiler pv bc lzop zip binfmt-support build-essential ccache debootstrap ntpdate gawk gcc-arm-linux-gnueabihf qemu-user-static u-boot-tools uuid-dev zlib1g-dev unzip libusb-1.0-0-dev parted pkg-config libncurses5-dev whiptail debian-keyring debian-archive-keyring f2fs-tools libfile-fcntllock-perl rsync libssl-dev nfs-kernel-server btrfs-tools ncurses-term p7zip-full kmod dosfstools libc6-dev-armhf-cross fakeroot curl patchutils python liblz4-tool libpython2.7-dev linux-base swig libpython-dev systemd-container udev g++-5-arm-linux-gnueabihf lib32stdc++6 libc6-i386 lib32ncurses5 lib32tinfo5 locales ncurses-base zlib1g:i386 pixz bison libbison-dev flex libfl-dev' returned a non-zero code: 100 [ error ] Docker container build exited with code: [ 0 ] When I try "http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/binary-i386/Packages" I get not found as well. Thank you for any help!

I bought two new SD-Card (Samsung Evo Select 32GB, ~13$), since they're not available here I bought them from amazon. A review claimed that their random write performance should be good, whenever the card has no A1 rating. The packaging looks original, but can't guarantee it. H2testw looked ok (my SD-card reader on the notebook is internally connected via USB2 so forget about read performance here ). So, I mounted this card on my OPi PC plus (armbian on eMMC) and did a first iozone which didn't looked promising. Random write 4k of about 850kB (3x). Slightly annoyed, I burned armbian for the tinker board on this card and gave it another try. Iozone looked not perfect, but ~50% faster. So, I thought this could be interesting, since a lot of numbers are presented here and the used SBC can have an impact on performance. Luckily, iozone has the possibility to save results in an excel file, because I'm definitely too lazy to play the copy paste monkey. A small bash script and some statistics did the rest (in principle, it's @tkaiser iozone test 50 times repeated). So, here are my findings for the Samsung EVO Select SD-Card: Posting the whole dataset would be an overkill so I only show you the random 4k write performance (if someone is interested, the whole dataset is available). Cause, they are some claimings about the performance of f2fs and btrfs, I formatted this card also with this two filesystems and gave them a try. All these measurements were made with the same SD-Card (I also tested the other one, but not 50x with all filesystems and the results looked similar). Since thomas noted that performance tests should run at min 1008MHz, the tests were repeated by cpu min freq. 1008MHz on the opi (setting cpu min on my tinker led to a non bootable system ) For those who are not familiar with this type of diagram, it's a box plot and wikipedia explains it quite good. We see that f2fs doesn't differ that much in performance but btrfs seems to be faster (but variation is also much higher!). To be complete: ARMBIAN 5.32.170629 nightly Ubuntu 16.04.2 LTS 4.11.7-sun8i (OrangePi PC+) Armbian_5.30_Tinkerboard_Ubuntu_xenial_default_4.4.71_desktop ((Tinker, latest stable legacy from download page)

Resizing the partition looks scary but it works. Resizing the filesystem is safe - either kernel supports on-line resizing and it can be done, or you have to reboot to finish it (for kernels < 3.10). I don't expect any changes to this code or changing the file path anytime soon, so it should be safe to experiment with btrfs and f2fs resizing.

Bingo. Worked with USB ethernet! Thanks!!! Now waiting for my serial to usb cable to arrive from China to better understand why my orangepi won't boot when I compile the same .img, but with F2FS instead of ext4. Most likely I'll be posting again in 3-4 weeks.

Since I had to wait for other stuff and had already 3 installations on SD card I thought let's give it a try (with the fast cards first and then let the crappy 4GB card run the next hours). Surprisingly my Phoronix style 'benchmark' already finished (time in seconds below): Good Average Crap F2FS EXT4 F2FS EXT4 F2FS EXT4 apt purge linux-headers 17 7 21 9 35 10 apt install linux-headers 37 119 196 165 205 289 I simply ran the two above calls to deinstall linux-header package and to reinstall it later (no idea whether that relates to the usual real-world scenario with Armbian where most likely the kernel headers get updated instead). The duration in seconds results from looking at /var/log/dpkg.log and doing the math dividing 'startup packages configure' entry from 'startup packages purge'/'startup archives unpack' entries (no idea whether that's correct). It should be noted that 3 runs were done with a full OMV installation on SD card. After I re-imaged the SD cards the test ran against a fresh Armbian install (so numbers without meaning anyway). I also don't trust that much in the 37 seconds for 'apt install linux-headers' on the good SD card with F2FS -- most likely it's an error caused by me reading timestamps in dpkg.log wrong and it should be 60 seconds more (can't check any more since I've overwritten the SD card for the ext4 test). Anyway it's somewhat surprising to me that kernel header compilation was that fast even on my crappy SD card (maybe not crappy enough? Maybe that what usually happens -- an apt upgrade -- generates a totally different IO pattern?). But it's still obvious that good or average SD cards should be preferred and crappy ones should be avoided regardless of the FS used.

Exactly. And the focus of this comparison was trying to get a clue about average 'real world' Armbian scenarios and also the claim F2FS would outperform ext4 on slow storage. I was interested to use a limited set of tests to get a clue whether it's worth a look to investigate whether F2FS is an option for OS images we provide and even more how the SD card 'class' affects this all (good, average, crappy). For example booting times: I provided the 'debug logs' for a reason (to be able to spot mistakes I made and to search for further stuff in the logs). And if we do a search for two common strings in dmesg output we get the confirmation that booting times of this mainline OS image are neither affected by random nor sequential performance of the storage media used: dmesg|grep $string Good Average Crap F2FS EXT4 F2FS EXT4 F2FS EXT4 'Starting Various fixups' 12.19 12.32 12.88 12.09 12.32 12.19 'Mounted /tmp' 12.38 12.51 13.12 12.27 12.51 12.38 Another interesting test that reflects a real-world Armbian scenario would be installation of kernel headers. We already know that users running off really crappy SD cards report hours or even days for this to finish. But I don't know whether I would further waste my time producing numbers here since the results are already known (don't be stupid and simply use storage with fast random (write) IO and this is done in minutes) the approach is totally wrong. With passive benchmarking I could come back with numbers that show that the SanDisk Extreme Plus will finish this in 90 seconds while the crappy Class 4 card takes 20 hours. But instead we should focus on improving this (we already started with: a 10 minute timeout for header compilation and if this timeout is triggered we should add a permanent motd warning to the user that he should immediately replace his SD card since way too slow) For me the above tests are sufficient to draw the following conclusions already: due to lack of real advantages and two major disadvantages a consideration of switching to F2FS on any default OS image is not justified (yet) the 'storage performance' issue is more one of documentation and educating users than of choosing filesystems. Instead of encouraging users to try out crappy storage (the 'Class 4 SD card' they found somewhere in the drawer) we should improve in pointing out that choosing a good new SD card is the way to go

Yes, I know but I never think in F2FS as an option in GNU/Linux system and finding two benchmarks close in time I'm thinking in take a look to all this numbers.

From left to right: Good, average and crap. The numbers combined below: Good Average Crap F2FS EXT4 F2FS EXT4 F2FS EXT4 iozone 4K random write IOPS 746 764 208 196 38 33 iozone 4K random read IOPS 1616 1568 1806 1842 1454 1461 iozone 1MB sequential write KB/s 20354 21988 7161 10318 8644 9506 iozone 1MB sequential read KB/s 22474 22548 22429 22476 15638 14834 ioping k iops 1.57 1.55 1.42 1.31 1.06 1.19 fio write iops 311 399 128 132 31 28 fio read iops 934 1197 384 395 93 85 OMV installation time in sec 862 791 886 943 3729 1480 If I look at these numbers I immediately stop thinking about filesystems but start to focus on hardware instead. Obviously avoiding crappy cards and choosing good or at least average ones helps a lot with performance. Interestingly such a task like OMV installation that does a lot of disk IO is somewhat affected by storage (random) performance but not that much. Installation duration with good and average SD card are more or less the same. Then we should keep in mind when looking at sequential speeds that most if not all SBC currently are limited to ~23MB/s here anyway (ASUS Tinkerboard one of the rare exceptions). So it's useless to get a SD card rated for 90MB/s since it will be bottlenecked by the interface anyway. Still random IO performance seems to be the most interesting number to focus on and I would assume those cards showing best performance/price ratio are still Samsung's EVO/EVO+ with 32GB or 64GB (can't test right now since all Samsung I own are busy in installations). One final word regarding F2FS 'real-world' performance. This filesystem comes from an Android vendor and maybe situation with Android where apps constantly issue fsync calls is really different compared to ext4. But for our uses cases this doesn't matter that much (especially having in mind that Armbian ships with ext4 defaults that try to minimize writes to SD card -- for some details regarding this you might want to read through article and especially comments here: http://tech.scargill.net/a-question-of-lifespan/)

And in the meantime the crappy 4GB card was also able to finish the tests. Debug log for EXT4 and for F2FS. Full storage test logs for EXT4 and F2FS. F2FS EXT4 iozone 4K random write IOPS 38 33 iozone 4K random read IOPS 1454 1461 iozone 1MB sequential write KB/s 8644 9506 iozone 1MB sequential read KB/s 15638 14834 ioping k iops 1.06 1.19 fio write iops 31 28 fio read iops 93 85 OMV installation time in sec 3729 1480 Again no real performance difference. The only number that really varies is the OMV installation time. What does this mean? No idea but since I did the F2FS test after EXT4 we just might watch this crappy card dying

Phoronix as usual produces only numbers without meaning. If there's one thing to learn from that 'benchmark' then that stuff like 'Copy on Write' matters (he used btrfs defaults where CoW is enabled for a database test. Any administrator out there doing this would be fired immediately) and that default block sizes matter. Btrfs uses 4K (and in case files with less size get changed btrfs always has to read those 4K first and then write them back entirely) and F2FS at least in the past used 512 bytes (no idea which record size he used in his test, not telling this alone disqualifies the whole 'benchmark'). With such a setup he has (which is something completely different compared to our SBC situation as @jernejalready pointed out) there would be a lot of interesting stuff to test (eg. adjusting filesystem blocksizes so they match database record sizes or page and/or erase block sizes of the SSDs). But it's just the usual Phoronix clickbait throwing out some weird numbers in as less time as possible and in passive benchmarking mode. It's data but not information.

That article compares F2FS and BTRFS on multiple SSDs. Here is comparison between F2FS and EXT4 on single SD card. Apple and oranges.

I don't want to be polemic but the last Phoronix test shows a different figures related to F2FS http://www.phoronix.com/scan.php?page=article&item=btrfs-f2fs-multi&num=1