Jump to content

[SOLVED]Confirming correct share settings please


kenzo86

Recommended Posts

Hi guys, Newbie here. I have read the wiki articles and blogs and just wanted to make sure everything was ok from my end.

 

Setup 4x3TB non parity array + 60gb SSD cache for plex files and plugins/dockers

 

I would like unraid to follow the following structure

 

Movies > "Movie folder" > "file"  *

TV > "TV Series folder" > "files"

 

The "movie folder" may contain nfo and ?metadata for plex, (or is all plex data stored on cache? sorry never used plex before)

 

I have created 2 Shares (2 top folders: Movies  and TV), both high-water allocation settings, both using 60gb cache disk. I have left split level as 1.

In windows, I see my disks (1-4), cache and "movies" (user share). Disk 1 has 2 folders called movies and TV, but the other disks don't. Do I need to add the folders myself, or will unraid do it when the first disk becomes half full (as per highwater allocation rules)

See here ::

 

Thanks

 

EDIT - SmallwoodDR82 has answered my questions. Thanks

Link to comment

Hi guys, Newbie here. I have read the wiki articles and blogs and just wanted to make sure everything was ok from my end.

 

Setup 4x3TB non parity array + 60gb SSD cache for plex files and plugins/dockers

 

I would like unraid to follow the following structure

 

Movies > "Movie folder" > "file"  *

TV > "TV Series folder" > "files"

 

The "movie folder" may contain nfo and ?metadata for plex, (or is all plex data stored on cache? sorry never used plex before)

 

I have created 2 Shares (2 top folders: Movies  and TV), both high-water allocation settings, both using 60gb cache disk. I have left split level as 1.

In windows, I see my disks (1-4), cache and "movies" (user share). Disk 1 has 2 folders called movies and TV, but the other disks don't. Do I need to add the folders myself, or will unraid do it when the first disk becomes half full (as per highwater allocation rules)

See here ::

 

Thanks

 

EDIT - SmallwoodDR82 has answered my questions. Thanks

 

Glad you got your questions answered.  For others that stumble on to this thread, unRAID will automatically create the folders on the drives in the system once high-water kicks in and tells it to.  You do not have to proactively create those folders.

Link to comment
  • 3 months later...

Hi guys, Newbie here. I have read the wiki articles and blogs and just wanted to make sure everything was ok from my end.

 

Setup 4x3TB non parity array + 60gb SSD cache for plex files and plugins/dockers

 

I would like unraid to follow the following structure

 

Movies > "Movie folder" > "file"  *

TV > "TV Series folder" > "files"

 

The "movie folder" may contain nfo and ?metadata for plex, (or is all plex data stored on cache? sorry never used plex before)

 

I have created 2 Shares (2 top folders: Movies  and TV), both high-water allocation settings, both using 60gb cache disk. I have left split level as 1.

In windows, I see my disks (1-4), cache and "movies" (user share). Disk 1 has 2 folders called movies and TV, but the other disks don't. Do I need to add the folders myself, or will unraid do it when the first disk becomes half full (as per highwater allocation rules)

See here ::

 

Thanks

 

EDIT - SmallwoodDR82 has answered my questions. Thanks

 

Glad you got your questions answered.  For others that stumble on to this thread, unRAID will automatically create the folders on the drives in the system once high-water kicks in and tells it to.  You do not have to proactively create those folders.

 

What if you don't want to wait for unRAID to create them? I've got mine set to "manual" and was hoping to setup as follows:

j7w1dy.jpg

 

I want those folders all on disk 2 as that's the "important" content I'd like to back up and it should help divide the data fairly evenly between disks. It also means that only disk 2 needs to spin up for backup.

 

So how do I do that...?

Link to comment

I want those folders all on disk 2 as that's the "important" content I'd like to back up and it should help divide the data fairly evenly between disks. It also means that only disk 2 needs to spin up for backup.

 

So how do I do that...?

Make each folder that you want to stay only on disk 2 its own share which includes only disk 2, instead of making them subfolders of shares that also include other disks.
Link to comment

I want those folders all on disk 2 as that's the "important" content I'd like to back up and it should help divide the data fairly evenly between disks. It also means that only disk 2 needs to spin up for backup.

 

So how do I do that...?

