Search the Community

Showing results for 'f2fs'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
  • Community/Newbie forums
    • Board does not start
    • Off-topic
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • TV boxes
  • Hobbyists forums
    • P2P help
    • Feature Requests
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Board Bring Up
    • Armbian Project Administration
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. Since I've been asked recently why Armbian doesn't ship with F2FS by default I thought let's have a look again what to gain from F2FS (a filesystem specially designed for use with flash media by Samsung few years ago). For a history of F2FS discussion please use the search function: https://forum.armbian.com/index.php?/search/&q=f2fs Armbian fully supports F2FS partitions for a long time now but we don't provide OS images with F2FS for a couple of reasons: F2FS still doesn't support resizing so our default installation variant (ship with a minimized rootfs that gets resized on first boot automagically to the size of SD card / eMMC) wouldn't work F2FS requires a pretty recent kernel and is therefore not an option for default images (since most of downloads use legacy kernel) Unfortunately those installations that would benefit the most from faster random IO (writes) are those using the kernels most outdated (Allwinner A20/H3 who are used by many people as 'desktop linux' where performance heavily depends on fast random writes) To use F2FS with Armbian you need to choose a SoC family that is supported by mainline kernel (or at least 4.4 LTS) and then build an image yourself using these options (choosing $FIXED_IMAGE_SIZE to be less than the capacity of the final installation media!) ROOTFS_TYPE=f2fs FIXED_IMAGE_SIZE=n In the past I tested through this many times and all my tests didn't show that great performance improvements would justify another installation variant but... let's have a look again and focus on the claims first. F2FS has been invented to solve certain problems with flash based media and promises better performance and higher longevity. At least measuring the latter is somewhat questionable but performance can be tested. So I decided to pick 3 different SD cards that represent roughly the kind of flash media people out there use: Crap: An Intenso 4GB Class 4 SD card Average: A random SanDisk 8GB card Superiour: An expensive SanDisk Extreme Plus with 16GB For the tests I used an OrangePi One with kernel 4.10 and a Debian Jessie variant to be able to use a scripted OpenMediaVault installation as some sort of a real-world benchmark (the script is roughly based on the results of our OMV PoC). The other 3 benchmarks are our usual iozone3 call, then ioping and a mixed workload measured with fio. Test script is this: https://pastebin.com/pdex14L9 First results with an average SanDisk 8 GB card (debug output with F2FS and with EXT4): F2FS EXT4 iozone 4K random write IOPS 208 196 iozone 4K random read IOPS 1806 1842 iozone 1MB sequential write KB/s 7161 10318 iozone 1MB sequential read KB/s 22429 22476 ioping k iops 1.42 1.31 fio write iops 128 132 fio read iops 384 395 OMV installation time in sec 886 943 I consider benchmark numbers that vary by less than 10% as identical and then it's easy: ext4 outperforms F2FS since all results are identical but sequential reads are +40% faster with ext4. Test results in detail: F2FS and EXT4. I'm really not impressed by any differences -- only two things are interesting: faster sequential reads with ext4 but very low random IO write performance at 16K blocksize (that's something we noticed with a lot of SD cards already, see first post in 'SD card performance' thread). At the moment I'm not that impressed by performance gains (but that might change later when the crappy 4GB card has finished) and just want to point out that there are other criteria too for choosing a filesystem for systems that are running with a high potential for bit flips (due to users using crappy chargers, bad DRAM clock settings when not using Armbian and so on). Just to give an idea please read through the PDF link here: https://news.ycombinator.com/item?id=11469535 (ext4 more than 1,000 times more reliable than F2FS when running the AFL test against) BTW: mkfs.f2fs info at image creation time (no idea whether something could be 'tuned' here): Info: Debug level = 0 Info: Label = Info: Segments per section = 1 Info: Sections per zone = 1 Info: Trim is enabled Info: sector size = 512 Info: total sectors = 7649280 (3735 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with "Linux version 4.4.0-72-generic (buildd@lcy01-17) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017" Info: Discarding device Info: Discarded 7649280 sectors Info: Overprovision ratio = 3.300% Info: Overprovision segments = 126 (GC reserved = 68) Info: format successful
  2. My Rock Pi S logs a NULL pointer dereference in the ext4 module after running for 1 to 3 hours. Subsequently existing processes continue to run but it appears that new processes can't start (eg I can't ssh in). The filesystem is on a new Sandisk Ultra Plus microSD card. As a test, I remounted the root filesystem read/write and the board ran flawlessly for 10 hours. When I get time I will try rebuilding the image with the root filesystem on F2FS. Aug 31 09:31:27 rockpi-s kernel: [ 1944.993824] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Aug 31 09:31:27 rockpi-s kernel: [ 1944.994681] Mem abort info: Aug 31 09:31:27 rockpi-s kernel: [ 1944.994952] ESR = 0x96000004 Aug 31 09:31:27 rockpi-s kernel: [ 1944.995248] EC = 0x25: DABT (current EL), IL = 32 bits Aug 31 09:31:27 rockpi-s kernel: [ 1944.995732] SET = 0, FnV = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996020] EA = 0, S1PTW = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996313] Data abort info: Aug 31 09:31:27 rockpi-s kernel: [ 1944.996587] ISV = 0, ISS = 0x00000004 Aug 31 09:31:27 rockpi-s kernel: [ 1944.996943] CM = 0, WnR = 0 Aug 31 09:31:27 rockpi-s kernel: [ 1944.997230] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000003851000 Aug 31 09:31:27 rockpi-s kernel: [ 1944.997813] [00000000000000f8] pgd=0000000000000000, p4d=0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1944.998587] Internal error: Oops: 96000004 [#1] PREEMPT SMP Aug 31 09:31:27 rockpi-s kernel: [ 1944.999104] Modules linked in: rfkill snd_soc_rk3308 snd_soc_core snd_pcm_dmaengine snd_pcm cdc_acm snd_timer snd soundcore cpufreq_dt zr am ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs Aug 31 09:31:27 rockpi-s kernel: [ 1945.001035] CPU: 3 PID: 213 Comm: kworker/u8:3 Not tainted 5.10.60-rockchip64 #21.08.1 Aug 31 09:31:27 rockpi-s kernel: [ 1945.001746] Hardware name: Radxa ROCK Pi S (DT) Aug 31 09:31:27 rockpi-s kernel: [ 1945.002197] Workqueue: writeback wb_workfn (flush-179:0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.003074] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--) Aug 31 09:31:27 rockpi-s kernel: [ 1945.004117] pc : clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.005032] lr : clear_page_dirty_for_io+0x18/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.005936] sp : ffff8000123db730 Aug 31 09:31:27 rockpi-s kernel: [ 1945.006875] x29: ffff8000123db730 x28: ffff8000123db9a0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.007607] x27: 00000000000021f9 x26: 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.009006] x25: 000000000008c1f9 x24: 000000000000000c Aug 31 09:31:27 rockpi-s kernel: [ 1945.009951] x23: fffffe00003c7340 x22: ffff0000066b5400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.010761] x21: ffff8000123db870 x20: fffffe00003c7340 Aug 31 09:31:27 rockpi-s kernel: [ 1945.012020] x19: fffffe00003c7340 x18: 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.012965] x17: 0000000000000000 x16: ffff000002259110 Aug 31 09:31:27 rockpi-s kernel: [ 1945.014196] x15: 0000000000000001 x14: 0000000000000002 Aug 31 09:31:27 rockpi-s kernel: [ 1945.014706] x13: 0000000000005966 x12: 000000000000000b Aug 31 09:31:27 rockpi-s kernel: [ 1945.015216] x11: 0000000000000000 x10: ffff000006804540 Aug 31 09:31:27 rockpi-s kernel: [ 1945.015724] x9 : 0000000000000001 x8 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.016230] x7 : 00000000001f9000 x6 : fffffe00003c7300 Aug 31 09:31:27 rockpi-s kernel: [ 1945.016751] x5 : 00000000171cc000 x4 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.017258] x3 : 00000000000021f8 x2 : ffff0000004df800 Aug 31 09:31:27 rockpi-s kernel: [ 1945.017779] x1 : 0000000000000000 x0 : ffff0000036799d8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.018291] Call trace: Aug 31 09:31:27 rockpi-s kernel: [ 1945.018544] clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.018998] mpage_submit_page+0x30/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.019379] mpage_map_and_submit_buffers+0x168/0x2a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.019856] ext4_writepages+0x748/0xc38 Aug 31 09:31:27 rockpi-s kernel: [ 1945.020236] do_writepages+0x58/0x100 Aug 31 09:31:27 rockpi-s kernel: [ 1945.020598] __writeback_single_inode+0x44/0x508 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021037] writeback_sb_inodes+0x1e0/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021460] __writeback_inodes_wb+0x78/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.021865] wb_writeback+0x26c/0x400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022218] wb_workfn+0x310/0x5f8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022549] process_one_work+0x1ec/0x4d0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.022935] worker_thread+0x48/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023287] kthread+0x140/0x150 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023605] ret_from_fork+0x10/0x34 Aug 31 09:31:27 rockpi-s kernel: [ 1945.023962] Code: b000b402 f9401401 f9474042 eb02003f (54000de0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.024526] ---[ end trace cdc066846165d221 ]--- Aug 31 09:31:27 rockpi-s kernel: [ 1945.025183] ------------[ cut here ]------------ Aug 31 09:31:27 rockpi-s kernel: [ 1945.025659] WARNING: CPU: 3 PID: 213 at kernel/exit.c:725 do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.026307] Modules linked in: rfkill snd_soc_rk3308 snd_soc_core snd_pcm_dmaengine snd_pcm cdc_acm snd_timer snd soundcore cpufreq_dt zram ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs Aug 31 09:31:27 rockpi-s kernel: [ 1945.028231] CPU: 3 PID: 213 Comm: kworker/u8:3 Tainted: G D 5.10.60-rockchip64 #21.08.1 Aug 31 09:31:27 rockpi-s kernel: [ 1945.029079] Hardware name: Radxa ROCK Pi S (DT) Aug 31 09:31:27 rockpi-s kernel: [ 1945.029525] Workqueue: writeback wb_workfn (flush-179:0) Aug 31 09:31:27 rockpi-s kernel: [ 1945.030047] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--) Aug 31 09:31:27 rockpi-s kernel: [ 1945.030612] pc : do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.030956] lr : die+0x208/0x248 Aug 31 09:31:27 rockpi-s kernel: [ 1945.031260] sp : ffff8000123db380 Aug 31 09:31:27 rockpi-s kernel: [ 1945.031576] x29: ffff8000123db380 x28: ffff0000029fe580 Aug 31 09:31:27 rockpi-s kernel: [ 1945.032086] x27: 00000000000021f9 x26: 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.032594] x25: ffff80001023b328 x24: 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.033100] x23: ffff8000123db497 x22: ffff800011270260 Aug 31 09:31:27 rockpi-s kernel: [ 1945.033605] x21: 000000000000000b x20: ffff8000118b9948 Aug 31 09:31:27 rockpi-s kernel: [ 1945.034112] x19: ffff0000029fe580 x18: 0000000000000010 Aug 31 09:31:27 rockpi-s kernel: [ 1945.034617] x17: 0000000000000000 x16: ffff000002259110 Aug 31 09:31:27 rockpi-s kernel: [ 1945.035128] x15: 00000000000001b7 x14: ffff8000123db0c0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.035643] x13: 00000000ffffffea x12: ffff80001194ee98 Aug 31 09:31:27 rockpi-s kernel: [ 1945.036152] x11: 0000000000000003 x10: ffff800011936e58 Aug 31 09:31:27 rockpi-s kernel: [ 1945.036660] x9 : ffff800011936eb0 x8 : 0000000000017fe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.037167] x7 : c0000000ffffefff x6 : 0000000000000001 Aug 31 09:31:27 rockpi-s kernel: [ 1945.037689] x5 : 0000000000000001 x4 : 0000000000000000 Aug 31 09:31:27 rockpi-s kernel: [ 1945.038200] x3 : 0000000000000000 x2 : ffff8000118b9948 Aug 31 09:31:27 rockpi-s kernel: [ 1945.038707] x1 : ffff8000123dbc90 x0 : ffff00001d6b8c88 Aug 31 09:31:27 rockpi-s kernel: [ 1945.039216] Call trace: Aug 31 09:31:27 rockpi-s kernel: [ 1945.039471] do_exit+0x44/0xab8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.039783] die+0x208/0x248 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040070] die_kernel_fault+0x64/0x78 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040441] __do_kernel_fault+0x74/0x148 Aug 31 09:31:27 rockpi-s kernel: [ 1945.040826] do_page_fault+0x1c8/0x3a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041206] do_translation_fault+0x50/0x60 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041605] do_mem_abort+0x40/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.041944] el1_abort+0x48/0x70 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042263] el1_sync_handler+0x64/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042625] el1_sync+0x84/0x140 Aug 31 09:31:27 rockpi-s kernel: [ 1945.042942] clear_page_dirty_for_io+0x38/0x278 Aug 31 09:31:27 rockpi-s kernel: [ 1945.043374] mpage_submit_page+0x30/0xa0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.043753] mpage_map_and_submit_buffers+0x168/0x2a8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044225] ext4_writepages+0x748/0xc38 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044601] do_writepages+0x58/0x100 Aug 31 09:31:27 rockpi-s kernel: [ 1945.044960] __writeback_single_inode+0x44/0x508 Aug 31 09:31:27 rockpi-s kernel: [ 1945.045398] writeback_sb_inodes+0x1e0/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.045804] __writeback_inodes_wb+0x78/0xe8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046209] wb_writeback+0x26c/0x400 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046563] wb_workfn+0x310/0x5f8 Aug 31 09:31:27 rockpi-s kernel: [ 1945.046897] process_one_work+0x1ec/0x4d0 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047296] worker_thread+0x48/0x478 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047648] kthread+0x140/0x150 Aug 31 09:31:27 rockpi-s kernel: [ 1945.047963] ret_from_fork+0x10/0x34 Aug 31 09:31:27 rockpi-s kernel: [ 1945.048302] ---[ end trace cdc066846165d222 ]---
  3. Hello, i've preordered an Helios64 and would like to install the main os on a f2fs formatted sd-card. your documentation says that this is not possible, and i would love to see this possibility. i guess most eMMC devices would also benefit
  4. I make apt full-upgrade after apt-update, but many - many errors: ip not found & ignore for packets. Make apt-get autoclean, but nothing... apt-get autoclean Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово apt full-upgrade Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Расчёт обновлений… Готово Следующие пакеты устанавливались автоматически и больше не требуются: libdrm-freedreno1 libf2fs0 libllvm6.0 Для их удаления используйте «apt autoremove». Следующие НОВЫЕ пакеты будут установлены: android-libboringssl android-libcrypto-utils libf2fs-format4 libf2fs5 libllvm8 libmaxminddb0 libwayland-egl1 python3-netifaces Следующие пакеты будут обновлены: adb android-libadb android-libbase android-libcutils android-libf2fs-utils android-liblog apt apt-transport-https apt-utils armbian-config curl f2fs-tools firefox firefox-locale-ru hostapd htop libapt-inst2.0 libapt-pkg5.0 libarchive13 libcogl20 libcurl3-gnutls libcurl4 libgl1-mesa-dri libgtk-3-0 libnss-myhostname libnss-systemd libpam-systemd libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-minimal libpython3.6-stdlib libsdl2-2.0-0 libsoup-gnome2.4-1 libsoup2.4-1 libsystemd0 libudev1 libwayland-egl1-mesa linux-libc-dev netplan.io python2.7 python2.7-minimal python3.6 python3.6-minimal systemd systemd-sysv udev wireshark-common wireshark-qt Обновлено 50 пакетов, установлено 8 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено. Необходимо скачать 83,2 MB/87,1 MB архивов. После данной операции объём занятого дискового пространства возрастёт на 127 MB. Хотите продолжить? [Д/н] y Игн:1 http://ports.ubuntu.com bionic-security/main armhf libnss-systemd armhf 237-3ubuntu10.29 Игн:2 http://ports.ubuntu.com bionic-security/main armhf libsystemd0 armhf 237-3ubuntu10.29 Игн:3 http://ports.ubuntu.com bionic-security/main armhf libnss-myhostname armhf 237-3ubuntu10.29 Игн:4 http://ports.ubuntu.com bionic-security/main armhf libpam-systemd armhf 237-3ubuntu10.29 Игн:5 http://ports.ubuntu.com bionic-security/main armhf systemd armhf 237-3ubuntu10.29 Игн:6 http://ports.ubuntu.com bionic-security/main armhf udev armhf 237-3ubuntu10.29 Игн:7 http://ports.ubuntu.com bionic-security/main armhf libudev1 armhf 237-3ubuntu10.29 Игн:8 http://ports.ubuntu.com bionic-security/main armhf systemd-sysv armhf 237-3ubuntu10.29 Ошб:9 http://ports.ubuntu.com bionic-updates/main armhf libapt-pkg5.0 armhf 1.6.12 404 Not Found [IP: 91.189.88.152 80] Ошб:10 http://ports.ubuntu.com bionic-updates/main armhf libapt-inst2.0 armhf 1.6.12 404 Not Found [IP: 91.189.88.152 80] Ошб:11 http://ports.ubuntu.com bionic-updates/main armhf apt armhf 1.6.12 404 Not Found [IP: 91.189.88.152 80] Ошб:12 http://ports.ubuntu.com bionic-updates/main armhf apt-utils armhf 1.6.12 404 Not Found [IP: 91.189.88.152 80] Игн:13 http://ports.ubuntu.com bionic-security/main armhf libpython3.6 armhf 3.6.8-1~18.04.2 Игн:14 http://ports.ubuntu.com bionic-security/main armhf python3.6 armhf 3.6.8-1~18.04.2 Игн:15 http://ports.ubuntu.com bionic-security/main armhf libpython3.6-stdlib armhf 3.6.8-1~18.04.2 Игн:16 http://ports.ubuntu.com bionic-security/main armhf python3.6-minimal armhf 3.6.8-1~18.04.2 Игн:17 http://ports.ubuntu.com bionic-security/main armhf libpython3.6-minimal armhf 3.6.8-1~18.04.2 Игн:18 http://ports.ubuntu.com bionic-security/main armhf libpython2.7 armhf 2.7.15-4ubuntu4~18.04.1 Игн:19 http://ports.ubuntu.com bionic-security/main armhf python2.7 armhf 2.7.15-4ubuntu4~18.04.1 Игн:20 http://ports.ubuntu.com bionic-security/main armhf libpython2.7-stdlib armhf 2.7.15-4ubuntu4~18.04.1 Игн:21 http://ports.ubuntu.com bionic-security/main armhf python2.7-minimal armhf 2.7.15-4ubuntu4~18.04.1 Игн:22 http://ports.ubuntu.com bionic-security/main armhf libpython2.7-minimal armhf 2.7.15-4ubuntu4~18.04.1 Ошб:23 http://ports.ubuntu.com bionic-updates/main armhf netplan.io armhf 0.97-0ubuntu1~18.04.1 404 Not Found [IP: 91.189.88.152 80] .............................................................. E: Не удалось получить http://ports.ubuntu.com/pool/universe/w/wireshark/wireshark-qt_2.6.8-1~ubuntu18.04.0_armhf.deb 404 Not Found [IP: 91.189.88.152 80] E: Не удалось получить некоторые архивы; возможно, нужно запустить apt-get update или попытаться повторить запуск с ключом --fix-missing? armbianmonitor -u ### Installed packages: ii armbian-config 5.95 all Armbian configuration utility ii armbian-tools-bionic 5.75 armhf Armbian tools, Cubie bt utils ii hostapd 3:2.7-99~armbian5.86+1 armhf IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator ii linux-base 4.5ubuntu1 all Linux image base package ii linux-bionic-root-next-orangepiplus2e 5.90 armhf Armbian tweaks for bionic on orangepiplus2e (next branch) ii linux-dtb-next-sunxi 5.92 armhf Linux DTB, version 4.19.62-sunxi ii linux-image-next-sunxi 5.92 armhf Linux kernel, version 4.19.62-sunxi ii linux-libc-dev:armhf 4.15.0-60.67 armhf Linux Kernel Headers for development ii linux-u-boot-orangepiplus2e-next 5.90 armhf Uboot loader 2019.04 ii sunxi-tools 1.4.2-2~armbian5.86+1 armhf tools for working with Allwinner (sunxi) ARM processors
  5. @tkaiser could you rerun the ext4 vs. f2fs tests with the latest version of Armbian? Perhaps somebody can offer f2fs image builds so many people can test it, as is being done for https://github.com/RPi-Distro/pi-gen/issues/471#issuecomment-732223791
  6. After checking, /var/log/armbian-hardware-monitor.log I detected btrfs did not exist in my build. I went back to lib/configuration.sh and saw btrfs-progs package was not installed if BUILD_MINIMAL = YES. if [[ "$BUILD_MINIMAL" != "yes" ]]; then # Essential packages PACKAGE_LIST="$PACKAGE_LIST bridge-utils build-essential fbset \ iw wpasupplicant sudo linux-base crda \ wireless-regdb unattended-upgrades \ console-setup unicode-data initramfs-tools \ ca-certificates expect iptables automake html2text \ bison flex libwrap0-dev libssl-dev libnl-3-dev libnl-genl-3-dev keyboard-configuration" # Non-essential packages PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL alsa-utils btrfs-progs dosfstools iotop stress screen \ ntfs-3g vim pciutils evtest pv libfuse2 libdigest-sha-perl \ libproc-processtable-perl aptitude dnsutils f3 haveged hdparm rfkill vlan bash-completion \ hostapd git ethtool unzip ifenslave libpam-systemd iperf3 \ software-properties-common libnss-myhostname f2fs-tools avahi-autoipd iputils-arping qrencode sunxi-tools" fi I changed then this from PACKAGE_LIST="bc cpufrequtils device-tree-compiler fping fake-hwclock psmisc chrony parted dialog \ ncurses-term sysfsutils toilet figlet u-boot-tools usbutils openssh-server \ nocache debconf-utils python3-apt" to PACKAGE_LIST="bc btrfs-progs cpufrequtils device-tree-compiler fping fake-hwclock psmisc chrony parted dialog \ ncurses-term sysfsutils toilet figlet u-boot-tools usbutils openssh-server \ nocache debconf-utils python3-apt" And now it works. I suppose btrfs-progs needs to be added to PACKAGE_LIST (or DEBOOTSTRAP_LIST?) only in the case ROOTFS_TYPE=btrfs and irrespectively of BUILD_MINIMAL.
  7. Focal / root on eMMC / ZFS on hdd / LXD / Docker I received my Helios64 yesterday, installed the system, and decided to write down my steps before I forget them. Maybe someone will be interested. :-) Preparation: Assembly your box as described here. Download Armbian Focal image from here and flash it to SD card. You may use Ether. Insert the SD card to your Helios64 and boot. After 15-20s the box should be accessible via ssh. (Of course you have to find out it's IP address somehow. For example check your router logs or use this.) First login: ssh root@IP Password: 1234 After prompt - change password and create your daily user. You should never login as root again. Just use sudo in the future. :-) Note: The auto-generated user is member of "disk" group. I do not like it. You may remove it so: "gpasswd -d user disk". Now move your system to eMMC: apt update apt upgrade armbian-config # Go to: System -> Install -> Install to/update boot loader -> Install/Update the bootloader on SD/eMMC -> Boot from eMMC / system on eMMC You can choose root filesystem. I have chosen ext4. Possibly f2fs might be a better idea, but I have not tested it. When finished - power off, eject the sd card, power on. Your system should now boot from eMMC. If you want to change network configuration (for example set static IP) use this: "sudo nmtui". You should also change the hostname: sudo armbian-config # Go to: Personal -> Hostname ZFS on hard disk: sudo armbian-config # Go to Software and install headers. sudo apt install zfs-dkms zfsutils-linux # Optional: sudo apt install zfs-auto-snapshot # reboot Prepare necessary partitions - for example using fdisk or gdisk. Create your zfs pool. More or less this way: sudo zpool create -o ashift=12 -m /mypool -mypool mirror /dev/disk/by-partuuid/abc123 /dev/disk/by-partuuid/xyz789 Reboot and make sure the pool is imported automatically. (For example by typing "zpool status".) You should now have working system with root on eMMC and ZFS pool on HDD. Docker with ZFS: Prepare the filesystem: sudo zfs create -o mountpoint=/var/lib/docker mypool/docker-root sudo zfs create -o mountpoint=/var/lib/docker/volumes mypool/docker-volumes sudo chmod 700 /var/lib/docker/volumes # Option: If you use zfs-auto-snapshot, you might want to consider this: sudo zfs set com.sun:auto-snapshot=false mypool/docker-root sudo zfs set com.sun:auto-snapshot=true mypool/docker-volumes Create /etc/docker/daemon.json with the following content: { "storage-driver": "zfs" } Add /etc/apt/sources.list.d/docker.list with the following content: deb [arch=arm64] https://download.docker.com/linux/ubuntu focal stable # deb-src [arch=arm64] https://download.docker.com/linux/ubuntu focal stable Install Docker: sudo apt install apt-transport-https ca-certificates curl gnupg-agent software-properties-common curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add - sudo apt update sudo apt install docker-ce docker-ce-cli containerd.io #You might want this: sudo usermod -aG docker your-user Voila! Your Docker should be ready! Test it: "docker run hello-world". Option: Install Portainer: sudo zfs create rpool/docker-volumes/portainer_data # You might omit the above line if you do not want to have separate dataset for the docker volume (bad idea). docker volume create portainer_data docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce Go to http://yourip:9000 and configure. LXD with ZFS: sudo zfs create -o mountpoint=none mypool/lxd-pool sudo apt install lxd sudo lxc init # Configure ZFS this way: Do you want to configure a new storage pool (yes/no) [default=yes]? yes Name of the new storage pool [default=default]: Name of the storage backend to use (dir, btrfs, ceph, lvm, zfs) [default=zfs]: zfs Create a new ZFS pool (yes/no) [default=yes]? no Name of the existing ZFS pool or dataset: mypool/lxd-pool [...] #You might want this: sudo usermod -aG lxd your-user # Option: If you use zfs-auto-snapshot, you might want to consider this: sudo zfs set com.sun:auto-snapshot=false mypool/lxd-pool sudo zfs set com.sun:auto-snapshot=true mypool/lxd-pool/containers sudo zfs set com.sun:auto-snapshot=true mypool/lxd-pool/custom sudo zfs set com.sun:auto-snapshot=true mypool/lxd-pool/virtual-machines That's it. Lxd should work now on ZFS. :-)
  8. If you, like myself, installed on eMMC and are experiencing the crashes on 20.08.14 - I booted up via a 20.08.10 sdcard and fixed the environment on emmc # mount the emmc + get ready to chroot mkdir /mnt/chroot mount /dev/mmcblk1p2 /mnt/chroot/ mount /dev/mmcblk1p1 /mnt/chroot/media/mmcboot mount --bind /mnt/chroot/media/mmcboot/boot/ /mnt/chroot/boot/ mount --bind /dev /mnt/chroot/dev/ mount --bind /proc /mnt/chroot/proc/ mount --bind /tmp /mnt/chroot/tmp/ # chroot in and downgrade to 20.08.10 chroot /mnt/chroot/ /bin/bash apt install \ linux-dtb-current-rockchip64=20.08.10 \ linux-headers-current-rockchip64=20.08.10 \ linux-image-current-rockchip64=20.08.10 \ armbian-config=20.08.10 \ armbian-firmware=20.08.10 \ linux-focal-root-current-helios64=20.08.10 \ linux-u-boot-helios64-current=20.08.10 exit # now remove the sd card and hit reset @aprayoga It's probably unrelated, but while working through the above I noticed that I ran out of space on /boot. I installed to eMMC the first version that was working, if that helps. I chose f2fs when I installed on eMMAC and this is the resulting partition layout mmcblk1 179:32 0 14.6G 0 disk ├─mmcblk1p1 179:33 0 96M 0 part └─mmcblk1p2 179:34 0 14.3G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk Sadly I didn't grab enough info from what was in the boot partition before I nuked it and reinstalled the appropriate packages.
  9. only through a fresh install? i would have preferred f2fs. for flash memory it has a way better durability. anyway... thank you. i wont write much there anyway - all data is in docker volumes on hdd
  10. @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!
  11. @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.
  12. Sorry for a newbie question. I am setting up a raid system based on flash drives on a Orange Pi One and every thing is working fine. I am now thinking of moving from ext4 for F2FS but I can't figure out how to get it to work. I have installed f2fs-tools and managed to format the drive but I can't seem to mount it. I can't seem to run "modprobe f2fs". Does this mean that I need to recombile the kernel or what? I am not intending to boot from f2fs. Just mount the raid system for storage.
  13. What to do to switch from ext4 to F2FS (one big caveat: Partition/filesystem resizing doesn't work with F2FS so this is only for you if you know the size of your SD card prior to building the image)? I tried the following so far: apt-get install f2fs-tools define size of f2fs partition in compile.sh (eg. for a 4 GB SD card use »SDSIZE="3600"«) adjust »BOOTSIZE=16« in lib/configuration.sh (line 26) replace »mkfs.vfat -n "$IMAGEVOLUME"« with »mkfs.ext4 -q« in lib/deboostrap.sh (line 66) replace »mkfs.ext4 -q« with »mkfs.f2fs« in lib/deboostrap.sh (line 67) add »-tf2fs« to mount option in lib/deboostrap.sh (line 68) comment »shrinking_raw_image "$DEST/output/$VERSION.raw"« out in lib/common.sh (line 463) change fstab entry to »echo "/dev/mmcblk0p2 / f2fs defaults,noatime,nodiratime,errors=remount-ro 0 0" >> $DEST/output/sdcard/etc/fstab« in lib/distributions.sh (line 105) comment »install -m 755 $SRC/lib/scripts/resize2fs $DEST/output/rootfs/$CHOOSEN_ROOTFS/etc/init.d« out in lib/distributions.sh (line 138) avoid partition resizing on first run by removing lines 89-101 in lib/scripts/firstrun But the Banana Pro I test with doesn't boot. I would assume that I have to modify boot.cmd (and exchange /boot/ with /)? Thx
  14. 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
  15. Hi, just a question to be discussed: Would it... 1. ...be possible to use F2FS as default filesystem for images using the vanilla kernel? 2. ...make sense to use it? benchmarks show that write operations could get a huge boost in comparison to ext4. i believe write operations are quite slow right now (using cubietruck with sd-card) What do you think?
  16. 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.
  17. 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
  18. @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.
  19. 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.
  20. 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
  21. 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...
  22. 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).
  23. 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).
  24. 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
  25. 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