onefastfreak

I have the 4GB so I'll give that a whirl as I have the next 2 days off... I'll report back with an update either way

That should be "Unraid is not set to be the master" (auto correct is only as good as the user.........) Anyways, does anyone have any idea? I've got zip response here and neither Tom or marcusone replied to PM's... As I can't find any consistent cause as to why some files get this message and others don't, I'm about to go back to 4.7. It seems I can try clicking on a file to open it sometimes 2, 3, or 4 times and get this error message... But hit the 'enter' key once and it opens right up... Go back just for kicks and try to click on it again and I get the error message. This is the same on 2 different wire networked pc's, a 2 month old, clean Win7 install with little on it but XBMC and the basics needed for an htpc, and my other Win7 workstation desktop. Help, please!? I waited on 5.0 forever and now I'm ready to go back...

Yes, I set the new permissions... Unfair is not set to be the master, but yes they're in the same group :-(

Anybody?? :-( I don't believe it's a drive spin up issue. I'm quickly losing the wife approval factor with this sporadic error....

I just upgraded from 4.7 to 5.0 over the weekend and have come across a new quirk... I've tried to do some research on it but the below post is all I can find mention of it... Specifically, I get the error message "The directory name is invalid" when I attempt to open a file through windows explorer (typically only the first time but sometimes the second time I try to open it too, but the file always opens by the third attempt). Any ideas on this or did this ever get ironed out? I don't know if this is connected, but I recently updated XBMC to a recent beta and occasionally it gives me an error message "The file is no longer available, would you like to remove the file from the library". It didn't do this in the latest stable release (but I need something in the newer beta), I had assumed this was because maybe the actual drive was spun down? I know this isn't the case with the first issue listed above as I can try to play two media files back to back after the drive is spun up and still get the error on the second file. Any input on these? I tried to follow the RC's without ever updating to them but now I'm trying to wade through a couple years worth of trouble-shooting to see if I have anything in common with anyone else. Thanks in advance!

I can't find the link now, but do a quick search for the file system : unknown message or whatever it is... it doesn't become "known" until the array is started. It's been covered, I ran across the same thing in my upgrade to 5.0 but remembered that it was expected.

Just upgraded from 4.7 to 5.0, all went smoothly here! Only questions now are surrounding the new plugins and if I need to reinstall any of the old "4.7 add-ons"... from what I can tell I don't think I need anything additional. I only ever had unmenu and a few of its "packages". Ready to toss my 3tb disks in there and get going! Thanks Tom(s)!

+1

Supermicro motherboards that have "-F" at the end have IPMI built in which allows nearly complete remote access to the machine over network interface (video, keyboard/mouse, even power & BIOS control)... Thus, no need for separate video functionality. I know several who have setup their servers hardware wise without ever attaching a monitor, put them away in the basement doing all the software install/setup remotely and never needed to see the hardware again for years.

yes, you can add them, but once assigned they cannot be pre-cleared, and since that step helps burn them in (to detect early failures) you might want to let that finish. Once precleared, it is easy to stop the array, assign them, and then start it up again. You can pre-clear them (un-assigned ) while parity is being initially calculates. Yeah thanks, I had them both running at the sametime (parity build and preclear on new disk)... The build is done and everything's good there... the preclear should be done in the morning and I'll add it to the array then. Thank you all for the help -- couldn't've done it without you.

Cool that's what I thought/meant... so I can physically add/plug it in so I can start the pre-clear while the array is rebuilding parity, then add it as disk4 later. It'll be a while, but I'll check back in when it's all good to go (crosses fingers). Thanks again to all who chimed in!

Wow, I get help from Joe! So since I have to rebuild the parity from scratch then, am I safe to add data disk4 to the server at this time? I figure it could be pre-clearing while the parity it being built... but I don't want to be wrong!

The license is tied to the GIUD of a usb stick. Should your stick die, Tom will provide you with a new key for your new stick. He doens't make you pay twice If what you're thinking about is to replace the stick by another and having a downtime of about a minute or so, no. Unless you buy two keys and replicate the configuration on the backup stick. Tom has been knows to provide users with a replacement key extremele quickly, in some cases within the hour. So if you made a backup of your configuration files, you will have a downtime of about an hour or so. Case in point, I was bringing my array down yesterday morning to add in an additional drive... went to fire it back up and my flash drive wasn't recognized by the bios, tried it in my Win7 machine, nothing. Ran to the store, got a new flash drive and emailed Tom with the new flash GUID and had a new key for it in about 30 minutes! I have my own support thread going to make sure I'm going through the right steps but so far I think I'm in good shape--and making a backup flash this time too

Alright done, now I have a blue ball by the parity and data disk1-3, still a green light on my cache drive. Do I bring the array online now? And will it automatically start the parity check? Wandering around the forums I've seen mention of correcting and non-correcting parity checks, which one would I want to run? Thank you again to all who've helped!

Right now here's what I have in there (Have another 2tb ready to put in, but not in yet): Parity - 2tb Hitachi Data - (2) 1.5tb Samsung, (1) 2tb WD Cache - 750gb WD I'm just not certain what order I had the (2) 1.5tb Samsungs installed... I know the rest of the configuration. So right now, I've got a blue ball next to the parity drive, green balls on disk1-3 and a green ball on my cache... but also a red ball on my phantom disk4 (actually my parity drive--but follow the above steps to assign them all as data drives to be sure). What's the next step to clear this error ("Too many wrong and/or missing disks!") and make sure my parity's still okay?