Jump to content

manolodf

Members
  • Content Count

    201
  • Joined

  • Last visited

Community Reputation

1 Neutral

About manolodf

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Dallas, TX
  • ICQ
    2812478
  • AIM
    manolodf
  • YIM
    manolodf
  • MSN Messenger
    manolodf@gmail.com

Recent Profile Visitors

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

  1. Has anyone had any luck with the Sym Links?
  2. I installed the metadata, its pretty cool! How would you recommend I do a write test to cache drive? When I was transferring the appdata from array to cache, well my dockers were off, so I could not really see that. Do you recommend a different test I could setup to see the write speed? Do you think there is something in bios I need to do to improve on this? My previous 256gb NVMe M.2 SSD did not have any issues on the speed department that I noticed.
  3. Yes correct, same thing, but I guess I was looking more for the specific command if possible to extract just one folder (to keep permissions as mentioned)
  4. Is there a way to restore a backup of only one docker? It seems my Deluge restore got corrupted at some point. Deluge would not recognize my password, it was reset to default password, as well as some plugins were not working. So i wanted to only restore that one hoping to get it back to how it was. I know on a previous restore it was intact.
  5. With Parity Build Paused, Dockers off, is it normal for 40GB of appdata being transferred from Disk2 to NVMe Cache drive to take over 4hrs?
  6. What about when writing to NVMe Cache drive only and not disks in the Array?
  7. I have installed the new cache M.2 NVMe SSD, but not sure why it seems that it is running slower than it should. Is there something in the Bios that I should look for to perhaps speed up the write speed? One example is a 20gb file that took 8mins to transfer to Disk2 yesterday took about 18mins to transfer to Cache today on the M.2 SSD that should be way faster. Or the ~40gb appdata I am transferring just is taking hours upon hours when I remember previously it performed to and from array much faster. When Dockers are off parity checks at about 100MB/sec, when they are on, it is about 20MB/sec, and when mover and dockers are off it can hit 160MB/Sec tower-diagnostics-20190618-2348.zip
  8. Yep that’s what I did for now. Turned docker service off for the night hoping to get parity rebuild done as fast as possible. Hopefully get it all back to normal right when the new drive and heat sync arrives tomorrow
  9. The docker image is in /mnt/cache/docker.img the appdata used to reside as a cache only share though I did move to the array temporarily since I have been having those vicious cache drive issues and got tired of restoring often until my new nvme drive arrives. I did update firmware on the nvme drive though for now was leaving the appdata in the array and off cache for now though. I will set it back once I feel a bit more comfortable
  10. I disabled Dockers and now the speed is more like 100MB/sec, which should be a bit more normal?
  11. Ok, I have done so, but maybe too much has happened in the Array in the past 8 hours since it happened where it is not as close. It does say Parity Invalid now, and it is rebuilding. Is it normal for it to be going at ~10MB/sec?
  12. Is my only way to get parity back to my array to do the following: 1. Stop Array 2. Remove Parity Drive Again 3. Start Array 4. Stop Array 5. Add Parity drive again 6. Start array to rebuild parity? is there no shortcut since parity was good?
  13. Oh wow, ok well bios is updated but the firmware I was not even aware of, I actually ordered a new one, so I will see if I can somehow get an external adapter to plug into windows or something like that. Right now, while moving my box my parity showed me a red X out of nowhere, I started another thread with diagnostics. Not sure how to get parity back now before the replacement Cache arrives tomorrow.
  14. I received the Parity Device Disabled with an X next to it. I think it may have been due to a physical issue since I moved the box slightly to check what I needed for my cache drive issue that I have been dealing with and need to replace the M.2 SSD. So after some movement randomly I got the error and now it says Parity device disabled. I am not sure what the proper procedure is to get it to see the parity again. The Short SMART report came back just fine, the long one has been sitting on 10% for a while. I started the Read test thinking that would re-enable the parity but not sure what the proper sequence would be. I did power down the machine and remove, refasten the data and power plugs to the drive and on the board. tower-diagnostics-20190617-2011.ziptower-smart-20190617-1544.zip
  15. Yes, someone asked me to download and put a file in boot/extra for xfsprogs 5.0 so I did that. I noticed it was a file that started in ._ so it's likely the Apple extension or something so I deleted that extra file, but I left the other in /boot/extra