johmei

I'm gonna go that route then for sure. Thanks very much for the input!

So I guess that means doing this over SMB really isn't ideal....I'll give a search and pursue that route.

I've been running my torrents such that the client runs on my primary system, and I save the actual data on unraid via an SMB share via a network mapped drive (that is to say, when I open a torrent and qBittorrent asks me where I want to save the actual data, I choose my unraid SMB share that is mapped to a drive letter). I'm starting to think....maybe this isn't such a great idea. Am I on the right path with that thought? If I am...what would be a suggested alternative method for torrenting on unraid? 🤔 Thank you kindly!!

Thank you!!

Thanks for the explanation there! And that's a really good point. While I was loosely throwing around the term formatting incorrectly, the one thing I do know is that formatting will always obliterate the data (or at least the index) and in this case, it doesn't matter (the clearing would have destroyed any data already). But I can see where if I was replacing a drive, and it finished rebuilding and this popped up, I could have made a mistake. So I feel better about it now! Thanks again so much!

Also, I feel REALLY stupid. The option to format them is RIGHT there in front of my face. I jumped to making a post WAY too fast which I usually avoid doing but....ughhh...the information is on the web, readily available, and I didn't bother checking. I am so sorry. 😕

My mistake; I used to do full formats that would take hours so that's where my mind was. Awesome, thanks! Could you elaborate on what these log entries mean? I'd like to understand them a bit better. Thanks again!!

Sometime last year or the year before I purchased 3 x 12 TB drives. I made two my new parity drives, and added the third one as a data drive. This year I discovered 18 TB drives were now the same cost as the 12 TB drives I purchased previously, and 12 TB drives were not that much cheaper, so I bought 2 x 18 TB to replace my 12 TB parity drives. All went well with that, but when I tried to add my 12 TB drives to the array as data drives I was greeted with that wonderful error after it spent over 12 hours formatting them both. So....things that are different; All my drives were previously connected to an LSI SAS2008 controller. It has a capacity of 8 SATA drives and since I just added 2 beyond that, my parity drives are now on the integrated controller, X370 Series Chipset SATA Controller. Those seem to be working fine and without issue. In fact, all the 12 TB drives aren't even on a different physical cable than they were previously...and I've heard that a bad cable can cause this issue. I've attached the Diag here. I could try again but I wanted to run it by some experts before I try again since I'm assuming if I try to add them again, it'll clear the drive again and will take another 12 plus hours to do so. Thanks so much! johnsnas-diagnostics-20230215-0922.zip

Hmmm....well I didn't change anything, but I did restart the entire server and it seems to be working? I guess it wasn't captured properly when it last started up *shrugs*. I still don't see the Nvidia audio in the device manager, but I don't need it so as long as that won't cause issues...I guess I'm okay

I'm at a complete loss here. I have an MSI X370 Gaming Carbon pro with a Ryzen 5 5600G. I was having trouble getting my NVIDIA card passed through but thanks to spaceinvader one's advanced GPU passthrough video, I got it working along with audio. Great! But I wanted to use the onboard realtek audio controller that the manual swears up and down it has (even though you won't see any mention of realteck in the below PCI device) but while I got it working without issue just a few days ago, I went to bootup my VM today and was surprised and confused to see no audio controller. I had to do some fiddling with the XML file for the video card to work, but I didn't for the audio....but now I'm guessing there is more I might have to do? I'm including my VM XML file below as well as my PCI Devices and IOMMU groups. Does anybody have any idea what might be going on? Please let me know if you want me to provide any specific information as well. Thanks so much!

Yeah, I'd definitely prefer to just let it build without writing to it in that case. Thanks!! Got ya. I'm gonna play it safe from this point forward!

Also, the extended smart test passed without any issues! So I'll go ahead and rebuild parity when I get home onto my new 18 TB...should I still refrain from writing to my server while rebuilding even if it's only 1 of the 2 parity drives?

All sounds good, thanks! I'll still probably replace it one at a time because I'm paranoid, but it's good to know it would be fine either way! Thanks again!

Is that general rule about hotswapping true even if the MB bios has settings for hotswap support? I still would rather not risk it in the future so I'll probably abandon that regardless, but I'm just curious. I suppose if it has to be rebuilt anyway...I might as well have it rebuild onto the new 18 TB drive? I assume I should replace each parity drive only one at a time to reduce the risk of data loss should something go wrong? Thanks!! johnsnas-diagnostics-20230130-1159.zip

I currently have 2 x 12 TB parity drives, 1 x 12 TB data drive and 3 x 4 TB data drives (4 TB drives are by far the oldest). I am wanting to replace both 12 TB parity drives with 18 TB drives and either add the two 12 TB parity drives to the array as data drives, or replace two of the 4 TB drives with the 12 TB drives. I wanted to preclear my 18 TB drives so I plugged one into my system (I have a dock at the top that plugs into the MB, the other drives are all on an "LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)" controller)....the very second I did this, I received the follow errors in my notification bar. So I'm running an extended SMART test on the parity drive now but I just can't imagine there is any connection to plugging in that drive...is that possible or is it a coincidence? I have the errors below from the notification archive. 29-01-2023 20:23 Unraid array errors Warning [JOHNSNAS] - array has errors Array has 1 disk with read errors warning Parity disk - ST12000VN0008-2PH103_ZS80483R (sdc) (errors 2048) 29-01-2023 20:23 Unraid Parity disk error Alert [JOHNSNAS] - Parity disk in error state (disk dsbl) ST12000VN0008-2PH103_ZS80483R (sdc) alert Thanks!