Rizlaw

Members
  • Posts

    34
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Rizlaw's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks to all who helped. Everything appears to be working on reboot, no error messages seen.😄
  2. itimpi, I couldn't find an option to "unassign" the 2 cache drives, but I did find and select a "no" option which seemed to remove the drives and also give me 2 red warning boxes that the cache drives were missing. However, to the right of the greyed out start button, there was a message, which, if checked, said the cache drives would be removed and the array reconfigured without the cache drives. I clicked the box with a "check" mark and the array restarted with the two red warning boxes gone. Here is a screenshot of my system after removing the 2 cache drives and restarting the array. x-special/nautilus-clipboard Can I now power down the array and remove the 2 drives and then restart the array without any problems?
  3. No, I don't have any docker or VMs. I may add a faster SSD cache in the future when I rebuild the box, but for now no.
  4. I'm running unRAID 6.3 Pro with a cache mirror consisting of two Western Digital Green 2TB drives. It's slow and I want to totally remove both cache drives permanently without damaging the rest of my array and data. Oddly, my past reading of the UR Manual does not explain how to do this. My search of this forum yielded 1000 results on "How to remove cache drives". I read the first 10 pages which did not provide a specific answer to my problem. I gave up reading the rest. I'd greatly appreciate a step by step explanation describing how to do this safely. Thanks for any help.
  5. Every top level directory is considered a share so you were creating top level directories on the cache drive which became shares and were moved to the array. You have to create or write into the share directory structure when you write directly to a disk. I think your fill-up allocation method could still cause you heartache. Agreed: reverted all share split-levels to the default, "automatically split any directory as required".
  6. Robj, Thanks, I didn't know that. It provides more insight how this is all supposed to work, or not.
  7. Limetech (Tom) thanks for the clarifications on sharing. I really hope you can find the time to make a Linux version of the "make_bootable" file so that the two of us who have asked for it, don't always have to do it from a Windows machine. lionelhutz Thank you for your help. I'm marking this post solved for now. I shut down my unRAID 6 server last night. I turned it on this AM and found all the unexpected shares had disappeared. I think I now understand what I (and I think unRAID 6.0, too) did that created the problem in the first place. 1. As I previously mentioned (I think), when I originally created the BLURAY share it was for ALL four of my new 4TB data disks. At that point I hadn't written any files to the share, but I did notice that unRAID had only created a "Bluray" folder on disk 1 and disk 2. It did not create a similar "Bluray" folder on disks 3 or disk 4. I don't know why and I didn't think much about it at the time. 2. I also created a two disk cache and enabled "caching" for the BLURAY share. I did not create a "Bluray" folder on the cache drive (two WD Greens) as limetech suggested I could. 3. I then changed my mind about the BLURAY share being on all four data disks; I excluded disk 1 and also manually deleted the "Bluray" folder created by unRAID 6 on disk 1. Again, nothing had been written to the share at this point. 4. I then began my first batch transfer of files from my workstation to the "Bluray" share. For reasons I still don't understand (and which haven't been explained to me by anyone else) they found there way to data disk 1 (which was excluded from the share). As far as I understand, removing disk 1 from the share and deleting the "Bluray" folder should prevent any files copied to the "Bluray" or "Cache" shares from winding up on disk 1. 5. Because of what happened in "4" above, I transferred the rest of my files directly to the CACHE drive and let the "mover" do it's work. A few of the files/folders continued to find their way to disk 1, but all the rest where spread out on disks 2, 3 and 4. Now, this is the point where I noticed that my GUI "SHARES" tab was filling up with lots of folder filenames as "shares" beyond the basic three shares I had originally created (Bluray, DVD and TV). At the time, I couldn't understand why this was happening, hence my original post. Last night I realized that this might have something to do with unRAID 6 not automatically creating "Bluray" share folders on disk 3 and disk 4 (which it did do on disks 1 and 2). So I manually created a "Bluray" folder on disk 3 and disk 4 and simply selected all the files that were placed in the root of those drives and moved them into the new "Bluray" folder on disks 3 and 4. I shut down the server and this morning turned it on and all the unwanted shares were gone from the GUI "Shares" section, leaving only the original three shares (Bluray, DVD and TV). Until I have more files to transfer, I won't be absolutely sure if everything is back to normal. But, I think for now everything is OK and I will go back to copying files to the "Bluray" share and NOT to the "Cache" share. Again, thanks for your help.
  8. I have unRAID 6.0.0 installed. I have created 3 shares (Bluray, DVD, TV). Initially, I created "Bluray" to include disks 1, 2, 3 and 4. I then changed my mind and excluded disk 1 and also deleted the "Bluray" folder created by the share on disk1. My /config/share/bluray.cfg file shows that disk 1 is excluded from the share # Generated settings: shareComment="All Bluray Movies and Media Content" shareInclude="disk2,disk3,disk4" shareExclude="disk1" shareUseCache="yes" shareCOW="auto" shareAllocator="fillup" shareSplitLevel="0" shareFloor="15000000" shareExport="e" shareSecurity="public" shareReadList="" shareWriteList="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="public" shareHostListNFS="" shareExportAFP="-" shareSecurityAFP="public" shareReadListAFP="" shareWriteListAFP="" shareVolsizelimitAFP="" shareVoldbpathAFP="" The "Bluray" share is set to "Fill-up" and split level is set to "Manual:do not automatically split levels". It also has disk caching enabled. The other two shares (DVD and TV) are set to use disk 1 only and exclude disks 2,3 and 4. From my Linux workstation I connected to the "Cache" share and copied 500GB of files. When the copy completed, I saw all of the files on the Cache drive. I then manually ran the "Mover" script via the GUI button on the "Main" tab. As I understand things (and apparently I don't), the "mover" script should be copying these files to disk 2's "Bluray" share which has 750GB free space left. It should copy to the first "Bluray" share disk that has sufficient free space. It's not doing that! It's copying all the files to disk 1 which is excluded from the "Bluray" share. Question 1: What am I doing wrong? Question 2: (proper use of cached shares) Based on this thread: http://lime-technology.com/forum/index.php?topic=5754.msg240860#msg240860 If sharing and caching are setup correctly: I gather that you are supposed to copy files from your workstation to the unRAID server share location you ultimately want the files copied to (in my case the "Bluray" share. If the share is cached, this actually copies the files to the cache drive and NOT to the array containing the "Bluray" share. Thus, files sit on the cache drive until they are either manually moved via the "mover" button in the GUI or automatically moved at 3:40am to the correct share (again, in my case "Bluray"). This doesn't happen for me. Firstly, if I copy a file from my workstation to my "Bluray" share and then look in the "Cache" folder, the file is not displayed. Nor, is the file displayed on any of the three disk drives which have a "Bluray" share (disks 2,3 and 4). Why can't I see the file anywhere. Where has it gone? If, on the other hand, I copy the file or files directly from the workstation to the "Cache" share (presumably the wrong way to do it), I can see the file(s) in the "Cache" drive's directory. The problem doing it this way, as I described at the beginning of this post, is that the files do not ultimately get "moved" to where I expect them to be moved even though I only have one share (Bluray) cached. So, I am totally confused how this is all supposed to work in version 6. I need a better, clearer explanation how to set this up correctly (assuming I haven't already done so) and how to mechanically make the copy from computer A to computer B (unRAID 6). Thanks.
  9. I'd appreciate it if you shared your solution and marked your post "SOLVED". I have/had a similar issue.
  10. unRAID 6.0.0 runs Linux as do all my other computers. I do have Win7 as a VMware virtual machine, but I don't use it to access my unRAID 6 server. Beyond my all Linux system, another reason for considering NFS is that many of the large files I have use special characters that are forbidden in Windows (for example, the colon : ). When I try to copy files from my Ubuntu workstation to unRAID 6 with the SAMBA protocol, I always get a file copy error regarding any filename with a colon. I don't feel like finding and renaming hundreds of files; although on all new files I am using "-" in lieu of ":". I've done a search on the unRAID Version 6 support forum and the online manual for version 6 and I don't seem to find an anwer to these questions: 1. Is the NFS filesystem under unRAID 6 stable enough to use (any other downsides to NFS)? 2. Would using the NFS filesystem result in faster transfers than using SAMBA? Currently, I'm seeing about 45-50 MB/s file transfer speeds via SAMBA directly to unRAID6 disk shares. I also see the same speeds when copying to unRAID 6 cache drives ( I thought copying to cache would be faster because of the lack of parity writing, but it's not the case). 3. Can NFS and SAMBA co-exist? If so, are the shares displayed differently to me on my local Linux workstation; in other words, how would I know the difference between doing a SAMBA transfer and an NFS transfer? 4. Besides enabling NTF in "Network Services" are there any other settings I need to enable in unRAID 6 or on my Ubuntu 14.04LTS workstations to make this all work properly? What are they? Thanks for any help.
  11. No, I didn't do that, but I will try it now and see if that works. Thanks, it worked. Seems this should be semi-automatic, or at least noted in the online help information.
  12. Yesterday, I finished reinstalling a 16TB Unraid 6.0.0 PRO system from scratch (still have to put back all the data files :'( . My desktop workstation runs Linux (no Win7,8 or 10 involved). Yesterday, I also installed a single WD Green 2TB drive as a single "cache" drive. Today I want to add a second WD Green 2TB drive to the existing "cache" for redundancy protection. Currently, my setup sees the new 2TB drive as an "unassigned Device". I can assign it to the "Array Devices" section, but I can't seem to assign it to the "Cache Devices" section. The new drive appears (along with the first cache drive) in the cache drop down menu, but I can only select one drive. The "Slots" drop down menu only allows the default number "1" to be entered. I'm guessing I need "slots" to allow me to enter "2", but it won't. Is this a bug? How can I get a redundant btrfs two cache drive setup? The built in GUI help file is useless and the Wiki for "Cache Drives" has instructions which are apparently out of date for the new version 6.0.0: Any help is appreciated.
  13. Who and where...... without a cite, it is just hearsay. I'm afraid it's not "hearsay". http://www.osnews.com/story/22872/Linux_Not_Fully_Prepared_for_4096-Byte_Sector_Hard_Drives Good article on 4k sectors: http://lwn.net/Articles/322777/ Latest info on 4K: http://www.h-online.com/open/news/item/Kernel-Log-Linux-and-hard-disks-with-4-KByte-sectors-939523.html More info (with solutions) from Western Digital Community website: http://community.wdc.com/t5/Desktop/Problem-with-WD-Advanced-Format-drive-in-LINUX-WD15EARS/td-p/6395 http://www.h-online.com/open/news/item/Kernel-Log-Linux-and-hard-disks-with-4-KByte-sectors-939523.html
  14. I recently purchased this HD stacker from FrozenCPU and gave it a 3.5 star rating out of 5 on FrozenCPU's website. I'm a big Lian-Li Fan, but this rack could have been better engineered. As I noted in my very short review: (1) installing SATA cables is a true PITA for anyone with adult sized hands (the 4 SATA connectors are located, more or less, in the middle of the backplane, rather than to one side or the other) and requires removal of the rear fan assembly (4 very small Phillips screws) to reach the connectors; (2) There is one 4 pin molex power connector to power all 4 drives which is not fixed to the backplane, but dangles from 4 wires which are short and make connection to the power supply difficult (at least in my case); IMO it would have been better for the connector to be attached to the backplane board and Lian-Li should have provided a second SATA power connector; (3) No case rails are supplied. The sides of the rack have two threaded case rail holes per side which are NOT parallel. They are offset, so if you have thin metal case rails, you may be out of luck unless you're willing to drill and tap additional holes (as I had to do). I found this odd, as most HD stackers I've used have had 2 sets of parallel holes per side. (4) 4 SATA cables are provided: 90/180 degree type. Depending on the size of your case and the distance from the cage to the SATA controller, the supplied cables may be too short. Plan on buying longer cables if you have a large tower. (5) The 120mm/1000rpm fan is fairly quiet. Basically a good, but not great 3rd party drive cage. I also own every version of the Addonics hot swap drive cages (3SA, 4SA and 5SA). IMO, were it not for the horribly cheap and noisy fans in the Addonics units, they would be the better choice.