kin0kin

Members
  • Posts

    51
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

kin0kin's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I've set min free to 500mb. The disk has for example 10GB left. When I transfer a folder that's 14gb in total (12GB movie, 1mb this, 100mb that, and etc), all the smaller files would get copied over and when unraid attempts to copy the file larger than the available space it will fail, leaving all the previously copied files in the disk. This can be resolved if unraid treats every folder as a "container" like iso, but it doesn't. It's not possible to tell how big the smallest file may be. BDrip can be as big as 25-30GB. If I were to set 30GB free space, it'd probably weed out most of the problems but that's a lot of wasted space that needs to be used up manually. Is there a proper solution to this? I don't use split level. Can split level solve the problem? My structure is like this: /mnt/disk#/Movies/HD/<movie>/<content> /mnt/disk#/Movies/NEW/<movie>/<content> /mnt/disk#/TV Series/<tv series>/<season>/<content> I used to use high-water but it was huge mess when browsing through movie collection with fragmented files all over the array and some disks spun-down.
  2. I've always had this problem but never bothered to find a solution but I think it's about time. Share = Movies Included Disks = 1,2 Min Space = 50000 Allocation = fill-up Usually a movie folder would have Folder, a bunch of images, subtitle, and the movie file itself. Let's just say that the the hdd has 10GB left in it. When transferring a movie that is 14GB, unraid will copy everything in the content to the disk, but when it tries to copy the actual movie file, it will fail with insufficient space because the movie file is 14GB but the folder may include contents that are smaller in size. How could I set it so that unraid would automatically use the next disk instead of trying to "fill up" this hdd which is large enough for some files in a movie folder but not large enough for the movie itself?
  3. How do we go about exporting a list, i.e. csv of Disk, and what shares/folders are in the disk?
  4. Folks, I use fill-up for all the HDDs and manually move the folders from one disk to another. After lots of moving around, I just noticed that there are some duplicates here and there. However, how do I go about finding duplicates in every disk?
  5. I resolved the issue: #1 - Remove Simple Features (which I had installed) from flash drive #2 - Update to latest unraid #3 - Reboot #4 - Under Settings update the GUI Now adding the drive works
  6. I had the same issue and resolved it this way: #1 - Remove Simple Features (which I had installed) from flash drive #2 - Update to latest unraid #3 - Reboot #4 - Under Settings update the GUI Now adding the drive works
  7. Been using unraid for many years and today I decided to add 2 more drives. I inserted 2 x WD 20EURX into the array, stop the array, added the two disk, checked: Start will record the new disk information and bring the expanded array on-line. All new disks which have not been factory-erased will be cleared first; and, the array will be available after the clear completes. This process takes time, but the array remains protected at all times. Caution: any data on the new disk(s) will be erased! If you want to preserve the data on the new disk(s), reset the array configuration and rebuild parity instead. and click start. Nothing happens, it goes back to the same screen and unraid fails to clear the drives. I've never needed to use preclear script, what seems to be the problem? Jan 18 14:35:47 SV-UNRAID emhttp_event: driver_loaded Jan 18 14:35:48 SV-UNRAID emhttp: shcmd (258): rmmod md-mod |& logger Jan 18 14:35:48 SV-UNRAID emhttp: shcmd (259): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Jan 18 14:35:48 SV-UNRAID kernel: md: unRAID driver removed Jan 18 14:35:48 SV-UNRAID emhttp: shcmd (260): udevadm settle Jan 18 14:35:48 SV-UNRAID emhttp: Device inventory: Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD20EADS-00R6B0_WD-WCAVY4778249 (sda) 1953514584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD10EAVS-14D7B1_WD-WCAU49737055 (sdc) 976762584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD5000AAKS-00TMA0_WD-WCAPW1176824 (sdd) 488385527 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD10EAVS-00D7B1_WD-WCAU49248571 (sde) 976762584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD10EALS-00Z8A0_WD-WCATR0532565 (sdf) 976762584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD10EADS-00L5B1_WD-WCAU45849312 (sdg) 976762584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD20EURS-63SPKY0_WD-WMC300266546 (sdh) 1953514584 Jan 18 14:35:48 SV-UNRAID emhttp: SAMSUNG_HD204UI_S2H7J1AZA08751 (sdi) 1953514584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD6400AAKS-75A7B0_WD-WCASY1489916 (sdj) 625131864 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD6400AAKS-75A7B0_WD-WCASY1185307 (sdk) 625131864 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD20EURX-63T0FY0_WD-WCC4M1229044 (sdl) 1953514584 Jan 18 14:35:48 SV-UNRAID emhttp: WDC_WD20EURX-63T0FY0_WD-WCC4M0867681 (sdm) 1953514584 Jan 18 14:35:48 SV-UNRAID kernel: md: unRAID driver 2.2.0 installed Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (1): import 0 8,0 1953514552 WDC_WD20EADS-00R6B0_WD-WCAVY4778249 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk0: [8,0] (sda) WDC_WD20EADS-00R6B0_WD-WCAVY4778249 size: 1953514552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (2): import 1 8,32 976762552 WDC_WD10EAVS-14D7B1_WD-WCAU49737055 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk1: [8,32] (sdc) WDC_WD10EAVS-14D7B1_WD-WCAU49737055 size: 976762552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (3): import 2 8,48 488385496 WDC_WD5000AAKS-00TMA0_WD-WCAPW1176824 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk2: [8,48] (sdd) WDC_WD5000AAKS-00TMA0_WD-WCAPW1176824 size: 488385496 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (4): import 3 8,64 976762552 WDC_WD10EAVS-00D7B1_WD-WCAU49248571 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk3: [8,64] (sde) WDC_WD10EAVS-00D7B1_WD-WCAU49248571 size: 976762552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (5): import 4 8,80 976762552 WDC_WD10EALS-00Z8A0_WD-WCATR0532565 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD10EALS-00Z8A0_WD-WCATR0532565 size: 976762552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (6): import 5 8,96 976762552 WDC_WD10EADS-00L5B1_WD-WCAU45849312 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk5: [8,96] (sdg) WDC_WD10EADS-00L5B1_WD-WCAU45849312 size: 976762552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (7): import 6 8,112 1953514552 WDC_WD20EURS-63SPKY0_WD-WMC300266546 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk6: [8,112] (sdh) WDC_WD20EURS-63SPKY0_WD-WMC300266546 size: 1953514552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (: import 7 8,128 1953514552 SAMSUNG_HD204UI_S2H7J1AZA08751 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk7: [8,128] (sdi) SAMSUNG_HD204UI_S2H7J1AZA08751 size: 1953514552 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (9): import 8 8,144 625131832 WDC_WD6400AAKS-75A7B0_WD-WCASY1489916 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk8: [8,144] (sdj) WDC_WD6400AAKS-75A7B0_WD-WCASY1489916 size: 625131832 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (10): import 9 8,160 625131832 WDC_WD6400AAKS-75A7B0_WD-WCASY1185307 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk9: [8,160] (sdk) WDC_WD6400AAKS-75A7B0_WD-WCASY1185307 size: 625131832 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (11): import 10 8,176 1953514552 WDC_WD20EURX-63T0FY0_WD-WCC4M1229044 Jan 18 14:35:48 SV-UNRAID kernel: md: import disk10: [8,176] (sdl) WDC_WD20EURX-63T0FY0_WD-WCC4M1229044 size: 1953514552 Jan 18 14:35:48 SV-UNRAID kernel: md: disk10 new disk Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (12): import 11 8,192 1953514552 WDC_WD20EURX-63T0FY0_WD-WCC4M0867681 Jan 18 14:35:48 SV-UNRAID emhttp: shcmd (261): /usr/local/sbin/emhttp_event driver_loaded Jan 18 14:35:48 SV-UNRAID emhttp_event: driver_loaded Jan 18 14:35:48 SV-UNRAID kernel: md: import disk11: [8,192] (sdm) WDC_WD20EURX-63T0FY0_WD-WCC4M0867681 size: 1953514552 Jan 18 14:35:48 SV-UNRAID kernel: md: disk11 new disk Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (13): import 12 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (14): import 13 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (15): import 14 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (16): import 15 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (17): import 16 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (18): import 17 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (19): import 18 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (20): import 19 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (21): import 20 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (22): import 21 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (23): import 22 0,0 Jan 18 14:35:48 SV-UNRAID kernel: mdcmd (24): import 23 0,0
  8. Here's what I did: - PC has no login therefore guest account is used. - Set Public to Public - Tries to copy stuff to it = no permission to wrtite - Went to unraid and set new permission - set public share to public access - Tried to copy a file into public = you need permission to perform this action
  9. Does that mean if I had a public folder and guest (read access only to other shares) writes stuff to it, there will always be permission issue?
  10. Why is it that I do not have permission to access all the files copied into unraid 5.x? I have run fix permission. Tried Public/Secure (read write)/Private (read write), create guest account with no password in user. For example. - PC 3 copies a file into unraid PUBLIC folder (security = Public / Security = Secured/Private with read/write to everybody) - PC 1, 2 cannot open the file. "You do not have permission to access \\tower\xxxxxxx" The only way I can fix the permission issue is to manually apply Chmod -R 777 to the file/folder. I'd never had this issue with unraid 4.x EDIT: Btw, only root account has full access to the files written to unraid. Nobody would be able to access the files even though the security is set to public/guest user granted full read/write. The disks are all given public access (hidden)
  11. Why is it that I need to do "chmod -R 777 Music" every time I added new music to the folder? If I didn't do that, new music could not be scanned.
  12. Following is what I have as settings: Cache Drive: Private Root: RW Guest: R All other disks: Private Root: RW Guest: R Movie Folder: Secure Root: RW Guest: R I have couchpotato automatically move completed files into Movies\New. From there, I'd use EmberMediaManager to scrape all the metadata using my laptop logged into root account. When all the files are scraped, here are the permission I ended up with: No problem accessing any files with the guest account for the following movie However, I cannot access folder.jpg and poster.jpg with a guest/anonymous account. Same thing happened to some of my music. I would use Jriver Media Jukebox to scrape and auto move the files within unraid. However, unless I assign +R 777 to the new files, I cannot access them with a guest account.
  13. Is it possible to setup anonymous access in 5.0 without using anonymous.sh script? I'd guest account created with no password but it seems like I still need to somehow have to map guest=nobody in order to access the network without entering password
  14. Is it possible to implement a timer-plugin for unraid where user could specify when to put unraid to sleep and when it wakes up automatically?
  15. I have 5 disks in unRaid 0 - Parity 1 - Data 2 - Data 3 - Data 4 - Data In user shares, I've set all to use fill-up allocation. With 0 min space. Split level is left blank. These are the samba share folders: \\tower\Movies \\tower\Tv Series \\Tower\DVD I have set: - DVD to include only disk3 - TV Series to include only disk 2 - Movies to include disk 1, disk 4 / exclude disk 2, disk 3 My disk 1 is full, disk 4 has over 260gb. I dropped in 250gb of movies into \\tower\Movies. unRaid then tries to fill up disk1, then windows tells me there is not enough disk space. The notification then goes away and it tries to fill up disk 1 again. Transfer speed drops to 1-2mb and I only see disk activity on disk 1. unRaid is not filling up my disk 4. What could be the problem?