sovking

This system is working 24h/7/365 with installed quite a lot of daemon needed for automation system, that works and log to sd: the load is usually between 2 and 3. The power supply is the original power supply provided with OrangePI. Now I don't remember the SD card brand & model, usually I use premium ones because these systems are installed in remote locations. However I ran armbianmonitor -C on both partition of SD card (the first one is the system and the second one is for data and local automation programs). These are the results: orangepipc:~$ armbianmonitor -C /mnt/ Starting to fill /dev/mmcblk0p1 with test patterns, please be patient this might take a very long time Free space: 2.08 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Free space: 48.91 MB Average writing speed: 1.67 MB/s Now verifying the written data: SECTORS ok/corrupted/changed/overwritten Validating file 1.h2w ... 2097152/ 0/ 0/ 0 Validating file 2.h2w ... 2097152/ 0/ 0/ 0 Validating file 3.h2w ... 73624/ 0/ 0/ 0 Data OK: 2.04 GB (4267928 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 19.74 MB/s Starting iozone tests. Be patient, this can take a very long time to complete: Iozone: Performance Test of File I/O Version $Revision: 3.429 $ Compiled for 32 bit mode. Build: linux Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner, Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone, Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root, Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer, Vangel Bojaxhi, Ben England, Vikentsi Lapa. Run began: Tue Sep 25 19:52:39 2018 Include fsync in write timing O_DIRECT feature enabled Auto Mode File size set to 102400 kB Record Size 4 kB Record Size 512 kB Record Size 16384 kB Command line used: iozone -e -I -a -s 100M -r 4k -r 512k -r 16M -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 1402 1812 6524 6962 6876 531 102400 512 8538 8357 15965 20754 20937 885 102400 16384 6792 4577 18907 22626 22657 5715 iozone test complete. The results from testing /dev/mmcblk0p1 (ext4): Data LOST: 0.00 Byte (0 sectors) Average writing speed: 1.67 MB/s Average reading speed: 19.74 MB/s Data OK: 2.04 GB (4267928 sectors) random random reclen write rewrite read reread read write 4 1402 1812 6524 6962 6876 531 512 8538 8357 15965 20754 20937 885 16384 6792 4577 18907 22626 22657 5715 Health summary: OK Performance summary: Sequential reading speed: 19.74 MB/s 4K random reading speed: 6876 KB/s Sequential writing speed: 1.67 MB/s (way too low) 4K random writing speed: 531 KB/s (too low) The device you tested seems to perform too slow to be used with Armbian. This applies especially to desktop images where slow storage is responsible for sluggish behaviour. If you want to have fun with your device do NOT use this media to put the OS image or the user homedirs on. orangepipc:~$ armbianmonitor -C /home/ Starting to fill /dev/mmcblk0p2 with test patterns, please be patient this might take a very long time Free space: 956.04 MB Creating file 1.h2w ... OK! Free space: 174.16 MB Average writing speed: 2.07 MB/s Now verifying the written data: SECTORS ok/corrupted/changed/overwritten Validating file 1.h2w ... 1601272/ 0/ 0/ 0 Data OK: 781.87 MB (1601272 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 18.41 MB/s Starting iozone tests. Be patient, this can take a very long time to complete: Iozone: Performance Test of File I/O Version $Revision: 3.429 $ Compiled for 32 bit mode. Build: linux Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner, Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone, Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root, Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer, Vangel Bojaxhi, Ben England, Vikentsi Lapa. Run began: Tue Sep 25 19:10:09 2018 Include fsync in write timing O_DIRECT feature enabled Auto Mode File size set to 102400 kB Record Size 4 kB Record Size 512 kB Record Size 16384 kB Command line used: iozone -e -I -a -s 100M -r 4k -r 512k -r 16M -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 1152 1333 6787 6787 6085 407 102400 512 3787 2493 18622 20376 20797 1145 102400 16384 3553 2476 19991 14727 18804 2787 iozone test complete. The results from testing /dev/mmcblk0p2 (ext4): Data LOST: 0.00 Byte (0 sectors) Average writing speed: 2.07 MB/s Average reading speed: 18.41 MB/s Data OK: 781.87 MB (1601272 sectors) random random reclen write rewrite read reread read write 4 1152 1333 6787 6787 6085 407 512 3787 2493 18622 20376 20797 1145 16384 3553 2476 19991 14727 18804 2787 Health summary: OK Performance summary: Sequential reading speed: 18.41 MB/s 4K random reading speed: 6085 KB/s Sequential writing speed: 2.07 MB/s (way too low) 4K random writing speed: 407 KB/s (too low) The device you tested seems to perform too slow to be used with Armbian. This applies especially to desktop images where slow storage is responsible for sluggish behaviour. If you want to have fun with your device do NOT use this media to put the OS image or the user homedirs on. Then h3consumption settings are quite conservative as you can see: root@orangepipc:~# h3consumption -p Active settings: cpu 912 mhz allowed, 1200 mhz possible, 4 cores active dram 624 mhz hdmi/gpu off usb ports active eth0 100Mb/s/Full, Link: yes Because the system is remote, swapping card and other manual intervation takes a lot of time (at least 1 day) and money; if there is not another major problem: the system can run even in this state. If a blocking problem arise I'll bring there a complete new system (board, sd, psu) and I'll investigate later at home. However I would like to check if there is anything I can do, safely, from remote. I'm quite skeptical about sd card or psu problem because the system is quite loaded and probably it shoud show these problem during other activities too, and not only during polkit upgrade. There is any way to diagnose what force a reboot during such operation ? Another doubt I have is on that system there are configured both systemd watchdog and the usual software watchdog: I don't know if they can interfere one with the other.

