J.R.

Moving them via an Explorer window, why? Is there another method I'm supposed to use with unRAID? I'll try that (New Permissions) once the parity drive is finished re-syncing. What am I looking for it to do?

I get that that's how it's supposed to work but when I move the folder from disk 2 to disk 3 or create a duplicate (Media) folder on disk 3 the content in those disk 3 folders is not showing up in the "Public Data" folder or Media" share folder as you're telling me/I understood it should.

First there is no "level 0" in V6 it's just "Manual: do not automatically split directories", which yes, I have my shares set to but unRAID doesn't seem to want to let me actually manually do anything. I try to create a share to be on a specific disk and it simply won't create it. I try to move data to the disk on the share I FINALLY created and it tells me there's no space. Not only that but the new "Public Data" share I created that I told to exclude disk two...was on disk two!! (Though I assume that's why it's telling me it's out of space)

Ugghhh... Well now I've actually manged to create the "Public Data" folder and I've set it to exclude the 1st disk so that the data moves to the disk I want and now it's telling me there's not enough space on an empty 2TB drive for 80GB of files.

Yes but as I've posted before, I want to manually allocate which data is on which disk. I don't want unRAID to do it. Currently, it seems unRAID won't let me manually manage my data and create shares specific to or shared with drives at my discretion.

Well holy flying @#$%! As a last ditch effort, I tried not specifying an "included disk" and leaving it at the default "all"...and lo and behold *poof * it created the share!! Now how the hell do I manually organize the the shares on to separate disks to more evenly distribute the data across drives? Is this a limitation of the unregistered version? I'm planning on upgrading to Plus (and adding two more data drives and a cache drive) but was hoping get all the data sorted and situated BEFORE upgrading (Get the basic functionality working first THEN add the bells and whistles.)

Ran chkdsk on the USB flash drive. No problems on it.

So I moved everything off the 2nd disk and still getting the same "no space left on the device" error. Anyone have any brilliant suggestions before I do a fresh install of unRAID? (Gordie help me if I run in to this problem again on the fresh install!). Anything I need to know to do a reinstall?

Tried this, copied my existing "Media.cfg" share and renamed it "Public.cfg", rebooted server and the new share is still not showing up, just "media" still. I'm absolutely baffled, I though for sure that would HAVE to work. I'm going to try shifting all my data back on to one disk, clearing the second disk and seeing if that somehow fixes the problem...beyond that I just don't know what to do? Fresh install of unRAID? Is that easy enough to do without losing data from the array? It just seems odd to me that everything else seems to be working but this!

Fair enough! That's a typo (now fixed), should be TB, thanks. Running XFS, not RFS Not yet...was planning on adding that once I got the shares sorted.

I set up the Flash drive as per instructions, can't see why it wouldn't be or why that would have changed but I can check. I'll try copying one of the share files as suggested as well.

Wasn't my thread. I was trying not to clutter the board by making an unnecessary thread for a topic that already existed but here we are...

Yes, I tried just naming it "Public". Same error message as when I tried to name it "Public Share". I'm seeing that message on the monitor run directly from the server. I have free space set at 15GB. I'm also trying to create the share on the drive with 1.2TB of space so I can't see how that's the problem (nor 787GB free on the other). It's the same issue/error from a few days ago, so I doubt it's the flash drive but I can check that when I get home. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The only other thing I can think of trying is to remove everything back off the second drive to the first, reboot and see if I can create a new directory on second drive. A lot of hours of file moving though...I hope it actually accomplishes something

Yeah, I've tried rebooting a few times. I've got other folders I've created on the drives and they aren't showing up as shares...could that be related?

I can not seem to create further shares on my unRAID 6 server. This is the message unRAID is giving me: There is 787GB free on one drive and 1.27TB free on the other. So I don't know why unRAID thinks there's no space or how to correct that (which is obviously causing the issue with creating new shares). Here is my syslog: http://lime-technology.com/forum/index.php?action=dlattach;topic=35553.0;attach=24136 PLEASE, any help with solving this would be GREATLY appreciated.

OK, back home and the exact message I'm getting is: Can ANYONE help me figure out why it won't let me create any shares? Why does unRAID think there's no space?

Anyone?

I'm having this problem as well. unRAID 6 will not let me create user shares even after rebooting as stated above. Here's my syslog: http://lime-technology.com/forum/index.php?action=dlattach;topic=35553.0;attach=24136 Any help? FWIW, when I actually switched over to the servers monitor/keyboard it's telling me it can not create the share as the disk is too full (which does not appear to be showing up in the syslog). One disk has 787GB free, the other1.27GB free so I'm not sure what's in error there...? But Obviously it has something to do with why it's not working!

No that (PublicShare) didn't work either. It surely has something to do with unRAID thinking I have no room on the drives...I just don't know why it thinks that!

Left it blank (it showed 0KB) and still the same problem.

You mean the minimum free space? Set it to... blank?

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog Thanks, here it is. FWIW, when I switched over to my unRAID I saw that it's telling me it can not create the share as the disk is too full. One disk has 787GB free, the other1.27GB free so I'm not sure what's in error there...? syslog-2015-01-02-1545.zip

How would one do this....?

There looks to be nothing in the syslog after the reboot...WTF? I'm trying to create another "Media" share as outlined in the posts above and/or a "Public Share" folder. Neither are doing a thing. Yes I've tried both. Not sure how much of this you want/need to see so I've just copied a chunk. I believe this is all just boot up stuff...there's NOTHING showing I tried to add a share that I can see (though admittedly I'm a newb). Feb 1 14:52:21 tower rsyslogd: [origin software=rsyslogd" swVersion="8.4.2" x-pid="1142" x-info="http://www.rsyslog.com] start Feb 1 14:52:21 tower kernel: Initializing cgroup subsys cpuset Feb 1 14:52:21 tower kernel: Initializing cgroup subsys cpu Feb 1 14:52:21 tower kernel: Initializing cgroup subsys cpuacct Feb 1 14:52:21 tower kernel: Linux version 3.17.4-unRAID (root@develop64) (gcc version 4.8.2 (GCC) ) #1 SMP Fri Nov 21 17:43:18 PST 2014 Feb 1 14:52:21 tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Feb 1 14:52:21 tower kernel: e820: BIOS-provided physical RAM map: Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c6170fff] usable Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000c6171000-0x00000000c6177fff] ACPI NVS Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000c6178000-0x00000000c65c2fff] usable Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000c65c3000-0x00000000c69f0fff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000c69f1000-0x00000000d8697fff] usable Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000d8698000-0x00000000d88a0fff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000d88a1000-0x00000000d88b7fff] ACPI data Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000d88b8000-0x00000000d8df1fff] ACPI NVS Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000d8df2000-0x00000000d9ffefff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000d9fff000-0x00000000d9ffffff] usable Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000db000000-0x00000000df1fffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Feb 1 14:52:21 tower kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021fdfffff] usable Feb 1 14:52:21 tower kernel: NX (Execute Disable) protection: active Feb 1 14:52:21 tower kernel: SMBIOS 2.7 present. Feb 1 14:52:21 tower kernel: DMI: ASUS All Series/H87I-PLUS, BIOS 1005 01/06/2014 Feb 1 14:52:21 tower kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Feb 1 14:52:21 tower kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Feb 1 14:52:21 tower kernel: AGP: No AGP bridge found Feb 1 14:52:21 tower kernel: e820: last_pfn = 0x21fe00 max_arch_pfn = 0x400000000 Feb 1 14:52:21 tower kernel: MTRR default type: uncachable Feb 1 14:52:21 tower kernel: MTRR fixed ranges enabled: Feb 1 14:52:21 tower kernel: 00000-9FFFF write-back Feb 1 14:52:21 tower kernel: A0000-BFFFF uncachable Feb 1 14:52:21 tower kernel: C0000-CFFFF write-protect Feb 1 14:52:21 tower kernel: D0000-E7FFF uncachable Feb 1 14:52:21 tower kernel: E8000-FFFFF write-protect Feb 1 14:52:21 tower kernel: MTRR variable ranges enabled: Feb 1 14:52:21 tower kernel: 0 base 0000000000 mask 7E00000000 write-back Feb 1 14:52:21 tower kernel: 1 base 0200000000 mask 7FE0000000 write-back Feb 1 14:52:21 tower kernel: 2 base 00E0000000 mask 7FE0000000 uncachable Feb 1 14:52:21 tower kernel: 3 base 00DC000000 mask 7FFC000000 uncachable Feb 1 14:52:21 tower kernel: 4 base 00DB000000 mask 7FFF000000 uncachable Feb 1 14:52:21 tower kernel: 5 base 021FE00000 mask 7FFFE00000 uncachable Feb 1 14:52:21 tower kernel: 6 disabled Feb 1 14:52:21 tower kernel: 7 disabled Feb 1 14:52:21 tower kernel: 8 disabled Feb 1 14:52:21 tower kernel: 9 disabled Feb 1 14:52:21 tower kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Feb 1 14:52:21 tower kernel: e820: update [mem 0xdb000000-0xffffffff] usable ==> reserved Feb 1 14:52:21 tower kernel: e820: last_pfn = 0xda000 max_arch_pfn = 0x400000000 Feb 1 14:52:21 tower kernel: found SMP MP-table at [mem 0x000fd6f0-0x000fd6ff] mapped at [ffff8800000fd6f0] Feb 1 14:52:21 tower kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576 Feb 1 14:52:21 tower kernel: Using GB pages for direct mapping Feb 1 14:52:21 tower kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Feb 1 14:52:21 tower kernel: [mem 0x00000000-0x000fffff] page 4k Feb 1 14:52:21 tower kernel: BRK [0x01a09000, 0x01a09fff] PGTABLE Feb 1 14:52:21 tower kernel: BRK [0x01a0a000, 0x01a0afff] PGTABLE Feb 1 14:52:21 tower kernel: BRK [0x01a0b000, 0x01a0bfff] PGTABLE Feb 1 14:52:21 tower kernel: init_memory_mapping: [mem 0x21fc00000-0x21fdfffff] Feb 1 14:52:21 tower kernel: [mem 0x21fc00000-0x21fdfffff] page 2M Feb 1 14:52:21 tower kernel: BRK [0x01a0c000, 0x01a0cfff] PGTABLE Feb 1 14:52:21 tower kernel: init_memory_mapping: [mem 0x21c000000-0x21fbfffff] Feb 1 14:52:21 tower kernel: [mem 0x21c000000-0x21fbfffff] page 2M Feb 1 14:52:21 tower kernel: init_memory_mapping: [mem 0x200000000-0x21bffffff] Feb 1 14:52:21 tower kernel: [mem 0x200000000-0x21bffffff] page 2M Feb 1 14:52:21 tower kernel: init_memory_mapping: [mem 0x00100000-0xc6170fff] Feb 1 14:52:21 tower kernel: [mem 0x00100000-0x001fffff] page 4k

Ok...I've been trying to do this with no luck. At this point I can't even seem to add ANY share folder at all. Let alone the shared one I'd like to add for my "Media" folder. I fill out all the info (share name, free space, split level, disk allocation) and click "Add Share"...and nothing. I even tried rebooting the server. Any help?