UnRaid_11317

Members
  • Posts

    7
  • Joined

  • Last visited

UnRaid_11317's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thank you for all the help! I have a couple of 10TB Iron Wolfs on the way to start my great XFS migration.
  2. My disks are very full 98%-100% So as the disks get full with the REISERFS file system it takes a hit to performance? Does XFS have the same limitation? Is there a % threshold I should stay below? Is there an easy way to move the data off those drives to new larger drives?
  3. Hello, I am having performance issues with my 6.4.1 unRAID server. Opening folders, creating text files, transferring files, moving files around is all running extremely slow. Sometimes have to wait a full min before system is responsive again. Video Playback from server will sometimes just stop. Docker containers can become unresponsive. Nothing ever crashes, just takes a long time or will become unresponsive. If I give it a min, unRAID eventually does what it was commanded to do. However each task can suddenly take a full min to complete. No problem navigating the WebGUI. No apparent slow downs. HDDs are a bit full (can that be a problem?) In Dashboard HDDs are Green, AVG CPU Load is around 20-30%, Memory Usage 20-30% Network equipment reset, just in case - no change. Nothing red or yellow appears in the Logs. I have attached my diagnostics file. In the System folder under the memory.txt it reads a total of 15G, 3.9G used and 229M free. Is there a problem there or is that normal because it also reads buff/cache 11G and available 10G. Very obviously, I don't know what I should be looking for in the diagnostic files. I appreciate any and all help! media-diagnostics-20180809-0631.zip
  4. Thank you for the follow up everyone!! I really appreciate your help!
  5. Thank you both for your answers! PWM just to clarify: The missing parity drive is from a 20 drive array with 3 drives that are 3TB and the remaining 17 drives are 4TB, The missing parity is actually drive #2 in a 2 parity configuration. Both parity drives were 4TB. So if I understand both pwn and bonienl correctly: in this particular situation there is no opportunity for any information (Files, File Names, Directory structures) to be retrievable or recoverable from the missing drive and I can tell everyone involved that there is nothing to worry about and we do not need to track down this drive.
  6. Is there any recoverable or identifiable information from a single parity drive on its own, out side of the array? Can any information be recovered from it? Files? File lists? Directory structures? Someone pulled the parity drive rather than one of the blank extra drives for a return. Should I be worried about a possible data breach or the ability for anyone to recover any data off that parity drive that is now out in the world or is the information on it useless without the array?
  7. Hello, I have been a happy unRAID user for several years. I feel like a bad community member because this may be the first time I have ever posted to the forums. I want to start off by giving my sincerest appreciation to this community and everyone in this forum for all the unbelievable help and guidance! The reason for my post today is that "Fix Common Problems" out of the blue has reported: Call Traces found on your server: Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums. I have ran Memtest on the system for 48 hours without any errors. Is this an error I can Acknowledge or Ignore? Is this a huge problem? Should I re-run the scan as an "extended test"? I'm not really sure what to do with this information and would appreciate any help or insight. What can I do to fix the problem? I noticed there is a newer version of fix.common.problems available which i have not updated to yet, should I do that first? I have attached the diagnostics as a .zip file named media-diagnostics-20171103-0012.zip. Thank you for your help! media-diagnostics-20171103-0012.zip