dar

Thanks for the pointer to the readme - I should have read this 1st When I powered on my array now, the issue was gone. I'm now thinking this could have been a browser issue instead since the only thing that changed was my browser session. I don't think this was related to unraid at this point since the array seemed to be working fine - just a browser display issue. I will monitor and if this happens again I will post diagnostics.zip as suggested. Thanks.

I just upgraded from 4.7 to latest stable 6 release (6.1.9 I believe) - all good, seamless upgrade, array fully working except that it wanted to rebuild parity. I followed the procedure to create a new config and simply validate parity. Parity validate passed with 0 errors but all my drives are missing from the configuration (in the dashboard and main UI). Unraid says the configuration is valid. Before I redo the config again I just wanted to know if this is a known issue. Did I miss something? Reboot of the array does not bing the drives back to the UI. My shares are there and they seem to work so this appears to be a UI display issue only - for all other purposes it appears my array is online and good.

Just getting started with unraid - so far so good. I've noticed a couple of things that I'm not easily finding clear answers on. 1) Physical file size. I moved about 1.3TB over to a share that spans 2 disks. If I compare sizes, the folder I moved (HFS+) is taking up about 100G less than the unraid (reiserFS) physical size. Is this normal? I also see all small files taking up 1MB. Is this normal also? Does this mean small <1K files will always use up 1M of space in ReiserFS? 2) File permissions. It seems the unraid shares have execute permissions set on some files. I don't think this is an issue but was wondering if I can change the permissions on the share folder or if there is a reason to leave it as it is? If someone can explain or point me to a link that covers this it would be much appreciated. Cheers. [update] Found out why sizes were confusing in OSX. This link provided the solution http://hints.macworld.com/article.php?story=20110208234803495 To fix the 1M file reporting problem add the following line to the server's smb.conf (use config/smb-extra.conf for unraid): allocation roundup size = 0 Restart the Samba daemon, reconnect to the share, and files under one megabyte should now be calculated correctly in Finder. It appears the unraid SMB server rounds up all reported file sizes by default to 1M and osx appears to be one of the few smb clients that actually use this reported size. This smb-extra.conf file will also allow me to change the share permissions as well.

I'm new to unraid and in the process of researching my build. I'm just now trying a Seagate ST2000DL003 (2TB, 6gb/s SATA III) in a single drive enclosure that is rated for SATA II 3gb/s. My motherboard EP45-UD3R will support drives at 3gb/s so I thought that the enclose would be fine since the drive would run at SATA II speeds. However, I'm noticing unexpected errors and random drive dismounts when the drive is in the enclosure - seems fine however directly connected to the MB. Does anyone have experience with this? Google points to some issues with the Seagate drives as well so there are lots of variables still for me to sift through. My enclosure is the Thermaltake N0023SN rated to SATA II speeds but with the connection being largely passive (single drive with some LED's for activity etc.) so I was thinking this should be a non issue. Any thoughts would be appreciated. Thanks