Jump to content

Grobalt

Members
  • Posts

    122
  • Joined

  • Last visited

Posts posted by Grobalt

  1. So, habe eben nochmal einen neuen share "scraping" eingerichtet ... 

    nichts reinkopiert, der ordner ist leer. gemounted und er zeigt mir nun den inhalt vom share download an ... völlig wild

     

    hab das ganze dann mal lokal auf meinem unraid server gemacht, ich kann ja genauso mounten ... identisch.

    export.PNG.35d97d08873336c2f5ae2798ae4b5b64.PNG

  2. So, habe eben nochmal einen neuen share "scraping" eingerichtet ... 

    nichts reinkopiert, der ordner ist leer. gemounted und er zeigt mir nun den inhalt vom share download an ... völlig wild

     

    hab das ganze dann mal lokal auf meinem unraid server gemacht, ich kann ja genauso mounten ... identisch.

     

    neuer share.png

    settings.PNG

    falscher inhalt.png

    inhalt von download.PNG

    local mount to test.PNG

  3. Schön - aber daran kann es nicht liegen da user "Ron" mit dem unassigned devices mounted und ich testweise bei user Alex es manuell gemacht hab mit meinem "falschen" mount Befehl, das Ergebnis aber identisch ist, beide sehen den Ordnerinhalt vom share aufnahmen und nicht von share Ron.

  4. weil ich mounts habe die ich alle 24 stunden neu setzen muss .. dsl zwangstrennung - und mit dem bisherigen weg gab es nun 1 jahr lang kein problem das über userscripts abzubilden. das kann ich mir daher auch nicht als fehlerquelle vorstellen

  5. auf dem remote rechner:

    root@Tower:/mnt# mkdir /mnt/remotes/10.253.1.1_ron
    root@Tower:/mnt# mount 10.253.1.1:/mnt/user/ron /mnt/remotes/10.253.1.1_ron
     

    auf dem unraid server:

    root@unraid:~# showmount -e
    Export list for unraid:
    /mnt/user/serien    *
    /mnt/user/ron       *
    /mnt/user/filme     *
    /mnt/user/download  *
    /mnt/user/aufnahmen *
     

  6. Servus, ich hab was sehr merkwürdiges ... ich hab 2 remote Rechner die per wiregate sich verbinden und shares zugreifen.

    Ich habe einen neuen share namens "ron" angelegt und da liegen ca. 100 ordner drin die man bearbeiten muss. Den share habe ich freigegeben und wenn ich im LAN über SMB zugreife ist auch der Inhalt korrekt.

    Per VPN remote mount ist der Inhalt jedoch komplett falsch und zeigt den Inhalt von /mnt/user/aufnahmen statt /mnt/user/ron

    wie zum Teufel geht das denn ?

    shares.thumb.PNG.53b752756621d32457ccf2a673916846.PNG

    share settings.PNG

    share content.png

    remotes.png

    remotes content.png

    share aufnahmen.PNG

  7. Thanks guy.davis, since sync is complete the unraid node is running flawless with machinaris. So i tried to change my bare metal farmer to docker and machinaris as well, but i needed to open a bug report as the interface does not show any plots but is farming without any issue, but it needed several restarts until all plots were loaded.

    https://github.com/guydavis/machinaris/issues/763

  8. First - thanks for the docker, i tried to move my installation to an unraid setup to be more flexible, so i am copying 24 disks step by step. Machinaris was installed some days ago and sync is nearly done, wallet is already finished. But somehow the plots are recognized, the pool connection is back alive as before, but it is not farming. Harvester appears to be offline.

     

    9.thumb.PNG.ac180a89b81235078d03bda6a7e86909.PNG8.thumb.PNG.10e7ff0314e7b29973dc48d3a8051832.PNG7.thumb.PNG.b18c59a6da642afb54d8ab3d09b590c2.PNG6.thumb.PNG.31396c7326d933982a766334b12a7923.PNG5.thumb.PNG.6201c64384f3eff170b35b2cee6ecf1c.PNG4.thumb.PNG.cb0f75e1fb9a5860573d64e4b7388983.PNG3.thumb.PNG.81eff097fdff8a8ea8097937ecb243a2.PNG2.thumb.PNG.fd6703b10a112d91043770fa37602447.PNG1.thumb.PNG.3d8d6462f359e8ee8929df91922d990a.PNG

    11.PNG

    10.PNG

  9. Hi,

    just installed a new server with unraid, switching from ubuntu. All disks are full, so i would like to start with unassigned devices and copy one by one to the unraid. Some of the disks are not mountable (unassigned devices plus is installed) - some are.

     

    What can i check  ? Example /dev/sdj is not mountable in the GUI with ext4 on it, but other ext4 disks are mountable.

     

    image.thumb.png.089ccdf33e4f1865f87ec2209db3b8db.png

  10.  

    Habs mit -C versucht und auch mit rauslöschen des Eintrags, beides nicht erfolgreich, Container wird sofort gestoppt

     

    root@unraid:~# lspci
    00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
    00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630]
    00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
    00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
    00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
    00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
    00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
    00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
    00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
    00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
    00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0)
    00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 10)
    00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
    00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
    00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
    02:00.0 Non-Volatile memory controller: ADATA Technology Co., Ltd. XPG SX8200 Pro PCIe Gen3x4 M.2 2280 Solid State Drive (rev 03)
    04:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card

    image.thumb.png.d1cca0b961927899d13a463373677432.png

    image.thumb.png.f27f5f065e425b75e1724dae33f9d275.png

  11. Habe gestern einen Stromausfall gehabt und die USV hat nicht funktioniert ,) System ist normal hochgefahren, Parity check läuft, soweit nichts auffälliges.

    Durch den Neustart habe ich die Docker Contrainer alle auf den aktuellen Stand gebracht, auch tvheadend. Daraufhin startet der Container nicht mehr. Das Docker log hilft mir kein bisschen weiter.

     

    text  error  warn  system  array  login  
    
    s6-rc: info: service 99-ci-service-check: starting
    s6-rc: info: service 99-ci-service-check successfully started
    s6-rc: info: service 99-ci-service-check: stopping
    s6-rc: info: service 99-ci-service-check successfully stopped
    s6-rc: info: service legacy-services: stopping
    s6-rc: info: service legacy-services successfully stopped
    s6-rc: info: service init-services: stopping
    s6-rc: info: service 00-legacy: stopping
    s6-rc: info: service init-services successfully stopped
    s6-rc: info: service init-mods-end: stopping
    s6-rc: info: service 00-legacy successfully stopped
    s6-rc: info: service init-mods-end successfully stopped
    s6-rc: info: service init-mods-package-install: stopping
    s6-rc: info: service init-mods-package-install successfully stopped
    s6-rc: info: service init-mods: stopping
    s6-rc: info: service init-mods successfully stopped
    s6-rc: info: service legacy-cont-init: stopping
    s6-rc: info: service legacy-cont-init successfully stopped
    s6-rc: info: service fix-attrs: stopping
    s6-rc: info: service fix-attrs successfully stopped
    s6-rc: info: service s6rc-oneshot-runner: stopping
    s6-rc: info: service s6rc-oneshot-runner successfully stopped
    [ls.io-init] done.
    Usage: /usr/bin/tvheadend [OPTIONS]
    
    Generic options
    
      -h, --help                  Show this page
      -v, --version               Show version information
    
    Service configuration
    
      -c, --config                Alternate configuration path
      -B, --nobackup              Don't backup configuration tree at upgrade
      -f, --fork                  Fork and run as daemon
      -u, --user                  Run as user
      -g, --group                 Run as group
      -p, --pid                   Alternate PID path
      -C, --firstrun              If no user account exists then create one with
                                  no username and no password. Use with care as
                                  it will allow world-wide administrative access
                                  to your Tvheadend installation until you create or edit
                                  the access control from within the Tvheadend web interface.
      -a, --adapters              Only use specified DVB adapters (comma-separated, -1 = none)
          --satip_bindaddr        Specify bind address for SAT>IP server
          --satip_rtsp            SAT>IP RTSP port number for server
                                  (default: -1 = disable, 0 = webconfig, standard port is 554)
          --nosatip               Disable SAT>IP client
          --satip_xml             URL with the SAT>IP server XML location
    
    Server connectivity
    
      -6, --ipv6                  Listen on IPv6
      -b, --bindaddr              Specify bind address
          --http_port             Specify alternative http port
          --http_root             Specify alternative http webroot
          --htsp_port             Specify alternative htsp port
          --htsp_port2            Specify extra htsp port
          --useragent             Specify User-Agent header for the http client
          --xspf                  Use XSPF playlist instead of M3U
    
    Debug options
    
      -d, --stderr                Enable debug on stderr
      -n, --nostderr              Disable debug on stderr
      -s, --syslog                Enable debug to syslog
      -S, --nosyslog              Disable syslog (all messages)
      -l, --logfile               Enable debug to file
          --debug                 Enable debug subsystems
          --trace                 Enable trace subsystems
          --subsystems            List subsystems
          --fileline              Add file and line numbers to debug
          --threadid              Add the thread ID to debug
          --libav                 More verbose libav log
          --uidebug               Enable web UI debug (non-minified JS)
      -A, --abort                 Immediately abort
      -D, --dump                  Enable coredumps for daemon
          --noacl                 Disable all access control checks
          --nobat                 Disable DVB bouquets
      -j, --join                  Subscribe to a service permanently
    
    Testing options
    
          --tsfile_tuners         Number of tsfile tuners
          --tsfile                tsfile input (mux file)
          --tprofile              Gather timing statistics for the code
          --thrdebug              Thread debugging
    
    For more information please visit the Tvheadend website:
    https://tvheadend.org
    
    ** Press ANY KEY to close this window ** 

     

    Habe docker service mal gestopt und neu gestartet, auch unraid nochmal neu gebootet, keine Änderung.

     

    Syslog sieht so aus.

     

    Aug 15 10:56:15 unraid rc.docker: tvheadend: started succesfully!
    Aug 15 10:56:15 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface vethdc8c431.IPv6 with address fe80::80e2:26ff:fed4:32b6.
    Aug 15 10:56:15 unraid avahi-daemon[12747]: New relevant interface vethdc8c431.IPv6 for mDNS.
    Aug 15 10:56:15 unraid avahi-daemon[12747]: Registering new address record for fe80::80e2:26ff:fed4:32b6 on vethdc8c431.*.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface veth1811f3b.IPv6 with address fe80::ac2a:c2ff:feb3:6a8b.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: New relevant interface veth1811f3b.IPv6 for mDNS.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Registering new address record for fe80::ac2a:c2ff:feb3:6a8b on veth1811f3b.*.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface veth9d324cf.IPv6 with address fe80::7465:a1ff:fec3:6727.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: New relevant interface veth9d324cf.IPv6 for mDNS.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Registering new address record for fe80::7465:a1ff:fec3:6727 on veth9d324cf.*.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:5aff:fe86:fb9d.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: New relevant interface docker0.IPv6 for mDNS.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Registering new address record for fe80::42:5aff:fe86:fb9d on docker0.*.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface veth798940b.IPv6 with address fe80::b818:3cff:feed:627d.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: New relevant interface veth798940b.IPv6 for mDNS.
    Aug 15 10:56:16 unraid avahi-daemon[12747]: Registering new address record for fe80::b818:3cff:feed:627d on veth798940b.*.
    Aug 15 10:56:19 unraid Parity Check Tuning: Send notification: Array operation restarted: Automatic Correcting Parity Check (18.7% completed)  (18.7% completed)
    Aug 15 10:56:19 unraid Parity Check Tuning: Send notification: Automatic unRaid Automatic Correcting Parity Check will be started: Unclean shutdown detected  (18.7% completed)
    Aug 15 10:56:20 unraid kernel: docker0: port 4(veth798940b) entered disabled state
    Aug 15 10:56:20 unraid kernel: veth8a3f435: renamed from eth0
    Aug 15 10:56:20 unraid avahi-daemon[12747]: Interface veth798940b.IPv6 no longer relevant for mDNS.
    Aug 15 10:56:20 unraid avahi-daemon[12747]: Leaving mDNS multicast group on interface veth798940b.IPv6 with address fe80::b818:3cff:feed:627d.
    Aug 15 10:56:20 unraid kernel: docker0: port 4(veth798940b) entered disabled state
    Aug 15 10:56:20 unraid kernel: device veth798940b left promiscuous mode
    Aug 15 10:56:20 unraid kernel: docker0: port 4(veth798940b) entered disabled state
    Aug 15 10:56:20 unraid avahi-daemon[12747]: Withdrawing address record for fe80::b818:3cff:feed:627d on veth798940b.
    Aug 15 10:56:24 unraid unassigned.devices: Mounting 'Auto Mount' Remote Shares...
    Aug 15 10:56:24 unraid unassigned.devices: Remote Share '10.253.1.2:/mnt/user/filme' is not set to auto mount.
    Aug 15 11:00:59 unraid flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
    Aug 15 11:01:22 unraid kernel: docker0: port 4(veth8c511ff) entered blocking state
    Aug 15 11:01:22 unraid kernel: docker0: port 4(veth8c511ff) entered disabled state
    Aug 15 11:01:22 unraid kernel: device veth8c511ff entered promiscuous mode
    Aug 15 11:01:23 unraid kernel: eth0: renamed from veth7079779
    Aug 15 11:01:23 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8c511ff: link becomes ready
    Aug 15 11:01:23 unraid kernel: docker0: port 4(veth8c511ff) entered blocking state
    Aug 15 11:01:23 unraid kernel: docker0: port 4(veth8c511ff) entered forwarding state
    Aug 15 11:01:24 unraid avahi-daemon[12747]: Joining mDNS multicast group on interface veth8c511ff.IPv6 with address fe80::c8e9:e0ff:fea1:c56b.
    Aug 15 11:01:24 unraid avahi-daemon[12747]: New relevant interface veth8c511ff.IPv6 for mDNS.
    Aug 15 11:01:24 unraid avahi-daemon[12747]: Registering new address record for fe80::c8e9:e0ff:fea1:c56b on veth8c511ff.*.
    Aug 15 11:01:35 unraid kernel: docker0: port 4(veth8c511ff) entered disabled state
    Aug 15 11:01:35 unraid kernel: veth7079779: renamed from eth0
    Aug 15 11:01:35 unraid avahi-daemon[12747]: Interface veth8c511ff.IPv6 no longer relevant for mDNS.
    Aug 15 11:01:35 unraid avahi-daemon[12747]: Leaving mDNS multicast group on interface veth8c511ff.IPv6 with address fe80::c8e9:e0ff:fea1:c56b.
    Aug 15 11:01:35 unraid kernel: docker0: port 4(veth8c511ff) entered disabled state
    Aug 15 11:01:35 unraid kernel: device veth8c511ff left promiscuous mode
    Aug 15 11:01:35 unraid kernel: docker0: port 4(veth8c511ff) entered disabled state
    Aug 15 11:01:35 unraid avahi-daemon[12747]: Withdrawing address record for fe80::c8e9:e0ff:fea1:c56b on veth8c511ff.

     

    Also der Docker wird gestartet und schließt sich nach wenigen Sekunden wieder, bevor ich in die Console komme oder auch Webinterface. Jemand eine idee wie ich vorgehen kann bei der Fehlersuche ?

  12. I use no transcoding / streaming, just plain playback from unRAID files with Nvidia Shield + Kodi. Files are scraped with Ember Media Manager.

     

    But a real deduplication does not care about the software on top 🙂

  13. As i am storing a huge movie collection, the scraper download pictures of actors as example based on the titles. So some of the pictures i have nearly 100 times on my unraid as that actor played in 100 movies. A real dedup with symbolic links would be very nice :)

    • Like 1
  14. I upgraded from RC2 to RC4 and network went corrupt. Downgrade to RC2 the problem stayed. So i created new usb sticks with demo version and startet with 6.9.2 -> RC2 -> RC4. Confirmed, with RC4 the USB 2.5gbit NIC is no more recognized.

    RTL8156B Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN

  15. ja, soweit war ich nun auch vor 15 Minuten :) 

    hatte wp-quick up und down gefunden etc aber ...der job ist invalide wenn die Laufwerke nicht von anfang an da sind. Schau mir nun also backup scripte an die einfach auf cron basieren, den "fehlerfreien" rsync Befehl hat mir lucky backup ja erstellt :)

     

    *edit* es hilft da es mir zumindest beim loslaufen fehlerfrei VPN aufbaut und das Laufwerk mounted, weil permanent mounten kann ich es ja nicht. Nun muss "nur" noch schauen das der Job in weniger als 24 Stunden fertig ist

  16. Hi everyone,

    I backup a fair amount to a second server once a week, but it is behind "classic" DSL with forced disconnection every night at almost identical times. Now the backups partly don't work when they run into the forced disconnection. The connection breaks down, VPN breaks down and a remote mount hangs, half-finished files hang around.

     Now I have seen that luckybackup supports scripts before and after the job.

    How can I script the VPN connection and then mount the share, and unmount the share cleanly after the job and disable VPN ?
     
    Thanks a lot

    Patrick

  17. 2 days later. It seems the issue was the following. Somewhen during the luckybackup work the GUI was minimized. Then with the VNC settings was tested with scaling, the scroll bar disappeared. The old laptop where i have remote access to access the unraid server has 1200x800 resolution. Now with the wrong scaling applied it was even after updating no task bar visible to bring the application to forground. Most likely everyhing was running flawless, just "off" screen and minimized.

×
×
  • Create New...