treefour

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by treefour

  1. Thanks Joe, that's weird I guess both of them were failing at the same time. Thanks for the help will get a new one ordered up today. Thanks a lot for the help. Treefour
  2. thanks for the reply Joe, here is the smart report. smartreport112413.zip
  3. Hi everyone, I have a problem and am unsure where to start, about a week ago while I was watching a movie it started buffering a lot, I thought it might just be network traffic. Then when I tried writing to the disk it started writing then the disk would become unavailable. When I check the drive it showed a ton of errors. I ran a smart report and it came back as passed, So I removed all the cables and reseated everything thinking it was a cabling issue. the errors still persisted but I had an extra drive, ran the preclear on it with no problem, then added the new disk to the array. Everything seemed fine for a few days and then last night I started getting errors again and am not sure where to start. I have attached a syslog in hopes that someone can help me as to where to start. Thanks Treefour syslog-2013-11-24.zip
  4. upgraded from rc16c no problems so far, parity check is smoking right along ------------------------------------------------------------------------------------------------ Total size: 2 TB Current position: 213.33 GB (11%) Estimated speed: 96.67 MB/sec Estimated finish: 308 minutes Sync errors detected: 0 ------------------------------------------------------------------------------------------------ Thanks for the hard work Tom! Cheers
  5. Yup, I am and I followed the instructions on the first post for deleting previous installs as well before installing.
  6. I've been having the same problem, but rather than delete the files I just opened them up and changed them, then saved them and blam-o everything works.
  7. That's what I thought but as I said I was a bit confused. Thanks for the help. Cheers
  8. I have a question about removing HPA from my system. I have read through the various posts made regarding this and understand what is required to remove it from the system, like run the hdparm -N pxxxxxxxxxx /dev/xxx command, then hdparm -N /dev/xxx to verify that it has been removed. I also understand that I can only do one drive per power cycle, but am a little confused about the rebuilding process. I understand that I will have to do a parity check once hpa is removed but I have it on two drives. Does this mean that I can only do one drive then rebuild parity, then do the second drive and rebuild parity for that drive or can I remove hpa from one drive, cycle the power and remove it from the second drive, then rebuild parity?
  9. I like to test new stuff and am not overly afraid of screwing things up as that's how I seem to learn best. When I first found unraid I did exactly that, grabbed a beta and gave it a go. Being a complete Linux moron I quickly found out that, going that route was like trying to swim with and anchor tied to my foot. So I used a stable to start and have stayed with them as I learn. I have since spent about 30 hours reading these forums figuring out all the little problems that have arisen with the server. As I'm sure you can see I have only posted once or twice as I have yet to find a problem that I couldn't figure out without info from the forum and the awesome the users here. That being said I also think it should be a little harder for newbies like myself to access the betas, but not impossible, as I would be willing to give it a go once I was a bit more comfortable with my abilities/understanding. Lastly I want to say thanks to all veteran users for all the time and effort they put in for the newbies like me.
  10. You and me both buddy. Assuming you've already installed Transmission, try running these commands while substituting the paths with your own. /boot/custom/transmission/transctl stop installpkg /boot/custom/transmission-2.11-i486-1gsb.txz installpkg /boot/custom/libevent-1412-i486-1.txz /boot/custom/transmission/transctl start That should get you going until your next reboot. I guess you can add those lines to the go script to make it persistent. You can add me too the list as well! Thanks for the help