Yorgo

Members
  • Posts

    46
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    Left of Center

Yorgo's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. http://lime-technology.com/forum/index.php?topic=51308.msg494307#msg494307 I'd like to second this. I upgraded from 6.1.9 to 6.2 stable today only to discover the NFS user share was not available on my media players (Mede8er MED600X3D); only empty subfolders displayed. Downgraded to 6.1.9 and all is back to normal. Not asking this be placed on the highest priority list but would feel comfortable knowing it will be addressed at some point. Thanks!
  2. http://lime-technology.com/forum/index.php?topic=50548.0 "I would make a request to the fine folks at Limetech that, if this feature truly is not available and if doing so does not break some other important function, the ability to spin down the drives if the array is stopped be added." Thank you for the consideration. Y
  3. Thanks again, Frank1940. The button(s) on the Array Operation tab to spin up and spin down drives are also not available, it appears, when the array is stopped so won't have a chance to test what that does to the drive being pre-cleared. Yes, this is going to be a long pre-clear process; 6TB drive via USB 2.0, and I'm okay with that. Perhaps it's a bit of paranoia since a drive just failed or simply that I don't see a reason to having the drives spinning for so long if they don't need to be, ultimately it is what it is at the moment...but... I would make a request to the fine folks at Limetech that, if this feature truly is not available and if doing so does not break some other important function, the ability to spin down the drives if the array is stopped be added. Thanks, Y
  4. Thanks, Frank1940. If I read what you suggested correctly, clicking the symbol (see photo) does not change spin up or down. Clicking the drive itself gets me into the drive's settings page but nothing is offered there to immediately spin down or spin up the drive.
  5. Had a drive fail a couple days ago and didn't have a spare ready to go immediately. So, I powered down my server until the new drive arrived. Upon receipt, I powered up the server so that I could use Unassigned Devices to Pre-Clear the drive first (connected via USB to the server) but did not start the array. However, noticed all the drives, except the bad one, are spun up. Since the pre-clear is going to take a long while and the server is effectively down until I replace the drive, I don't need them spun up. I read a 2013/V5 and older post from Tom (http://lime-technology.com/forum/index.php?topic=27796.msg245605#msg245605) where he said this is normal operation but was wondering if in the intervening years another option to spin them down has been made available. Thanks, Y
  6. Which 6 TB disks do you use? WD reds? WD Green
  7. I don't recall exact numbers but under 6.1.3, my previous parity check speed was under 20MB/sec and took way too many days. Was just about to run a monthly parity check (if numbers came in similarly, was going to bring to LT's attention in the forum) when 6.1.4 was released. Installed, ran parity check, and happy to report speeds have gone up again: Estimated speed: 83.1 MB/sec Elapsed time: 19 hours, 50 minutes Thanks, team! Y
  8. http://lime-technology.com/forum/index.php?topic=36527.0 Procedure starts about 2/3 down but I'd suggest reading the OP in its entirety. Y
  9. Thank you for confirming, interwebtech. Yes, long pre-clear time indeed; 50% through Post Read, 144+ hours. I didn't need the drive immediately and figured this would be a good way to "test" it anyway. Thanks, trurl. Yes, all data has been transferred off the drive. Been successful twice before moving from RFS to XFS just haven't tried it during a pre-clear. Y
  10. I believe the answer is "yes" but would like confirmation before proceeding... Can one stop an array while a pre-clear is in process without terminating pre-clear? I would like to transition one of my array drives from RFS to XFS which requires stopping the array but I'm in the middle of a looooong pre-clear of a 6TB drive (USB via SNAP) which I'd prefer to not terminate. TIA, Y
  11. Upgraded from 5.0.5 to 6b12, all good so far (in fact, it's gone very smoothly, hope I didn't just curse myself...). Except for one drive possibly remaining spun up (need to verify) and CPU at 100% (would doing a preclear to a USB drive via SNAP possibly cause this?), no issues to report. But then, I'm not pushing the envelop either, my server is exclusively for content storage and access, with only two plugins (SNAP and APC UPS Support). Only reason I upgraded was for improved web gui and potentially moving to a different file system (though at the moment I still haven't seen any clear reason to move off of ReiserFS). Y
  12. Of course, had to be that simple...replaced the USB dock with a newer one and voila, 4TB showing! Thanks, BRiT! Y
  13. Purchased a new WD 4TB Green drive yesterday and prepped to preclear. Preclear is to be performed via the drive inserted into a USB 2.0 dock connected to a USB port on my unRaid server (details in signature), using SNAP. Telnet reports "1,801,763,774,464 read". I checked unMENU and it also reports the drive as being 1.8TB. Photos attached, syslog can be provided if needed. I've precleared and installed larger than 2TB drives before, usually within the server and with no issues but this time, as all drive bays within the server are all full, I'm attempting via USB (and SNAP seemed like a cool thing to try out anyway ). From what I've read, BIOS not seeing larger than 2TB is okay but if unRaid doesn't, something may be amiss. Is something wrong or am I being paranoid? Any help would be appreciated. Thanks, Y
  14. 2gb, also didn't vote. It may make sense to change the first option to "2gb or less".
  15. I suggest this a while back also. We used to do it. I had compiled ctorrent as a static binary to make it easier for people too. +1