rsd

I know I tried with no luck. But if anyone else wants to confirm...

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.

I do (I'm the OP)

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?

all sold

1 sold, 2 left

another price drop!

PRICE DROP

bump, still available!

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....

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).

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

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

I haven't seen above 35 for my reds in a mid tower ATX case (NZXT Elite 210). Seems high

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!!

(I don't even have the SATA card yet but couldn't resist a good deal) Fyi, the seller accepted my offer of $4 each for 4 cables.

I've created the directories and run the update and restarted unraid multiple times and it isnt upgrading. This is what i get after hitting install each time: images/MyServer.jpg matched md5sum images/MySlots.jpg matched md5sum images/stock/Hitachi.png matched md5sum images/stock/Kingston.png matched md5sum images/stock/Maxtor.png matched md5sum images/stock/MyServer_sample.jpg matched md5sum images/stock/MySlots_sample.jpg matched md5sum images/stock/Samsung.png matched md5sum images/stock/Seagate.png matched md5sum images/stock/WD.png matched md5sum images/stock/bolt.png matched md5sum images/stock/down.png matched md5sum images/stock/myMainLogo.jpg matched md5sum images/stock/refresh.png matched md5sum images/stock/refreshall.png matched md5sum images/stock/spinning.gif matched md5sum images/stock/status_bt.gif matched md5sum images/stock/status_cache.png matched md5sum images/stock/status_dsbl.png matched md5sum images/stock/status_dsbl_new.png matched md5sum images/stock/status_dsbl_np.png matched md5sum images/stock/status_invalid.png matched md5sum images/stock/status_mt.gif matched md5sum images/stock/status_new.gif matched md5sum images/stock/status_np.png matched md5sum images/stock/status_np_missing.png matched md5sum images/stock/status_ok.png matched md5sum images/stock/status_raw.gif matched md5sum images/stock/status_wrong.png matched md5sum images/stock/up.png matched md5sum myMainConfigMain.html matched md5sum Downloading myMain_local.conf rev $Revision: 178 $ $Date: 2010-12-03 08:32:35 -0500 (Fri, 03 Dec 2010) $ Local myMain_local.conf file exists, /tmp/unmenu_tmp/myMain_local.conf not installed Exact same message here

Thanks Joe, you're the best!

Hi Joe, I could greatly use some help with cache dirs. I recently upgraded my mobo to a biostar 760+ and upgraded to unraid 4.54. I call cache_dirs in my go script using: /boot/cache_dirs -d 5 -w -e "VMC" Everything was working for a few weeks but now twice in the past 3 days I got some strange error that hard froze unraid (can't telnet to it, can't refresh the unmenu/web, when I manually hook up a monitor to it no commands are acknolwedged, can't see it on the network etc). It doesn't freeze after a reboot or anything but some random time afterwards (hours/days). This is what the last few syslog lines read from Unmenu: I see some different error messages when I go to the unraid box itself, a lot of stuff but this is the part that makes me think it is something cache_dirs related: I know my cache_dirs call is slightly modified from before (I didn't use to exclude the "VMC" folder), so I'll try just calling it with -w and see what happens. Any help is greatly appreciated!

I have 2 of the Samsung EcoGreen 1.5tb's in my unraid for a while (and same for a friend) and no issues. Maybe bad luck?

Having a BIOS that allows HPA to be disabled is not good enough. You need a BIOS that has the HPA off by default. Otherwise it's a time ticking bomb: the moment your CMOS battery dies, the HPA monster will strike. Perfect. You can forget about HPA now. Correct, to be more clear none of the bios's for rev 1.1 allowed you to manually turn off HPA or seemed to have it off by default from what I could tell.

Just thought I'd mention I decided to replace my GIGABYTE GA-MA74GM-S2 rev 1.1 which had no bios's that allowed for turning off hpa. I believe rev 2 and later have bios's that allow this to be disabled. So replaced it with a Biostar 760g mobo. No issues, and everything run well so far with this mobo! Very happy I made the change.

Thought I'd mention I installed this mobo to replace a GIGABYTE GA-MA74GM-S2 rev 1.1 which had no bios's that allowed for turning off hpa. No issues, and everything run well so far with this mobo! Very happy I made the change.

Thanks again for your help! I upgraded the MB bios but I do not see any option to disable HPA (I realize it's called a few different things but I don't see any of the expected terms). I have the Rev 1.x version of this MB and upgraded to the F5B bios. Anyone know if this version has a way to disable hpa or if it disables it by default now?

I checked and I actually only have HPA on Disk 3 of my data disks. I will upgrade bios/disable HPA, but do I need to remove the HPA via the hdparm command? If I do so, do I need to stop the array or do anything in particular? I just don't want to potentially corrupt/lose data on Disk 3. Thanks!