Technikte

Members
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

 Content Type 

Posts posted by Technikte

    WireGuard - VPN Tunneled Access to a commercial VPN provider

    in Plugin Support

    Posted · Edited by Technikte

    I am not quite sure about a DNS Server Problem but it seems like it doenst work. I am on unraid Version: 6.10.0-rc7.

     

    The config from my provider. 

    [Interface]
PrivateKey = xxx
Address = 10.aaa.bbb.128/32
DNS = 100.xxx.xxx.3

[Peer]
PublicKey = yyy
AllowedIPs = 0.0.0.0/0
Endpoint = 194.aaa.bbb.33:51820


    The imported config in unraid. 

    [Interface]
PrivateKey=xxx
Address=10.aaa.bbb.128
PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started'
PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped'
PostUp=ip -4 route flush table 200
PostUp=ip -4 route add default via 10.aaa.bbb.128 table 200
PostUp=ip -4 route add 192.xxx.0.0/16 via 192.xxx.1.1 table 200
PostDown=ip -4 route flush table 200
PostDown=ip -4 route add unreachable default table 200
PostDown=ip -4 route add 192.xxx.0.0/16 via 192.xxx.1.1 table 200

[Peer]
PublicKey=yyy
Endpoint=194.aaa.bbb.33:51820
AllowedIPs=0.0.0.0/0
PersistentKeepalive=60


    I have even tried to manually add to "Peer DNS server:" but it doenst seems to work. Any idea to fix this, it seems to be the cause of dns leaks inside the docker containers.

    [Plugin] DVB-Driver

    in Plugin Support

    Posted · Edited by Technikte

    22 minutes ago, ich777 said:

    Do you think it's caused by the Plugin/DVB Stick? Can you post your Diagnostics please (Tools -> Diagnostics -> Download -> drop the downloaded zip file here in the text box - you can also send me the Diagnostics via PM if you feel more comfortable to do it that way ;) ).

     

    This seems like a unstable connection or it fall from the bus.

    Have you already tried another USB port?

     

    Can you remember since when you got that issue, sounds like it was not always the case that the server crashes and the DVB Stick drops.

     

    I will send diagnostics.

     

    I look like it, the connection breaks and a call trace happens and so. In the 6.10 rc1 its seems like it wouldnt crash instant with this, before in 6.09 it would crash every time the sticks acts buggy.

     

    I cant quite remember, I changed now port because before I was using a usb 3.0 motherboard extension.

     

    [Plugin] DVB-Driver

    in Plugin Support

    Posted · Edited by Technikte

    Hi,

    I have a problem since quite some time with my xbox one tv dvb-c stick. After some time my complete host crash and needs a hard reboot. 

    https://www.linuxtv.org/wiki/index.php/Xbox_One_Digital_TV_Tuner

    Often I can see in the tvheadend docker..

    Quote

    2021-09-05 18:51:30.194 [WARNING] linuxdvb: Panasonic MN88472 #1 : DVB-C #0 - poll TIMEOUT

     

    And in the syslog this looks like this.

    Quote

    Sep  5 18:13:27 ByteNet kernel: usb 1-7: USB disconnect, device number 2
    Sep  5 18:13:27 ByteNet kernel: BUG: kernel NULL pointer dereference, address: 0000000000000028
    Sep  5 18:13:27 ByteNet kernel: #PF: supervisor read access in kernel mode
    Sep  5 18:13:27 ByteNet kernel: #PF: error_code(0x0000) - not-present page
    Sep  5 18:13:27 ByteNet kernel: PGD 0 P4D 0 
    Sep  5 18:13:27 ByteNet kernel: Oops: 0000 [#1] SMP NOPTI
    Sep  5 18:13:27 ByteNet kernel: CPU: 20 PID: 38156 Comm: kdvb-ad-1-fe-0 Tainted: P           O      5.13.8-Unraid #1
    Sep  5 18:13:27 ByteNet kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X399 Taichi, BIOS P3.90 12/04/2019
    Sep  5 18:13:27 ByteNet kernel: RIP: 0010:mn88472_sleep+0x1e/0x58 [mn88472]
    Sep  5 18:13:27 ByteNet kernel: Code: 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 44 00 00 53 48 8b 87 00 03 00 00 ba 30 00 00 00 be 0c 00 00 00 48 8b 98 98 00 00 00 <48> 8b 7b 28 e8 fe 29 ee e0 85 c0 75 2b 48 8b 7b 28 ba 30 00 00 00
    Sep  5 18:13:27 ByteNet kernel: RSP: 0018:ffffc90003b4fe68 EFLAGS: 00010282
    Sep  5 18:13:27 ByteNet kernel: RAX: ffff88811233e000 RBX: 0000000000000000 RCX: 0000000000000000
    Sep  5 18:13:27 ByteNet kernel: RDX: 0000000000000030 RSI: 000000000000000c RDI: ffff8881025a7830
    Sep  5 18:13:27 ByteNet kernel: RBP: ffff88811233d800 R08: ffff88903d52a8b0 R09: ffff88903d52a8b0
    Sep  5 18:13:27 ByteNet kernel: R10: 0000000000000000 R11: fefefefefefefeff R12: 0000000000000001
    Sep  5 18:13:27 ByteNet kernel: R13: ffff88811233d9b8 R14: 0000000000000000 R15: ffff88811233d9e0
    Sep  5 18:13:27 ByteNet kernel: FS:  0000000000000000(0000) GS:ffff88903d500000(0000) knlGS:0000000000000000
    Sep  5 18:13:27 ByteNet kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep  5 18:13:27 ByteNet kernel: CR2: 0000000000000028 CR3: 00000001022d4000 CR4: 00000000003506e0
    Sep  5 18:13:27 ByteNet kernel: Call Trace:
    Sep  5 18:13:27 ByteNet kernel: dvb_usb_fe_sleep+0x36/0x4d [dvb_usb]
    Sep  5 18:13:27 ByteNet kernel: dvb_frontend_thread+0x473/0x4d4 [dvb_core]
    Sep  5 18:13:27 ByteNet kernel: ? init_wait_entry+0x29/0x29
    Sep  5 18:13:27 ByteNet kernel: ? dvb_frontend_get_event.isra.0+0x184/0x184 [dvb_core]
    Sep  5 18:13:27 ByteNet kernel: kthread+0xdf/0xe4
    Sep  5 18:13:27 ByteNet kernel: ? set_kthread_struct+0x32/0x32
    Sep  5 18:13:27 ByteNet kernel: ret_from_fork+0x22/0x30
    Sep  5 18:13:27 ByteNet kernel: Modules linked in: dm_mod dax vhci_hcd usbip_host usbip_core xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap nvidia_modeset(PO) nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat br_netfilter xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 md_mod nvidia(PO) drm backlight agpgart nct6775 hwmon_vid tda18250 mn88472 rtl2832_sdr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev r820t rtl2832 i2c_mux regmap_i2c dvb_usb_dib0700 dib3000mc dib9000 dib0070 dib7000m dibx000_common dib0090 dvb_usb_rtl28xxu dvb_usb dvb_usb_v2 dvb_core mc corefreqk(O) efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit wmi_bmof mxm_wmi edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd nvme btusb cryptd btrtl btbcm rapl nvme_core btintel cdc_acm
    Sep  5 18:13:27 ByteNet kernel: bluetooth ecdh_generic k10temp i2c_piix4 i2c_core ccp ecc ahci wmi libahci button acpi_cpufreq [last unloaded: i2c_algo_bit]
    Sep  5 18:13:27 ByteNet kernel: CR2: 0000000000000028
    Sep  5 18:13:27 ByteNet kernel: ---[ end trace 0061b763dc503d32 ]---
    Sep  5 18:13:27 ByteNet kernel: RIP: 0010:mn88472_sleep+0x1e/0x58 [mn88472]
    Sep  5 18:13:27 ByteNet kernel: Code: 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 44 00 00 53 48 8b 87 00 03 00 00 ba 30 00 00 00 be 0c 00 00 00 48 8b 98 98 00 00 00 <48> 8b 7b 28 e8 fe 29 ee e0 85 c0 75 2b 48 8b 7b 28 ba 30 00 00 00
    Sep  5 18:13:27 ByteNet kernel: RSP: 0018:ffffc90003b4fe68 EFLAGS: 00010282
    Sep  5 18:13:27 ByteNet kernel: RAX: ffff88811233e000 RBX: 0000000000000000 RCX: 0000000000000000
    Sep  5 18:13:27 ByteNet kernel: RDX: 0000000000000030 RSI: 000000000000000c RDI: ffff8881025a7830
    Sep  5 18:13:27 ByteNet kernel: RBP: ffff88811233d800 R08: ffff88903d52a8b0 R09: ffff88903d52a8b0
    Sep  5 18:13:27 ByteNet kernel: R10: 0000000000000000 R11: fefefefefefefeff R12: 0000000000000001
    Sep  5 18:13:27 ByteNet kernel: R13: ffff88811233d9b8 R14: 0000000000000000 R15: ffff88811233d9e0
    Sep  5 18:13:27 ByteNet kernel: FS:  0000000000000000(0000) GS:ffff88903d500000(0000) knlGS:0000000000000000
    Sep  5 18:13:27 ByteNet kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep  5 18:13:27 ByteNet kernel: CR2: 0000000000000028 CR3: 00000001022d4000 CR4: 00000000003506e0
    Sep  5 18:13:27 ByteNet kernel: usb 1-7: dvb_frontend_stop: warning: thread 000000004e08ff08 won't exit
    Sep  5 18:14:33 ByteNet ool www[102152]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config
    Sep  5 18:14:36 ByteNet rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="102212" x-info="https://www.rsyslog.com"] start
    Sep  5 18:16:04 ByteNet kernel: BUG: unable to handle page fault for address: ffffffff8172dede
    Sep  5 18:16:04 ByteNet kernel: #PF: supervisor write access in kernel mode
    Sep  5 18:16:04 ByteNet kernel: #PF: error_code(0x0003) - permissions violation
    Sep  5 18:16:04 ByteNet kernel: PGD 600e067 P4D 600e067 PUD 600f063 PMD 56001e1 
    Sep  5 18:16:04 ByteNet kernel: Oops: 0003 [#2] SMP NOPTI
    Sep  5 18:16:04 ByteNet kernel: CPU: 6 PID: 38124 Comm: tvh:mtimer Tainted: P      D    O      5.13.8-Unraid #1
    Sep  5 18:16:04 ByteNet kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X399 Taichi, BIOS P3.90 12/04/2019
    Sep  5 18:16:04 ByteNet kernel: RIP: 0010:_raw_spin_lock_irqsave+0x1f/0x33
    Sep  5 18:16:04 ByteNet kernel: Code: 8f ff 48 8b 04 24 48 83 c4 10 c3 0f 1f 44 00 00 41 54 51 48 89 3c 24 e8 ce 72 8f ff 49 89 c4 31 c0 48 8b 3c 24 ba 01 00 00 00  0f b1 17 74 07 89 c6 e8 ca 72 8f ff 4c 89 e0 5a 41 5c c3 cc cc
    Sep  5 18:16:04 ByteNet kernel: RSP: 0018:ffffc900039b7db0 EFLAGS: 00010046
    Sep  5 18:16:04 ByteNet kernel: RAX: 0000000000000000 RBX: ffff8881025a7830 RCX: 0000000000000000
    Sep  5 18:16:04 ByteNet kernel: RDX: 0000000000000001 RSI: 0000000080046f45 RDI: ffffffff8172dede
    Sep  5 18:16:04 ByteNet kernel: RBP: ffffffff8172dede R08: 000014cf5b4f5f8c R09: 0000000000000000
    Sep  5 18:16:04 ByteNet kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000286
    Sep  5 18:16:04 ByteNet kernel: R13: 0000000000000002 R14: ffff888742c36500 R15: ffffc900039b7e38
    Sep  5 18:16:04 ByteNet kernel: FS:  000014cf5b4f6b20(0000) GS:ffff88903d180000(0000) knlGS:0000000000000000
    Sep  5 18:16:04 ByteNet kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep  5 18:16:04 ByteNet kernel: CR2: ffffffff8172dede CR3: 00000007404ce000 CR4: 00000000003506e0
    Sep  5 18:16:04 ByteNet kernel: Call Trace:
    Sep  5 18:16:04 ByteNet kernel: ? addrconf_exit_net+0x39/0x45
    Sep  5 18:16:04 ByteNet kernel: down_interruptible+0x11/0x44
    Sep  5 18:16:04 ByteNet kernel: ? addrconf_exit_net+0x39/0x45
    Sep  5 18:16:04 ByteNet kernel: dvb_frontend_do_ioctl+0x44/0xb9 [dvb_core]
    Sep  5 18:16:04 ByteNet kernel: dvb_usercopy+0xbf/0x136 [dvb_core]
    Sep  5 18:16:04 ByteNet kernel: ? dvb_frontend_compat_ioctl+0x94/0x94 [dvb_core]
    Sep  5 18:16:04 ByteNet kernel: ? _raw_spin_unlock_irqrestore+0x19/0x1b
    Sep  5 18:16:04 ByteNet kernel: ? get_sd_balance_interval+0x19/0x3c
    Sep  5 18:16:04 ByteNet kernel: ? rebalance_domains+0x1f9/0x22f
    Sep  5 18:16:04 ByteNet kernel: dvb_frontend_ioctl+0x22/0x25 [dvb_core]
    Sep  5 18:16:04 ByteNet kernel: vfs_ioctl+0x1f/0x2d
    Sep  5 18:16:04 ByteNet kernel: __do_sys_ioctl+0x51/0x74
    Sep  5 18:16:04 ByteNet kernel: do_syscall_64+0x63/0x76
    Sep  5 18:16:04 ByteNet kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
    Sep  5 18:16:04 ByteNet kernel: RIP: 0033:0x14cf5fdcf697
    Sep  5 18:16:04 ByteNet kernel: Code: 63 f6 48 8d 44 24 60 48 89 54 24 30 48 89 44 24 10 48 8d 44 24 20 48 89 44 24 18 b8 10 00 00 00 c7 44 24 08 10 00 00 00 0f 05 <48> 63 f8 e8 fd ad fe ff 48 83 c4 58 c3 0f be 05 d7 1b 06 00 c3 53
    Sep  5 18:16:04 ByteNet kernel: RSP: 002b:000014cf5b4f5ef0 EFLAGS: 00000206 ORIG_RAX: 0000000000000010
    Sep  5 18:16:04 ByteNet kernel: RAX: ffffffffffffffda RBX: 000055e4625146e0 RCX: 000014cf5fdcf697
    Sep  5 18:16:04 ByteNet kernel: RDX: 000014cf5b4f5f8c RSI: ffffffff80046f45 RDI: 0000000000000018
    Sep  5 18:16:04 ByteNet kernel: RBP: 00000000000f4240 R08: 8080808080808000 R09: ffcfdcdfbcd2bda9
    Sep  5 18:16:04 ByteNet kernel: R10: fefefefefefefeff R11: 0000000000000206 R12: 000014cf5b4f61d0
    Sep  5 18:16:04 ByteNet kernel: R13: 0000000000000001 R14: 000055e462492710 R15: 000055e4624921a0
    Sep  5 18:16:04 ByteNet kernel: Modules linked in: dm_mod dax vhci_hcd usbip_host usbip_core xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap nvidia_modeset(PO) nvidia_uvm(PO) veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat br_netfilter xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 md_mod nvidia(PO) drm backlight agpgart nct6775 hwmon_vid tda18250 mn88472 rtl2832_sdr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev r820t rtl2832 i2c_mux regmap_i2c dvb_usb_dib0700 dib3000mc dib9000 dib0070 dib7000m dibx000_common dib0090 dvb_usb_rtl28xxu dvb_usb dvb_usb_v2 dvb_core mc corefreqk(O) efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit wmi_bmof mxm_wmi edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd nvme btusb cryptd btrtl btbcm rapl nvme_core btintel cdc_acm
    Sep  5 18:16:04 ByteNet kernel: bluetooth ecdh_generic k10temp i2c_piix4 i2c_core ccp ecc ahci wmi libahci button acpi_cpufreq [last unloaded: i2c_algo_bit]
    Sep  5 18:16:04 ByteNet kernel: CR2: ffffffff8172dede
    Sep  5 18:16:04 ByteNet kernel: ---[ end trace 0061b763dc503d33 ]---
    Sep  5 18:16:04 ByteNet kernel: RIP: 0010:mn88472_sleep+0x1e/0x58 [mn88472]
    Sep  5 18:16:04 ByteNet kernel: Code: 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 44 00 00 53 48 8b 87 00 03 00 00 ba 30 00 00 00 be 0c 00 00 00 48 8b 98 98 00 00 00 <48> 8b 7b 28 e8 fe 29 ee e0 85 c0 75 2b 48 8b 7b 28 ba 30 00 00 00
    Sep  5 18:16:04 ByteNet kernel: RSP: 0018:ffffc90003b4fe68 EFLAGS: 00010282
    Sep  5 18:16:04 ByteNet kernel: RAX: ffff88811233e000 RBX: 0000000000000000 RCX: 0000000000000000
    Sep  5 18:16:04 ByteNet kernel: RDX: 0000000000000030 RSI: 000000000000000c RDI: ffff8881025a7830
    Sep  5 18:16:04 ByteNet kernel: RBP: ffff88811233d800 R08: ffff88903d52a8b0 R09: ffff88903d52a8b0
    Sep  5 18:16:04 ByteNet kernel: R10: 0000000000000000 R11: fefefefefefefeff R12: 0000000000000001
    Sep  5 18:16:04 ByteNet kernel: R13: ffff88811233d9b8 R14: 0000000000000000 R15: ffff88811233d9e0
    Sep  5 18:16:04 ByteNet kernel: FS:  000014cf5b4f6b20(0000) GS:ffff88903d180000(0000) knlGS:0000000000000000
    Sep  5 18:16:04 ByteNet kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep  5 18:16:04 ByteNet kernel: CR2: ffffffff8172dede CR3: 00000007404ce000 CR4: 00000000003506e0

    Quote

    Sep  5 18:51:32 ByteNet kernel: dvb-usb: Microsoft Xbox One Digital TV Tuner successfully deinitialized and disconnected.
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager usb_remove  Microsoft_Corp._Xbox_USB_Tuner_006379040615 /dev/bus/usb/001/002 001 002 
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager Device Match Microsoft_Corp._Xbox_USB_Tuner_006379040615 vm:   001 002 
    Sep  5 18:51:33 ByteNet usb_manager: usb_manager virsh called  1 2 error: Failed to get option 'domain': Option argument is empty  
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager Disconnect  Microsoft_Corp._Xbox_USB_Tuner_006379040615 vm:  nostate 001 002 
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager Removed Microsoft_Corp._Xbox_USB_Tuner_006379040615 vm:  nostate 001 002
    Sep  5 18:51:33 ByteNet kernel: usb 1-7: new high-speed USB device number 6 using xhci_hcd
    Sep  5 18:51:33 ByteNet kernel: dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
    Sep  5 18:51:33 ByteNet kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    Sep  5 18:51:33 ByteNet kernel: dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
    Sep  5 18:51:33 ByteNet kernel: usb 1-7: media controller created
    Sep  5 18:51:33 ByteNet kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
    Sep  5 18:51:33 ByteNet kernel: mn88472 3-0018: Panasonic MN88472 successfully identified
    Sep  5 18:51:33 ByteNet kernel: tda18250 3-0060: NXP TDA18250BHN/M successfully identified
    Sep  5 18:51:33 ByteNet kernel: usb 1-7: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)...
    Sep  5 18:51:33 ByteNet kernel: dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88472' registered.
    Sep  5 18:51:33 ByteNet kernel: dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager usb_add Microsoft_Corp._Xbox_USB_Tuner_006379040615 /dev/bus/usb/001/006 001 006
    Sep  5 18:51:33 ByteNet usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Microsoft_Corp._Xbox_USB_Tuner_006379040615 /dev/bus/usb/001/006 001 006 port 1-7

     

    Anyone else has problems with these xbox one tv sticks ?

    HBA Controller recommendation

    in Storage Devices and Controllers

    Posted

    Hello,
    I am looking for a controller that can address min. 15 SATA-3 HDD, so a controller for 16 Sata disks would be ok.

    Best would be a card with already set IT mode from the factory so that I do not have to reflash anything or the like.

    Price-wise it shouldn't be too extreme, since I'll probably wait anyway with the current price increases, or should be well available on the used market like ebay.


    I would be very grateful for a recommendation or other opinions and insights.

    Translated with www.DeepL.com/Translator (free version)

    [Plugin] CA User Scripts

    in Plugin Support

    Posted

    Is there any way to get rid of "Full logs for this script are available at /tmp/user.scripts/tmpScripts/xxxxxx/log.txt" in the log ?

    My script for ddns runs every 5 minutes for 24h/7day, so my log gets very long.

    If there is a better way to handle the log with a script that has a so short schedule ?

    USB Passthrough: device location changing

    in Docker Engine

    Posted

    On 8/5/2018 at 4:14 AM, MindRazorblade said:

    With a little bit of studying and experimentation I got this to work but I'm sure someone more experienced with udev would get this better I used the "User Scripts" app to setup a startup script that copies and refreshes the rules for the device so that the rules you setup in "99-usb-rules.rules" are loaded properly.

     

    Here it is: 

    
