Posts by bugado

    Hi.

    Try this:

    1. Stop your Jdownloader container.

    2. Edit org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json (you will find it your config folder: /srv/dev-disk-by-label-datadisk/appdata/config/jdownloader) if not present, create it.

    3. Add:

    {

    "email" : "login",

    "password" : "pass"

    }

    4. Restart the container.

    5. Go to myJdwonloader and connect.

    6. Go to Settings and change download folder with: /downloads


    and it will be done.

    Hi everyone,


    A few days ago, my Raid 6 array turn in read-only mode, but stay clean.


    dmesg gave me this:

    Code
    Aborting journal on device md0-8.
    EXT4-fs error (device md0): ext4_journal_check_start:61: Detected aborted journal
    EXT4-fs (md0): Remounting filesystem read-only
    EXT4-fs error (device md0): ext4_journal_check_start:61: Detected aborted journal



    cat /proc/mdstat

    Code
    Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
    md0 : active raid6 sdn[1] sdm[6] sdl[11] sdj[0] sdk[10] sdh[9] sdi[12] sdg[7] sde[3] sdf[2] sdd[4]
    26371215360 blocks super 1.2 level 6, 512k chunk, algorithm 2 [11/11] [UUUUUUUUUUU]
    bitmap: 1/22 pages [4KB], 65536KB chunk
    unused devices: <none>

    mdadm -D /dev/md0

    On this array, I have only one ext4 partition (named Stock) .




    df -Th | grep "^/dev"

    Code
    /dev/sdc1 ext4 79G 7.6G 67G 11% /
    /dev/sdb1 ext4 234G 19G 216G 8% /srv/dev-disk-by-label-AppData
    /dev/sda1 ext4 2.7T 23G 2.7T 1% /srv/dev-disk-by-label-Downloads
    /dev/md0 ext4 25T 14T 12T 55% /srv/dev-disk-by-label-Stock


    So, after some search, I run
    e2fsck -fy /dev/md0

    After a reboot, everything is good. My Raid array is clean, my filesystem is writable.
    Every HDD of this array is good on Smart Status.
    But after a random time, it turn on read-only and I have to remake e2fsck and reboot.
    I have this error about 1 time a day, so it's not very practical...


    Is there a way to fix this??

    Hi


    My NAS turn with a I7-7700K, here is lscpu result:


    My OMV CLI is displaying me a regular error message related to overheating of my processor and the cores:

    Code
    CPU0: Core temperature above threshold, cpu clock throttled (total events = 458)
    CPU6: Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU2:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU3:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU1:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU7:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU5:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU0:Package temperature above threshold, cpu clock throttled (total events = 926)
    CPU4:Package temperature above threshold, cpu clock throttled (total events = 926)

    First, I check the hardware. The CPU fan is OK, the rad is clean. All the case fan are OK.


    I check my BIOS settings and I set the fan speed at the max (3200 rpm). The BIOS show a temperature about 30°C for the CPU.


    In OMV CLI, sensors give a normal temp, even after big loads:


    The speed of the cpu_fan is not correct: it keep turning at high rate.




    I do not understand why this message continues to appear...
    Does my CPU pause regularly?


    Thks for the help...

    Thank you again ryecoaaron, your advice is always a grim help


    My OMV has been running for 2 days on proxmox, no error since!!


    The Raid array work like a charm and all my services are On (Docker, plex, remote mount...)

    I'm giving up...
    I tried a lot of different thing:
    . I change my SataCard with a Marvell 9215 for test
    . I have done a clean installation of OMV 4.14
    . I made all OMV and OMV-Extra updates.
    . Erase all disks and make a Raid6 Array in 4.19 bpo2. and... got the same error: mdadm blocked for more than 120sec Not tainted for 4.19 bpo2
    . I try adding GRUB_CMDLINE_LINUX="scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0" in /etc/default/grub. Nothing change...
    . So I downgrade kernel to 4.14, pin it with apt-mark hold 4.14.0-0.bpo.3-amd64
    . The array resync work well without any freeze or error message.
    . Every disk is OK with Smart status
    . I check every Sata cableSo I can stay in 4.14 but I prefer be up to date...
    Any advice??

    Finally, I installed OMV 4 on another disk available to do my tests.Here I am in 4.14 and I find my RAID clean, accessible and error free ...I am making copies of my data then I will delete and put back a new RAID 6 under linux 4.19, which normally should settle things ... I hope.I'm just worried that my SATA card will not be properly handled by Linux updates ... I'm using this 10xSATA card (https://www.amazon.fr/gp/product/B01ENKHLS6/ref=ppx_yo_dt_b_asin_title_o07__o00_s00?ie=UTF8&psc=1)
    Thks, I follow the evolution...

    Hi,


    My raid 6 array won't work on kernel higher than 4.14 bpo3.
    If I try 4.19, my Raid array block:


    Code
    Jan 18 14:59:52 BigNAS kernel: [ 363.708804] INFO: task md127_raid6:270 blocked for more than 120 seconds.
    Jan 18 14:59:52 BigNAS kernel: [ 363.708873] Tainted: G U E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
    Jan 18 14:59:52 BigNAS kernel: [ 363.708953] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 18 14:59:52 BigNAS kernel: [ 363.709030] md127_raid6 D 0 270 2 0x80000000

    I try all 4.18 and 4.19 kernel and it block my Raid array
    The 4.14 kernel is no more available in OMVExtra on my OMV Gui
    Is there a way for reinstall this kernel??
    Thanks

    Hello,


    My NAS turn on OMV 4.1.17-1 Arrakis.


    I have a little (or not) problem with my Raid 6.
    The array is composed of 11 HDD, some are wired on the motherboard and the other on a SataCard (Kalea-Informatique PCIe 10xSATA 3.0 found on Amazon)


    If I keep my kernel at 4.14.0-0.bpo.3-amd64, I have no pb: Array is displayed as clean in OMV Gui; CIFS, FTP or other services works like a charm.
    If I upgrade my kernel to 4.18.0-0.bpo.1-amd64, 4.18.0-0.bpo.3-amd64 or 4.19.0-0.bpo.1-amd64, the Array is diplayed as Active in the Gui. Also if I try CIFS or FTP folder display, it stucked for long long time.


    This is then displayed in my syslog:


    Code
    Jan 18 14:59:52 BigNAS kernel: [ 363.708804] INFO: task md127_raid6:270 blocked for more than 120 seconds.
    Jan 18 14:59:52 BigNAS kernel: [ 363.708873] Tainted: G U E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
    Jan 18 14:59:52 BigNAS kernel: [ 363.708953] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 18 14:59:52 BigNAS kernel: [ 363.709030] md127_raid6 D 0 270 2 0x80000000

    Someone can help me please?

    I think I'm done :D



    I tried a lot of methods with a single openvpn container in order to point my other containers on. Such as chuckremes/openvpn-client dperson and others.
    I failed :(


    So finally I create my jdownloader container and use the network of my tansmission one:


    For transmission, I use


    Code
    docker run --privileged --restart=always --name=transmission -d -v /srv/dev-disk-by-label-Downloads/:/data \
    -e "OPENVPN_PROVIDER=IPVANISH" \
    -e "OPENVPN_USERNAME=xxxx@xx.xx" \
    -e "OPENVPN_PASSWORD=xxxxx" \
    -e "OPENVPN_CONFIG=ipvanish-AL-Tirana-tia-c02" \
    -e "LOCAL_NETWORK=192.168.1.0/24" \
    -e "TRANSMISSION_DOWNLOAD_DIR=/data/Downloads/Torrents" \
    -e "TRANSMISSION_INCOMPLETE_DIR=/data/TorrentTemp" \
    -e "TRANSMISSION_WATCH_DIR=/data/TorrentSurv" \
    -p 9091:9091 haugene/transmission-openvpn

    add your username, pass and for config, use your favorite ovpn


    and then, for Jdownloader, I use -net=container:transmission


    Code
    docker run -d --name Jdownloader --net=container:transmission --restart=always \
    -v /srv/dev-disk-by-label-Downloads/Jdownloader/cfg:/opt/JDownloader/cfg \
    -v /srv/dev-disk-by-label-Downloads/Downloads/Directs:/downloads \
    plusminus/jdownloader2-headless

    At first load, after few min for Jdownloader update, stop the container


    Code
    docker stop Jdownloader

    and modify org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json (in the folder /cfg set upside).


    If the file does not exist, create it . Then add your mydownloader mail and password

    Code
    {
    "email" : "login",
    "password" : "pass"
    }

    Restart the container


    Code
    docker start Jdownloader

    And then the Jdownloader container can be adminisstrated with MyJdownloader, Web or apps 8o


    You can check you Wan IP with FTP.
    I grabb a file on my OMV Ftp with Jdownloader (ftp://FTPlogin:FTPpass@OMV.WAN.FTP.IPyourLanIP/directories/file) and I check the IP of the device in my OMV gui , in the FTP system logs.


    Wonderful :thumbsup::thumbsup:
    It's my IPVANISH IP!!!!!


    If it can help somebody


    The thing I have to check is the kill switch.


    Edit:


    ;( Jdwonloader don't write anything to my download folder ( /srv/dev-disk-by-label-Downloads/Downloads/Directs for me).


    I'll have to dig a little bit more :S

    Edit 2:


    Ok just modify the download folder in myjdownloader settings with /downloads
    IT S DONE :thumbsup::thumbsup::thumbsup:


    I resolve the Thread

    Hi
    I come back to this post after several months


    I tried several methods to create an OpenVPN IPvanish client via Docker, without ever really succeeding.
    Even less to pass the traffic of a jdownloader container through I try chuckremes/openvpn-client, dperson/openvpn-client with no succeed.
    Finally, I continue to use haugene/transmission-openvpn for Transmission with Http access via local network


    I put my nose back in Docker to jdownloader these days because it would make my life easier.
    But I am noob on docker and I really need help.
    Someone would have a tutorial to advise me or even scripts to launch?
    I'm struggling docker run --privileged -d \ -e "OPENVPN_PROVIDER=PIA" \ -e "OPENVPN_CONFIG=Netherlands" \ -e "OPENVPN_USERNAME=user" \ -e "OPENVPN_PASSWORD=pass" \ chuckremes/openvpn-client for chuckremes/openvpn


    The script is successful but how to be sure of the connection to the VPN, how to get the Internet IP of this container?
    Next, how can I use this container so the jdownloader or the transmission container pass through?
    And finally, can I manage jdownloader with http like haugene/transmission-openvpn do?


    Thanks again for the help!!!

    Hello!


    I want to protect my downloads behind a VPN (for me, Ipvanish), but just my downloads plugins (transmission for torrent and jdownloader 2 for direct downloads), so Ftp, plex and the other plugins work without VPN to be accessible from the outside.


    I did not manage to use OpenVPN like this: by selecting the plugins to use or not with VPN


    After some search, I succeeded with transmission: I use docker with haugene/transmission-openvpn and it work fine for me, after a few attempts


    My search are not successful with Jdownloader 2...
    Can someone give me hints, or better, a tutorial, to isolate Jdownloader (or an other direct down manager)?



    NB. Sorry for my bad english...

    Hello,


    I don't succeed on making remote mount work with my OMV3 Erasmus bpo2 with the GUI


    I try to mount it with the GUI, with Remote Mount service



    I don't have any error when I apply changes:



    But errors in Filesystem



    The monit send this mail:
    Date: Wed, 19 Apr 2017 14:51:30
    Action: alert
    Host: BigNAS.local
    Description: unable to read filesystem '/srv/8b6c369b-e382-485c-a069-230c26b94021' state


    Your faithful employee,
    Monit



    I try to test it on CLI:


    Create /media/partagetest folder
    and launch:
    mount -t cifs -o username=admin,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 //txx.xxx.org/Documents /media/partagetest


    And It work: I can navigate, create folders...
    But I want a filesystem working with Remote Mount. (for rsync and other things...)


    Can somebody help me??

    I try month ago to use VPN just for Downloads (tansmission) and leave Plex and other services use "normal" connexion.


    I try OpenVPN but it's too complex for me.. Never succeed.. I'm not skilled in linux as in engligh ;)
    So finally, I use Docker.
    Transmission is the only service that use VPN (Ipvanish) on my OMV.



    You can find a nice tuto here for synology, but very easy to apply to OMV. Sorry, in french... cool for me :P
    http://www.babash.fr/2015/12/0…mission-a-travers-un-vpn/
    haugene/transmission-openvpn work with a lot of VPN providers


    If you want to try and block, I can help

    ;(;(
    with extundelete, you think I can revocer my files (My raid 5 is in ext4) and copy them in some other disk?


    Sorry, but I have to do
    apt-get install extundeleteand extundelete /dev/md127 --restore-directory /Audio
    for exemple?
    on the Raid we just mount? or disk by disk?

    [/tt]mdadm --readwrite /dev/md127
    Nothing displayed


    cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : active raid5 sdi[5] sdh[4] sdf[3] sde[2] sdb[1] sda[0]
    14650675200 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/6] [UUUUUU]


    unused devices: <none>


    blkid
    /dev/sdb: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="659ed876-b4e8-167e-3c46-5cd94b431a84" LABEL="NasMaison:127" TYPE="linux_raid_member"
    /dev/sdg: UUID="343e9353-fa4e-c1d3-d6b9-1659b517e910" UUID_SUB="acdb4fd4-3a19-b021-dfd3-6849997e4ec7" LABEL="NAS-Maison:Stock" TYPE="linux_raid_member"
    /dev/sdh: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="50c2a64a-bb40-e6a2-6613-0a53d8a7fb67" LABEL="NasMaison:127" TYPE="linux_raid_member"
    /dev/sdi: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="51a7c2ae-c1ad-4693-e75e-7bb93b699a0a" LABEL="NasMaison:127" TYPE="linux_raid_member"
    /dev/sdc1: UUID="2642ec6c-7f02-40f5-8d30-9278d409aee7" TYPE="ext4"
    /dev/sdc5: UUID="7b189bc1-bc83-4ed5-bf4a-d5933a418d3f" TYPE="swap"
    /dev/sdd1: UUID="b07fb66d-1528-49ef-8760-6b762f9eacf7" TYPE="ext4"
    /dev/sde: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="c39dc121-8694-8d16-6312-3aa644484849" LABEL="NasMaison:127" TYPE="linux_raid_member"
    /dev/sdf: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="f43cae35-4d82-4acb-2e89-41574e351322" LABEL="NasMaison:127" TYPE="linux_raid_member"
    /dev/sda: UUID="3870e4d0-e0fd-2494-b32a-f0f93d47e9d7" UUID_SUB="f746cc3b-3a52-dae6-7422-21a625764976" LABEL="NasMaison:127" TYPE="linux_raid_member"

    I don't have any other chance, I try...


    the result:
    mdadm: layout defaults to left-symmetric
    mdadm: layout defaults to left-symmetric
    mdadm: chunk size defaults to 512K
    mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=7 ctime=Mon May 16 20:34:29 2016
    mdadm: /dev/sde appears to be part of a raid array:
    level=raid5 devices=7 ctime=Mon May 16 20:34:29 2016
    mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=7 ctime=Mon May 16 20:34:29 2016
    mdadm: /dev/sdh appears to be part of a raid array:
    level=raid5 devices=7 ctime=Mon May 16 20:34:29 2016
    mdadm: /dev/sdi appears to be part of a raid array:
    level=raid5 devices=7 ctime=Mon May 16 20:34:29 2016
    mdadm: size set to 2930135040K
    Continue creating array? y
    mdadm: Defaulting to version 1.2 metadata
    mdadm: array /dev/md127 started.


    cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : active (auto-read-only) raid5 sdi[5] sdh[4] sdf[3] sde[2] sdb[1] sda[0]
    14650675200 blocks super 1.2 level 5, 512k chunk, algorithm 2 [6/6] [UUUUUU]


    unused devices: <none>


    mdadm --detail /dev/md127
    /dev/md127:
    Version : 1.2
    Creation Time : Tue Jan 24 14:44:28 2017
    Raid Level : raid5
    Array Size : 14650675200 (13971.97 GiB 15002.29 GB)
    Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB)
    Raid Devices : 6
    Total Devices : 6
    Persistence : Superblock is persistent


    Update Time : Tue Jan 24 14:44:28 2017
    State : clean
    Active Devices : 6
    Working Devices : 6
    Failed Devices : 0
    Spare Devices : 0


    Layout : left-symmetric
    Chunk Size : 512K


    Name : NasMaison:127 (local to host NasMaison)
    UUID : 3870e4d0:e0fd2494:b32af0f9:3d47e9d7
    Events : 0


    Number Major Minor RaidDevice State
    0 8 0 0 active sync /dev/sda
    1 8 16 1 active sync /dev/sdb
    2 8 64 2 active sync /dev/sde
    3 8 80 3 active sync /dev/sdf
    4 8 112 4 active sync /dev/sdh
    5 8 128 5 active sync /dev/sdi


    The OMV Gui recognise the Raid as clean but not the System Files (n/a)