unconcerned-beloved6864

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

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

unconcerned-beloved6864's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Thanks for the help. After looking online it does seem like there are ways to remove 1 of 2 parity drives without leaving the array unprotected but this is not done by default. My original feature request stands, it would be nice to be able to remove 1 of 2 parity drives without potentially putting data at risk. Additionally, I understand how parity bits, backups and SMART error detection work, I know that 2 parity drives are better than 1. It is incredibly insulting to be talked down by anyone let alone a moderator. Once I can afford it I will be moving away from Unraid. I am closing this as the solution and turning off notifications.
  2. Thanks for the reply I appreciate it. This has been frustrating for me and I know the frustrating was likely caused by my own doing. I am trying not to let my frustration get the best of me here and apologize if it comes through. Probably the way I should have done it. However, when I originally got the first alert I was planning to just remove it from the pool and not replace it. After I got the second alert for the newer larger parity drive I decided that I should just get 2 drive and do them both I don't know why I'd ever reach out for advice on replacing two drives, the process should have been pretty straight forward. The 2TB drives in my system are approaching 6-7 years old, and the 8TB is just over 2 years old. The 8TB was unexpected and probably could have lived for a while longer as it was only 8 uncorrectable sectors, however since its use as a parity device is critical I opted for replacement. I've rebooted recently so I don't expect there to much present here but attached. Also to note, I did find online that when making changes to the array via "new config" there should have been an option to check saying that parity is valid. For some reason I didn't have this option but after a reboot it did! I figured while time consuming, I should run a parity check to be safe. titan-02-diagnostics-20230915-1258.zip
  3. Recently one of the drives in my pool had gone into pre-failure presenting in multiple SMART errors. First thing I did was empty the contents of the drive to prevent any potential data loss. After the drive was emptied I got an alert that my parity drive was entering pre-failure as well. I purchased 2 new drives to place into the system and started by replacing the drive in the pool. The array had to do a full rebuild for the 0GB drive that took 24 hours. After that I put in the new parity drive which took another 24 hours to sync up which was understandable. Finally I went to remove the failing parity drive and was notified that I would need to rebuilt the entire parity drive again wasting ANOTHER 24 hours. At this point I am looking at a total of 4 million useless reads/writes off my entire array and 72 hours of downtime. This seems incredibly inefficient to do and is not acceptable at all. There must be a better way that the system can handle removing one of two parity drives without resulting in 48 hours of downtime and millions of pointless writes.