February 17, 20197 yr For some reason I am having a chronic issue with loosing connectivity to unraid. The dashboard, the array, everything becomes inaccessible. The server is still working cause I can access the server management dashboard and I can see unraid is still running, but the network is down. This has happened three or four distinct times. Once is when I stopped the array. I restarted it and things were going fine. I then started my windows vm and a few minutes later the system became inaccessible. The second is when I wake the system from sleep. The system comes up fine then goes offline. Only way to get access is to restart the server. From a clean reboot, when I start the dockers and all vms everything works fine. Not sure where to look for solutions. Any help would be appreciated.
February 24, 20197 yr Author Another odd, possibly related issue. I'm watching Plex and deleting a few files using krusader docker and all of a sudden I loose connectivity to the shares folder. From what I can see the user folder with all my shares is empty. Fortunately all the files and shares still live on a user0 drive. A reboot appears to have fixed the problem. I've attached the part of the log that appears relevant. Any help is, of course, appreciated. new 2.txt
February 26, 20197 yr Author Ok. I am beginning to think this is connected to the vm. After rebooting a windows server vm, I lost connectivity for a short time (perhaps until the vm started back up). In the log I have these odd entries: Quote Feb 25 22:48:28 Unraid kernel: clocksource: timekeeping watchdog on CPU31: Marking clocksource 'tsc' as unstable because the skew is too large: Feb 25 22:48:28 Unraid kernel: clocksource: 'hpet' wd_now: 66658f6d wd_last: 8973c104 mask: ffffffff Feb 25 22:48:28 Unraid kernel: clocksource: 'tsc' cs_now: be07e86a944c cs_last: bd9b688cd446 mask: ffffffffffffffff Feb 25 22:48:28 Unraid kernel: tsc: Marking TSC unstable due to clocksource watchdog Feb 25 22:48:28 Unraid kernel: br0: port 1(eth0) entered disabled state Feb 25 22:48:28 Unraid kernel: br0: port 1(eth0) entered blocking state Feb 25 22:48:28 Unraid kernel: br0: port 1(eth0) entered forwarding state Feb 25 22:48:28 Unraid kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Feb 25 22:48:28 Unraid kernel: sched_clock: Marking unstable (115906422025000, 2138118)<-(115906854020732, -429783621) Feb 25 22:48:28 Unraid kernel: clocksource: Switched to clocksource hpet Feb 25 22:48:28 Unraid kernel: igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Down Feb 25 22:48:32 Unraid kernel: igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 25 22:48:33 Unraid kernel: br0: port 1(eth0) entered disabled state Feb 25 22:48:33 Unraid kernel: br0: port 1(eth0) entered blocking state Feb 25 22:48:33 Unraid kernel: br0: port 1(eth0) entered forwarding state A quick Google search and I came up with a few entries all dealing with vms including this one. I have a 750w power supply with two Intel® Xeon® CPU E5-2648L v3 @ 1.80GHz. I have two vms and 13 dockers running at all times. Average cpu load is about 40-50%. Could this be a hardware issue?
Archived
This topic is now archived and is closed to further replies.