March 28, 201214 yr Author DAMMIT! Spoke too soon... yes, I can see and read from the shares now, but I can't WRITE to them... tried to TerraCopy some files in and get a popup "<folder name> is no longer accessible" and copies nothing.. CRAP! HELP, anyone?
March 29, 201214 yr Check and make sure your permissions for the shares are set correctly. Doesn't sound like a samba permission issue but best check.
March 29, 201214 yr Author Check and make sure your permissions for the shares are set correctly. Doesn't sound like a samba permission issue but best check. well the problem is that I can SEE them and read them, but when I try to write its a 'the folder is no longer available' not 'unable to write' (unless that's the same thing), but I went in and checked them all, actually reset them all (again the strangeness, I had all the disk'x' shares set to be exported but hidden... and it unhid them. I redid all the shares (that is set them over and re-saved them...) no difference. I did notice one ... odd... thing... on 4.7, the Server is identified as 'BURBANK' (caps), on 5b14, it's 'burbank' (all lower case). Probably means nothing but it's a difference. I'm back on 4.7 now and everything is working fine... tomorrow I'm going to try it over and change the name of the server.. something not getting cleared out somewhere perhaps? If anyone has ANY ideas, HELP! I'm wondering if the configs somehow are borked up and I need to start from scratch... is there a wipe out the configs rebuild the array and KEEP the data on the disks?
March 29, 201214 yr Author ok that last sentence didn't make sense, too much caffeine I guess... Is there a way to just start with a brand new, empty 5b14 setup, new config, KEEP the data on the existing drives and rebuild parity. I would HOPE that would correct any gotcha's in the configs that could be causing this?
March 29, 201214 yr Take a screen shot of the disk assignments. Format and prepare the flash as if new. When the system start assign the drives as recorded and start the array. Parity will rebuild. DO NOT FORMAT any disks!!. If a data disk is reported as unformatted then ask for further instructions.
March 29, 201214 yr Author Thank's.. that's my last resort, I'm still hoping to hear something from Tom (I know he's moving and busy), this MUST be something simple or I'm totally unique (ha!)
April 1, 201214 yr Author Well it's been over a week since I heard from Tom and no solution. And this has stumped all here it seems. I'm going to take a large step back and see what I can do short of wiping out my data and starting over. If I succeed I'll post what I did, if I fail.. I'll start a new thread with a fresh statement of the problem
April 1, 201214 yr This is one of those that being in front of the console would come in handy. Some things are just hard to figure out over the internet,
April 1, 201214 yr Author This is one of those that being in front of the console would come in handy. Some things are just hard to figure out over the internet, Yeah, been there, done that, stinking t-shirt. I think something is just borked that doesn't migrate over properly, rebuilding the arrary (metioned earlier) may be the best solution. Either that or I'm putting together a second build and just start with 5b14 and copy everything over and then wipe the 1st one and go from there.
Archived
This topic is now archived and is closed to further replies.