egeis

Members
  • Posts

    45
  • Joined

  • Last visited

About egeis

  • Birthday 09/25/1978

Converted

  • Gender
    Male
  • Location
    Florida
  • Personal Text
    All in One Box = Unending config problems...

Recent Profile Visitors

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

egeis's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. I updated to the newest docker image yesterday and seeing the slowest indexing of my music collection ever. Now taking minutes for a single folder after being relatively quick through the first 200 folders. Anyone else seeing this behavior?
  2. I inserted the SAS HBA and moved all 4 disks to the card. Everything is recognized, parity is being rebuilt. Speeds look good, disks look good.
  3. Actually, I'm gonna buy a SAS HBA card and move all the disks to those ports I've already shifted around some SATA ports. Definitely worried that it's the mobo's native controllers causing issues
  4. Things were running well for more than 2 weeks. Parity was disabled last night. Any last suggestions before I buy a new Mobo? unraidtower-diagnostics-20211201-2125.zip
  5. In the process of trying to rebuild parity using a bigger drive..., it disabled the new parity disk about an hour in. This has now happened 2 times. I changed the connection and it happened again (third time). I think this is a mobo - controller problem. I'm attaching diagnostics in case anyone is interested... but I'm pretty sure I'm just gonna buy a new motherboard. The motherboard I built this with probably wasn't a good choice for Unraid (Asus - X99 TaiChi). I didn't really understand too much about the long-term consequences when I went down this road initially. It's been running since 2017, so I guess it gave me a good 4 years... but these disk problems definitely aren't worth it. unraidtower-diagnostics-20211123-1548.zip
  6. It mounted! I may have lost a few things, but I'm super happy I made it through this nightmare. Thanks to you guys!
  7. The original disk1 is not readable. I saved a ton of what I needed before I rebuilt the data. Running xfs_repair now.
  8. Here's the output. Lots of xfs_repair_output.txt text! I'll rerun with a flag assuming "filesystem flush" is a good thing!
  9. When I initially stated my problem, I mentioned that I attempted the first data rebuild on this disk for disk2. Then disk1 was showing failures during that rebuild; It was only done with 60GB (2.6%) 12 hours later. That's when I asked for help. The filesystem probably wasn't empty. I don't think a format would've been pointless.
  10. So the format was set on "auto" so there was no "Check Filesystem" dialog. I changed from "auto" to "xfs". The check button appeared with a "-n" flag. I ran that process... there is a LOT of output. It finished with statements about "No modify flag set, skipping filesystem flush and exiting". I can't find anything in the manual/storage management page that makes sense except adding the flag "-L". But I'm not sure I'm looking to do a "filesystem flush"... Appreciative of any guidance.
  11. I wasn't going to format it while it was assigned... So it's unmountable. What does this imply for the new disk1? I think I found some documentation suggesting xfs_repair
  12. OK... so everything is saying it's done... but I did not format disk 1... cause I thought that would automatically be part of the process... It's currently saying that the new disk is unmountable. I saw this warning... probably should've asked the question before the process began... Not a big deal to lose another 3 hours overnight... assuming the right thing to do is to format and restart. unraidtower-diagnostics-20211115-2056.zip Here, I'm attaching a new diagnostics file. Should I restart the process?
  13. I'll let you know. I just backed up a ton of data and I'm ready to start the rebuild. I'm also going to follow the rebuild by cloning the parity drive to a new and larger disk, then move the parity disk in to replace the suspicious disk2. I definitely haven't "knowingly" written new information to the files since the system acted up. If it was operating from an emulated disk for more than 2 months, then what you're saying makes sense. I'll be sure to integrate more monitoring protocols and email updates...
  14. I'm on step 8. All disks mounted and there looks to be emulation. I'm copying over some super important stuff before I start the rebuild. So HUGE thanks for getting me this far. Note... maybe I'm a very unaware person, but a few basic text files I was using for keeping records don't look like they're "up-to-date"... last modified date is 3 months ago and I'm pretty sure I made updates to that file in October. Is it possible that modifications would get "missed" from missing a disk? Seems super weird. I'll rebuild the disk as soon as I get some stuff backed up.
  15. So I rebooted and all four disks are now able to be allocated... though I still think disk2 is suspect given my previous post. Looking forward to your suggestions of whether I should continue given the previously mentioned errors.