April 9, 20215 yr Hello , This is my unraid system log information. I don't know what caused this error? Please help guide how to solve it. unraid 6.9.1 Quote Apr 9 14:19:24 Unraid smbd[4492]: [2021/04/09 14:19:24.486335, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:19:24 Unraid smbd[4492]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:20:42 Unraid smbd[5051]: [2021/04/09 14:20:42.466587, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:20:42 Unraid smbd[5051]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:20:42 Unraid smbd[5261]: [2021/04/09 14:20:42.466746, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:20:42 Unraid smbd[5261]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:22:57 Unraid smbd[6457]: [2021/04/09 14:22:57.924431, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:22:57 Unraid smbd[6457]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:23:13 Unraid smbd[6669]: [2021/04/09 14:23:13.943007, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:23:13 Unraid smbd[6669]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:23:19 Unraid smbd[6719]: [2021/04/09 14:23:19.121476, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:23:19 Unraid smbd[6719]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:23:32 Unraid smbd[6867]: [2021/04/09 14:23:32.432259, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:23:32 Unraid smbd[6867]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:23:35 Unraid smbd[6876]: [2021/04/09 14:23:35.183484, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:23:35 Unraid smbd[6876]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:23:53 Unraid smbd[7050]: [2021/04/09 14:23:53.537080, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:23:53 Unraid smbd[7050]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:27:33 Unraid smbd[8837]: [2021/04/09 14:27:33.579287, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:27:33 Unraid smbd[8837]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:27:33 Unraid smbd[9053]: [2021/04/09 14:27:33.626223, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:27:33 Unraid smbd[9053]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:28:14 Unraid smbd[9408]: [2021/04/09 14:28:14.937391, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:28:14 Unraid smbd[9408]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:28:29 Unraid smbd[9568]: [2021/04/09 14:28:29.707793, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:28:29 Unraid smbd[9568]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:28:35 Unraid smbd[9615]: [2021/04/09 14:28:35.890673, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:28:35 Unraid smbd[9615]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:28:50 Unraid smbd[9756]: [2021/04/09 14:28:50.467672, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:28:50 Unraid smbd[9756]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:34:11 Unraid smbd[12682]: [2021/04/09 14:34:11.929214, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:34:11 Unraid smbd[12682]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:34:33 Unraid smbd[12893]: [2021/04/09 14:34:33.156798, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:34:33 Unraid smbd[12893]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:38:50 Unraid smbd[15110]: [2021/04/09 14:38:50.005370, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:38:50 Unraid smbd[15110]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:38:50 Unraid smbd[15304]: [2021/04/09 14:38:50.007151, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:38:50 Unraid smbd[15304]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:41:15 Unraid webGUI: Successful login user root from ***** Apr 9 14:44:23 Unraid smbd[18611]: [2021/04/09 14:44:23.864468, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:44:23 Unraid smbd[18611]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 9 14:44:44 Unraid smbd[18816]: [2021/04/09 14:44:44.560457, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 9 14:44:44 Unraid smbd[18816]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Well, things turned out to be not that complicated. Ultimately by the official usb creator tool, I refresh the system again, and removed all docker, all the problems are gone. Edited April 25, 20215 yr by phoenix13023
April 11, 20215 yr Community Expert 2 hours ago, phoenix13023 said: hello？ anyone konws? Do you have a device trying to map a share? Post diagnostics.
April 12, 20215 yr Author 20 hours ago, SimonF said: Do you have a device trying to map a share? Post diagnostics. here is the diagnostics unraid-diagnostics-20210412-1352.zip
April 12, 20215 yr Community Expert Is your system open to the internet? As I can see connection attempts for NFS from public IPs also. Apr 4 07:00:04 Unraid smbd[25230]: [2021/04/04 07:00:04.169159, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 4 07:00:04 Unraid smbd[25230]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 4 07:46:52 Unraid emhttpd: read SMART /dev/sdd Apr 4 08:35:16 Unraid emhttpd: spinning down /dev/sdd Apr 4 08:53:23 Unraid emhttpd: read SMART /dev/sdd Apr 4 09:43:17 Unraid emhttpd: spinning down /dev/sdd Apr 4 10:17:04 Unraid rpcbind[28958]: connect from 192.241.222.21 to dump() Apr 4 10:24:04 Unraid emhttpd: read SMART /dev/sdd Apr 4 11:36:33 Unraid rpcbind[9494]: connect from 146.88.240.4 to dump()
April 12, 20215 yr Author 6 hours ago, SimonF said: Is your system open to the internet? As I can see connection attempts for NFS from public IPs also. Apr 4 07:00:04 Unraid smbd[25230]: [2021/04/04 07:00:04.169159, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Apr 4 07:00:04 Unraid smbd[25230]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET. Apr 4 07:46:52 Unraid emhttpd: read SMART /dev/sdd Apr 4 08:35:16 Unraid emhttpd: spinning down /dev/sdd Apr 4 08:53:23 Unraid emhttpd: read SMART /dev/sdd Apr 4 09:43:17 Unraid emhttpd: spinning down /dev/sdd Apr 4 10:17:04 Unraid rpcbind[28958]: connect from 192.241.222.21 to dump() Apr 4 10:24:04 Unraid emhttpd: read SMART /dev/sdd Apr 4 11:36:33 Unraid rpcbind[9494]: connect from 146.88.240.4 to dump() This is not my connection. I don't know how to close those.
April 12, 20215 yr Community Expert Have you put your machine into a DMZ port on your router? or setup any port forwards?
April 13, 20215 yr Author 9 hours ago, SimonF said: Have you put your machine into a DMZ port on your router? or setup any port forwards? Oh...... Yes, I set this before. I turn off the dmz now. Have anything need to do ?
April 13, 20215 yr Author 2 hours ago, SimonF said: Have the logs stopped? Post a new Diags. Can you give a guild for how to check and clean the unraid ?
April 14, 20215 yr Author 18 hours ago, SimonF said: Some helpful info is here. Thank you very much for following up on my question and for always giving back. But now the server seems to have a lot of trouble, so that it is impossible to give a direct solution through a diagnosis log. Here I want to change the way to solve the problem: If I want to reinstall unraid, I hope to keep the data in docker and the hard disk. Is there any operation guide?
April 14, 20215 yr Community Expert 9 hours ago, phoenix13023 said: Thank you very much for following up on my question and for always giving back. But now the server seems to have a lot of trouble, so that it is impossible to give a direct solution through a diagnosis log. Here I want to change the way to solve the problem: If I want to reinstall unraid, I hope to keep the data in docker and the hard disk. Is there any operation guide? Are you able to provide more info on the issues you are having.
April 18, 20215 yr Author On 4/14/2021 at 11:07 PM, SimonF said: Are you able to provide more info on the issues you are having. unraid-diagnostics-20210418-1318.zip I unplugged its network cable for 3 days. Today I have time, I downgraded it to 6.8.3, and then upgraded to 6.9.2. Now the docker server cannot be started and I don't know how to operate it. What do you think should be done next?
April 18, 20215 yr Community Expert 3 hours ago, phoenix13023 said: unraid-diagnostics-20210418-1318.zip 89.57 kB · 0 downloads I unplugged its network cable for 3 days. Today I have time, I downgraded it to 6.8.3, and then upgraded to 6.9.2. Now the docker server cannot be started and I don't know how to operate it. What do you think should be done next? Looks like you may need to recreate the docker image.
April 19, 20215 yr Author 21 hours ago, SimonF said: Looks like you may need to recreate the docker image. Sorry, I cannot provide a screenshot of the docker page of unraid gui at the moment. Only "the docker service failed to start" on the docker page, and there is no button to stop or add a new docker. Edited April 19, 20215 yr by phoenix13023
Archived
This topic is now archived and is closed to further replies.