TheLawyerMan

I think that is possible. I also posted this to Reddit and got some responses there as well. I think this all comes down to unRAID trying to correct a mistake that I made. Please take a look here:

ahh gotcha rebuilding, I think. As per attached screen shot Oh I completely agree. I just thought it would probably be okay as I've never encountered something like this, but here we are...

EDIT: Thank you to Reddit Users u/isvein and u/geekypenguin91 who have explained that "you dont need to write a anything to the drive. Once drive is removed, formatted and readded, it will be rebuilt, even if the rebuild is just zeros" and "unraid doesn't know that it's never had any data on it so it needs to actually wipe it so every bit is a zero". I am now rebuilding this disk and will report back in about 15 days... This was what I went to bed to and what I woke up to. A few days ago, l added a new Exos drive to my server. Pre-clear took 50 something hours--whatever. After that completed, I shut down the array and added the new drive. Upon starting the array, I was given the error "Unmountable: Unsupported partition layout". I couldn't figure out just what to do because there was nowhere to format the new drive (not even unassigned devices). I decided to go ahead and update everything (notably, here, unassigned devices and unRAID). That all worked, and I was able to format the drive. Problem is, unRAID thinks this drive needs to be rebuilt from parity. This is a brand new drive, assigned to a brand new disk number (7). I humored it, and had it run for 10 hours. 2.8% complete. I have since cancelled the rebuild and stopped the array until I can figure out what to do. Please tell me somebody knows what to do. I leave for vacation tomorrow morning, and need this server operating. Specs: Supermicro H23SSL-CT, AMD EPYC 7282, 48 GB DDR4 Multi-bit ECC, 14TB parity, 8TB disks 1-6, 14TB disk 7, and a number of SSDs.

Well, you could just duck tape the two together and call it a day. I have this and really like it.

I find this hilarious because I just reinstalled Windows and just grabbed the drivers. Windows is... fun...

2021-04-11 15-14-19_Trim.mp4

Bump

I'll give this a shot later, thanks.

*sorry for the long (and disorganized) post, but it was necessary; therefore, no TLDR* Hello, I've been spending the last two days on this, and, let me tell you, they were some of the most infuriating and least productive days in my life. It all started when updating ASUS Aura or Armoury Crate (I don't remember). I was running 20H2--terribly unstable, do not recommend. This update required a restart, so I did that. First thing I saw during boot was "Fixing (C:) Stage ___: __% (_______ of _______) Total: __%; ETA: _:__:__," then it got stuck on "Scanning and repairing Drive (C:): 100% complete" for way to long, so regretfully, I forced power down. Then, on next boot, I got "Diagnosing your PC," then BSnotOD: "Automatic Repair / Windows couldn't load correctly." Here, I got quite annoyed, and went and bought a new drive. A few hours later, I loaded up the original drive, and it worked fine, but now, "We can't sign into your account." For this, none of the steps here worked, and for the last one, I don't have enough drive space. Back to the new drive, everything was working fine with a clean install (of 20H2 because that's all I could get from Microsoft's website) and I went about installing all my programs and restoring my documents, pictures, music, videos, desktop, and downloads folders (this time, I installed all the before mentioned on another, separate drive. Then I restarted. This lead to the worst BSOD I have ever encountered: "CRITICAL_PROCESS_DIED." Computer launched itself into diagnosing and drive recovery, then promptly spit out: "Automatic Repair / Automatic Repair couldn't repair your PC." I couldn't even boot into safe mode. Then: "CRITICAL_PROCESS_DIED" again. I also went into the command prompt and ran chkdsk "C: /f /r /x," but to no avail; drive still no work. So, I'm at a standstill, what the heck do I do?

Updating driver worked. Thanks!

fun... I'll do this shortly. Thanks

this

Hello, Adobe Media Encoder is not using my GPU while encoding videos (GPU is idle, CPU is maxed). Yes, the renderer is set to Mercury Playback Engine GPU Acceleration (CUDA). I came across this thread here, but the video linked 1) is from 2014, and 2) deals with Premiere Pro, not Media Encoder. Thanks

Thank you

Hey, Legacy or UEFI: is either better for unRAID (i.e. more stable)? Disregard system support, is one better than the other?