Jump to content

Neldonado

Members
  • Posts

    76
  • Joined

  • Last visited

Everything posted by Neldonado

  1. Finished scrubbing and including diagnostics after finishing. also noticed my log is full, what should next steps be? skynet-diagnostics-20230510-1535.zip
  2. Tons of errors being corrected… this is all good I hope? Looks like I’ve got some downtime before it’s finished.
  3. So I do that and it refreshes and says aborted? UUID: xxxx Scrub started: Mon May 8 05:57:58 2023 Status: aborted Duration: 0:00:00 Total to scrub: 3.04TiB Rate: 0.00B/s Error summary: no errors found
  4. So is this what I want to do? btrfs scrub start -B -d -r /dev/sdaa1 and btrfs scrub start -B -d -r /dev/sdx1
  5. Are these the same errors (see picture) sdx is the other drive in this cache pool. BTFS error (device sdl: state EA): parent transid verify failed on 316334 9286912 wanted 36459 found 36425 uploading diagnostics again. Somethings weird going on, I replaced all my cables a month or two ago and I just started noticing these errors out of nowhere. skynet-diagnostics-20230508-0436.zip
  6. looks like the drive is throwing the same errors, I imagine it'll drop offline any minute.
  7. I’ve got roughly 1.2TB of data on this cache pool, would it be safe to run the mover and get the data off?
  8. I started getting these notifications a few weeks ago, "fstrim: /mnt/mediacache: the discard operation is not supported". I went to poke around and checked my logs to find a wall of this: BTRFS error (device sdaa1): bdev /dev/sdaa1 errs: wr 106017132, rd 82906, flush 0, corrupt 0, gen 0 what causes this, and what should I do to remedy the situation? Shut down, reseat cables, start back up? I've uploaded my diagnostics skynet-diagnostics-20230506-0817.zip
  9. Anyway to know what caused the crash? I use NFS to mount shares back and forth between this unraid server and another unraid server.
  10. Hi all, Last night I updated a few dockers and hit "invoke mover" and went to bed. When I woke up I noticed none of my shares were present. This is what my logs show. I have attached my diagnostics as well. t1000-diagnostics-20230412-0339.zip
  11. Hey all, I am trying to figure out how to safely increase my vdisk. I am using a 1tb m.2 drive almost entirely for this vdisk so I want to increase it from 300 to like 800 or so. Is it as easy as clicking on the 300G and changing it from there?
  12. rebooted/ shut down server and went to replace the sata power splitters, found one with a bent / smashed pin. Culprit? IMG_0534.heic
  13. no progress 2hrs later. Edit: it's been over 24 hours with no progress... what should I do?
  14. So my parity rebuilds have never taken this long... it's been hovering around 20% since this morning... any reason to worry?
  15. Hmm ok. Were you able to tell what happened with my first diagnostics yesterday? What are the next steps if the cables I just replaced are fine?
  16. I just replaced the breakout cables for this drive even though it didn't cause issues before. I will check connections again. Since parity rebuild is 25% complete should I let that finish before stopping/ checking cables? How do I go about running a scrub and what does that do?
  17. Oops! accidentally attached the smart drive test twice. I attached my diagnostics. I went and moved some drives around and a different drive was throwing errors which made me think it was the cables. So I replaced both of the breakout cables. I saw no errors after this so I started the parity rebuild. Fast forward 7-8hrs and I see now one of my cache drives is giving me errors. I am a bit lost at this point. I included the diagnostics for right now as well. skynet-diagnostics-20230315-1907.zip skynet-diagnostics-20230316-0345.zip
  18. SO! it's been almost a week and I just got a notification that same parity drive was disabled. I attached a short smart test of the disk a screen shot of errors, and my diagnostics. I haven't had any issues for over a week! All I did was maybe 30 minutes ago invoke the mover. ST10000NM0226_ZA290T3P0000C905MDCF_35000c500a6c8fc23-20230315-1905.txt skynet-smart-20230315-1905.zip
  19. Connected the SSD's to onboard sata ports and rebuilt the data disk + parity, all is well! Thank you!
  20. as in, remove the disabled data disk, and put in a new disk? I don't have an extra disk lying around, unless I used my cache drive to replace it. but then I would be moving data from my cache back to my emulated array.
×
×
  • Create New...