Hi, some times ago I installed an Orange PI with armbian-5.31 (stable, kernel 3.4.113). Now I needed to upgrade some installed packages, but when I run apt-get upgrade at some point the process interrupts and the system reboots. Now I have an interrupted upgrade process, and each time I try to restart this process with sudo dpkg --configure -a the system try to upgrade the policykit-1, it reboots. Looking at messages or syslog I don't find any particular error. Any suggestion where to look for this problem ? Watchdog process could be responsible for such reboots ? Thanks in advance for any suggestion

Thanks!.I'll take care that " such job is not recommended without access to console". Another question,according your esperience, it's worth continue using EMMC only ? Or I could put a good micro-SD (Samsung Evo or Sandisk Extreme) on Lime2, with a fresh installed system, leaving on EMMC my scripts, and maybe logs and collected data ? (in this case, I also can leave EMMC untouched in case something does not work / goes wrong).

Hi guys! I've an Olimex LIME2 EMMC installed in a remote location: I installed it with Olimex provided image of debian Jessie, which has kernel 3.4.103-00033-g9a1cd03-dirty. The installation has been done over internal EMMC and it worked. Now, for various reason I would like to switch to armbian. I would like to install armbian over the existing image. so not to have to reinstall packages ad my local software. I would like to keep the installation on internal 4GB EMMC memory. I'm asking if it's possibile to do it without having to reinstall and possibily over ssh, because the board is in remote location. Thanks for your suggestions.

Done! I removed armbian-firmware and the library was still there: good! Then I checked no update was pending before reboot. Now everithing work fine. I could be nice if in future when a new armbian package release can overwrite another package (fowrwhatever reason) report how to deal with this situation, if it cannot be resolved automatically: for example warning about different files revision, sizes, benefits, drawback and so on. Of course this could be done just per armbian packages which you can control and manage, for other packages I think could be too much work or not reasonable. Thank you very much for your help!

Probably I should ask this question in debian/ubuntu because is not specific to H3/H2 devices... Unfortunaly this board is in remote location and is connected trhough Wi-Fi, so if I make a mistake I will lost the connection

I experencing the following error upgrading orangePI-PC with connected a WiFi ralink key: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-firmware 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,617 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://apt.armbian.com/ jessie/main armbian-firmware armhf 5.25 [1,617 kB] Fetched 1,617 kB in 11s (138 kB/s) (Reading database ... 44676 files and directories currently installed.) Preparing to unpack .../armbian-firmware_5.25_armhf.deb ... Unpacking armbian-firmware (5.25) over (5.22) ... dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_5.25_armhf.deb (--unpack): trying to overwrite '/lib/firmware/rt2870.bin', which is also in package firmware-ralink 0.43 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/armbian-firmware_5.25_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Now my system is with: # dpkg-query -l | grep 5.25 ii armbian-tools-jessie 5.25 armhf Armbian tools, temper, Cubie bt utils ii hostapd 1:2.5~armbian5.25+1 armhf IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator ii linux-headers-sun8i 5.25 armhf Linux kernel headers for 3.4.113-sun8i on armhf ii linux-image-sun8i 5.25 armhf Linux kernel, version 3.4.113-sun8i ii linux-jessie-root-orangepipc 5.25 armhf Armbian tweaks for jessie on orangepipc (default branch) ii linux-u-boot-orangepipc-default 5.25 armhf Uboot loader 2017.01 ii sunxi-tools 1.4.2-1~armbian5.25+1 armhf tools for working with Allwinner (sunxi) ARM processors root@genka-h3:/# dpkg-query -l | grep 5.22 ii armbian-firmware 5.22 armhf Linux firmware dmesg stays that the device is: rt2800usb It will boot with this one packages which is still at 5.22 and the other at 5.25 ? And it will connect to wifi with the armbian-firmware not upgraded by firmware-ralink present ? Should I uninstall armbian-firwmare leaving firmware-ralink only ? Any suggestion to solve this ?

