Jump to content

kifysara

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by kifysara

  1. I have attached the results of the long SMART test. It seems to pass, even though the same known warnings are reported. 1.5TB_SeagateLP_SMARTb.txt
  2. Yes, I had a few issues with the Seagate drive when it was running on my Windows box (sometimes I could hear it trying to spin up unsuccessfully) but it passed the pre-clearing process with just a few SMART-related warnings and seemed to be working fine. Anyhow, I'll run the full SMART test and get back to you!
  3. Thanks for the reply! SATA ports are set to AHCI, yes. I can also confirm that from the most recent syslog (attached). I removed the flash drive, plugged it on my PC, indeed got a "need to run checkdisk"-type of message, run a full scan but found no errors. Still, replugging the flash drive doesn't bring up the "check disk" alert anymore. Plugged the drive back, loaded everything and got the attached SMART reports from the drives. I should mention that the drives passed the pre-clearing process prior to adding them to the array. Hope that helps! syslog-2014-02-01.txt 3TB_WDRed_SMART.txt 2TB_WDGreen_SMART.txt 1.5TB_SeagateLP_SMART.txt
  4. Also attaching my syslog for your reference. syslog-2014-01-31.txt
  5. Hey all, Having installed unRAID (5.0.5 Plus) on my new HP Microserver (54L, AMD Turion II, 2GB ECC RAM, everything stock), I think I'm experiencing sub-par performance and would appreciate your feedback. I'm running unRAID off a Lexar Jump Drive S23 USB3.0 stick and the only "aftermarket" addon I have is Unmenu. At first, the array consisted of a WD Green 2TB and a Seagate LP 1.5TB drive (see Disk_setup.JPG for exact model numbers). I did not immediately add a parity drive, as I wanted to migrate my data to the array first (and said data was temporarily stored on a 3TB WD Red which was my soon-to-be-parity drive). As I was transferring data from my PC to the array, I noticed that the write speeds were pretty slow @ around 30MB/s (fluctuating 25-35MB/s). I thought perhaps this was normal (network bottleneck), but then, monitoring memory usage, I noticed that - while things looked pretty normal memory-wise on boot up (with unRAID occupying ~250 megs of RAM) - during transfers there was barely 50MB of free RAM (see HPM_Free and HPM_Free_transfer JPEGs). Again, I thought that this could be normal - perhaps some OS caching. But now, having transferred all files and having added the 3TB Red drive as parity, I run "Tunables Tester" script to fine-tune those tunable values. I was expecting to get a bit of performance boost prior to building the parity (which initially said it'd need 22 hours). To my surprise, the values seem to make no difference, with parity building being capped at 33.6MB/s (see Tunables.JPG)! This does not seem to match the behavior other setups seem to exhibit when tweaking those values (based on what I see from the above-linked thread). All of the above have me a bit worried about my setup and, of course, I would like to troubleshoot any issues before proceeding with the final setup (plugins etc.) Any comments would be welcome as I'm new to unRAID and don't know what to make out of this situation. Thanks in advance!
×
×
  • Create New...