KC

Members
  • Posts

    75
  • Joined

  • Last visited

Everything posted by KC

  1. Yes, I had this issue about a year ago where CPU usage would skyrocket - it was Cache Directories. Right now I only have two plugins installed, System Stats and Open Files
  2. Woah ... ok kindergarten #1 of running servers. Overclock and die. I'm just gonna bail on this thread - it has no obvious positive solution.
  3. Wiz: He's overclocking?
  4. No worries - but it's hard to diagnose something if you have X# of addons installed. I'd suggest removing them all and going stock for a while - be easier to find out exactly what's going on.
  5. Is the behavior the same if all plugins are removed? Just going stock for a day or week? Looks like you've got a lot of plugins installed.
  6. If they were necessary for proper operation they'd be included in the base. Remove them - then check again.
  7. If you have any plugins installed remove them - then check CPU use. I've seen plugins cause ginormous cpu usage.
  8. You do the SMRT on all drives? If not, start now. If they all pass SMRT. Do a parity check w/ no correction. If they all pass? Sometimes shit happens. To be Sammy Safety recheck all power/SAS-SATA connections and repeat. Otherwise? Drives can and will correct themselves if they find a few bits off. However not reporting via SMRT is kind of rare. See this older topic SMRT and bit correction are still the same on physical drives. https://forums.unraid.net/topic/27913-parity-disk-red-balled/?tab=comments#comment-260742 ***Edit Long smart test - to be sure.
  9. Run a SMART report on the disk if you can. http://SrvrName-IP/Main/Device?name=disk? inserting of course your server & disk # http://136.294.75.128/Main/Device?name=disk## It'll tell you what's wrong . If you suspect otherwise replace both data/power cables on it and test again. Do you have Backups or a Spare disk? I personally check my array everyday for errors/issues. I know it's not very cool - but it keeps to above the curve, right?
  10. Only 2 hours to go, and it corrected 6095 errors. Now if could just see which files the errors where corrected on. However that's a pretty big ask for Unraid. Thanks again for the input. I appreciate it. *** Edit Kind of makes me glad I did a MD5 on all files on my array - might take a week to figure out which (if any) files are damaged ... but I'll find em. And a side note - I don't mind thrashing my disks. I have spares.
  11. itimpi - Thank you for the reply. I do have a UPS - but it's too small to spin up the server and 16 drives (even one controller at a time) I had to remove it temporarily - which has become 8 months :( I actually did what you suggested and trusted parity - the array is currently rebuilding with only 4 hours to go.
  12. As Jon has said - there are a lot of ways to do this. However I'd like to say what I did and how I did it. This was going from 1.5 tb drives to 3tb drives - so it's old info, take it with a grain of salt (and it's been like 6 years) New server, new drives. Ran PreClear on all new drives. 3x Read/Write - basically ensuring the new drives are good. I then did a unraid format / import on all disks. Once all disks passed that I then inserted one of the old disks at a time, copying them to whichever drive I wanted. I did this via SSH/Telnet via MidnightCommander. After all disks (in my case it was 8) I did a rebuild array. (which IIRC rebuilds parity based on the data disks info) I have since added a 2nd parity drive - and all seems well. YMMV - but that's what I did. And a side note - get another drive for dual parity. It's well worth it. One thing to keep in mind - if you do it this way all of your data is unprotected until it's finished - it's dangerous.
  13. If anyone cares, It's still going after 5 years and 10 months poweron hours. Power on hours 0x0032 030 030 000 Old age Always Never 51209 (5y, 10m, 4d, 17h
  14. Last feb I had a power outage as multiple disks where writing to the server. Since then I've had 6095 errors in parity. Now my question - what is the order in which parity is written? 1: Write data disks then calculate parity? 2: Simultaneous Parity Calc? 3: Calc Parity before data is written. I'm just wonder what I should trust first, data disks or parity. Thanks for any help you can give.
  15. KC

    Bit Rot

    It isn't the server. It's my stupid fire-stick. Apologies.
  16. KC

    Bit Rot

    I've been using an uraid server for almost 10 years. It's had power failures, disk failures, moves etc. However today I decided to watch a show that I've stored on it since almost day one. The amount of failures in the video ... pretty high. Almost unwatchable. So - what am I doing wrong? How much other data have I lost due to this? I notice the monhtly parity check trusts the data disks over parity disks - is this the correct thing? I've got 2 parity disks 8 data disks and some cache/etc disks - but why is my data being corrupted?
  17. Thread Necro? I use Sophos UTM as my firewall/router and Sophos AV clients on my computers - it allows me to control what/where clients can connect on a network level, and the low level agent on the client protects against. It supports AD integration, department control, and individual control.
  18. KC

    Oldest Drive

    Thanks. I thought I was special till read that post.
  19. KC

    Oldest Drive

    So, if this has been posted previously let me know. What is the oldest drive in your system? Mine is a Toshiba at 41029 (4y, 8m, 5d, 13h)
  20. From what I see (and really, take internet advice with a grain of salt) ... The current pending sector is 0. The Reallocated sector count is 0. So, your drive either decided the sectors it had previously thought were iffy weren't, and said 'fuck it, good enough for me' the one bit I don't know about is: 7 Seek Error Rate 0x000f 062 060 030 Pre-fail Always Never 1743018 Otherwise, from what you've posted your HD has been powered up for 65 days(1575 hours), has had zero reallocated sectors, has a pending reallocated sector count of 0. Anyone else care to chime in? If i"m reading these correctly, I'd run it as is, with a backup drive available in case of failure.
  21. Ahh, quantum drives. Makes me think of my PD210 that I bought in 89. It started to fail in 1992. I called Quantum. I got to speak with one of the guys who *designed* the hard drive. He said it had started to 'squanch' (spelling?) ... He had me plug in the power, and twist the drive violently counterclockwise. Once it had spun it, he said it'd run forever. I ran that drive as my main BBS (Amiga CNET) drive for another 2 years. Until I got sick of spinning it violently every time I had to power cycle. On a reboot it was fine, it wouldn't spin down. On a power cycle it'd spin down. I miss that level of service/support. When one could speak with someone who *made* the hardware, well, that was something special.
  22. http://en.wikipedia.org/wiki/S.M.A.R.T. http://en.wikipedia.org/wiki/S.M.A.R.T.#ATA_S.M.A.R.T._attributes Current Pending Sector is the # of sectors the disks firmware of the drive. While they've probably read back correctly 99 out of 100 times, there has been at least one failure on that sector. This could be by a re-read of the sectors with a cheap md5 not matching, or other similar issues. Basically SMART is saying 8 sectors on your harddrive can't be trusted 100%. This while sounding bad is *NOT* the end of the disk. It just means that what it wrote and read back weren't the same. On modern Hard disks they expect this over the life of the drive. HOWEVER, clearing them isn't exactly straight-forward. I've found removing the disk and doing 3 or more preclears on it will force the bios to reallocate the pending sectors, or clear them as good. The downside? Doing this on a parity drive, or other drive in the array will leave it in an unprotected state. Safest method? Buy new drive of equal size, replace it with possible failing drive. Rebuild parity. After parity has been rebuilt, run a pre-clear on that drive with at least 3+ cycles. If it shows as 0 pending after the pre-clears, you've got them reallocated or reassigned as good. If it doesn't? Well..... what's 200.00?
  23. It's quite possible the smart output will lead us to a bad power/data cable rendering my fear mongering invalid ... However, it's always a good idea to keep a spare drive (as large if not larger than your parity drive) for just such issues.
  24. What's the SMART output? Do you have smart history report available? If not, are you able to telnet into your unraid server? If you're able to telnet into your unraid server run this command and post the output ... smartctl -A /dev/hdc this will gives more information on what SMART bits failed. However, if SMART has failed, your drive is either toast, or will be shortly toast - aka don't trust it. At all. While there is a small chance the cable for data or the cable for power has failed, there is a greater chance the drive has failed. While this is bad - this is why we have parity calculating arrays. It supports a single drive failure. Right now, if I was in your shoes I'd buy a new drive, and pray nothing else fails while you wait for shipping and a parity rebuild.
  25. <Clarification needed> Do I get the Case *AND* the jump drive for 59.00? If so, I'll take 6. If it's just a 59.00 add-on to the case, I'll stop being a pedantic idiot.