Posts by wojciszpl

    Thank You for Your answer.

    Personally I checked comparision on the other bechmark, and the difference was quiet big:


    The question is - which bechmark is more valuable in reality.


    The reason why I changed it was:

    - Want to increase performance - I saw that some apps like Nextcloud was too heavy for J5040 (it worked but no quick as expected)

    - Having better iGPU with QVS supporting more video codecs (and this is fine - transcoding in jellyfin is much better)

    - Expected the power consumption will drop down


    If I would not read so many positive info about this board, I would not buy it - J5040 met 98% of my needs, had 4SATA by default + 2 thanks to M2 Wifi slot, was rock stable and as I see now - really good optimised in power consumption.


    That's why I;m so dissapointed and now I also thought the replace was not good idea.


    I tried switch off everything in bios but consumption is on the same level (17-18W in idle) - powertop -autotune helped a bit, because before it was a 21W


    Have no idea what to do more...

    Did You make any special settings in BIOS regarding power consumption?

    I ordered this mobo to replace my AsRock J5040, after reading this topic I expected to have similar or lower power consumption and much powerful CPU and iGPU

    But after setting everything and launch, I'm really disappointed - power consumption is ~19-20W in idle while it was 12-13W on J5040 (all disk in standby).

    I'm using PicoPSU 160W

    I made print screen on which ideally we can see the problem - if I use manually "hdparm -y /dev/sdb to spin down the drive, then it's ok up to next spin up (usually caused by midnight sync)

    After spin up, disk is not going spin down unless I use again hdparm -y

    XjNaikl.png


    Does anybody has idea what can be done more to fix this?

    Thanks for tip, but think it's not the case in my scenario, as I especially to avoid often spinning up of HDD bought 2x2tb SSDs ale all the stuff for containers, often used data, etc are ONLY one those disks. HDD stare only media like movies and one of them should be activated only once per day at midnight for backup, but even this one very often spin up all the day (spin up at midnight and not spinning down until I use hdparm -y)

    No, they won't wake up as far as i remember. Otherwise the info wouldn't make much sense. See https://github.com/openmediava…smartinformation.inc#L676

    From my experience this page wake up the disk, in the previous post of this topic I saw same experience of other users. Unfortunately recently (I think it's from v7, so probably migration from hdparm into smartmontools, I have contant problem with spinning down the disk - they not spin down for long time (unless I use hdparm -y) or wake up with different activities in GUI. I can't solve it for quiet long time.

    Hi, I have problem with not spinning down my disk - I believe it's connected with this change, as on prevous server with OMV6 it worked fine.

    I found that /etc/hdparm.conf  is all commented out, after that I found this topic on forum about replacement with smartmontools. Can anybody explain in simple works how it works know, how to debug it and why it can not work with my hdd's?

    In the config.xml I found section of hdparm with properly (as I set in GUI) values of APM and spindown:

    The problem is, that when I tried to check using sudo hdparm -I /dev/sda in my output I found:

    Code
            Standby timer values: spec'd by Standard, no device specific minimum
            R/W multiple sector transfer: Max = 16  Current = 16
            Advanced power management level: 64

    So it looks that APM is set to 64, but the standby timer is not set (spindown time?)


    I've tried also using omv-salt deploy run smartmontools


    Any ideas what I'm doing wrong or how to find the problem?

    There is only one issue. folder2ram is rotating logs which can be slow on slow systems. This delay can cause services not to start.

    It isn't breaking postfix. It is just causing it to not start on boot.

    My system is based on j5040, so maybe not super fast, but thought that more than enough for normal use, especially with omv which is known for low resoursces good solution. Is it possible that the problems is not with speed of cpu, but just writing/reading speed of the usb thumb?

    I'll try to search forum more to find solutions for the problem with postfix, but seriously thinking about buing just ssd, plug it via usb connector and remove flash memory - would You suggest it ?


    Btw in last post I mentioned about other problems after installing flash memory - one of them below:

    Code
    process_usershare_file: stat of /var/lib/samba/usershares/data_kc3000 failed. 

    I had lot of such errors with flash memory installed. Tried everything to solvd it without any results. After removing the plugin, those logs stopped appear - thought problem is solved. After installing plugin again, they are showing again. What's interesting, I don't have kc3000 share from long time, so it has to use some very old info but don't understand from where it took it.

    No, I don't think it's No, I don't think it's normal. I'm just surprised with some many issues with this, I thought maybe my server is problematic, but it's new instance and I'm trying not mess too much, everything trying to isolate installing in docker or lxc.

    Missing logs it's only one of the problems, but what about breaking postfix? I installled again the plugin and all the problems came back - postifx doesnt work after reboot, again in my syslog appears a lot of warning which are totally no sense (about old smb share which is not present from long time). Without the plugin those problems disappeared. Hope this info will be useful for You. Crossing finger!

    which variant You have? Purple with 2 NICs or black with 4?
    what is Your power consumption in idle?

    Interesting, looks that more and more people have same issue with postfix - maybe there is some kind of bug in late version of omv?

    Thank moflix for Your solution - I'll try this.

    In my instance it looks like postix started and immetiately stopped, maybe indeed just strarted too early?


    edit://

    ryecoaaron it looks like literally ALL my problems (smb, postfix and other posted on this forum/solved in the meantime) disappeared after temp remove Flash Memory plugin. Is it normal that this plugin is making a lot of troubles? Now I'm thinking of buing another SSD and put system on it, leaving this plugin alone, but till this, I need to install it again, to save my usb stick :)

    Don't get me wrong - I don't judge anybody, just asking to better understand the process. I just didn't know that syncing command is making logs invisible in OMV GUI or Cockpit.

    When I removed from my cron schedule for -syncall it looks problem is solved.

    What is curious, now even after reboot I'm not loosing logs from - totatally don't understand why but happy with this :)

    Hello,


    Since reboot I have only following output:

    Code
    -- Boot a438ce9243894892801b5739d2261d77 --
    lis 21 09:29:52 omv systemd[1]: Starting postfix.service - Postfix Mail Transport Agent...
    lis 21 09:29:52 omv systemd[1]: Finished postfix.service - Postfix Mail Transport Agent.
    lines 111-173/173 (END)

    Hi all,

    I have another problem with my omv instance, after solving few already.
    I'm using notification built-in omv based on postfix
    Everything works fine until reboot
    After each reboot I don't get any notifications, I need manually go into omv gui, disable then enable again notifications and after that it works until next reboot
    My logs below:


    I've tried to solve my issue with chatgtp, but it suggested me to edit me lib/systemd/system/postfix.service by replacing ExecStart/ExecReload values from original /bin/true into different ones, which totally broken postfix, so I stopped solving issue with it :)

    Code
    ExecStart=/bin/true
    ExecReload=/bin/true

    so this is the reason of my problem? Just to be sure: with this plugin each sync will rotate logs and make it invisible in gui?

    So it means also that with this plugin all logs will disappear after each reboot?

    No, system is uptime for many days.

    But I found somewhere in this forum years ago suggestion to make -syncall command via cron every few hours, just for safe - is this not a good idea? is this can have influence on this problem?