Beiträge von sbocquet

    It seems that I have missed Something...



    For me, the conf file is fine...
    Any idea to "patch" this error message?

    Hi Volker,


    After googling a few...


    - I stopped the collectd and rrdcached service
    - Made some cleaning in /var/lib/rrdcached/localhost (because I have changed a mount point yesterday... I know, that thing should be avoid ;) )
    - Ran omv-mkconf collectd and omv-mkconf rrdcached
    - Restarted the 2 services


    and all is back to normal. Collecting and graphing, except that it is impossible to see the Time/Operation for my 2 RAID arrays since the beginning (maybe it's impossible)


    Hi everybody !


    Could someone give me some info on the magic behind the graphs and stats, as some graphs are not showing in my OMV GUI... (Time/operation on my 2 RAID devices /dev/md0 and /dev/md1)


    Would like to check some params...


    Thanks a lot.

    OK... file found.


    /etc/monit/conf.d/openmediavault-filesystem.conf


    [EDIT] And if you have some rsnapshot saves configured on that drive, don't forget to delete/re-create them... else your / drive will be quickly full ;) (like me this morning ! lol)


    Cheers,

    Hi,


    First, I know that it's better to let OMV GUI do its magic, but...for different reasons, I have change a mount point in /etc/fstab.


    The mount point was linked "by label" and I changed it "by-id" (see lines 7 & 8 )

    Code
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    UUID=052263f1-d951-4a32-bdbf-052649fe60da /               ext4    errors=remount-ro 0       1
    tmpfs           /tmp            tmpfs   defaults        0       0
    # >>> [openmediavault]
    /dev/disk/by-id/ata-SAMSUNG_MZ7LN512HCHP-000L1_S1ZKNXAG526958-part5 /srv/dev-disk-by-id-ata-SAMSUNG_MZ7LN512HCHP-000L1_S1ZKNXAG526958-part5 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
    /dev/disk/by-id/md-name-home-server:DiskPool /srv/dev-disk-by-id-md-name-home-server-DiskPool ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    /dev/disk/by-id/md-name-home-server:Backup /srv/dev-disk-by-id-md-name-home-server-BackupPool ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    # /dev/disk/by-label/BackupPool /srv/dev-disk-by-label-BackupPool ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
    # <<< [openmediavault]


    I have also changed config.xml file to match the previous change...



    Everything works fine, but the problem is that I'm receiving an email at each reboot saying ;)


    "Status failed Servicemountpoint_srv_dev-disk-by-label-BackupPool


    Date: Tue, 20 Mar 2018 17:14:06
    Action: alert
    Host: home-server
    Description: status failed (1) --/srv/dev-disk-by-label-BackupPool n'est pas un point de montage


    Your faithful employee,
    Monit"


    So I know that I there is still one ref to the old mount point, but where ???


    Thanks for the help,


    Cheers,

    Hi tkaiser,


    I already done my research but haven't had the time to post here ;)


    Code
    root      1077     1  0 mars19 ?       00:00:11 /usr/bin/monit -c /etc/monit/monitrc
    ...
    root     20316  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>
    root     20317  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>
    root     20318  1077  0 11:42 ?        00:00:00 [mountpoint] <defunct>

    And here is the answer ;)

    Love that case... and the rock solid motherboard.
    I have 1x2,5" SSD + 7x3,5" disks in it, and the 5,25" bay is still empty ;)


    The CPU + RAM is overkill for OMV but my previous build was a Windows Server 2k12 Essential... so this power was necessary (3Go of RAM used at idle vs 800Mo for OMV ! lol).
    The fact is that I have the CPU for free from some old desktop, and it's only 15W at nearly idle... which is 90% of my NAS time.


    It's clearly not the best power saver NAS in the world, but the package runs silently in a cupboard of my home office since +10 years without a single disk crash ;)

    Hi,


    I have nearly the same mobo (GA-G33-DS2R) since more then 10 years (24/7) for my NAS and really love this one... ;)
    Only 6 SATA for mine so I have to buy a dedicated 2 SATA card, but it's unbreakable, even with overclock !


    Cheers,

    Hi,


    Same problem here every time I reboot/start my server... Network interface is down.
    My server is build from scratch (Debian 9.x + OMV 4.x install via package).


    I need to connect to the console, and restart the networking service manually with /etc/init.d/network restart and the network comes up !!!




    Still searching a solution...

    The problem with just "updating" things based on what others tell you is that you can't test these things yourself if you don't have the hardware the updates are applicable to.


    I can't speak for the plugin developer, but it seems to me this could be why there is so far no version for OMV 4.


    As for my application of the plugin on OMV 4, I spoke too soon. The CPU temperature part was working fine, but when I looked at it today, the graphs are swinging wildly and show a history of negative temperatures! I have removed the plugin and won't be returning to it until an official version shows up, if one shows up. My motherboard has IPMI and I can get that information from there, as well as the fan speeds which the plugin could never provide.

    1 point for you !...


    But as I understand, the plugin is working fine with OMV v3.x, so the "hard" code should be enough and tested (read it this afternoon and there's plenty of chipset already coded).
    It's the interface with OMV v4.x that needs to be updated to let it work like before. Not a big step forward I think...
    For new hardware, you can see later...


    P.S: lm-sensors can read my motherboard fan speed.

    Hi,


    You have to connect to your server with SSH, and run


    Code
    # env | grep LANG
    
    
    # dpkg-reconfigure locale

    You're language should be da-da.UTF8 I think...


    Reboot and it's done.
    Verify the new locale settings with the previous command.


    Cheers,

    Hi !


    I start this thread just to show you my NAS build.


    Case: Lian Li PC-V354
    Motherboard: Gigabyte GA-G33M-DS2R (6 x SATA II with ICH9R Chipset)
    CPU: Intel Core 2 E8400 @ 3,6Ghz
    RAM: 6GB Corsair XMS2 DDR2 PC6400
    PSU: Seasonic M12 - 500W
    CPU Fan: 1 x Artic with PWM
    System Fans: 4 x Be-Quiet @ 5V
    SATA Card: Startech PEXESAT322I (2 x SATA III)
    System Disk: SAMSUNG SSD MZ7LN512 - 512GB (12GB OMV/500GB Data)
    HDD Datas/Snapshots: 4 x WD Green 2TB + 3 x Seagate 2TB - RAIDz2


    OMV: 4.x (Linux 4.14.0-0.bpo.3-amd64)


    Hi all !


    I finished to configure my "new" NAS with OMV 4.x, and pretty happy with it.
    The only thing I miss now is some hardware information to monitor it.


    First, I've tried to install omv-sensors v3.x but no chance... the scripts are looking for omv-mkgraph that it cannot find.
    I think it's surely not a big thing to upgrade the plugin, and I've tried to look at it at https://github.com/OpenMediaVa…rs/openmediavault-sensors but clearly, I'm not good enough to do the job. But I can help to test it without a problem.


    Second... It would be nice to have more hardware info on the Dashboard, like disks and motherboard temp and, fan speed. So that you could check your NAS health at a glance.
    At the moment, I must use 2 ssh terminal to monitor this in real time with hddtemp and sensors packages.

    Bash
    # watch -n 1 hddtemp /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
    /dev/sdb: SAMSUNG MZ7LN512HCHP-0001L: 31°C
    /dev/sdc: WDC WD20EZRX-00DC0B0: 37°C
    /dev/sdd: WDC WD20EZRX-00DC0B0: 38°C
    /dev/sde: WDC WD20EZRX-00DC0B0: 39°C
    /dev/sdf: WDC WD20EZRX-00DC0B0: 36°C
    /dev/sdg: ST2000DM001-1ER164: 38°C
    /dev/sdh: ST2000DM001-1ER164: 36°C


    So, openmediavault-sensors is desperatly needed, and I would glad to help in any way that I can to make it nice and work.


    Cheers,


    (Something is missing ;) )

    Same here... 2 zombies processes


    Code
    root@omvglbvprd1:~# ps aux |grep 'Z'
    USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
    root     15366  0.0  0.0      0     0 ?        Zs   10:49   0:00 [mountpoint] <defunct>
    root     15367  0.0  0.0      0     0 ?        Zs   10:49   0:00 [mountpoint] <defunct>
    root     15373  0.0  0.0  12788  1000 pts/0    S+   10:49   0:00 grep Z

    Ok... got errors but the answer was post several times... If someone could delete post 6 to 10 !!!


    When I try to activate the plugin, I have this error. It seems that omv-mkgraph is no more present in v4.x...
    Maybe some works to do on the plugin to have it running on OMV v4.


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf sensors balls 2>&1' with exit code '2': sed: can't read /usr/sbin/omv-mkgraph: No such file or directory