The Problem
-Two syslogs are attached. AfterBootup is from the initial usb stick, New is from a fresh one. I copied all the files from the old to my Windows laptop as a backup in case the old syslog has something of importance.
-I can't access the UnRaid gui at 192.168.1.100, //tower/, or the SMB share via a Macbook
-Gui page times out, Chrome says ERR_CONNECTION_REFUSED. Finder doesn't show any connection activity.
-Problem started after attempting & successfully getting Xenserver running
-Problem exists whether UnRaid is a Xen VM or booted "bare metal" from the usb drive
-Problem existed on my old UnRaid usb drive and persisted after formatting/unzipping/make-bootable-ing it fresh
Steps Leading Up to the Problem
-Was working fine until I decided to try getting Xenserver up & running yesterday
-Followed this guide http://lime-technology.com/forum/index.php?topic=30719.0
-Eventually got Xenserver running and was able to boot unraid & run commands from my Windows laptop (not the Tower machine)
-Tower machine had the local IP 192.168.1.100 and UnRaid had 192.168.1.124, verified by "ifconfig eth0" and info in my router's client table
-Like "The Problem" states, after this, I couldn't access the gui or the SMB share.
Attempted Solutions
-Reboots (virtual & physical)
-Booting Tower machine directly from usb rather than through Xenserver
-Backing up UnRaid usb drive, formatting, unzipping UnRaid v5.x, make-bootable.bat
System Specs
-Note that my Win8, Xen, and UnRaid are all on the same physical machine, I interrupt the boot process depending which one I need at the time.
Intel i7 3770 3.4 Ghz
Gigabyte GA-Z77-DS3H rev1.0
16 GB Patriot 1600 Mhz
Nvidia GeForce GTX 670
120 GB Samsung 840 Pro SSD (Win8 OS)
250 GB WD Blue (Win8 Docs & Programs, temp)
1.5 TB WD Green (Win8 Docs & Programs, not currently installed)
250 GB WD Green (Xenserver) *
4 TB WD Green (UnRaid disk1)
4 TB WD Green (UnRaid disk2)
*note this drive is weird. 3-4 years ago I was trying to format the 250 GB WD Blue above for my old Xbox and selected this drive by mistake. It physically has 2 TB of storage, but the program I used really, really messed the drive up at a super low level, so it now only reports as 250 GB. No amount of wiping, partitioning, new volumes, etc has fixed it. The IT guy at my old internship was even stumped. Shouldn't matter here, but full disclosure I guess.
More Info to Provide
ifconfig eth0
Link encap:Ethernet HWaddr [what I assume is my mobo's mac address]
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:2981 (2.9 KiB) TX bytes:8367 (8.1 KiB)
Ping Results
C:\Users\[Windows user name]>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time=213ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 213ms, Average = 54ms
syslogAfterBootup.txt
syslogNew.txt