Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DS418 with QNA-UC5G1T not working #70

Closed
mlynch1985 opened this issue May 10, 2022 · 1 comment
Closed

DS418 with QNA-UC5G1T not working #70

mlynch1985 opened this issue May 10, 2022 · 1 comment

Comments

@mlynch1985
Copy link

Description of the problem

Driver installed successfully after running ssh command and re-attempting the install. Was able to also direct connect to Windows Server and configure iSCSI target. Connection drops when initializing the Disk in Disk Management tool. Can recreate the connection drop when mounting an SMB share and attempting to copy a file or create new folder.

Description of your products

Synology DS418 - Amazon Link
QNA-UC5G1T Adapter - Amazon Link

Product Version

ash-4.4# uname -a
Linux mynas 4.4.180+ #42661 SMP Fri Apr 1 15:31:28 CST 2022 aarch64 GNU/Linux synology_rtd1296_ds418

DSM 7.1-42661 Update 1

Description of your environment

PC and Synology device both use same QNAP adapter
Connected and tested with a 1meter Cat5e and Cat7 cable

Output of dmesg command

ash-4.4# dmesg
[  304.148161] aqc111 5-1:1.0 eth2: Link Speed 5000, USB 3
[  304.155683] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[  305.089262] iSCSI:iscsi_target.c:545:iscsit_add_np CORE[0] - Added Network Portal: 10.0.0.2:3260 on iSCSI/TCP
[  305.101782] iSCSI:iscsi_target.c:545:iscsit_add_np CORE[0] - Added Network Portal: [fe80::265e:beff:fe6a:6945]:3260 on iSCSI/TCP
[  365.678466] iSCSI_F:iscsi_target_login.c:800:iscsi_post_login_handler Discovery session from I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50873]
[  365.692813] iSCSI:iscsi_target.c:2797:iscsit_handle_logout_cmd Logout - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50873], T[(null)]
[  365.705538] iSCSI_F:iscsi_target.c:4746:iscsit_close_connection Close - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50873], T[(null)]
[  381.361551] iSCSI_F:iscsi_target_login.c:803:iscsi_post_login_handler Login - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50924], T[iqn.2000-01.com.synology:catbug-nas.Target-2.8993e3f6a4a][10.0.0.2:3260], P[iSCSI/TCP]
[  388.339147] iSCSI_F:iscsi_target_login.c:800:iscsi_post_login_handler Discovery session from I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50927]
[  388.353400] iSCSI:iscsi_target.c:2797:iscsit_handle_logout_cmd Logout - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50927], T[(null)]
[  388.366109] iSCSI_F:iscsi_target.c:4746:iscsit_close_connection Close - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50927], T[(null)]
[ 1915.431473] iSCSI:iscsi_target_util.c:1004:iscsit_handle_nopin_response_timeout Did not receive response to NOPIN on CID: 1, failing connection for I_T Nexus iqn.1991-05.com.microsoft:catbug-pc,i,0x400001370000,iqn.2000-01.com.synology:catbug-nas.Target-2.8993e3f6a4a,t,0x01
[ 1915.456334] iSCSI:iscsi_target_util.c:1228:iscsit_fe_sendpage_sg tcp_sendpage() failure: -512
[ 1915.466182] iSCSI_F:iscsi_target.c:4746:iscsit_close_connection Close - I[iqn.1991-05.com.microsoft:catbug-pc][10.0.0.1:50924], T[iqn.2000-01.com.synology:catbug-nas.Target-2.8993e3f6a4a]

Output of lsusb command

ash-4.4# lsusb
|__usb2          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller xhci-hcd.2.auto) hub
|__usb3          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller xhci-hcd.2.auto) hub
|__usb4          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller xhci-hcd.5.auto) hub
|__usb5          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhci-hcd xHCI Host Controller xhci-hcd.5.auto) hub
  |__5-1         1c04:0015:0101 00  3.20 5000MBit/s 896mA 1IF  (QNAP� Pacific� 1BI10104)

Output of ifconfig -a command

ash-4.4# ifconfig
eth0      Link encap:Ethernet  HWaddr 90:09:D0:0C:4A:B9
          inet addr:192.168.1.2  Bcast:192.168.151.255  Mask:255.255.255.0
          inet6 addr: fe80::9209:d0ff:fe0c:4ab9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12726 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15335 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4549565 (4.3 MiB)  TX bytes:17783448 (16.9 MiB)
          Interrupt:11

eth1      Link encap:Ethernet  HWaddr 90:09:D0:0C:4A:BA
          inet addr:10.10.10.11  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::9209:d0ff:fe0c:4aba/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24484803 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88438103 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7556015096 (7.0 GiB)  TX bytes:305525204510 (284.5 GiB)
          Interrupt:28 base 0x4000

eth2      Link encap:Ethernet  HWaddr 24:5E:BE:6A:69:45
          inet addr:10.0.0.2  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::265e:beff:fe6a:6945/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9847950 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4914088 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14743670107 (13.7 GiB)  TX bytes:332634920 (317.2 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:27527 (26.8 KiB)  TX bytes:27527 (26.8 KiB)
@bb-qq
Copy link
Owner

bb-qq commented Dec 4, 2022

This symptom appears to be a problem with the rtd1296 platform.
I decided to merge topics on rtd1296 into the issue #275 in the r8152 project.
If you notice anything new, please comment there.

@bb-qq bb-qq closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants