Jump to content

0x349850341010010101010100

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation Activity

  1. Like
    0x349850341010010101010100 reacted to RlndVt in Helios64 - Armbian 23.08 Bookworm issues (solved)   
    Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems registered: /dev/sdd registered: /dev/sdb registered: /dev/sde registered: /dev/sdc registered: /dev/sda done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 56356/1891776 files, 967727/7708672 blocks done. done. Begin: Running /scripts/local-bottom ... /scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdadm: rm: not found done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.8.3 bookworm! [...] Starting networking.service - Raise network interfaces... [ 16.458082] Internal error: Oops - Undefined instruction: 0000000002000000 [#1] PREEMPT SMP [ 16.458852] Modules linked in: ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_multiport xt_comment lz4hc nft_limit lz4 leds_pwm gpio_charger pwm_fan rockchip_vdec(C) hantro_vpu panfrost snd_soc_hdmi_codec snd_soc_rockchip_i2s v4l2_vp9 videobuf2_dma_contig v4l2_h264 rockchip_rga gpu_sched xt_limit drm_shmem_helper rockchip_rng snd_soc_core xt_addrtype videobuf2_dma_sg v4l2_mem2mem rng_core snd_compress videobuf2_memops snd_pcm_dmaengine xt_tcpudp videobuf2_v4l2 snd_pcm binfmt_misc videobuf2_common xt_conntrack videodev nf_conntrack snd_timer nf_defrag_ipv6 mc snd nf_defrag_ipv4 nft_compat soundcore nf_tables nfnetlink zram gpio_beeper cpufreq_dt sg ledtrig_netdev lm75 nfsd auth_rpcgss nfs_acl lockd grace dm_mod sunrpc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod realtek fusb302 tcpm dwmac_rk stmmac_platform stmmac typec pcs_xpcs adc_keys [ 16.466751] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G C 6.1.50-current-rockchip64 #3 [ 16.467567] Hardware name: Helios64 (DT) [ 16.467920] pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 16.468542] pc : __this_cpu_preempt_check+0x24/0x40 [ 16.468996] lr : ct_nmi_exit+0x80/0x280 [ 16.469348] sp : ffff800009ef3be0 [ 16.469647] x29: ffff800009ef3be0 x28: ffff000000762d00 x27: 0000000000000000 [ 16.470292] x26: ffff000000762d00 x25: 0000000000000000 x24: 0000000000000000 [ 16.470934] x23: ffff0000f779e8f0 x22: ffff800009a3dc70 x21: ffff8000094ea818 [ 16.471575] x20: ffff800009766900 x19: ffff8000097668f0 x18: 0000000000000000 [ 16.472215] x17: ffff8000ee038000 x16: ffff800009d20000 x15: 0000000000000000 [ 16.472857] x14: 0000000000000000 x13: 0000000000000303 x12: 0000000000000000 [ 16.473501] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000f77a1f80 [ 16.474142] x8 : 0000000000000005 x7 : ffff0000f77a28f8 x6 : 00000000ffffffff [ 16.474781] x5 : ffff80000959a7e0 x4 : 0000000000000001 x3 : ffff800009757008 [ 16.475422] x2 : ffff000000762d00 x1 : ffff8000094ea818 x0 : 0000000000000005 [ 16.476063] Call trace: [ 16.476286] __this_cpu_preempt_check+0x24/0x40 [ 16.476700] ct_irq_exit+0x10/0x80 [ 16.477014] exit_to_kernel_mode.isra.0+0x20/0x2c [ 16.477440] el1_interrupt+0x58/0x6c [ 16.477766] el1h_64_irq_handler+0x18/0x2c [ 16.478139] el1h_64_irq+0x64/0x68 [ 16.478450] arch_cpu_idle+0x18/0x2c [ 16.478778] default_idle_call+0x38/0x17c [ 16.479143] do_idle+0x23c/0x2b0 [ 16.479442] cpu_startup_entry+0x24/0x30 [ 16.479800] secondary_start_kernel+0x124/0x150 [ 16.480221] __secondary_switched+0xb0/0xb4 [ 16.480627] Code: 9115e040 97ffffa6 a8c17bfd d50323bf (d65f03c0) [ 16.481180] ---[ end trace 0000000000000000 ]--- [ 16.481594] Kernel panic - not syncing: Attempted to kill the idle task! [ 16.482189] SMP: stopping secondary CPUs [ 16.482555] Kernel Offset: disabled [ 16.482869] CPU features: 0x40000,20824084,0000421b [ 16.483308] Memory Limit: none [ 16.483592] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---  
     
    No luck, see kernel panic above. The missing command can be seen below; `Unknown command 'kaslrseed' - try 'help'`:
     
     
    U-Boot 2022.07-armbian (Aug 22 2023 - 15:26:42 +0000) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 Core: 339 devices, 31 uclasses, devicetree: separate SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: dw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found. scanning bus for devices... Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3252 bytes read in 5 ms (634.8 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 166 bytes read in 4 ms (40 KiB/s) 24417797 bytes read in 1036 ms (22.5 MiB/s) 29792768 bytes read in 1264 ms (22.5 MiB/s) 86670 bytes read in 12 ms (6.9 MiB/s) 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=3f00000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 24417733 Bytes = 23.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4794000, end f5edd5c5 ... OK Loading Device Tree to 00000000f4716000, end 00000000f4793fff ... OK Starting kernel ...  
  2. Like
    0x349850341010010101010100 reacted to wurmfood in Migrate from ramlog to disk   
    Sorry, the line about disabling was just to make sure you disable the armbian-zram-config service by setting ENABLED to false.
     
    As a warning, though, I found some problems with this if you log to a zfs share. It seems you have to make sure zfs gets loaded before the logging starts up, otherwise you can get a kernel panic on occasion. I didn't really dig into how to fix this, so I just log and swap to a usb drive instead now.
  3. Like
    0x349850341010010101010100 reacted to Igor in ZFS on Helios64   
    You don't need to do anything. 
  4. Like
    0x349850341010010101010100 reacted to gprovost in Feature / Changes requests for future Helios64 board or enclosure revisions   
    RK3399 has a single PCIe 2.1 x 4 lanes port, you can't split the lanes for multi interfaces unless you use a PCIe switch which is an additional component that would increase a lot the board cost.
     
    That's clearly the intention, we don't want either to restart form scratch the software and documentation :P
     
    Yes this will be fixed, it was a silly design mistake. We will also make the back panel bracket holder with rounder edges to avoid user to scratch their hands :/
     
    We will post soon how to manage fan speed based on HDD temperature (using hddtemp tool), that would make more sense than current approach.
    You can already find an old example : https://unix.stackexchange.com/questions/499409/adjust-fan-speed-via-fancontrol-according-to-hard-disk-temperature-hddtemp
     
  5. Like
    0x349850341010010101010100 reacted to Zac in Feature / Changes requests for future Helios64 board or enclosure revisions   
    The design is awesome so I'd definitely not change it!
    I would have liked to have WoL working, that is an important feature for those who don't plan on having it on 24/7. (I know, a NAS is intended to be on 24/7, but to have something more environmental friendly, the ability to turn it off and on without physically touching the device is a must)
     
    Other than that, I'd also add the option to disable or at least deem the front leds (can't place it in a visible place it near the TV). 
    and ECC ram would also be very welcome.
     
  6. Like
    0x349850341010010101010100 reacted to Igor in ZFS on Helios64   
    ZFS was just upgraded to v2.0.1 https://armbian.atlassian.net/browse/AR-614 which is a preparation for pushing a kernel on and above 5.10.y. Upgrade was tested on Armbian Buster/Bullseye/Focal/Hirsute. My test ZPOOL was always loaded without any troubles.

    We only support upgrade troubles - for ZFS functional problems, please check / file a bug report here https://github.com/openzfs/zfs/issues
     
  7. Like
    0x349850341010010101010100 reacted to Werner in No HDD1 when using M.2 SATA on SHARED port.   
    Shared lines are not uncommon even on x86 mainboards. For example: https://www.asrock.com/mb/intel/fatal1ty z97 killer/#Specification
    Take note at Storage and Slots sections:
    That is to mention as addition to @tommitytom.
    You can try to sell it in forums. I already noticed a few people who did this successfully here. However if I were a potential buyer I'd consider a person with such an attitude not necessarily trustworthy
  8. Like
    0x349850341010010101010100 reacted to tommitytom in No HDD1 when using M.2 SATA on SHARED port.   
    Seems like the mistake is yours.  It's made pretty clear that the port is shared (it's even mentioned twice on the front page of kobol.io), it's not exactly a secret.
  9. Like
    0x349850341010010101010100 reacted to barnumbirr in 1 ssd + 5 hdd   
    From the wiki:
    Source: https://wiki.kobol.io/helios64/sata/#sata-controller-diagram
  10. Like
    0x349850341010010101010100 reacted to Igor in ZFS on Helios64   
    I added zfs zfs-dkms_0.8.5-2~20.04.york0_all to our repository so at least Ubuntu version works OOB (apt install zfs-dkms). I tested installation on Odroid N2+ running 5.9.11

    * packaging mirrors need some time to receive updates so you might get some file-not-found, but it will work tomorrow. Headers must be installed from armbian-config.
     
     
  11. Like
    0x349850341010010101010100 reacted to gprovost in ZFS on Helios64   
    Yeah definitely the topic deserved a dedicated thread, even a page on our wiki if someone feel like contributing https://github.com/kobol-io/wiki
     
    IMHO zfs-dkms would the easiest approach for most people.
  12. Like
    0x349850341010010101010100 reacted to gprovost in Helios64 Support   
    Yes you can upgrade. The issue of instability wasn't related to the kernel actually but to some silly bug in Armbian hardware optimization script.
  13. Like
    0x349850341010010101010100 reacted to Igor in Helios64 Support   
    Patch versions are reserved for emergency fixes, but we don't necessarily update all kernels. We need to test things before pushing out update to minimize unpleasant surprises.

    A major update (20.11) is around the corner and things will be updated then.
  14. Like
    0x349850341010010101010100 reacted to lyuyhn in Helios64 Support   
    To fellow zfs users, I just saw that the 0.8.5 release is out with many compatibility patches, we should wait until this version lands in the repos to use it on the Helios64
  15. Like
    0x349850341010010101010100 reacted to Igor in Helios64 Support   
    *** ZFS Version: zfs-0.8.3-1ubuntu12.4
    *** Compatible Kernels: 2.6.32 - 5.4

    For 5.8.y you need at least 0.8.4 from sources: https://github.com/openzfs/zfs/issues
     
    DKMS on Debian / Ubuntu is simply too old. Install attached .deb package (i tested this on Ubuntu Focal) and it will work:
     
     
    zfs-dkms_0.8.4-1ubuntu11_all.deb
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines