rsd

Members
  • Posts

    80
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

rsd's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I know I tried with no luck. But if anyone else wants to confirm...
  2. I actually forgot I believe I tested this before I started this thread, but it's possible I missed a device (as I have several). Would be curious to see anyone else try it. I know I turned off my wife's mac when testing.
  3. I'm no expert but it seems like this message started appearing for people around the same time. Was there some IOS update that could have been the trigger?
  4. I would agree with you if you were talking the desktop drives like my ST3000DM001s. But I've seen many posts of good things about the NAS variety. Was going to say the same thing as BobPhoenix. The NAS drives are generally well reviewed. Ironically I had recently ordered 6 WD 4TB Reds and I had to RMA 2 of them. Oddly enough my 1.5TB Seagates that were notorious for going bad are still going strong in my other Unraid box....
  5. EDIT: 1 sold, 2 drives left: $150/ea or $295 for both Ended up not needing these for my server, so I have 3 brand new and unopened/unused Seagate 4TB NAS Hard Drives ST4000VN000: http://www.amazon.com/Seagate-SATA-Cache-Drive-ST4000VN000/dp/B00D1GYO4S 3 Year Warranty on each. PRICE DROP - Selling for $150/ea or $435 for all three shipped to CONUS via USPS Priority (I'm shipping out of the USA).
  6. I couldn't figure out why I was getting this message anymore but I found a line to add to my go script that turns off avahi and that made it go away. I don't have many IOS products and my wifes macbook can still connect to the unraid server via smb anyway. She doesn't use timemachine so I was happy with this resolution. Here is the line I added: for i in /etc/rc.d/rc.avahi* ;do :>$i ;done
  7. Hi, Just noticed that suddenly I have this error message repeating over and over in the log: Jul 2 22:28:13 Tower avahi-daemon[8475]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?) Jul 2 22:28:45 Tower last message repeated 4 times Jul 2 22:29:49 Tower last message repeated 8 times Jul 2 22:30:54 Tower last message repeated 9 times I've attached a full syslog too (after multiple reboots). I've tried doing a check disk on the USB drive, powering down, updating dynamix and unmenu. Still appears. Attached Log is after doing all this I tried rebooting and still the same error message popping up. I have tried replacing the network cable. Never seen it before, and don't have any issues. I'm running unraid 5 final with Dynamix. Been running this server for a few months. Reading more it seems like Avahi is related to AFP and/or IOS stuff, which I have never enabled. Any ideas? I found one person who posted the same/similar error in the v6 forum but no explanation/solution that I could find. Should I be worried? Thanks syslog-2014-07-02.zip
  8. I haven't seen above 35 for my reds in a mid tower ATX case (NZXT Elite 210). Seems high
  9. Selling a SUPERMICRO MBD-C2SEE-O LGA 775 Motherboard (new in box never used) + Intel Celeron-L 430 (purchased used, I never personally used it; includes heatsink from another LGA 775 CPU I had) all for $20 + s/h (within CONUS) Would make a nice spare Unraid build Unraid like it's 2009!!