I join to the crew of people with stability issue with Orange Pi. Usually I need to place SBC in rural areas to monitor solar production: tipical equipment is a board connected to ethernet or wifi, and with attacched one or two usb-rs485 converters. They run some simple sampling software, a webserver and php. Tipically very low load, no performance required. Once I've used a meanwell 15-5 for power supply, some other tumes chepear alternative, 5V 2A psu. In any case, a powerbank in the middle or lithium battery are used as USP (For power bank my choice is Easyacc PB10000CF, which usually is capable to continusly power the board when there are power outages - it's not common among power banks). For SD card I use 16 GB Sandisk Extreme or Extreme Plus, nothing cheaper. Until now I've used raspberry and olimex A10 and A20. A single core A10 is enough for me, and they have the good AXP209 for multiple power management, it's own lithium battery... but sometimes can be little bit expensive, when configured with full optionals. So I'm tring H3 chips, and I started using Orange PI PC, with armbian 5.23 Jessie Server. And while in laboratory it seems work, when I place into the field, its maxium uptime is around 3 days. Probably the voltage supplied to the psu is very noisy and dirty, and the power outages can happen quite often even for few minutes, but it seem unreliable: it seems that it reboots, but sometimes, it hangs during boot. So I've to recall the unit back to the lab, and probably I will put another A10 into the field, until it can deal with different power condition. I'm triend to provide it good compnent around it, but it has to work flawlessy as A10-A20 do. I'm open to read any suggestion to improve the stability, and if something is wrong with my hardware setup, please, tell me.b

Found... the 3rd and 4th cable worked! Thanks!

not uboot... But kernel begin to load it shuold output , or I have to wait last phase, around login to see the prompt ? Regarding the stuff used: 1) monitor I used both a DELLU2410 and a mini 7" monitor, 2) two different HDMI cables (I can try other two different cables) 3) I did not read 720p default, I ve tried different modes using h3disp 4) I've used the supplied power supply at beginning, but now I'm using a powerbank connected to power: EasyAcc PB10000CF) that works well as UPS and should provide 2A (I've tried different ones, most of them are not able to switch without interruption/power loss). I could restore the original script.bin, maybe some settings was corrupter around hdmi: I found that using h3consumption if I descrease core, in some situation I'm not more able to restore the original 4 cores, because a setting remains in rc.local, and it's not deleted by h3consumption. Last question, the difference between desktop and server are only due to differents packages that provide X functionlity ?

I'm running an OrangePI PC with legacy Jessie server and armbian 5.23 and kernel 3.4.112. I never seen the ouput through the HDMI monitor. It's always without signal, even at boot when uboot start. Is that normal ? I played with h3disp, but it never work. I would like to see just the boot and the text console. Any suggestion ? Thanks

The origin of overtemperature was a big router were the board was sitting : it was heating the case and then the board. Now, in the proper place, the board closed into its plastic case with heatisink, everything enclosed into IP65 abs case run nice at 35-37 C, so just 15 degree over-ambient. In the summer it will be not exposed to direct sunlight, it will be in a ventilated container with other elettronic equipments... so I hope not more than 40 degree of ambient temperature . I'll monitor and I'll tell you how it will work

If I try echo 1 > /dev/watchdog after some second the machine reboot. Looking in /var/log/messages I see: Nov 17 16:17:09 localhost kernel: [ 3.249893] sunxi_wdt_init_module: sunxi WatchDog Timer Driver v1.0 Nov 17 16:17:09 localhost kernel: [ 3.259938] sunxi_wdt_probe: devm_ioremap return wdt_reg 0xf1c20ca0, res->start 0x01c20ca0, res->end 0x01c20cbf Nov 17 16:17:09 localhost kernel: [ 3.271394] sunxi_wdt_probe: initialized (g_timeout=16s, g_nowayout=0) Nov 17 16:17:09 localhost kernel: [ 3.284826] wdt_enable, write reg 0xf1c20cb8 val 0x00000000 Nov 17 16:17:09 localhost kernel: [ 3.294179] timeout_to_interv, line 167 Nov 17 16:17:09 localhost kernel: [ 3.301540] interv_to_timeout, line 189 Nov 17 16:17:09 localhost kernel: [ 3.308824] wdt_set_tmout, write 0x000000b0 to mode reg 0xf1c20cb8, actual timeout 16 sec It seems watchdog module... Isn't it ? Looking at /etc/default/watchdog # Start watchdog at boot time? 0 or 1 run_watchdog=1 # Start wd_keepalive after stopping watchdog? 0 or 1 run_wd_keepalive=1 # Load module before starting watchdog watchdog_module="none" # Specify additional watchdog options here (see manpage). (I've non manpages...) I tried even adding in that file: watchdog_options=" -F -v " without any results. I don't find any process watchdog except [watchdog], nor wd_keepalive. I'm running Armbian 5.23 (Legacy/default server). Any suggestion ?

armbianmonitor -m shows that my Orange PC temperature at idle was about 35 C when the board was open with ambient temperature of 20C. Then I added an heatsing with 3M strip attached that bought for another board but that perfectly fit on H3. Finally I put the board into the original clear case. Now armbianmonitor -m show temperature at idle around 47-50 C, so almost 30 degree over ambient, and about 15 degree more that when running open, without case and heatsing. Is normal this value inside that case ? I have to worry about it ? Take into account that the final destination will be into a container that in summer could reach 40-45 C. I should expect throttling in summer or worse ?

I've an OrangePI PC. I would like install, enable and start watchdog. I installed watchdog using apt-get install watchdog. But install seems to require some tweaks. I tried to googling but until now nothing works. Any hints ? Thanks!