Make each folder that you want to stay only on disk 2 its own share which includes only disk 2, instead of making them subfolders of shares that also include other disks.

 

I want Photos, Music, TV shows (and the Family genre under Movies) to all show up in Media though. I don't want two separate media folders that I need to browse to for media content.

 

If I temporarily set the minimum free space to something larger than what's available on disk 1, will unRAID create the appropriate shared folder on disk 2?

Link to comment

I want those folders all on disk 2 as that's the "important" content I'd like to back up and it should help divide the data fairly evenly between disks. It also means that only disk 2 needs to spin up for backup.

 

So how do I do that...?

Make each folder that you want to stay only on disk 2 its own share which includes only disk 2, instead of making them subfolders of shares that also include other disks.

Isn't the better way to do this setting the split level as 0, then manually creating the share folder on the disks you want it to stay on or split on?

Link to comment

I want those folders all on disk 2 as that's the "important" content I'd like to back up and it should help divide the data fairly evenly between disks. It also means that only disk 2 needs to spin up for backup.

 

So how do I do that...?

Make each folder that you want to stay only on disk 2 its own share which includes only disk 2, instead of making them subfolders of shares that also include other disks.

Isn't the better way to do this setting the split level as 0, then manually creating the share folder on the disks you want it to stay on or split on?

 

Thanks, that's exactly what I'm trying to do but I don't know how to get the shared folder to span two drives so all the media shows up in the one "Media" share. Will my minimum free space idea above fix that?

Link to comment

Split level 0 gives you a level of manual control on the granularity if where files and folder will be placed albeit at a little bit of additional effort to create the folder structure you want on each drive.

 

If you use split-level 0, then if you want a folder to span multiple disks, then simply create them manually on the required disks.  inRAID will see what disks the folder can occur on, and apply the allocation method to decide which of them should get a particular file or folder.

Link to comment

Split level 0 gives you a level of manual control on the granularity if where files and folder will be placed albeit at a little bit of additional effort to create the folder structure you want on each drive.

 

If you use split-level 0, then if you want a folder to span multiple disks, then simply create them manually on the required disks.  inRAID will see what disks the folder can occur on, and apply the allocation method to decide which of them should get a particular file or folder.

 

So If I create a second "Media" folder on disk 2 unRAID is smart enough to know to just add it to the "Media" share on disk 1 so long as the original share is setup to span both disks? Is that correct?

Link to comment

Split level 0 gives you a level of manual control on the granularity if where files and folder will be placed albeit at a little bit of additional effort to create the folder structure you want on each drive.

 

If you use split-level 0, then if you want a folder to span multiple disks, then simply create them manually on the required disks.  inRAID will see what disks the folder can occur on, and apply the allocation method to decide which of them should get a particular file or folder.

 

So If I create a second "Media" folder on disk 2 unRAID is smart enough to know to just add it to the "Media" share on disk 1 so long as the original share is setup to span both disks? Is that correct?

 

That is my understanding. When you look at the share level view it'll aggragate the folders. 

 

Edit: Just to clarify though. If you navigate to mnt/disk1/sharename it won't show the stuff on disk two. If however you look at the user level /mnt/user/sharename it'll show stuff on both disk1 and disk2, even if you manually create the folder on disk2.

Link to comment

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?

Link to comment

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?

Post your syslog.  And, what is the name you're giving the share?

Link to comment

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

 

 

 

Link to comment

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).

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

Link to comment

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).

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

Link to comment

Just for the heck of it, try getting rid of the space.  I very vaguely remember when I set my server up and problems with spaces in share names.  (my shares are called BackupDocuments, MusicLibrary, etc etc etc)

 

I could be wrong but its worth the 5 seconds of time to try

 

Link to comment

Just for the heck of it, try getting rid of the space.  I very vaguely remember when I set my server up and problems with spaces in share names.  (my shares are called BackupDocuments, MusicLibrary, etc etc etc)

 

I could be wrong but its worth the 5 seconds of time to try

 

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

Link to comment

Just for the heck of it, try getting rid of the space.  I very vaguely remember when I set my server up and problems with spaces in share names.  (my shares are called BackupDocuments, MusicLibrary, etc etc etc)

 

I could be wrong but its worth the 5 seconds of time to try

 

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

You can leave the free space blank (can't hurt), but what I was talking about was PublicShare instead of Public Share

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...