Jump to content

thejellydude

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by thejellydude

  1. So at this point is the only option to replace the hardware? Should I try swapping the port and power cable with a different drive to see if the issue migrates, and use that to isolate what I should replace? Or could that cause damage to my array?
  2. What issues do you see with parity? I've already swapped out to a fresh cable. Outside of a getting a new power supply or a new sata expansion card, I don't think there's much I can do. I know that my UDMA CRC error count was at 30, but it's never increase since I made the build about 3 months ago.
  3. I just replaced the cable on the parity drive. Are you talking about the 30 UDMA CRC error count? Also, I'm stuck on the Check Filesystem process. I ran check filesystem, and it looks like I didn't get any errors? XFS_REPAIR Summary Wed Jan 27 02:59:04 2021 Phase Start End Duration Phase 1: 01/27 02:58:23 01/27 02:58:23 Phase 2: 01/27 02:58:23 01/27 02:58:29 6 seconds Phase 3: 01/27 02:58:29 01/27 02:58:58 29 seconds Phase 4: 01/27 02:58:58 01/27 02:58:59 1 second Phase 5: Skipped Phase 6: 01/27 02:58:59 01/27 02:59:04 5 seconds Phase 7: 01/27 02:59:04 01/27 02:59:04 Total run time: 41 seconds But the drive still won't mount properly. I then tried to do a repair command, but got "ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this." Should I delete the log? I feel very out of my wheelhouse here. Thank you again for any and all help.
  4. Not really sure what's going on, but since it's a 12tb drive, I'm hoping it's an easy fix. I was in the middle of a parity rebuild, but I stopped it since I assume missing an entire drive might be important. Are there possibly some commands I can run in terminal to fix things? nasbox-diagnostics-20210127-0311.zip
  5. I unfortunately already started the rebuild, but it seems to be going well so far. nasbox-diagnostics-20210126-2205.zip
  6. Earlier today I made a thread about my parity drive being very slow. I got the advice to redo the wiring on my drives: I don't know which drive specifically was parity drive 2, so I stopped the array and rewired everything. Now it looks like parity drive 2 is fine, but parity has a red x on it. When I hover over the X, I see "PARTIY DEVICE IS DISABLED". Can I get some advice on what I should do? Thank all of you on this server for being so helpful. nasbox-diagnostics-20210126-1927.zip
  7. Thank you both! I will try replacing the cables today. I appreciate the help.
  8. I have no idea why my parity check is taking so long. Anyone have an idea of what's causing such a huge amount of time? nasbox-diagnostics-20210125-1755.zip
  9. I'm trying to set up a docker container myself. Do you have any links that you found helpful?
  10. Basically I'm trying to set up an Among Us server for my friends and I since we constantly have issues with the public ones provided. https://github.com/Impostor/Impostor/blob/dev/docs/Running-the-server.md I've added it to my list of dockers by using "Add container" and filling out the info, but now I can't figure out where to add plug-ins or configure the .json files. I've *extremely* new to docker and containerization, so I'm sure I'm missing something here. Thank you for any and all help.
  11. I wasn't caching the initial data load. When I migrated to UnRaid, I messed up copying a few TB of data that I'm now having to redownload. I will probably re-enable the cache afterwards.
  12. I didn't even realize parity was running! I will wait for that to resolve and try again. Thank you so much. As for the cache drive, it would only help writing to the drive, right? Or does enabling cache on a server help with reading from the drive as well? I don't have any of my shares currently cache enabled as they were willing with data too fast and causing issues.
  13. UnRaid Version: 6.8.3 Hardware: 4x 12TB Shucked Western Digital Hard Drives (Two set as parity drives) 4x 8TB Shucked Western Digital Hard Drives Crucial M500 SSD as cache drive Plugins: Docker: I'm trying to copy over files like videos, music, or games, and they are all super slow. Way under what I would expect. I don't expect full gigabit speeds, but I'm getting about 1~4 MB/s which is pitiful. Are there settings I need to tweak on either the Windows side or Unraid? I expect to get very good speeds on my desktop, and at least 10MB/s via WiFi since I have an eero mesh network. Thanks for any and all help. nasbox-diagnostics-20201214-1646.zip
×
×
  • Create New...