So I upgraded from 4.7 to 5.0-rc8a over the weekend pretty easily.

The only thing that I got confused on, was once the upgrade was complete, I could not connect to my existing shares.

Well,...went back and read the REST of the upgrade instructions, and found out that I needed to run the utility to assign new permissions to all of the drives. Once I did that, I disconnected the existing shares, re-established the connections and all is well.

 

I then upgraded my parity drive from 2T to 3T,..again, no problems, just too pretty long (which was expected)

Now I took the 2T drive, and replaced a 256G drive. No problems.

 

I then took that 256G drive and replaced the 120G cache drive.

Once I booted up,..everything was fine,..but then I realized, the data that was on the 256G drive was still there (duh! of course it is).

 

I also noticed that the one of the shares had the orange ball letting me know that soemthing for this share is on the cache drive.

I suppose I could have just allowed it to push the data from cache to that share since the data was identical.

But, here's what I did,..I mapped to the cache drive and deleted everything there manually.

That deleted everything,..except,...it couldn't delete, a couple of folders and files, saying that those files were in use by something else. ?

 

I didn't have that folder or files open somewhere else,...so was puzzled?

I was able to rename the folder to "delete_me",...thinking that I'd let the cache push this to the share, and then maybe, I'd be able to delete this folder then. Well, no dice, once over there,...same thing,..couldn't delete the "delete_me" folder,..with same error.

 

I'm thinking that that folder, for some reason may have some permission issues? But then why the error, "files in use,..."

 

So here's the questions:

 

What do I do to get rid of the folder? Telnet to that share and check permissions, then chmod, then delete? Run the premission tool again? Something else?

 

What is the proper way to replace a cache drive,..since you'd probably want to replace it with a larger one, and probably one of the drives in the array? (I ask this question, and will be searching the Forum for the answer as well)

 

 

 

 

 

Okay,..so I telnet'ed into the folder and sure enough, it was a permission issue.

Since I was signed in as root,...I was able to do a "rm -rf delete_me" on that folder and its contents.

 

Lesson learned.