#!/bin/bash
# copy persistent script from usb drive to drive at startup
cp /boot/config/userFiles/99-usb-serial.rules /etc/udev/rules.d/
chmod 644 /etc/udev/rules.d/99-usb-serial.rules

# udav has likely run before the copy completes so udev needs its rules refreshed
udevadm control --reload-rules

# a reset of the device is needed so the rules just copied can take hold
udevadm trigger --attr-match=subsystem=tty

    I'm a little nervous about the last line resetting all tty subsystems since I wasn't able to get something like : 

    
udevadm trigger --attr-match=serial=0000:00:11.0

    to work for some reason after confirming the serial with: 

    
udevadm info -a -n /dev/ttyUSB1 | grep '{serial}' | head -n1

    Here are some links for education:

    http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/

    https://www.thegeekdiary.com/beginners-guide-to-udev-in-linux/

    http://reactivated.net/writing_udev_rules.html

    https://unix.stackexchange.com/questions/39370/how-to-reload-udev-rules-without-reboot

    http://www.reactivated.net/writing_udev_rules.html#example-printer

    https://askubuntu.com/questions/445735/why-do-my-udev-rules-run-if-i-use-udevadm-trigger-but-not-at-boot-time/635477

    https://www.linux.com/news/udev-introduction-device-management-modern-linux-system

     

    If you run into any commands that look like they're aren't installed be conscious that udev changed a bit since some of these were written and there are new commands for these (e.g. udevadm info instead of udevinfo).

     

     

    First thanks for your script. *Thumbs up*

    The other thing..I tried to get it succesfully running using UserScript (StartUp at first Array start) but didnt survived any reboot until I noticed that you are resting tty but I use SUBSYSTEM=="usb" so the correct syntax for this thread would be. 

    udevadm trigger --attr-match=subsystem=usb

    A short info in your post would have saved me 2 hours. :D

     

    Idea's mounting 2,5" SSD backside fan mount holes

    in Hardware

    Posted

    On 10/28/2018 at 9:36 PM, Jcloud said:

    Speaking in general, but there's always making a metal bracket, or 3D-printed shim, such that you could mount it to the to fan mounts and mount the 2.5" bays connect to the piece.  Unfortunately I don't know of a specific product to do what you would like to do.

     

    The idea with 3D printing is not bad and the finshed product should fit  my needs the most. Do you have any recommendation for an programm or free model website for beginner in 3D design ?

    Idea's mounting 2,5" SSD backside fan mount holes

    in Hardware

    Posted · Edited by Technikte

    Hi,

    I currently building my unraid server and have already most planned and/or installed. Now to the question..I have planned to install at max. config 15x 3,5" at the front in the 5-in-3 cage (pic 3.), but also at least 3x 2,5 SSD planned and thought maybe putting these behind the HDD cages (pic 5.). The easiest way would be to put some double side tape on it and stick to the side and/or the middle plane, but a litte bit more professional would be great. Since I bought the case (Lian Li PC-D600) used I got rid the original HDD cages and maybe reuse them to mount them somehow at the back (pic 1). I noticed then this wouldn't work since I could not get the drives in or out.

    Next Idea was to do the cage vertically (pic 2.) and this would work quite ok but not really usable mounting points in this orientation. I have got around max. 20cm (15cm more reasonable for airflow) space between the 3,5" cage and the backside of the case.

     

    Does anyone have an idea or do know a part like 2,5" cage that can be easily mount at 120/140mm fan mounting points ?

     

    My components that are important for the question:

    - Case PC-D600 (http://www.lian-li.com/pc-d600/)

    - 3,5" HDD cage MB155SP-B (https://www.icydock.de/goods.php?id=129)

     

    English is not my native language so please be forgiving. :)

    Ps. online store for parts I would only use EU ones..

     

    20181028_190252.jpg

    20181028_190312.jpg

    20181028_190351.jpg

    20181028_190549.jpg

    20181028_190614.jpg