January 18, 20188 yr For some reason, since I upgraded (from 6.3.5 to 6.4.0) and put in a key (was on a trial and went with a pro key and bought it) I've been having issues.. I haven't had this many problems (other than making them for myself learning unraid) before this. Dockers not starting or not working like they did, Now trace calls and /var/log is getting full (currently 60 % used). I don't know what is going on... When I built the server a month ago, I put new drives in and a mobo that I know is good with liquid cooling. I tested the drives with a burn in program and before I started the array, I did a full preclear on all the drives to find issues.. I know they can still fail, but I didn't have any issue before going to 6.4.0 Any Thoughts? Is it something I am over looking? Thanks for any help... whs-diagnostics-20180117-2359.zip Edited January 18, 20188 yr by Melocco
January 18, 20188 yr Community Expert This error is filling your log, and makes it difficult to check for other issues: Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Jan 16 15:16:37 WHS kernel: i2c i2c-0: Failed! (01) Never seen this error before, try googling it to see if there's a solution, other than that noticed this also: Jan 16 15:09:06 WHS unassigned.devices: Mount of '/dev/sde1' failed. Error message: does not match (record 0). Failed to mount '/dev/sde1': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details.
Archived
This topic is now archived and is closed to further replies.