leawhig

Members
  • Posts

    67
  • Joined

Posts posted by leawhig

  1. On 9/4/2023 at 5:32 AM, wdnaser said:

    Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly.
     

    图像 4.png

    Can someone reply to my message?

  2. Just now, wdnaser said:

    Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly.
     

    图像 4.png

    The issue only seems to occur when I attempt to upload the same file again. This problem went unnoticed with my previous file uploads, which got corrupted as well.

  3. Hi! I've run into a rather frustrating issue. Whenever I try to upload files using this plugin, no matter what I do, the uploaded files end up getting corrupted. What's even stranger is that the file size always becomes 2.1MB, and they can't be opened correctly.
     

    图像 4.png

  4. On 3/23/2023 at 5:53 AM, insomnia417 said:

    这个界面是在的,最右侧的不见了,

    image.thumb.png.7e3e73128f149ce1a7dad242d5e86613.png

    请问大佬Docker 页面要怎么调成这种画面? 我是6.10.3

    设定怎么调都调不出来

  5. 2 hours ago, ich777 said:

    Again, this is the wrong thread for that as explained above, this package only includes the DVB drivers from LibreELEC and not capture card drivers.

    Last question, can I use an undriven device in Docker? (Container has the driver)

     

    Where do I go to ask Capture questions?

  6. On 1/6/2023 at 3:11 AM, ich777 said:

    What is the output from:

    ls -l /sys/bus/usb/drivers/snd-usb-audio/

     

    /bin/ls: cannot access '/sys/bus/usb/drivers/snd-usb-audio/': No such file or directory

     

    But  /sys/bus/usb/drivers has something

    图像 1.png

  7. 6 hours ago, alturismo said:

    you want to decode ... what ? the file which is written then ?

     

    you have some stb, mediaplayer, ... connected via hdmi or component to the card and then via USB to your server, this is something tvheadend wont handle anyway as its a tvbackend server expecting a dvb input (.ts stream or a m3u or HLS piped via ffmpeg or ...) but not a capture card device writing a file to the disc and then serve it as a "live" stream.

     

    so you should use this in a vm while passing through this device and use a software which can handle this device.

     

    图像 5.png

  8. 4 hours ago, ich777 said:

    Is this a HDMI capture device?

     

    Can you post a link to the product page please?

    This device doesn't install drive in linux release

    Normally, it should be included in LibreELEC.

  9. Want to decode hardware to Docker tvheadend

    But this plugin doesn't seem to work on MacroSilicon USB Video

     

    (Tried using /dev/bus/usb/003/003) but it doesn't work lol.

     

    This is really weird, it works on Raspberry pi & other LINUX.

  10. I want to use "MacroSilicon USB Video" to make the tvheadend hard to decode

    But unfortunately, this device is not supported by any driver on plugin.

     

    Can I add the driver of this device to the plugin? 

    Thanks a lot!

  11. On 10/17/2022 at 4:41 PM, BarbaGrump said:

    I'm to getting this today in 6.11 after trying to add a isolated bridge:

    1. virsh net-define /tmp/isolated0.xml

    2. virsh net-start isolated0

    3. virsh net-autostart --network isolated0

     

    /tmp/isolated0.xml:

    <network>
      <name>isolated0</name>
      <bridge name="virbr99" stp="on" delay="0"/>
    </network>

     

    Then after restarting VM-service - root: '/mnt/user/system/libvirt.img' is in-use, cannot mount

     

    Stopping docker-service, starting vm-service, starting docker-service works.

     

    Also, destroy and undefine the created network doesn't help 

    Also2, the virsh net-autostart --network isolated0 does not seems to work...I still have to start the network manually, but thats another thread I guess...

     

    Edit:

    Rebooted and dockers, VMs started as expected. But UR reported an unclean shutdown and started parity-check...not sure iff its connected, but if the /mnt/user/system/libvirt.img is in use, umount maybe unsuccessfull?

     

    Edit2:

    To make a custom defined network autostart, just make a symlink in /etc/libvirt/networks/autostart pointing to ../<whatever your network is called>

    Unfortunately, the silver lining is that the reboot restored normalcy

    But like this guy, after the reboot:UR reported an unclean shutdown 

  12. On 12/29/2021 at 3:32 AM, mgutt said:

    The same happened to me after stopping the VM service, renaming the "domains" share to "vdisks" and restarting the VM service.

     

    What I tried:

     

    root@thoth:~# umount /mnt/cache/libvirt/libvirt.img
    umount: /mnt/cache/libvirt/libvirt.img: not mounted.
    root@thoth:~# /usr/local/sbin/mount_image '/mnt/cache/libvirt/libvirt.img' /etc/libvirt 1
    /mnt/cache/libvirt/libvirt.img is in-use, cannot mount
    root@thoth:~# fuser -c /mnt/cache/libvirt/libvirt.img
    /mnt/cache/libvirt/libvirt.img:  6030m  6055m  7314m  7574m  8400m  8520m  8521m  8523m  8528m  8529m  8554m  8557m  8581m  8596m  8646m  8647m  8648m  8649m  8729m  8841m  8842m  8845m  9040m  9045m 12060m 12144m 16103m 16106m 16107m 16109m 16110m 16285m 16301m 16314m 16338m 16339m 16374m 16400m 16424cm 16446m 16455m 16479m 16488m 16658m 16659m 16662m 16663m 16678m 16893m 17537m 18805m 18818m 19679m 19680m 19681m 19682m 19683m 19684m 19685m 19686m 19687m 19688m 19689m 19690m 19691m 31769m 31843m 32152m 32155m 32195cm 32321m
    root@thoth:~# ps -p 6030
      PID TTY          TIME CMD
     6030 ?        00:00:39 dockerd
    root@thoth:~# ps -p 6055
      PID TTY          TIME CMD
     6055 ?        00:03:22 containerd
    root@thoth:~# ps -p 7314
      PID TTY          TIME CMD
     7314 ?        00:00:00 s6-svscan
    root@thoth:~# ps -p 7574
      PID TTY          TIME CMD
     7574 ?        00:00:00 s6-supervise
    root@thoth:~# ps -p 8400
      PID TTY          TIME CMD
     8400 ?        00:00:00 dumb-init
    root@thoth:~# ps -p 32321
      PID TTY          TIME CMD
    32321 ?        00:00:06 Plex Tuner Serv
    root@thoth:~# 

     

    Then while and after stopping the docker service:

    root@thoth:~# fuser -c /mnt/cache/libvirt/libvirt.img
    /mnt/cache/libvirt/libvirt.img:  5651m  6030m  6055m
    root@thoth:~# ps -p 5651
      PID TTY          TIME CMD
     5651 ?        00:00:00 s6-sync
    root@thoth:~# ps -p 6030
      PID TTY          TIME CMD
     6030 ?        00:00:39 dockerd
    root@thoth:~# ps -p 6055
      PID TTY          TIME CMD
     6055 ?        00:03:23 containerd
    root@thoth:~# fuser -c /mnt/cache/libvirt/libvirt.img
    /mnt/cache/libvirt/libvirt.img:  5651m  6030m  6055m
    root@thoth:~# fuser -c /mnt/cache/libvirt/libvirt.img
    root@thoth:~# 

     

     

    Then I started the docker service again:

    fuser -c /mnt/cache/libvirt/libvirt.img
    /mnt/cache/libvirt/libvirt.img:  8869m  8893m  9644m  9788m 10066m 10067m 10071m 10072m 10088m 10096m 10197m 10198m 10199m 10200m 10201m 10202m 10203m 10204m 10205m 10206m 10207m 10208m 10209m 10210m 10271m 10630m 10788m 10789m 10790m 10793m 10794m 10806m 10807m 10825m 10841m 10842m 10843m 10844m 10925m 11227m 11259m 11262m 11325m 11472cm 11474m 11570m 11571m 11572m 11729m 11745m 11754m 11755m 11757m 11762m 11826m 11863cm

     

    And started successfully the VM service, too (yes completely the same output):

    fuser -c /mnt/cache/libvirt/libvirt.img
    /mnt/cache/libvirt/libvirt.img:  8869m  8893m  9644m  9788m 10066m 10067m 10071m 10072m 10088m 10096m 10197m 10198m 10199m 10200m 10201m 10202m 10203m 10204m 10205m 10206m 10207m 10208m 10209m 10210m 10271m 10630m 10788m 10789m 10790m 10793m 10794m 10806m 10807m 10825m 10841m 10842m 10843m 10844m 10925m 11227m 11259m 11262m 11325m 11472cm 11474m 11570m 11571m 11572m 11729m 11745m 11754m 11755m 11757m 11762m 11826m 11863cm

     

    I'd say it has nothing to do with the output of fuser. Must be something else wrong.

    UNRAID 6.10.3

    The instruction output is the same as this guy.

    "It's still the same problem, it seems to be tied up by a lot of processes."

     

    图像 7.png

  13. Plugin: Unassigned Devices (UD)

    我有两台UNRAID

    現在需要让我的其中一台UNRAID挂载另一台UNRAID

    已经确认另一台UNRAID是正常的 (我的Windows和Linux皆可正常挂载)

     

    问题:"新增完后只能在使用一次,重开机后就不能使用"

    必须要将其删除后才再次正常使用!!

     

    附Debug图片

    1.可以按橘色的MOUNT按钮,但无法正常挂载

    2.系统SAMBA log

    3.unassigned.devices log

    图像 17.png

    图像 16.png

    图像 18.png