Kryspy

Members
  • Posts

    563
  • Joined

  • Last visited

Everything posted by Kryspy

  1. My first go at a little "Paint Love" customization. Can't really read the 3 lower boxes on the slots screen. They indicate blue for parity, green for data disk and grey for empty slot. By kryspy at 2010-12-05 By kryspy at 2010-12-05 Kryspy
  2. Extremely nice and well thought out piece of work. Valuable plugin to say the least. Kryspy
  3. As reported in PM works perfectly. Thanks again. Kryspy
  4. Here are my output files. mdcmdstrings.txt procpartitions.txt lsbylabelunraid.txt lsbyid.txt
  5. That is correct Joe L. Last drive is labelled as flash when in fact it is a 500 GB WD drive and the boot flash is missing. Kryspy
  6. I too am having the same problem. Kryspy
  7. Okay that makes sense now. So it isn't writing anything to the flash just to RAM. The output isn't important just the fact I thought they were also writes to the flash drive. Kryspy
  8. Hi, Today I notice like 3000 lines in the syslog from transmission; giving various updates. Can we change the location where this is saved as I assume that it just wrote 3000 times to the flash drive at /boot/custom/transmission? Kryspy
  9. 20 GB sounds about right. So what do we input on that line? 20 GB, 20, 20000 Kryspy
  10. Just bought a 1.5 TB EARS. I am going to use it as a server backup for all my data. Seeing as how it might be used later on in the unRAID array but most likely used in Windows 7 now and formatted as NTFS would it make sense to go ahead and jumper pin 7/8 before putting it into use? It is only going to be used currently outside the array as data backup of server user shares data. Kryspy
  11. Successfully upgraded to 4.2 today. No problem at all. Settings become persistent after the first 7:00 pm cron job runs that saves your config. Kryspy
  12. The only thing now I guess is to find a way to make it persistent. I guess a package is in order now that we know it works. I suppose I could dissect the transmission package as an example and see if I can make one. Keep in mind I have zero experience. Kryspy
  13. Okay, so I have 4.1 working now. To solve the dirname: missing operand Try `dirname --help' for more information. Solved it by: cd $(dirname $0) if [ -e /bin/readlink ] || [ -e /usr/bin/readlink ]; then cd $(dirname $(readlink -f $0)) fi and reboot. Kryspy
  14. Kryspy

    DLNA server

    The newer beta releases of PS3 Mediaserver support alternate renderers of which I believe the Samsung TV are suported. See: http://ps3mediaserver.org/forum/viewforum.php?f=15&sid=6bd5d42fe3d22606f66c2632a1a659ad Kryspy
  15. Any further work on this? This is the one thing I am missing to make me happy. Not that Joe L. is responsible for my happiness or nothing like that Kryspy
  16. I really gotta learn the craft of what all this stuff means or I am going to worry myself to death Kryspy
  17. Pre-clear finished. Some seek error anomalies but aside from that looks ok. Kryspy
  18. Okay so did it without the jumper and with and all seems well. I had a monitor hooked up while booting and no errors or hangs were evident. Sp can I now run a pre-clear on it and add it as parity or do I not need to run a pre-clear if using it for parity? Kryspy
  19. So, Run this command: dd if=/dev/zero of=/dev/sdX bs=512 count=500 Kryspy
  20. Hi, I have finally settled on unRAID as my server solution after trying out everything under the sun. I have a 1 TB EARS without the jumper in use formatted to NTFS that I am about to add as the parity drive. To be clear do I just delete the partitions in Windows, then add the jumper and insert it into unraid, run a pre-clear and then add it as parity? Is this enough? Kryspy
  21. Gotcha. They most likely removed it from the newer drives firmware due to the many complaints about high Load_Cycle_Count numbers. But I see mine is fine at a whopping (1) Kryspy
  22. Hmm, Good point. However I do not recall the same post pre-clear from my EARS drive. Kryspy
  23. Hi, After running pre-clear on my Western Digital 1 TB EADS drive it comes up with a load_cycle_count variance. I have attached a picture of the screen-cap. I assume after deciphering this is what it should say: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE <Load_Cycle_Count 0x0032 149 149 Old_age Always - 154581 >Load_Cycle_Count 0x0032 149 149 Old_age Always - 154582 Does this mean my drive is in danger of premature failure? Kryspy