Jump to content

dotn

Members
 View Profile  See their activity

  • Posts

    9

  • Joined

  • Last visited

 Content Type 

Posts posted by dotn

    Dynamix File Integrity plugin

    in Plugin Support

    Posted · Edited by dotn

    There are several unanswered questions regarding moving the export files to cache drive or another encrypted location. Does anybody find a proper solution to do that? Having complete list of files stored as an plain text on the USB drive is very bad idea from the security perspective.

    Firefox Sync Server

    in Docker Containers

    Posted

    Hi Jflo,

     

    you have an error in your template. It is not possible to disable new user account creation, which may be crucial functionality if you want to make your SyncServer available from the internet.

     

    The problem is in docker variable SYNCSERVER_ALLOW_NEW_USER, it should be SYNCSERVER_ALLOW_NEW_USERS

    see: https://github.com/mozilla-services/syncserver/blob/master/syncserver/__init__.py#L188

     

    Please fix it, it may save some debugging why the account creation is not disabled, for people who are using your template :)

    I can create pull request in your repository if you want.

     

    Thanks!

    • Thanks 1

    [SOLVED] Disabled Hard Drive - is it failing?

    in General Support

    Posted · Edited by dotn
    solved

    I've reused two 500GB old 2.5" drives from taken out from laptops in my unRAID server until I will get second WD RED 4TB (currently using only one as a parity drive).

     

    Today, older one of the 500GB was marked with red dot. I've disabled it, checked SMART. Because I did not see any errors, based on recommendations in other topics in the forum, I double check the HDD power supply and replaced SATA cable for a new one.

     

    Then I followed the disk replacement procedure (stop array, remove disk, start, stop, add disk and start again) with the same disk, because I believed it was a cabling problem. The drive had started to rebuilt, when I got the write error again.

     

    Also I need to mention that I experienced one unclean shutdown today - it can be possible related to HDD fail later.

     

    Relevant part from syslog: 

    May 31 19:58:11 unRAID kernel: ata5.00: qc timeout (cmd 0x47)
May 31 19:58:11 unRAID kernel: ata5.00: READ LOG DMA EXT failed, trying PIO
May 31 19:58:11 unRAID kernel: ata5: failed to read log page 10h (errno=-5)
May 31 19:58:11 unRAID kernel: ata5.00: exception Emask 0x1 SAct 0x400001f8 SErr 0x400001 action 0x6 frozen
May 31 19:58:11 unRAID kernel: ata5.00: irq_stat 0x40000008
May 31 19:58:11 unRAID kernel: ata5: SError: { RecovData Handshk }
May 31 19:58:11 unRAID kernel: ata5.00: failed command: WRITE FPDMA QUEUED
May 31 19:58:11 unRAID kernel: ata5.00: cmd 61/40:18:d0:77:38/05:00:3a:00:00/40 tag 3 ncq dma 688128 out
May 31 19:58:11 unRAID kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
May 31 19:58:11 unRAID kernel: ata5.00: status: { DRDY }
May 31 19:58:11 unRAID kernel: ata5.00: failed command: WRITE FPDMA QUEUED
May 31 19:58:11 unRAID kernel: ata5.00: cmd 61/40:20:10:7d:38/05:00:3a:00:00/40 tag 4 ncq dma 688128 out
May 31 19:58:11 unRAID kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)

...

May 31 19:58:29 unRAID kernel: print_req_error: I/O error, dev sdc, sector 976775080
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775016
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775024
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775032
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775040
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775048
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775056

