morgish
Members-
Posts
44 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
morgish's Achievements
Rookie (2/14)
0
Reputation
-
Hi Everyone, This is my array: Tonight I was watching a movie which is currently on Disk 1. The mover job started to move a 60GB file from the Cache to Disk 2 and throughput to the media box came almost to a complete hault. I tested pulling the same file to my desktop computer while mover was still running and could only manage 1MB/s. So when the mover job is running, IO on unused (during mover) disks is impacted. Can someone help me identify what I can do to reduce the impact on the machine when mover is running? Also the Cache is 2x 128 SSD's in Raid 0 (BTRFS) to make 256GB. Appreciate any help. Cheers, Kris
-
Gotcha. Appreciate the help Johnnie.
-
Thanks Johnnie, Just to clarify, my parity drive shows a Raw_Rear_Error_Rate of 120821149 but isn't showing/reporting anyway problems. I thought Reallocated sector count was the one to watch for?
-
Hi Everyone, I've been getting (disk has read errors) [NOK] in my daily report for (I know, i know) a couple of weeks now. It's reported on DISK 2. I ran a extended SMART test and it passed and from what I can see in the SMART stats, everything should be okay. I've attached my diagnostics log. Could someone please have a look over this and tell me what i'm dealing with? I did run the box out of space on the 6th of December (related?) Cheers, Kris unraid-diagnostics-20171220-0736.zip
-
Poor write speeds (Even inside VM) - Not cache problem
morgish replied to morgish's topic in General Support
Looking at the diagnostics (System - ethtool in particular) I found that 1) I still had bonding enabled from a previous setup (now back to a single NIC) 2) The link speed had been reduced to 10Mbit. Settings for bond0: Speed: 10Mb/s Settings for eth0: Speed: 10Mb/s I turned the bonding off and the network stack restarting returned it to speed: 1000Mb/s This may resolve my issue. -
Poor write speeds (Even inside VM) - Not cache problem
morgish replied to morgish's topic in General Support
Here is diagnostics of it in FAULT STATE. I'll get the fresh boot logs later, at this stage I would like to leave it in fault state to try to trouble shoot it. unraid-diagnostics-20170823-1016.zip -
Hi Everyone, This one is a bit weird - After my unRAID box is up for a couple of days I get poor writing speeds. -Reading form the array is full 1gbit speed. -Writing to the array drops from 1gbit to 20mbit and below. -Problem extends further than Samba. My VM doing a speedtest (fast.com) will drop from 100mbit to 20mbit. -Restarting unraid or unplugging/replugging the lan cable resolves the issue, but it does appear again in a couple of days. Not sure where to go from here, any advise as to here to look would be appreciated. Cheers, Kris
-
22 days strong! If this keeps going it seems it was either: ASPM disabled Disabled Observium Docker Link aggregation enabling
-
Just doing my jinx test by posting here. root@unRAID:/# uptime 14:42:46 up 15 days, 21:37, 1 user, load average: 2.04, 1.52, 1.37 15 days ago I found that pci 0000:06:00.0 already had ASPM disabled. This is eth1 so I moved my network cable from eth2 to eth1. I also enabled NIC bonding to enable another troubleshooting method.
-
NIC Bonding/Link aggregation - Status/Notification
morgish replied to morgish's topic in General Support
Thanks (as always) klamath. That's a good way to manually check. Is there a way for notification to be sent in the unraid warning emails? -
Hi Everyone, I have my 2 NIC's setup in active-backup mode. Apart from using ifstat to monitor traffic or reading dmesg log, is there a better way to view which NIC is active? Is there a plugin that can email me/notify me if a NIC fails and the backup becomes active? I tried searching but couldn't find much. Kris
-
root@unRAID:~# dmesg | grep eth2 e1000e 0000:06:00.1 eth2: (PCI Express:2.5GT/s:Width x4) 00:1f:29:57:08:d3 e1000e 0000:06:00.1 eth2: Intel® PRO/1000 Network Connection e1000e 0000:06:00.1 eth2: MAC: 0, PHY: 4, PBA No: D51930-004 device eth2 entered promiscuous mode e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx br0: port 3(eth2) entered listening state br0: port 3(eth2) entered listening state br0: port 3(eth2) entered learning state br0: port 3(eth2) entered forwarding state br0: port 3(eth2) entered disabled state br0: port 3(eth2) entered disabled state e1000e: eth2 NIC Link is Down e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx br0: port 3(eth2) entered listening state br0: port 3(eth2) entered listening state br0: port 3(eth2) entered learning state br0: port 3(eth2) entered forwarding state root@unRAID:~# Is entered disabled state a clue at all? Ned in this thread is showing the exact same symptoms: http://lime-technology.com/forum/index.php?topic=47927.0 I've disabled docker and rebooted. Time to start the clock again.
-
Having the exact same issue. Did you find a solution Ned?
-
aaaaaaaaaaand it happened again. This time I had a monitor attached. (Plugged keyboard in after couldn't ping unRAID box) -Terminal responds fine. -Cannot ping anything on the network but can ping it's own IP fine with returned packets. SYSLOG shows nothing out of the ordinary: Jul 22 18:00:01 unRAID logger: skipping "appdata" Jul 22 18:00:01 unRAID logger: mover finished Jul 22 19:00:01 unRAID logger: mover started Jul 22 19:00:01 unRAID logger: skipping "VDisks" Jul 22 19:00:01 unRAID logger: skipping "appdata" Jul 22 19:00:01 unRAID logger: mover finished Jul 22 19:13:09 unRAID kernel: usb 3-2: new low-speed USB device number 2 using uhci_hcd Jul 22 19:13:09 unRAID kernel: input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/0003:04F2:0403.0002/input/input5 Jul 22 19:13:09 unRAID kernel: hid-generic 0003:04F2:0403.0002: input,hidraw1: USB HID v1.11 Keyboard [Chicony USB Keyboard] on usb-0000:00:1a.0-2/input0 Jul 22 19:13:09 unRAID kernel: input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.1/0003:04F2:0403.0003/input/input6 Jul 22 19:13:09 unRAID kernel: hid-generic 0003:04F2:0403.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Chicony USB Keyboard] on usb-0000:00:1a.0-2/input1 Jul 22 19:13:20 unRAID login[4027]: ROOT LOGIN on '/dev/tty1' I ran /etc/rc.d.rc.inetd restart and everything returned to normal. I'm hoping this helps narrow it down. Thoughts?