BitterDone

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

BitterDone's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The Problem -Can't access SMB share from Finder on Max OS X 10 -Error Message: There was a problem connecting to the server "Tower". The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and try again. Steps Leading Up to the Problem -Previously was using UnRaid v5.06 trial. Filled my 2nd data drive so Pro key it is. -Might as well "update" to v6.0b, formatted flash & loaded v6.0b & Pro.key to it -SMB was working fine on same drive each time -Started & finished transferring in data from a 4 TB network drive -Shutdown etc to insert freshly precleared 6 TB WD Red -Now unable to get SMB working. No apparent errors from UnRaid server. Always get these errors in Finder http://i.imgur.com/c7LeKxK.jpg http://i.imgur.com/AsfxSFY.png -Next drive (2 TB) was NTFS-formatted, so I shutdown/etc and mounted with SNAP -Still unable to get SMB working. Same deal -Did internal copy via SNAP -Shutdown/etc to remove 2 TB drive, start up, nothing. -All sorts of SMB/NFS/AFP configuration attempts. -Currently AFP is working, but I can't see individual drives. Just the Share as a whole. Is this a bug/feature of AFP? Attempted Solutions -Connect via root/(blank), test user test/testa, Mac OS X username/password (registered user) -smb://Tower/ -smb://Tower/Media -smb://192.168.1.100 -smb://192.168.1.100/Media System Specs -Note that my Win8 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) 1.5 TB WD Green (Win8 Docs & Programs) 250 GB WD Blue (Spare drive, not currently installed) 250 GB WD Green (Xenserver, not currently installed) * 4 TB WD Green (UnRaid disk1) 4 TB WD Green (UnRaid disk2) 4 TB WD Green (UnRaid disk3) 6 TB WD Red (UnRaid disk4) 4 TB WD Green (UnRaid disk5) *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 eth0 flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255 ether [mobo MAC addr] txqueuelen 1000 (Ethernet) RX packets 399089 bytes 48918371 (46.6MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 228648 butes 43991860 (41.9MiB) TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0 Ping Results [Mac name]:~ [username]$ ping 192.168.1.100 PING 192.168.1.100 (192.168.1.100): 56 data bytes 64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=118.977 ms 64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=3.677 ms 64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=3.427 ms 64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=3.462 ms 64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=3.464 ms 64 bytes from 192.168.1.100: icmp_seq=5 ttl=64 time=3.406 ms 64 bytes from 192.168.1.100: icmp_seq=6 ttl=64 time=3.444 ms 64 bytes from 192.168.1.100: icmp_seq=7 ttl=64 time=3.090 ms 64 bytes from 192.168.1.100: icmp_seq=8 ttl=64 time=3.453 ms 64 bytes from 192.168.1.100: icmp_seq=9 ttl=64 time=3.432 ms 64 bytes from 192.168.1.100: icmp_seq=10 ttl=64 time=3.423 ms ^C --- 192.168.1.100 ping statistics --- 11 packets transmitted, 11 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 3.090/13.932/118.977/33.218 ms syslog.txt
  2. I freakin hate technology sometimes. tl;dr it's working now. I grabbed an old pc and boot from my current unraid drive. Started no problem and I could access the web gui. So, now it's either a problem with my original pc or some network-specific config. The first thing I did was remove my original pc (referred to as Tower from here on out)'s DHCP reservation from my router, as I'd previously set it to 192.168.1.100. AFter forgetting to hit Apply and a few reboots later, Safari on my Macbook still wasn't loading the page. I decided to try Firefox, and what the f do you know, the UnRaid gui loads. No idea why. Since I'm booting a fresh UnRaid drive it shouldn't matter, but my next thing to try is booting to safe mode, which honestly should've been the first thing I did. Also random tip, if your router has a usb port for networked storage and you're loading your UnRaid server from external usb hard drives, plug them into the router. Must faster transfer speeds than transferring over the network from another computer and uses less electricity (I assume).
  3. 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
  4. Link for the lazy http://www.newegg.com/Product/Product.aspx?Item=N82E16811112265