Search results

  1. epopen

    14.0-RELEASE weird build world/kernel/ports behavior

    Hi All Before, encounter out of swap -> system silent dead issue @ buildworld,:eek: System statistics weird also :rolleyes: Today, I saw the issue before system silent dead, therefore screen capture for reference. Note: After capture, I break buildworld by Crtl+C to prevent system silent dead...
  2. epopen

    14.0-RELEASE weird build world/kernel/ports behavior

    Hi All Test update... About H/W stability, I had tested by memtest86, pi and unix bench a all day @ i5-7200U, all passed.:) Storage status of # zpool status pool: zroot state: ONLINE scan: scrub repaired 0B in 00:29:07 with 0 errors on Fri Nov 24 15:04:57 2023 config: NAME...
  3. epopen

    14.0-RELEASE weird build world/kernel/ports behavior

    Thanks your suggestion, testing by memtest86...
  4. epopen

    14.0-RELEASE weird build world/kernel/ports behavior

    Hi All I upgraded from 13.2-RELEASE to 14.0-RELAESE by source code and one-shot build successful (git branch: releng/14.0) H/W: 16GB Physical RAM + 10 GB SWAP @ Root on ZFS But encounter build world/kernel/ports terminate anywhere randomly even code have no problem.:eek: Example (buildworld)...
  5. epopen

    Solved Upgrade 14-RELASE @ Root on ZFS, reboot before update boot code and stuck at EFI shell.

    Hi SirDic & T-Aoki I understood. In my UEFI-GPT booting case, can not update boot code # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 Only update /mnt/efi/boot/bootx64.efi by manual cp Thanks a lot.
  6. epopen

    Solved Upgrade 14-RELASE @ Root on ZFS, reboot before update boot code and stuck at EFI shell.

    Hi All I found other user topic like me as https://forums.freebsd.org/threads/upgrading-zfs-zpool-under-freebsd-14.91076/post-629535 gpart result => 40 2000409184 nvd0 GPT (954G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K)...
  7. epopen

    Solved Upgrade 14-RELASE @ Root on ZFS, reboot before update boot code and stuck at EFI shell.

    Hi grahamperrin Thanks your information. May I missed, I don't find boot code update by manual & upgrade without gpart 😅 Official update procedure update by release announcement possible.:-/
  8. epopen

    Solved Upgrade 14-RELASE @ Root on ZFS, reboot before update boot code and stuck at EFI shell.

    Hi T-Aoki, Emrion and grahamperrin The issue fixed.:D Basically, follows procedure of T-Aoki, overwrite /boot/loader.efi on the memstick to /mnt/efi/freebsd/loader.efi and /mnt/efi/boot/bootx64.efi Because could not boot when overwrite /mnt/efi/freebsd/loader.efi only. Next, I tried to update...
  9. epopen

    Solved Upgrade 14-RELASE @ Root on ZFS, reboot before update boot code and stuck at EFI shell.

    Hi All I executed zppol upgrade zpool, but reboot unexpected,🤯 Result: My system stuck at EFI shell, like 264453. I googled to trying to boot to system and update boot code. but either execute follows command @ EFI Shell FS0:\> efi\boot\bootx64.efi or FS0:\> efi\freebsd\loader.efi Got blank...
  10. epopen

    Solved Running jails from /etc/jail.conf.d?

    Hi All Is possible include common config/items for /etc/jail.conf.d/{jailname}.conf? Because my current /etc/jail.conf has it look like follows. # Common config FOO BAR jailname_1 { ... } jailname_2 { ... } ... Thanks a lot.
  11. epopen

    Just updated 13.1 to 13.2 via src and got buildworld failed about kbdcontrol

    Hi All As title, I switched source code to RELEASE-13.2 as follows and got buildworld failed about kbdcontrol, please refer build log git checkout releng/13.2 I tried to code search, google and relation result is follows for build control @ /etc/src.conf WITHOUT_LEGACY_CONSOLE=yes It added in...
  12. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    Hi All I tried to capture result of top per minute and noteworthy point found as follows. 2023/2/25 Sat 03:15:34 CST last pid: 48; load averages: 1.16, 1.85, 1.28 up 23+16:03:05 03:15:34 128 processes: 1 running, 119 sleeping, 3 stopped, 5 zombie CPU: 0.8% user, 0.5% nice, 0.9%...
  13. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    Follows your information, I regenerate report by smartctl -x ... (Prints all SMART and non-SMART information about the device.) Please reference https://termbin.com/8cvj7 Thanks a lot.
  14. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    Ans: 2 GB swapspace is not use almost (Configuration of all daemon from 256MB RAM machine and few modified to fit higher memory machine) Yes, I think so full swapspace problem, It caused by problem software (memory leak?) possible. Therefore monitoring to find which one causes. Thanks a lot.
  15. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    It is higher swap space😲 In my case, my server does not busy, almost personal use. Therefore my swap-space free almost. Thanks a lot.
  16. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    Yes, but do not know amount of free memory during problem occurring. Keep going monitor. Thanks a lot.
  17. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    It bought at 2014, but storage(no power) 2~3 years I remember. With mentioned Power_Cycle_Count and Power-Off_Retract_Count, the Power_On_Hours_and_Msec can not believe😅 Yes, I using custom kernel (device ada included). Thanks a lot.
  18. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    What is your ZFS setup? Using mirrors I presume? >> Only one driver. When the system freezes, can you access it remotely (ssh)? >> I can not access remotely, therefore ask my brother to press the reset button😅 When the system looks as being in a freezed state, a severely memory starved ZFS...
  19. epopen

    Troubleshoot of "a thread waited too long to allocate a page"

    Hi SirDice Please reference https://termbin.com/n2al I'm surprise about attribute of Power_Cycle_Count and Power-Off_Retract_Count Because the driver using for server and 24/7 power-up, power cycle times is low, will be damage? System not use smartctl frequency due kern_securelevel="2" EDIT...
Back
Top