boeingboi

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Everything posted by boeingboi

  1. boeingboi
    Alright, thanks, I'll do that when the phone opens tomorrow.
  2. boeingboi
    Hello. I am running Unraid 6.8.3 with two cache SATA SSDs, one data HDD, and one parity HDD. I go through the attributes of the data disk sort of often, and I noticed a few days ago that I had 100 pending sectors and offline uncorrectable. I've seen forum and Reddit posts about this before, so I started an extended SMART test. There were no errors. Last night, the server ran a scheduled parity check with no issues. Should I keep the drive or submit a warranty claim? Drive is Seagate ST2000DM008, warranty until 2022, I purchased in January or February.
  3. boeingboi
    Started it normally, was able to move images at an appropriate speed. SMART test ran fine, I will be buying a parity disk as soon as possible now that this has happened. Thanks!
  4. boeingboi
    I replugged the cables, booted it up, and got a message saying "Sector ct8 reallocated" or something similar. Drive appears to be working, should I boot up out of maintenance mode and see, or is there something else I should do? Thank you so much! elrond-diagnostics-20200926-0934.zip
  5. boeingboi
    Here you are. I’m off to bed now as it is 0002 here, but I will happily respond to and appreciate any help in the morning. Thanks! elrond-diagnostics-20200926-0001.zip
  6. boeingboi
    Hiya! A few days ago I noticed I couldn’t use my shares. Checked Unraid and my one disk has Unmountable: no filesystem I followed part of SpaceinvaderOne’s video and ran xfs_repair with -nv and got this: Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error I am running Unraid 6.8.3 on a R5 2600. The drive in question is a 2TB Seagate Compute (only drive in the array). I don’t have any parody drives (a big mistake, I’ve been planning on getting one for the longest time). Server was built in April, been up for 25 days without errors.
  7. boeingboi
    I used the trick from page five of this discussion, including cache, etc, and Chrome gives me this: Access to 10.0.1.187 was denied You don't have authorization to view this page. HTTP ERROR 403