...

     

    I'm also attaching my diagnostic files. (1743 - HDD fail, 2055 - rebuild attempt).

     

    Should I replace this drive or is the problem elsewhere?

     

    As I currently only experimenting with unRAID setup, I don't have any important data stored on those drives. However, I am curious what to do in such case once I will have my media library and personal data stored there.

     

     

    unraid-diagnostics-20200531-2055.zip unraid-diagnostics-20200531-1743.zip

    DHCP / networking issue - v 6.8.3

    in General Support

    Posted · Edited by dotn

    I've just purchased Intel PRO/1000 CT PCI-e adapter and it solved my issue.

    However, I'm not very excited about this solution, because if I was aware Realtec issues I would pick different mobo and save some money.

    Anyway, thank you guys for your support!

     

    4 hours ago, johnnie.black said:

    It could possibly work when the upcoming v6.9-rc1 is released since it will use a newer kernel (and rtl driver)

    I'm looking forward to that version. Was the ETA announced yet?

    DHCP / networking issue - v 6.8.3

    in General Support

    Posted

    14 minutes ago, Benson said:

    Does call trace stop when running with 6.9beta1 ?

    Yes, it does. There was no call trace in this version.

     

    14 minutes ago, Benson said:

    How about if disable the 2.5G NIC in BIOS, and running 6.8.2, call trace occur ?

    Once the 2.5G NIC was disabled in BIOS, I've run "inet restart".

    I've received "Cannot find device eth0" message, because there was no other NIC attached.

    No call trace has been returned.

     

    So it seems that it is caused by driver of Realtec 2.5G NIC. Do you have any recommendation how can I fix it?

    DHCP / networking issue - v 6.8.3

    in General Support

    Posted

    Thanks for advice. However, safe mode didn't help - I've got the same call trace as before.

     

    I've tried 6.9-beta1. In this version NIC wasn't show in interface list and Ethernet port LED was not lit up.

    Based on lscpi NIC was detected: 

    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
	Subsystem: ASRock Incorporation Device [1849:8168]
	Kernel modules: r8169

    But it seems that something went wrong with driver initialization (syslog): 

    May 28 22:42:27 unRAID kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
May 28 22:42:27 unRAID kernel: r8169 0000:02:00.0: unknown chip XID 641

    Attaching complete diagnostics from the most recent version again.

     

    Is there some way how can I fix this?

    If no, what options do I have? Will purchasing PCIe network card solve this problem?

    unraid-diagnostics-20200528-2251.zip

    DHCP / networking issue - v 6.8.3

    in General Support

    Posted · Edited by dotn
    Latest diagnostics attached

    Even if I set IP manually, networking is not working.

     

    I've noticed following Call Trace in dmesg and syslog - it appears there every time I apply changes in networking section or execute "inet restart":

      

    May 28 20:38:24 unRAID dhcpcd[7588]: dhcpcd exited
