korro

Members
  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

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

korro's Achievements

Noob

Noob (1/14)

5

Reputation

  1. yes, it was a notification. I received serveral notifications that looked like notifications from previous runs and i ignored them, but this was the notification about the finished data rebuild so it scared me a bit. If you say there's nothing to worry about then i think i can close the thread. Thank you very much, you have been very helpful, as always!
  2. sorry for the delay. new diags attached glados-diagnostics-20230703-1859.zip
  3. Ok, data rebuild completed with 33 errors but everything seems to be working correctly to me. Is this normal?
  4. ok, the second try did it. The content still looks quite good so i'm rebuinding, let's hope this goes smoothly.
  5. the check detected a corruption. Running it again with writing enabled gave me the following message: shoud i try to mount and replay the log as suggeted? how do i do that?
  6. ok, new diags attached glados-diagnostics-20230630-2023.zip
  7. Sorry for the delay, it has been a rough couple of days. I've done as you said and you can find the diags attached. I've also noticed an error on drive 2 smart, it's a very old drive, i think it's time to replace it after everything else is resolved. glados-diagnostics-20230630-1956.zip
  8. thank you for the very quick reply. I will check as soon as i get home EDIT: just a quick note on this, i'm quite sure the parity does say disabled when i hover on the red X
  9. Hi. Unfortunately, I'm having the same issue I had a couple of months back, but this time it looks even worse. You can find the original thread here: https://forums.unraid.net/topic/138169-recover-from-double-drive-issues/#comment-1254907 To sum it up the problem the last time was a drive having issues, (probably cables or the hard drive cage backplane). after trying to rebuild the drive the parity drive also started to throw errors. Luckily everything went well and I recovered all the data. This time the problem is similar, drive 6 started throwing errors, like last time, and yes, it's the same drive, in the same cage but with a different cable, so I'm starting to think it's the backplane of the cage. This time the drive was also unmountable due to file system corruption. I solved it following the official guide and started the rebuild. Like last time the parity drive started throwing errors during rebuild. Again, same drive, same cage, different cable. And again, this time it's worse than last time, after a reboot the parity is also disabled, so now the array has parity disabled and disk 6 emulated as you can see in the image attached (how? is it possible to have a disabled parity but still use it for drive emulation?) Unraid gives me the option to start the array and rebuild, but I don't know if it will keep all the data because of the 2 issues. Can I recover from this? glados-diagnostics-20230629-1932.zip
  10. ok, the rebuild was successful. Thank you!
  11. Ok, so i just start the array with both disk assigned? nothing special to be done?
  12. Quick update, in the meantime I've run an extended self test on both drives and they both passed.
  13. ok, so no harm in forcing the reboot i guess. You can find the diagnostics attached glados-diagnostics-20230420-2047.zip
  14. Hi. I'm having some trouble with 2 of my drives and I'm here to ask how to proceed. My setup is 1x parity, 7x data drives, and 1x cache drive. Cache is an internal drive, all other drives are in an external drive cage. The connection to the drive cage is not perfect, especially for disk6, and sometimes it gets disconnected. This happened again yesterday, disk 6 started throwing errors and got disabled, so I started with my usual procedure, I stopped the array, unassigned disk 6, checked all cables, tested the drive, reassigned it, and started data rebuild. Until this point, there was no problem. The rebuild should have finished today around the middle of the morning, but this evening I returned home and noticed that the rebuild was still not complete so I started looking for possible causes and I noticed a lot of errors on my parity drive. The drive was not disabled but I was unable to access it. My guess is that I have another connection issue, but it is strange since I checked all cables yesterday. Now my system is not responding and if I force the shutdown it would usually trigger a parity rebuild, but I don't know how it will behave now since I have 2 drives with errors. Since the parity shouldn't have had many writes during the day I guess my best option is to trust the parity and retry to rebuild disk 6 from it, even if I get some corrupted files it's still better than losing the entire disk. I've read the guide about trusting the parity but I'm not sure if it applies in this situation. Is my reasoning sound? Do you have any alternative to suggest? And if I'm right can I just follow the parity trusting guide? Thank you in advance for the help.