-
Posts
137 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by feins
-
-
Need Help.
Yesterday night my schedule Parity check started as usual and this morning when i login to my Unraid i notice that Disk 2 Disable and been notified Read Error.
There i no info wats the error and now my Parity check was paused at 3.2% and my Disk 2 is under disable.
What should i do now.
-
On 5/25/2023 at 10:49 PM, MAM59 said:
but... i dont get it... where are the cables of eth0 and eth1 connected to??? if you do not use the switch only one port can have a valid connection.
or is it switch->eth1|eth0->client
very mystic...
eth0 connect to my IPS router and eth1 connect to my workstation.
Now my setting are similar to guyth setup just that im still getting 2.5Gbe.
-
3 hours ago, MAM59 said:
but why bridge both ports ? Does not make any sense to me
Yeah, maybe, but still I would set up this docker to use "host" networking instead of a bridge. Would show the real IP Addresses instead of the virtual ones.
(and mayb a bit faster because the detour is not there anymore)
Ive tried if don't bridge eth1 i don't get any DHCP IP. Even if i configure static IP on both Port i can only ping to the Server but cant reach the internet seems it don't route out.
I didn't change anything while installing iperf3 as i don't change the default setting for docker unless been told or instructed. I will change it to Host and try.
Seems same result. poor throughput between Unraid and Windows.
I just perform a loopback test on my workstation and seems loopback i manage to get 10Gbe throughput.
-
On 5/24/2023 at 8:48 AM, Faceman said:
Don't buy anything labelled CAT7 or CAT8 on amazon, they are all fake. buy CAT6A (not CAT6E that doesn't exist) UTP patch cables from a respected data equipment supplier.
If the cable is "flat" it would barely meet cat5e specs.
All that aside, the cables are not your problem, the issue is a bottleneck somewhere in the chain, has someone ever done a proper throughput test on that switch? can it actually switch 10gbe at full speed through those ports? is it one 10gbe channel on the switch chip and they are splitting it for convenience?
Is there a CPU bottleneck somewhere, a PCIE lane limitation? have you tried a direct connection between the machines?
Ive bypass the switch and now doing back to back im still getting the same 2.5-3Gbe testing with iperf3. Both card are plug into a Gen 3 X16 Pcie Lane.
Before this i manage to get the max SSD SATA6 speed which is about 400MB/s but recently i notice that i only manage at about 40-60MB/s that's where i start to test the connection and notice my 10Gbe only do 2.5-3Gbe speed. and file transfer wont even goes above 80MB/s
-
On 5/24/2023 at 9:23 AM, aaronwt said:
I have a couple of those QNAP switches. I've never had any problem getting over 8Gbps throughput, between two PCs, using Commscope Cat6 patch cables. On the 10GbE ports. And then Cat5e is rated for up to 100 meters at 2.5 GbE. My unRAIDs are connected to the 2.5 GbE ports. Some using generic Cat5e. At 2.5 GbE, they work just the same as the ones using Commscope Cat6 cables.
That's the thing because my Unraid the Switch and my workstation all on the same location. I can connect to all the device using just 0.5m cable. From my understanding even a typical Cat6 cable can handle 10Gbe speed at short distance. i think 0.5m are consider very short distance.
Even now im connect back to back im still getting 2.5-3Gbe speed.
-
On 5/23/2023 at 6:53 PM, MAM59 said:
too bad, but I tell everybody that 10G with twisted pair is nothing for the wimp 🙂 You need strong nerves before you give up and move to fiber 🙂
But if I would be you, I would just leave out that switch and connect the computers back to back. See what they do then.
I just realize you are running iperf from within a docker or a vm? thats would I not call a serious environment for speed check.
?!?!?!?
I'm connecting Back to Back actually no more goes through the 10Gbe switch.
Now iperf3 for unraid is in docker now. no more under Nerdtools.
Both eth0 and eth1 are 10Gbe its the same card X540-2T comes with 2 10Gbe Ether port.
-
-
Today my Cat8 cable arrived and did a test and similar result.
C:\iperf3>iperf3 -c 10.10.2.10
Connecting to host 10.10.2.10, port 5201
[ 4] local 10.10.2.127 port 56119 connected to 10.10.2.10 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 372 MBytes 3.12 Gbits/sec
[ 4] 1.00-2.00 sec 378 MBytes 3.17 Gbits/sec
[ 4] 2.00-3.00 sec 367 MBytes 3.08 Gbits/sec
[ 4] 3.00-4.00 sec 384 MBytes 3.22 Gbits/sec
[ 4] 4.00-5.00 sec 391 MBytes 3.28 Gbits/sec
[ 4] 5.00-6.00 sec 402 MBytes 3.38 Gbits/sec
[ 4] 6.00-7.00 sec 375 MBytes 3.14 Gbits/sec
[ 4] 7.00-8.00 sec 386 MBytes 3.24 Gbits/sec
[ 4] 8.00-9.00 sec 381 MBytes 3.20 Gbits/sec
[ 4] 9.00-10.00 sec 382 MBytes 3.21 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 3.73 GBytes 3.20 Gbits/sec sender
[ 4] 0.00-10.00 sec 3.73 GBytes 3.20 Gbits/sec receiveriperf Done.
root@c9449a0498ba:/# iperf3 -c 10.10.2.127
Connecting to host 10.10.2.127, port 5201
[ 5] local 172.17.0.6 port 58088 connected to 10.10.2.127 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 293 MBytes 2.46 Gbits/sec 0 342 KBytes
[ 5] 1.00-2.00 sec 290 MBytes 2.43 Gbits/sec 0 325 KBytes
[ 5] 2.00-3.00 sec 302 MBytes 2.54 Gbits/sec 0 354 KBytes
[ 5] 3.00-4.00 sec 319 MBytes 2.67 Gbits/sec 0 354 KBytes
[ 5] 4.00-5.00 sec 319 MBytes 2.67 Gbits/sec 0 342 KBytes
[ 5] 5.00-6.00 sec 324 MBytes 2.72 Gbits/sec 0 339 KBytes
[ 5] 6.00-7.00 sec 321 MBytes 2.69 Gbits/sec 0 337 KBytes
[ 5] 7.00-8.00 sec 325 MBytes 2.73 Gbits/sec 0 334 KBytes
[ 5] 8.00-9.00 sec 296 MBytes 2.49 Gbits/sec 0 334 KBytes
[ 5] 9.00-10.00 sec 324 MBytes 2.72 Gbits/sec 0 334 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 3.04 GBytes 2.61 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 3.04 GBytes 2.61 Gbits/sec receiveriperf Done.
Ive no idea what went wrong.
-
57 minutes ago, MAM59 said:
yeah, you did not get my message. Of course these are suitable cables, but that does not mean a thing. Could even be Cat 7 or Cat 8. Does not mean a thing too (ok, its relevant too but only 50% of the problem)
The problems are the plugs on both ends. Before 2022 there were no cat6 plugs available, so they took real cables and attached bad plugs and sold it as "patch cable (raw cable)".
If you bought one of these you should read it as "does not work properly".
(sadly there is nothing written on the plugs, thats why I added the trick with moving the plug whilest it is attached, If if moves, you should consider to throw away that cable)
Btw, price is also no real way to tell. I've bought dozends of different brands before I realized that the rather cheap "Amazon basics, nylon covered" worked flawlessly.
I’ve just order two cat 8 Shielded cable and will try it out to see hows it’s going.
-
On 5/19/2023 at 12:40 PM, MAM59 said:
one more cable hint: try to pull the cable locked into the switch back and forth gently. If they move, they are wrong!
"real" Cat6 plugs are minimal longer than the old ones (even if you put them side by side, its hard to tell the difference), they are really fixed whereas "wrong" plugs can still be moved.
The problem is, that until a year ago or so, NO cable was really good enough for 10G. The cable type itself was ok, but the plugs on both ends were not. They have sold the stuff as "cat 7 raw cable" (or even cat8 sometimes).
10G on Twisted Pair is no child's play... I gave up and switched to fibre, no problems since then...
That's what i have AM cat6E 0.5M cable which I'm using or the Krone Cat6E cable which is 2M in length.
-
On 5/19/2023 at 8:25 AM, Faceman said:
If you run some traffic between those two 10g ports do any other lights flash on the switch? perhaps something funny with the routing forcing traffic to flow through a 2.5g connection? is your local traffic going from 10gbe to switch, then 2.5gbe to router and back, then 10gbe to the other end?
If you disconnect every other device (and any secondary NICS) and just run server to windows through that switch does it still cap out at 2.5?
Cables shouldn't be an issue, you can run 10GBaseT over UTP CAT6 if the distances aren't too long, and 2.5gbe over UTP Cat5e is just fine for short hops too, and those sorts of issues arent going to cut your throughput that far, a badly grounded FTP cable can cause more problems than that.
Both the 10Gbe port are connect to my Win11 Workstation and Unraid. The other 2 white cable are going to my Qnap NAS qhich is power down at meantime and the last port are going to my Telco Router so as now there is only 2 10Gbe connection are active only.
When i try to copy file from my windows 11 workstation to Unraid only both the 10Gbe port are blinking.
-
-
5 hours ago, MAM59 said:
can we affirm that both machines are plugged into the 2 10G ports of the switch (port #1 and #2) ? ? ?
The others are 2,5G only, so if one of them is in a "wrong" port (#3 to #6) it will result in 2,5g speed everywhere.
Yes both Unraid and my Workstation is connected to the 10gbit port. Picture attach.
I’ve also try to change the flow control to off as suggested from my Windows 11 Setting the issue still the same.
I’ve also try to enable jumbo frame to 9000 on both windows 11 and unraid tested also same result.
-
18 hours ago, JorgeB said:
iperf just does a LAN test, so could be NIC (or NIC settings), cables, switch, client PC, etc.
How could i pinpoint the issue? where should i start to troubleshoot?
-
17 hours ago, MAM59 said:
Note that there is no real "2,5G" defined.
Some Devices always show 10G connection but transfer at lower speeds. Depends on the driver / OS.
So, with bad/too long cables the devices could agree to step down to 5G or 2,5G transmission speed, whilst the connection still shows full 10G.
On all speeds the bitrate is the same, the difference is done by inserting more or less pauses to give the cable time to recover.
(whilst the real encoding now becomes really complicated, you can simply think of 10G=transmit all the time, 5G=transmit,pause,transmit,pause... and 2,5G=transmit,pause,pause,pause,transmit...)
You did not tell us the type of cards and switches involved, so no educated guess besides "check the cables" can be offered.
The cable is Genuine AMP Cat6E cable at 0.5M length. the card is HP Intel X540-2T. connected to a Qnap QSW-2104-2T unmanage switch.
-
17 hours ago, pidg30n said:
Check on the (managed) switch or gateway side. Look to see if flow control is enabled. The settings for flow control will affect the maximum throughput. If it's on, try disabling it. See what happens. Play with that control, if it's there.
Its an Unmanage Qnap QWS-2104-2T switch. no setting is required. On Unraid is there such setting? I know Windows i could try to disable flow control.
-
Hi all,
Need some help.
Ive been using 10Gbe since previous version.
Its been a while i notice that during copy files i only get to 100MB and sometime drop below 40MB and rarely goes up as previous usually can saturate until my SSD speed which is around 350-400MB.
I did iperf and notice that both site transfer only cap at 2.5Gbe and I'm wonder why and how to resolve this issue?
Under unraid i can see the Lan connection is 10Gbe same with my Windows 11 Lan connection show 10Gbe.
-
15 hours ago, Squid said:
There's absolutely nothing wrong with that expresion. Have you tried rebooting?
That's funny,
Before this ive rebooted the Server before posting the Syslog where I notice some of my CPU are at 100% and the server are not responding and very lagging.
Today i just check on the syslog again and notice all the error are no more.
text error warn system array login
Mar 25 20:12:58 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::dcbf:67ff:fe13:3570 on vethb94c914.*.
Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state
Mar 25 20:13:03 TS-P500 kernel: vethe26bc6e: renamed from eth0
Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Interface vethb94c914.IPv6 no longer relevant for mDNS.
Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Leaving mDNS multicast group on interface vethb94c914.IPv6 with address fe80::dcbf:67ff:fe13:3570.
Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state
Mar 25 20:13:03 TS-P500 kernel: device vethb94c914 left promiscuous mode
Mar 25 20:13:03 TS-P500 kernel: docker0: port 5(vethb94c914) entered disabled state
Mar 25 20:13:03 TS-P500 avahi-daemon[8587]: Withdrawing address record for fe80::dcbf:67ff:fe13:3570 on vethb94c914.
Mar 25 22:22:19 TS-P500 webGUI: Successful login user root from 10.10.2.127
Mar 25 22:32:02 TS-P500 emhttpd: read SMART /dev/sde
Mar 25 22:34:23 TS-P500 root: plugin: running: anonymous
Mar 25 22:34:23 TS-P500 root: plugin: creating: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.manager.txz
Mar 25 22:34:27 TS-P500 root: plugin: checking: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz - MD5
Mar 25 22:34:27 TS-P500 root: plugin: running: /boot/config/plugins/dynamix.file.manager/dynamix.file.manager.txz
Mar 25 22:34:28 TS-P500 root: plugin: running: anonymous
Mar 25 22:34:30 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 25 22:34:34 TS-P500 root: plugin: dynamix.file.manager.plg updated
Mar 25 22:55:52 TS-P500 emhttpd: read SMART /dev/sdd
Mar 25 23:13:32 TS-P500 emhttpd: spinning down /dev/sdd
Mar 26 00:00:01 TS-P500 Plugin Auto Update: Checking for available plugin updates
Mar 26 00:01:37 TS-P500 Plugin Auto Update: Community Applications Plugin Auto Update finished
Mar 26 00:07:50 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 02:03:58 TS-P500 emhttpd: read SMART /dev/sdg
Mar 26 02:04:09 TS-P500 emhttpd: read SMART /dev/sdf
Mar 26 02:14:16 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 02:19:05 TS-P500 emhttpd: spinning down /dev/sdg
Mar 26 02:20:18 TS-P500 emhttpd: spinning down /dev/sdf
Mar 26 02:29:29 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 03:19:29 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 03:34:40 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 03:40:16 TS-P500 crond[1725]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Mar 26 04:40:05 TS-P500 apcupsd[7683]: apcupsd exiting, signal 15
Mar 26 04:40:05 TS-P500 apcupsd[7683]: apcupsd shutdown succeeded
Mar 26 04:40:07 TS-P500 apcupsd[29382]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded
Mar 26 04:40:07 TS-P500 apcupsd[29382]: NIS server startup succeeded
Mar 26 05:37:21 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 05:37:45 TS-P500 emhttpd: read SMART /dev/sdi
Mar 26 05:54:50 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 05:54:50 TS-P500 emhttpd: spinning down /dev/sdi
Mar 26 06:00:01 TS-P500 Docker Auto Update: Community Applications Docker Autoupdate running
Mar 26 06:00:01 TS-P500 Docker Auto Update: Checking for available updates
Mar 26 06:04:35 TS-P500 Docker Auto Update: No updates will be installed
Mar 26 06:32:03 TS-P500 nginx: 2023/03/26 06:32:03 [crit] 7889#7889: *381228 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 106.75.223.209, server: 0.0.0.0:2443
Mar 26 09:39:50 TS-P500 webGUI: Successful login user root from 10.10.2.127
Mar 26 09:46:04 TS-P500 kernel: docker0: port 5(veth0d3315d) entered blocking state
Mar 26 09:46:04 TS-P500 kernel: docker0: port 5(veth0d3315d) entered disabled state
Mar 26 09:46:04 TS-P500 kernel: device veth0d3315d entered promiscuous mode
Mar 26 09:46:05 TS-P500 kernel: eth0: renamed from vethbe929c2
Mar 26 09:46:05 TS-P500 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0d3315d: link becomes ready
Mar 26 09:46:05 TS-P500 kernel: docker0: port 5(veth0d3315d) entered blocking state
Mar 26 09:46:05 TS-P500 kernel: docker0: port 5(veth0d3315d) entered forwarding state
Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: Joining mDNS multicast group on interface veth0d3315d.IPv6 with address fe80::e0b2:b1ff:fee3:d172.
Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: New relevant interface veth0d3315d.IPv6 for mDNS.
Mar 26 09:46:06 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::e0b2:b1ff:fee3:d172 on veth0d3315d.*.
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered disabled state
Mar 26 09:46:17 TS-P500 kernel: device veth0baf29d entered promiscuous mode
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered forwarding state
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered disabled state
Mar 26 09:46:17 TS-P500 kernel: eth0: renamed from veth790bf06
Mar 26 09:46:17 TS-P500 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0baf29d: link becomes ready
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered blocking state
Mar 26 09:46:17 TS-P500 kernel: docker0: port 6(veth0baf29d) entered forwarding state
Mar 26 09:46:18 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: Joining mDNS multicast group on interface veth0baf29d.IPv6 with address fe80::b81d:acff:fe95:8abb.
Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: New relevant interface veth0baf29d.IPv6 for mDNS.
Mar 26 09:46:18 TS-P500 avahi-daemon[8587]: Registering new address record for fe80::b81d:acff:fe95:8abb on veth0baf29d.*.
Mar 26 09:46:26 TS-P500 emhttpd: read SMART /dev/sdg
Mar 26 09:46:29 TS-P500 emhttpd: read SMART /dev/sdi
Mar 26 10:19:08 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 11:17:30 TS-P500 kernel: usb 3-5.4: new full-speed USB device number 10 using xhci_hcd
Mar 26 11:17:30 TS-P500 kernel: usb 3-5.4: device descriptor read/64, error -32
Mar 26 11:17:31 TS-P500 kernel: usb 3-5.4: device descriptor read/64, error -32
Mar 26 11:17:31 TS-P500 kernel: usb 3-5.4: new full-speed USB device number 11 using xhci_hcd
Mar 26 11:17:31 TS-P500 kernel: cdc_acm 3-5.4:1.0: ttyACM0: USB ACM device
Mar 26 11:17:31 TS-P500 kernel: usbcore: registered new interface driver cdc_acm
Mar 26 11:17:31 TS-P500 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Mar 26 12:32:20 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 12:35:51 TS-P500 emhttpd: read SMART /dev/sdd
Mar 26 12:51:35 TS-P500 emhttpd: spinning down /dev/sdd
Mar 26 13:28:58 TS-P500 emhttpd: read SMART /dev/sdd
Mar 26 13:43:24 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 13:57:36 TS-P500 emhttpd: spinning down /dev/sdd
Mar 26 14:52:31 TS-P500 kernel: usb 3-5.4: USB disconnect, device number 11
Mar 26 16:17:24 TS-P500 emhttpd: read SMART /dev/sde
Mar 26 16:29:52 TS-P500 emhttpd: read SMART /dev/sdd
Mar 26 16:33:16 TS-P500 webGUI: Successful login user root from 10.10.2.127
Mar 26 16:41:17 TS-P500 emhttpd: spinning down /dev/sde
Mar 26 16:45:01 TS-P500 emhttpd: spinning down /dev/sdd -
On 3/23/2023 at 5:45 PM, Squid said:
What is the output of each of these commands
crontab -l
and
cat /etc/cron.d/root
Here's the output from crontab -l
root@TS-P500:~# crontab -l
# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null. We'll do this here since these jobs should run
# properly on a newly installed system. If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this. If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
0 3 * * 1 /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1
28 8 * * * /usr/local/emhttp/plugins/nvidia-driver/include/update-check.sh &>/dev/null 2>&1
root@TS-P500:~#and here's the output for cat /etc/cron.d/root
root@TS-P500:~# cat /etc/cron.d/root
# Generated docker monitoring schedule:
10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check &> /dev/null# Generated system monitoring schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null# Generated mover schedule:
40 3 * * * /usr/local/sbin/mover &> /dev/null# Generated parity check schedule:
0 0 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null
# Generated plugins version check schedule:
10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null# Generated Unraid OS update check schedule:
11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null# Generated cron settings for docker autoupdates
0 6 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
# Generated cron settings for plugin autoupdates
0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1# CRON for CA background scanning of applications
50 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1# Generated file integrity check schedule:
0 3 * * 2 bash /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null# Generated system data collection schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
root@TS-P500:~# -
3 hours ago, ljm42 said:
Let's fix this first:
This error means there is an invalid custom contab in the CA Update Applications plugin. This website should be able to help you fix the crontab expression:
if you aren't sure, post a screenshot of what you're putting into the plugin and let us know what you are trying to do with it.
I didn't add any Custom (cron expression) at all and here is the screenshot of my CA Update Application plugin.
-
Dear Community recently my server start to behave funny like crash or all CPU Processor at 100% until i need to do a force restart and so on.
What i notice that after reboot i notice such output from the Syslog terminal.
Mar 21 01:20:08 TS-P500 root: plugin: setting: /tmp/unassigned.devices/add-smb - mode to 0770
Mar 21 01:20:08 TS-P500 root: plugin: running: anonymous
Mar 21 01:20:08 TS-P500 root: plugin: unassigned.devices.plg updated
Mar 21 01:20:32 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 01:21:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 01:39:32 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 01:42:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 02:02:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 02:19:34 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 02:23:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 02:33:35 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 02:35:35 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 02:45:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 03:05:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 03:15:38 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 03:23:42 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 03:26:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 04:39:54 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 04:44:12 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 04:45:23 TS-P500 crond[1737]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Mar 21 04:46:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 04:59:18 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 05:04:23 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 05:06:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 05:19:30 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 05:24:40 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 05:27:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 05:41:38 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 05:43:45 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 05:48:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 05:58:52 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 06:00:01 TS-P500 Docker Auto Update: Community Applications Docker Autoupdate running
Mar 21 06:00:01 TS-P500 Docker Auto Update: Checking for available updates
Mar 21 06:04:37 TS-P500 Docker Auto Update: No updates will be installed
Mar 21 06:04:37 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 06:05:13 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 06:20:20 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 06:25:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 06:27:41 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 06:42:47 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 06:46:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 06:49:35 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 07:04:42 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 07:07:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 07:11:59 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 07:28:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 07:29:25 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 07:35:54 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 07:48:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 07:51:01 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 07:58:40 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 08:09:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 08:13:45 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 08:16:09 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 08:30:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 08:42:56 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 08:51:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 09:06:03 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 09:11:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 09:32:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 09:53:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 10:14:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 10:35:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 10:50:17 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 10:56:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 11:16:11 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 11:32:48 TS-P500 webGUI: Successful login user root from 10.10.2.127
Mar 21 11:33:24 TS-P500 kernel: mdcmd (37): set md_num_stripes 1280
Mar 21 11:33:24 TS-P500 kernel: mdcmd (38): set md_queue_limit 80
Mar 21 11:33:24 TS-P500 kernel: mdcmd (39): set md_sync_limit 5
Mar 21 11:33:24 TS-P500 kernel: mdcmd (40): set md_write_method
Mar 21 11:34:04 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 11:34:27 TS-P500 kernel: md: sync done. time=38009sec
Mar 21 11:34:27 TS-P500 kernel: md: recovery thread: exit status: 0
Mar 21 11:35:04 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 11:37:40 TS-P500 emhttpd: read SMART /dev/sdg
Mar 21 11:38:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 11:49:29 TS-P500 emhttpd: spinning down /dev/sdd
Mar 21 11:52:46 TS-P500 emhttpd: spinning down /dev/sdg
Mar 21 11:58:01 TS-P500 crond[1737]: failed parsing crontab for user root: Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
Mar 21 11:59:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:00:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:01:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:02:05 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:03:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:05:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:06:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:11:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 21 12:12:03 TS-P500 emhttpd: read SMART /dev/sdd
Mar 21 12:12:06 TS-P500 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update -
-
On 12/28/2022 at 4:32 PM, JorgeB said:
I believe that for SMB multichannel with Linux, unlike Windows, you set the IP for each NIC using a different subnet.
Oooh. means that would be an issue as i only had one subnet throughout my network.
-
16 hours ago, JorgeB said:
First line is not needed, not sure about the other ones, best to leave them.
Thanks i'll remove the 1st line at leave the other for now.
How bout the error Multiple NICs on the same IPv4 networketh0 and eth1 both have IP addresses on the 10.10.2.0 network, should i just ignore them?
Another question since both Ethernet port 0 and 1 are connected to the switch and should i enable bridging for both port or just eth0 since all the docker and VM are point to Eth0?
Parity check paused Disk 2 Rear Error no info and no detail, what should i do next?
in General Support
Posted
Thanks for the info.
Ive perform SMART Short and Extended Self-test with no error.
Ive check the cable and power connector seems secure.
I'm now doing a rebuild since no error been report after that.