October 1, 201213 yr I am running unRaid Plus v4.7 I just recently added 2 hard drives after getting disk full messages when I try to transfer files to the array. I formatted both drives, assigned both drives a disk device number (e.g. disk3 device: pci-0000:00:0e.0-scsi-1:0:0:0 host6 (sdc) Hitachi_HDS5C3020ALA632_ML0220FA0SNXXX), and both drives have a green light next to them in the Disk status menu. Did I forget to do something when I upgraded to the plus version? I don't understand why I am out of space when I did the exact same procedures when I moved from 2 hard drives (parity + disk1 device) to the 3 hard drives limit of the free version. Thanks in advance for all your help. Day EDIT 10/01/2012 Joe L.'s advice worked. Under the 'Shares' menu, I modified my split level from 1 to 3 and modified my 'Min. free space' from blank to 10485760. Just like that I'm able to add data to the new drives.
October 1, 201213 yr I am running unRaid Plus v4.7 I just recently added 2 hard drives after getting disk full messages when I try to transfer files to the array. I formatted both drives, assigned both drives a disk device number (e.g. disk3 device: pci-0000:00:0e.0-scsi-1:0:0:0 host6 (sdc) Hitachi_HDS5C3020ALA632_ML0220FA0SNXXX), and both drives have a green light next to them in the Disk status menu. Did I forget to do something when I upgraded to the plus version? I don't understand why I am out of space when I did the exact same procedures when I moved from 2 hard drives (parity + disk1 device) to the 3 hard drives limit of the free version. Thanks in advance for all your help. Day Yes, you told us nothing about your "split levels", or "min-free-space", or included/excluded disks in BOTH user-shares in general and for the specific user-share user-shares involved. We would need to know the EXACT contents of those fields, as many have used them incorrectly. Without the fields being set correctly for your needs, 99% of every program out there starts new files as zero bytes and appends to it as the file is transferred. There is almost ALWAYS room for a zero length file, the transfer fails some time later when the disk actually fills. Joe L.
October 1, 201213 yr Author Thanks for your speedy response Joe L. "Yes, you told us nothing about your "split levels", " My split level is '1' "or "min-free-space", " This field was left blank. Do I need to specify this? I just assumed that when I had no problems going from 2 to 3 hard drives that I didn't need to fill this out. What % of free space would be best? "or included/excluded disks in BOTH user-shares in general and for the specific user-share user-shares involved." Both of these fields are left blank. Again I don't know enough about how to set these fields correctly. "We would need to know the EXACT contents of those fields, as many have used them incorrectly." Most of the fields in the 'Shares' menu are left blank. I just followed Robbie Ferguson's instructional video on YouTube to setup my server. I'm using unRaid as a media server for XBMC. FYI the rest of the 'Shares' menu looks like this: Export settings Flash share (SMB): Export read/write Disk shares (SMB): Export read/write Disk shares (NFS) : blank User shares: Enabled User Shares Share name: Backup Comments: Data Backup Allocation method: High Water Min. free space: blank Split level: 1 Included disk(s): blank Excluded disk(s): blank Export (SMB): Export read/write Export (NFS): blank Please inform me of whatever other settings I need to provide for y'all to help me. Thanks again, Day
October 1, 201213 yr Split level of 1 is probably incorrect. Only the top level (the user-share level) will ever be duplicated across a new disk with a split level of 1. To have a sub-directory duplicated across disks you need a split level of 2 or greater.. A blank "min-free" is also incorrect. It is in kb, and should be roughly twice as big as the biggest file you are storing on that user-share. If you store 5Gig ISO files, it should be set to 10Gig /1024 = 10485760 kB So, for 5 GB files, the min-free field should be set to 10485760 Only you will know the proper split level. What "directory" were you writing that fails due to a lack of space. (full path to directory/file) It is fine to leave the included/excluded fields blank. I've never needed them either. They just let you restrict/exclude data to the listed disks. Joe L.
October 1, 201213 yr Author Thank you so much for your help. I'm currently running my weekly parity check so once it's done, I'll implement your suggestions then I'll report back with my findings. Day
October 1, 201213 yr Everyone always suggests putting in a minimum free space, but it won't do anything useful with the wrong split level. Just letting you know, it's a fairly useless setting until your disks are close to full unless you're using the fill-up allocation method. Provide the directory structure you are using and also tell us which directory levels you are willing to let split to multiple disks. Have you tried reading the shares section in the unofficial manual in the wiki?
Archived
This topic is now archived and is closed to further replies.