Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Lantesh

  • Rank
    Advanced Member


  • Gender
  1. Central repository/Wiki: http://lime-technology.com/wiki/index.php?title=UnRAID_Wiki That is very unfortunate, and a hard lesson learned. I never work more than an hour without making a backup of the data I’m currently working with. I also save every few minutes to my local copy. Sounds like you’ve got a much better system in place now to prevent future loss. It would have been prudent to ask questions prior to starting such a labor intensive process. That is what these forums are for. I always make inquiries before diving in. Unfortunately that is the nature of a free public forum. There aren’t any paid employees reorganizing it. Every individual here is nothing more than another community member. Be appreciative that we can come together as a community to help each other. This forum may not be organized like a tech manual, but what can you expect for free assistance? You can always reference the Wiki instead if the personal help is not satisfactory, but I find it much better to talk with others. To be honest I think you are expecting a lot for the minimal cost of unRAID. How much of your time would the price of unRAID buy? I would imagine perhaps enough time to write one letter. Can I bill you for my reply here?
  2. Looks like you've got a decent plan laid out. As garycase said just make sure you use the correct split levels, and you will be fine.
  3. User shares offer much more flexibility over disk shares. If you don't want to mess with split levels you can keep it simple by restricting a user share to one drive. After you've written a significant amount of data to that drive simply change the setting to another drive. When you restrict a share to a given drive that restriction only applies to writing data, not reading it. So if you have a share called "Movies" and you once had it restricted to drive 1, and later changed that to drive 2 it will now only write to drive 2, but the end user when accessing the Movie share over the network will see all the files on both drives. If you don't want to actively manage it that closely allow the share to span multiple drives, but keep split level turned completely off. Set the share to use "most free" and files go to the most free drive, and never split the file tree. So a single movie will have all files copied to the same drive, the one that has the most free space. Finally you can always move files from one drive to another manually to free up space on one drive, and fill in on another. Simply telnet in, and use the Midnight Commander file browser that is built in to Unraid. I use this all the time to move things around. The shares don't care what disk something is on. So you are free to rearrange your data all you want.
  4. Nice build. I like the cable management that case provides.
  5. Thank you gentleman. I appreciate the feedback. I will leave things be for now.
  6. Assuming one's system is functioning normally is there really any compelling reason to migrate to XFS at the moment? I realize that RFS is no longer being developed, but I was thinking until I'm ready to replace a drive I'm not really feeling any sense of urgency. I currently have 3 2TB data drives, and 2 2TB parity drives. I do not have any free SATA ports on my motherboard, and I don't have an expansion card. So it is not physically possible to connect another drive at present. So I'm thinking until I need more storage, and want to invest in new hardware it seems best to just leave well enough alone. Your thoughts?
  7. Thanks for the explanation garycase. That makes perfect sense.
  8. Out of curiosity why don't you leave the old parity drive in place? Add your new 8TB drive in the parity 2 slot, and leave parity 1 alone for now. If you don't need any additional added capacity immediately you are better off leaving it in place. Then when you can afford to buy another drive for the parity 1 slot you can then recycle the old drive, and add it to the array.
  9. As the others have already said replace your current drives with higher capacity drives. You may have other reasons to build a new system, but if capacity is the only issue the easiest short term solution is to replace the drives.
  10. Nice job on the dremel work, and custom brackets. You made those drive enclosures look like they were made to fit there. Your case, and choice of drive enclosures makes for a very attractive looking system. If/when I rebuild my own server I'd love to go with some hot swap enclosures like that. Currently I have to pull out drive cages every time I need to pull a drive, which thankfully isn't often.
  11. This is a very interesting topic. My array is small enough that this isn't an issue for me, but I can see how it can be for some. One question, with stopping, and starting a parity check, and the potential for a check to take days how would writing data to the array during this time effect the check itself? I've always run my checks at night while sleeping, and never considered writing data to the array during a check.
  12. Whatever you do DON'T do a "new config." You are adding drives, not creating an entirely new configuration.
  13. I can certainly replace the SATA cable just to be safe. That is easy enough. I'll have to see what I have available inside the case in the power cable department. The power supply is not modular.
  14. I will do that. Thanks again for you help. I do appreciate it! Interestingly I'm currently through only 8.4% on my parity correction pass, and have already corrected 4776 of the 4779 errors.