Jump to content

JP

Members
  • Content Count

    385
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JP

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks. Everything is acting very wonky. Not sure what is going on. Normally, navigating through the GUI is very snappy. Now once I started the array, the new disk doesn't seem to want to mount properly. I actually think this issue might have caused my problem altogether and it somehow impacted the parity drive. It just sits here saying that it is attempting to mount the new drive. It formatted just fine. It has been sitting for 15 minutes on this screen. Well, now after 15 minutes, it did move on, but now it is stuck at attempting to mount the cache drive. Everything appears to be struggling. Also, I now noticed that the Parity Drive is reporting some unhealthy SMART data. The processor is doing something, not exactly sure what though.
  2. Thanks. I thought that might be the case. Oh well. At the very least I have my most important files backed up on an external hard drive so I should be ok or at least I hope so. I'll know more once I get all the dockers up and running, but first I need to ensure the new disk is operating properly and parity is up and running again. First, it would probably be better to change the FS from reiserfs to XFS on the replacement data drive since I think XFS is a more current standard and there isn't any data on the drive. Once I do that, I noticed that an option for a Parity Check no longer exists for me. Instead it wants to do a read-check on all the array disks. I guess after I do that, the option to rebuild Parity will appear...correct?
  3. I received the following. Doesn't sound too promising.
  4. reiserfs I believe. Is that what you are asking for?
  5. I just now installed the plugin. I see MOUNT reflected next to the drive, but hovering over it does nothing. I can't click on it. Does that mean the data on it is unrecoverable?
  6. The drive does show as unassigned, but isn't healthy. Is it possible to make an attempt to access the data on an unassigned drive outside of the array? I'm not sure how you would access data on an unassigned drive outside of the array.
  7. Thanks. The parity drive still reflects as having parity disabled, but the drive is healthy and I'm still not sure why that happened. Is it best to rebuild parity first so that all my other drives are protected and then attempt to bring the data over from the old data drive?
  8. Well, I tried the old data disk that was failing and I'm hesitant to force it because it is reflected as WRONG in the GUI. I didn't start the array with it reflected as WRONG, but I'm wondering if I should? If I can at least get to the contents on the drive then I can move them to another data disk, leverage the new blank 4 TB data disk in its place and then rebuild parity. Does this seem reasonable or should I be going down a better path?
  9. Thanks. The rebuild appears to have worked fine, but since there was never any data on this drive (it is new) there wasn't anything there to rebuild. It appears to simply reflect the space being used accurately now. Before it reflected something like a terabyte being used, now it only reflects 33MB being used, which is only one Folder and no files. I don't know why, but this drive mounts really poorly. It takes about 5 minutes to mount whereas all the other drives mount quickly. I'm not sure what is going on there. Ultimately, since the parity seems to be invalid, I continue to think I need to put the old drive back in the array and keep my fingers crossed that the data is still there and then do a parity check. Does that seem reasonable? I'm still very confused about what happened here since I've rebuilt drives before, but in this case it seems to have gone from one drive failing and then the parity failing and becoming disabled.
  10. I sincerely appreciate johnnie.black's help here, but I'm not exactly sure where he was heading with his guidance here and I don't think he has been online in a few days. If anyone has an idea of where he might have been heading with these steps and can provide additional guidance, I would appreciate it.
  11. Thanks. Just finished. Diags attached in case that is what is needed to see the results. tower-diagnostics-20190929-1537.zip
  12. Thanks johnnie.black. I did that. Attached are the results. I'm assuming I should start the array again (without maintenance mode)...correct? tower-diagnostics-20190928-1940.zip
  13. Thank you and very sorry. I don't always know exactly what information is needed. I attached the diags right after posting so you should see them now. DISK1 failed or at least was showing signs of failure (can't remember exactly). I have no idea why DISK1 is showing that there is data on it because there is clearly nothing there. I go look at it from FILE EXPLORER and it shows the MOVIES folder in it, but no files. Every other data disk shows files I would expect. Something tells me that maybe the parity tried to rebuild is, but failed in doing so. The parity becoming disabled seemed to take place after all this. This is pretty much when I stopped things and sought advice.
  14. I'm not sure what happened here because I have replaced failed drives before without any problem, but something odd happened here. I had an old 2 GB data that was either failing or completely failed. I still do have it. I purchased a new 4 GB drive to replace it and had to wait for it to come. unRAID was just shutdown while I waited. Once the new drive arrived I took out the old drive and put the new one in, started up the server, did a pre-clear (passed just fine) and for some reason after the pre-clear the mounting of the disks was very slow and then I couldn't even reach it. It appears to have just frozen. I had to force a reboot. Once I rebooted I think I started the array expecting the drive to be rebuilt, but instead it did a parity check and since the new drive didn't have any data on it, it looks to have resulted in a huge number of errors. So I'm left with an invalid parity drive and a new data disk that doesn't have any data rebuilt on it. I'm not exactly sure what the safest thing is to do from here. Should I try re-inserting the old data drive and see if I can possibly rebuild the parity drive and start over? Any guidance is appreciated. tower-diagnostics-20190927-1554.zip
  15. JP

    Memory Leaks?

    Sort of. I'm surprised more people aren't seeing this because it remains on my server as plain as day. Additionally, the solution I'm using isn't very elegant at all, but it works so I'll take it as a half-win. Here is all I did: 1) Increased Memory- I think I increased my memory to 32 gigs. I don't run that much and my hope was that this would give my server so much extra space that as Plex became bloated, at least the problem of running out of memory would take more time to reach. 2) Setup PLEX to receive auto-updates. Each time PLEX is updated it has to stop and restart the docker itself. This clears the memory and allows for the memory leak cycle to reset. Fortunately, PLEX receives updated pretty frequently, maybe every week or so. This frequent cycle really helps with the problem. These two items coupled together have basically returned my server to the state I once I had it at before this issue, that is, I just don't anything with it (for the most part). It simply does its job again without me having to do hardly any routine maintenance. Love unRAID :)