All Activity

This stream auto-updates

  1. Today
  2. Whenever you are asking for help, hints or solutions to your problem - provide full logs, not just some small detail.
  3. Ok, thanks. I did not realize I was on stretch I did this: sudo sed -i 's|stretch|buster|g' /etc/apt/sources.list sudo sed -i 's|stretch|buster|g' /etc/apt/sources.list.d/armbian.list sudo sed -i 's|stretch|buster|g' /etc/apt/sources.list.d/nodesource.list sudo apt update && sudo apt -y upgrade && sudo apt -y dist-upgrade then rebooted and run the update again. sudo apt-get update && sudo apt-get full-upgrade sudo apt autoremove sudo apt autoclean Seems to work!
  4. Hi I have a problem with USB tethering on my Armbian device (Nanopi Neo). It has static IP assigned to eth0 and I connect to it via ssh from another computer. My /etc/network/interfaces file is: auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.170 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 192.168.0.1 When I connect android tethering device to the USB on Armbian and run ifconfig -a I get eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.170 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::f819:6eff:fe30:1a04 prefixlen 64 scopeid 0x20<link> ether fa:19:6e:30:1a:04 txqueuelen 1000 (Ethernet) RX packets 1930 bytes 168366 (164.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1895 bytes 247095 (241.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 38 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 140 bytes 14942 (14.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 140 bytes 14942 (14.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.182.135 netmask 255.255.255.0 broadcast 192.168.182.255 inet6 fe80::9c58:5c52:4522:6467 prefixlen 64 scopeid 0x20<link> ether 66:d5:8c:d4:03:e9 txqueuelen 1000 (Ethernet) RX packets 30 bytes 3021 (2.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 4580 (4.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 It discovers usb0 but it assigns 192.168.182.135 and I have no internet access. Probably my interface settings are wrong. I'll be grateful for any help.
  5. Now, that patch applied since main line kernel 5.12.17,you don't need patch no longer.
  6. Hi, running armbian debian Linux odroid-backup 4.14.222-odroidxu4 ; and having attached 2x 3.5" disks i am getting so many disconnects in dmesg log paste.debian.net/1205714/ Is that armbian / kernel / or odroid issue? So i can further investigate. thank you
  7. You need to install UTM rather than trying to run it from the disk image... UTM is a hypervisor.
  8. Werner is right that this probably should have gone in peer to peer support or general chat. This forum is for bug reports with supporting debug information (armbianmonitor). Maybe he'll move this for you. In the meantime, maybe this would be worth a read. https://forum.armbian.com/topic/17022-automatic-kernel-control-of-nanopi-m4-m4v2-metal-case-fan/
  9. apparently my searching skills are rubbish, found a thread with the FPDMA QUEUED fault, will investigate that, but seems thats a seperate isue to the reboot.
  10. Yesterday
  11. Thanks! I still couldn't get it to boot off 5.10 or 5.12 buster. Probably something I did. I tried I ended up trying a random armbian 4.14 buster image and it booted. I tried `apt update; apt upgrade;` `armbian-config -> Install/Update the bootloader on SD/eMMC`. But that hangs on "Loading, please wait..." too. Not sure.
  12. Hi all, been trying to sort out a stability problem with what was a rock solid helios64, i moved from running armbian on the eMMC to a 256GB sandisk extreme SD card due to plex continually filling it up. currently running Armbian 21.05.6 Buster with Linux 5.10.43-rockchip64, running OMV, Plex and ZFS not much more it appears this is where things go pear shaped: [ 6636.457621] ata1.00: exception Emask 0x2 SAct 0x3800000 SErr 0x1000400 action 0x6 [ 6636.458306] ata1.00: irq_stat 0x08000000 [ 6636.458659] ata1: SError: { Proto TrStaTrns } [ 6636.459051] ata1.00: failed command: READ FPDMA QUEUED [ 6636.459516] ata1.00: cmd 60/58:b8:e0:b3:73/05:00:01:00:00/40 tag 23 ncq dma 7 00416 in [ 6636.459516] res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) [ 6636.460898] ata1.00: status: { DRDY } [ 6636.461227] ata1.00: failed command: READ FPDMA QUEUED [ 6636.461743] ata1.00: cmd 60/40:c0:80:ae:73/05:00:01:00:00/40 tag 24 ncq dma 6 88128 in [ 6636.461743] res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) [ 6636.457621] ata1.00: exception Emask 0[ 6636.463130] ata1.00: status: { DRDY } x2 SAct 0x3800000 SErr 0x1000400 action 0x6 [ 6636.458[ 6636.463942] ata1.00: failed command: READ FPDMA QUEUED 306] ata1.00: irq_stat 0x08000000 [ [ 6636.464874] ata1.00: cmd 60/20:c8:c0:b3:73/00:00:01:00:00/40 tag 25 ncq dma 16384 in [ 6636.464874] res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) 6636.458659] ata1: SError: { Proto TrStaTrns }[ 6636.466733] ata1.00: status: { DRDY } [ 6636.459051] ata1.00: failed command: READ FPDMA QUEUED [ 6636.459516] ata1.00: cmd 60/58:b8:e0:b3:73/05:00:01:00:00/40 tag 23 ncq dma 7 00416 in res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) [ 6636.460898] ata1.00: status: { DRDY } [ 6636.461227] ata1.00: failed command: READ FPDMA QUEUED [ 6636.461743] ata1.00: cmd 60/40:c0:80:ae:73/05:00:01:00:00/40 tag 24 ncq dma 6 88128 in res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) [ 6636.463130] ata1.00: status: { DRDY } [ 6636.463942] ata1.00: failed command: READ FPDMA QUEUED [ 6636.464874] ata1.00: cmd 60/20:c8:c0:b3:73/00:00:01:00:00/40 tag 25 ncq dma 1 6384 in res 40/00:bc:e0:b3:73/00:00:01:00:00/40 Emask 0x2 (HSM v iolation) [ 6636.466733] ata1.00: status: { DRDY } [ 6636.467511] ata1: hard resetting link [ 6636.943205] blk_update_request: I/O error, dev sda, sector 24359904 op 0x0:(R EAD) flags 0x700 phys_seg 12 prio class 0 [ 6636.944176] zio pool=helios vdev=/dev/disk/by-id/ata-WDC_WD40PURX-64GVNY0_WD- WCC4E2LRTU90-part1 error=5 type=1 offset=12471222272 size=700416 flags=40080ca8 [ 6636.945526] blk_update_request: I/O error, dev sda, sector 24358528 op 0x0:(R EAD) flags 0x4700 phys_seg 168 prio class 0 [ 6636.941590] ata1: SATA link up 6.0 Gbps (SS[ 6636.946685] blk_update_request: I/O error, dev sda, sector 24359872 op 0x0:(READ) flags 0x700 phys_seg 4 prio c lass 0 tatus 133 SControl 300) [ 6636.942889] ata1.00 6636.947962] zio pool=helios vdev=/dev/disk/by-id/ata-WDC _WD40PURX-64GVNY0_WD-WCC4E2LRTU90-part1 error=5 type=1 offset=12470517760 size=7 04512 flags=40080ca8 m: configured for UDMA/133 [ 6636.943169] sd 0:0:0:0: [sda] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 dr iverbyte=0x08 cmd_age=5s [ 6636.943179] sd 0:0:0:0: [sda] tag#23 Sense Key : 0x5 [current] [ 6636.943186] sd 0:0:0:0: [sda] tag#23 ASC=0x21 ASCQ=0x4 [ 6636.943196] sd 0:0:0:0: [sda] tag#23 CDB: opcode=0x88 88 00 00 00 00 00 01 73 b3 e0 00 00 05 58 00 00 [ 6636.943205] blk_update_request: I/O error, dev sda, sector 24359904 op 0x0:(R EAD) flags 0x700 phys_seg 12 prio class 0 [ 6636.944176] zio pool=helios vdev=/dev/disk/by-id/ata-WDC_WD40PURX-64GVNY0_WD- WCC4E2LRTU90-part1 error=5 type=1 offset=12471222272 size=700416 flags=40080ca8 [ 6636.945496] sd 0:0:0:0: [sda] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 dr iverbyte=0x08 cmd_age=5s [ 6636.945504] sd 0:0:0:0: [sda] tag#24 Sense Key : 0x5 [current] [ 6636.945511] sd 0:0:0:0: [sda] tag#24 ASC=0x21 ASCQ=0x4 [ 6636.945518] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x88 88 00 00 00 00 00 01 73 ae 80 00 00 05 40 00 00 [ 6636.945526] blk_update_request: I/O error, dev sda, sector 24358528 op 0x0:(R EAD) flags 0x4700 phys_seg 168 prio class 0 [ 6636.946645] sd 0:0:0:0: [sda] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 dr iverbyte=0x08 cmd_age=5s [ 6636.946659] sd 0:0:0:0: [sda] tag#25 Sense Key : 0x5 [current] [ 6636.946666] sd 0:0:0:0: [sda] tag#25 ASC=0x21 ASCQ=0x4 [ 6636.946676] sd 0:0:0:0: [sda] tag#25 CDB: opcode=0x88 88 00 00 00 00 00 01 73 b3 c0 00 00 00 20 00 00 [ 6636.946685] blk_update_request: I/O error, dev sda, sector 24359872 op 0x0:(R EAD) flags 0x700 phys_seg 4 prio class 0 [ 6636.947962] zio pool=helios vdev=/dev/disk/by-id/ata-WDC_WD40PURX-64GVNY0_WD- WCC4E2LRTU90-part1 error=5 type=1 offset=12470517760 size=704512 flags=40080ca8 [ 6636.949804] ata1: EH complete DDR Version 1.24 20191016 In soft reset SRX channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 323 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=244016MB FwPartOffset=2000 , 0 StorageInit ok = 56917 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 hdr 0000000003380880 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x0 0,0x00,0x00,0x00,0x00,0x00, Load OK, addr=0x200000, size=0xe5b60 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE init ialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (May 06 2021 - 17:13:15 +0000) SoC: Rockchip rk3399 Reset cause: WDOG DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... Card did not respond to voltage select! *** Warning - No block device, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... cannot reset port 4!? 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** Card did not respond to voltage select! Device 0: Vendor: Seagate Rev: 070B Prod: Expansion Desk Type: Hard Disk Capacity: 2861588.4 MB = 2794.5 GB (732566645 x 4096) ... is now current device ** Unrecognized filesystem type ** scanning bus for devices... Device 0: unknown device Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.254 (3 ms) *** Warning: no boot file name; using 'C0A800FE.img' Using ethernet@fe300000 device TFTP from server 192.168.0.1; our IP address is 192.168.0.254 Filename 'C0A800FE.img'. Load address: 0x800800 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-64-62-66-d0-01-58 I've aready given i a bump in voltage as recommended in the config file but i cant tell where to check if it took the settting, frequency is set in armbian-config to ondemand. does anyone have any ideas? Thanks in advance Krita
  13. Our system only publish packages for supported distributions. Xenial is EOL from our maintaining perspective. We have to cut what is not important, but eats resources.
  14. It seems things are proceeding faster:
  15. Thanks @lanefu , I can mount UTM and see the Contents folder. However, the volume drive is mounted in read only mode, so that I can't copy u-boot.bin to the folder. /Volumes/UTM/UTM.app on /private/var/folders/ns/bkcwhmm106j0_scbdvv_x29c0000gn/T/AppTranslocation/7DABB818-AE48-4EBF-9012-FF45CF3B9602 (nullfs, local, nodev, nosuid, read-only, noowners, quarantine, nobrowse, mounted by User). How can I mount the folder with read-write?
  16. # smartctl -a /dev/sdb smartctl 6.6 2017-11-05 r4594 [aarch64-linux-5.10.35-rockchip64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: TOSHIBA HDWD240 Serial Number: Z9J1S0I9S5HH LU WWN Device Id: 5 000039 9b560c2c2 Firmware Version: KQ000A User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jul 26 22:46:35 2021 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 120) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 502) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 8060 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 62 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 8809 10 Spin_Retry_Count 0x0033 101 100 030 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 244 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 18 (Min/Max 12/31) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0 222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 562 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0 224 Load_Friction 0x0022 100 100 000 Old_age Always - 0 226 Load-in_Time 0x0026 100 100 000 Old_age Always - 803 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0 SMART Error Log Version: 1 ATA Error Count: 3 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3 occurred at disk power-on lifetime: 8764 hours (365 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 98 28 0e c0 40 Error: UNC at LBA = 0x00c00e28 = 12586536 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 28 98 10 0e c0 40 00 22d+20:33:25.353 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 22d+20:33:25.353 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 22d+20:33:25.352 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 22d+20:33:25.352 IDENTIFY DEVICE ef 03 45 00 00 00 a0 00 22d+20:33:25.351 SET FEATURES [Set transfer mode] Error 2 occurred at disk power-on lifetime: 8764 hours (365 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 28 08 0e c0 40 Error: UNC at LBA = 0x00c00e08 = 12586504 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 30 28 08 0e c0 40 00 22d+20:33:22.242 READ FPDMA QUEUED 60 08 20 60 0d c1 40 00 22d+20:33:22.241 READ FPDMA QUEUED 60 08 18 78 0d c1 40 00 22d+20:33:22.240 READ FPDMA QUEUED 60 08 10 70 0d c1 40 00 22d+20:33:22.239 READ FPDMA QUEUED 60 08 08 68 0d c1 40 00 22d+20:33:22.238 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 8764 hours (365 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 28 00 0d c0 40 Error: UNC at LBA = 0x00c00d00 = 12586240 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 28 00 0d c0 40 00 22d+20:32:39.403 READ FPDMA QUEUED 60 08 20 80 08 c0 40 00 22d+20:32:39.292 READ FPDMA QUEUED 60 08 18 10 17 01 40 00 22d+20:32:39.291 READ FPDMA QUEUED 60 08 10 08 17 01 40 00 22d+20:32:39.290 READ FPDMA QUEUED 60 08 08 f8 16 01 40 00 22d+20:32:39.289 READ FPDMA QUEUED SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
  17. Hi, when ill try to update the repository has no xenial Release why??? Best regards, Nelson
  18. It does look like the same issue to me and filesystem does not matter, these SATA errors can present themselves simply by reading the disk. And as a result, filesystem corruption is not unexpected, ZFS does protect us from it though. But it can’t be discounted that this could be a disk error as well, perhaps it’s nearing its end-of-life. Which brand / model of disk do you have?
  19. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  20. I have a M4V2, and want to build a mini NAS with OpenMediaVault 5 under Armbian (OMV5 can only run under Armbiam/Debian, but not in Ubuntu) The M4V2 has a SATA hat, and it can support up to 4 hard drives (2.5 inches size), so the SATA hat is powered separately, and I guess this is why this hat always gets overheat. There is a 12V fan interface (2pin) on this SATA hat, just right biside the power button. And I found that there are already some solution in this forum, all kinds of scripts, can drive the Fan according to the CPU's temperature, or even SSD/HDD's temperature, this are so amazing. And then when I tried these scripts, I realized this PWM scripts won't solve the issue I am facing. bacause the SATA hat is getting heater and heater, whilr at this time the CPU's temperature remains in 100F, and the fan is not running. I guess if I can let the fan keep running in full speed, this issue would be solved. So I went to the FriendlyARM's Wiki page, and found they did provide a scrips to change working method of the FAN, here is the code: #!/bin/bash echo 0 > /sys/class/pwm/pwmchip1/export sleep 1 echo 0 > /sys/class/pwm/pwmchip1/pwm0/enable echo 50000 > /sys/class/pwm/pwmchip1/pwm0/period echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable echo 45000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle I have tried this script with the image name "Friendly Core" (branch of Ubuntu 18.04) image, it works fine. When system lights up, the fan will keep running, when system is done, the fan will shut down also. (before I have try the GPIO with another 5V fan, while in this case, the fan wont shutdown even the system is poweroff ) And now my problem is, this script can only run under Ubuntu, how can I make it available in Armbian also? Will be really appreciate to hear any response from you. Thanks, J.K.
  21. Nah, no soldering involved. Just cut of the data part of the connector. It destroys that bit irreversibly, but then you are just left with the power connector and you can plug that on the back of new connector I took the assembly image from the wiki and used my amazing paint.net skills to draw lines where to cut; just make sure you leave the power connector intact
  22. ? The problem begins with a READ FPDMA QUEUED error, and ends with a ro filesystem due to an I/O errors. The result may be different (maybe due to no raid/zfs), but the source looks the same to me. It worked for 8 months without problems, and now it works fine in slot 3. (Where slot 1 is the farthest from the mobo) And solder it on the power connectors of the new cables? Hm. I hoped for a simpler solution.
  23. sorry for asking about espressobin... I had this board working with armbian, but it was sitting in a box for a while. I remade the sd card with the new current 5.10 buster and it won't boot. I tried different sd cards and power supplies. It hangs at "Loading, please wait" Maybe I need new u-boot, but that https://minio.k-space.ee/ site isn't working or is gone. Not armbian's fault obviously. Anyone know another way to get a current u-boot image? I don't really want to build one. I don't have a toolchain set up and I'll probably buy a different board anyways. (Anyone know a well supported 2 port box that's easy to get in the USA?) These things are a pain.
  24. @Charles Bauer I guess the second option but I am just AFRAID to buy one that HASN'T eMCP. So shipping exactly THIS ONE " bricked" actually in your hands is the best solution to finally manage to study those damned eMCP. I'm afraid shipping to Italy will be around 30/40 USD This is the reason why UNTIL now I didn't invest money in buying one: not because of 20/30 or even 40 euros, but because I must be sure receiving the right one. I have plenty of emmc and nands rk322x boxes , imagine I buy another one sure it is eMCP and arrives ANOTHER emmc or nand Will write you in private but bit later !
  25. this here could be an idea for accurate time https://hackaday.com/2021/07/25/portable-gps-time-server-powered-by-the-esp8266/
  1. Load more activity