May 28 20:38:25 unRAID rc.inet1: ip link set eth0 down
May 28 20:38:25 unRAID kernel: ------------[ cut here ]------------
May 28 20:38:25 unRAID kernel: WARNING: CPU: 6 PID: 8638 at kernel/workqueue.c:2917 __flush_work+0x51/0x1a7
May 28 20:38:25 unRAID kernel: Modules linked in: md_mod x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper r8125(O) ahci nvme libahci nvme_core wmi_bmof intel_wmi_thunderbolt wmi video acpi_pad button pcc_cpufreq backlight acpi_cpufreq
May 28 20:38:25 unRAID kernel: CPU: 6 PID: 8638 Comm: ip Tainted: G        W  O      4.19.98-Unraid #1
May 28 20:38:25 unRAID kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z490 Steel Legend, BIOS P1.00 04/07/2020
May 28 20:38:25 unRAID kernel: RIP: 0010:__flush_work+0x51/0x1a7
May 28 20:38:25 unRAID kernel: Code: 13 48 c7 c7 21 fa d2 81 e8 f8 ab 02 00 0f 0b e9 47 01 00 00 48 83 7f 18 00 48 89 fb 75 10 48 c7 c7 21 fa d2 81 e8 db ab 02 00 <0f> 0b eb 23 e8 8f 41 62 00 fa 66 0f 1f 44 00 00 48 89 df e8 72 f7
May 28 20:38:25 unRAID kernel: RSP: 0018:ffffc900037f3390 EFLAGS: 00010246
May 28 20:38:25 unRAID kernel: RAX: 0000000000000024 RBX: ffff888448caec18 RCX: 0000000000000000
May 28 20:38:25 unRAID kernel: RDX: 0000000000000000 RSI: ffff88844e5964f8 RDI: ffff88844e5964f8
May 28 20:38:25 unRAID kernel: RBP: 0000000000000001 R08: 0000000000000003 R09: 0000000000010c00
May 28 20:38:25 unRAID kernel: R10: 0000000000000000 R11: 0000000000000044 R12: ffff888448caec18
May 28 20:38:25 unRAID kernel: R13: ffff8883f180aa00 R14: 0000000000000001 R15: 0000000000000000
May 28 20:38:25 unRAID kernel: FS:  0000147f6631e600(0000) GS:ffff88844e580000(0000) knlGS:0000000000000000
May 28 20:38:25 unRAID kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 28 20:38:25 unRAID kernel: CR2: 0000147f6663cfa0 CR3: 00000004499b4002 CR4: 00000000003606e0
May 28 20:38:25 unRAID kernel: Call Trace:
May 28 20:38:25 unRAID kernel: ? preempt_schedule_common+0x14/0x1d
May 28 20:38:25 unRAID kernel: ? _cond_resched+0x10/0x1e
May 28 20:38:25 unRAID kernel: ? _synchronize_rcu_expedited.constprop.0+0x2b7/0x2d9
May 28 20:38:25 unRAID kernel: __cancel_work_timer+0xf7/0x161
May 28 20:38:25 unRAID kernel: ? fq_reset+0x85/0x10a
May 28 20:38:25 unRAID kernel: rtl8125_close+0x43/0x221 [r8125]
May 28 20:38:25 unRAID kernel: __dev_close_many+0xa4/0xbb
May 28 20:38:25 unRAID kernel: __dev_change_flags+0xcd/0x191
May 28 20:38:25 unRAID kernel: dev_change_flags+0x1c/0x4d
May 28 20:38:25 unRAID kernel: do_setlink+0x2ed/0xbff
May 28 20:38:25 unRAID kernel: rtnl_newlink+0x381/0x6db
May 28 20:38:25 unRAID kernel: ? rtnl_newlink+0x13f/0x6db
May 28 20:38:25 unRAID kernel: ? nla_put_ifalias+0x33/0x7d
May 28 20:38:25 unRAID kernel: ? get_page_from_freelist+0x813/0xd0b
May 28 20:38:25 unRAID kernel: ? __nla_reserve+0x16/0x3e
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 28 20:38:25 unRAID kernel: ? __kmalloc_node_track_caller+0x59/0x12c
May 28 20:38:25 unRAID kernel: ? __kmalloc_reserve.isra.0+0x27/0x68
May 28 20:38:25 unRAID kernel: ? skb_queue_tail+0x16/0x3b
May 28 20:38:25 unRAID kernel: ? __netlink_sendskb+0x3a/0x42
May 28 20:38:25 unRAID kernel: ? netlink_sendskb+0xa/0x2a
May 28 20:38:25 unRAID kernel: ? netlink_unicast+0x1a1/0x1c9
May 28 20:38:25 unRAID kernel: ? rtnl_setlink+0x50/0x129
May 28 20:38:25 unRAID kernel: ? get_page_from_freelist+0x813/0xd0b
May 28 20:38:25 unRAID kernel: rtnetlink_rcv_msg+0x1f8/0x237
May 28 20:38:25 unRAID kernel: ? rtnl_calcit.isra.0+0xe5/0xe5
May 28 20:38:25 unRAID kernel: netlink_rcv_skb+0x80/0xd7
May 28 20:38:25 unRAID kernel: netlink_unicast+0x11e/0x1c9
May 28 20:38:25 unRAID kernel: netlink_sendmsg+0x2b1/0x306
May 28 20:38:25 unRAID kernel: sock_sendmsg+0x14/0x1e
May 28 20:38:25 unRAID kernel: ___sys_sendmsg+0x1b1/0x236
May 28 20:38:25 unRAID kernel: ? filemap_map_pages+0x1e9/0x2ca
May 28 20:38:25 unRAID kernel: ? nfulnl_rcv_nl_event+0x11/0x6d
May 28 20:38:25 unRAID kernel: ? __inode_wait_for_writeback+0x71/0xc6
May 28 20:38:25 unRAID kernel: ? init_wait_var_entry+0x3b/0x3b
May 28 20:38:25 unRAID kernel: ? fsnotify_grab_connector+0x5c/0x63
May 28 20:38:25 unRAID kernel: ? rcu_is_watching+0x5/0x9
May 28 20:38:25 unRAID kernel: ? __dentry_kill+0x12c/0x135
May 28 20:38:25 unRAID kernel: __sys_sendmsg+0x5b/0x91
May 28 20:38:25 unRAID kernel: do_syscall_64+0x57/0xf2
May 28 20:38:25 unRAID kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 28 20:38:25 unRAID kernel: RIP: 0033:0x147f6664dbc3
May 28 20:38:25 unRAID kernel: Code: c7 c0 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 c3 0f 1f 40 00 48 83 ec 28 89 54 24 1c 48
May 28 20:38:25 unRAID kernel: RSP: 002b:00007ffccdf4ff58 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
May 28 20:38:25 unRAID kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000147f6664dbc3
May 28 20:38:25 unRAID kernel: RDX: 0000000000000000 RSI: 00007ffccdf4ffd0 RDI: 0000000000000007
May 28 20:38:25 unRAID kernel: RBP: 000000005ed083b2 R08: 0000000000000001 R09: 000000000000007c
May 28 20:38:25 unRAID kernel: R10: 0000000000406d00 R11: 0000000000000246 R12: 0000000000000001
May 28 20:38:25 unRAID kernel: R13: 00007ffccdf50770 R14: 00007ffccdf50090 R15: 0000000000486540
May 28 20:38:25 unRAID kernel: ---[ end trace 08addafe9bbbc8d0 ]---
May 28 20:38:25 unRAID rc.inet1: ip -4 addr add 10.0.10.10/255.255.255.0 dev eth0
May 28 20:38:25 unRAID rc.inet1: ip link set eth0 up

    It is probably somehow related to my networking issue.

     

     

    unraid-diagnostics-20200529-0538.zip

    DHCP / networking issue - v 6.8.3

    in General Support

    Posted

    Hi guys,

     

    I've just installed unRAID v 6.8.3 on my new desktop tower, but I'm not able to setup networking.

    It is not router port issue, because I'm able to connect from other devices on the same cable.

     

    On my router I have defined a static IP address assigned to unRAID server MAC address.

    Though this IP address is offered by DHCP server, unRAID does not set it and use 169.254.29.200 address instead: 

    May 28 17:26:28 unRAID kernel: r8125: eth0: link up
May 28 17:26:28 unRAID dhcpcd[8652]: eth0: carrier acquired
May 28 17:26:28 unRAID dhcpcd[8652]: eth0: soliciting a DHCP lease
May 28 17:26:28 unRAID dhcpcd[8652]: eth0: offered 10.0.10.10 from 10.0.10.1
May 28 17:26:33 unRAID dhcpcd[8652]: eth0: probing for an IPv4LL address
May 28 17:26:37 unRAID dhcpcd[8652]: eth0: using IPv4LL address 169.254.29.200

     

    I'm attaching my diagnostics zip.

     

    Do you have any idea what can be wrong with my configuration?

     

    unraid-diagnostics-20200528-1741.zip

×
×
  • Create New...