About7Deaths

I rebuilt the array and all works as expected; thank you all for the advice.

Definitely not best practice on my part but I usually did it manually from time to time. I just set it for a year in case I managed to totally forget (which I never did). I just find it odd how after the parity check I am not even able to detect the drive after plugging it in, let alone running tests on it.

I went ahead and plugged in the one drive and am currently pre-clearing it. Although, thinking back on this I'm surprised that I have the settings to do a parity check once a year and it coincidentally failed the one day that I have it automatically check? Seems odd. It had checked a month prior because of a power failure and was fine.

For this I meant how long does a small 3TB rebuild usually take time-wise.

If I were to plug in two drives instead of one, would it split the data between the two drives when rebuilding? Whereas if I only put in a single drive for rebuild it would definitely fill the whole drive.

The parity drive seems to be fine and I have backup spare drives. Is it to the point where I should ditch the drive and rebuild the array with the spare? (The current two drives are the same age at 5+ years.) The rebuild would be around 3 TB. I actually have two extra drives at 3 TB; would it be advisable to plug them both in (making it 3 total at 3/3/3 TB) and rebuild instead of just doing 1 to 1?

Correct, the drive is not available. The SMART test I provided was what was available to download after selecting the extended test option from the portal. However, it is possible that the test failed to run in its entirety.

After the parity check started itself, it failed to complete after a few hours and my main drive (the other drive being the parity drive) was taken offline and SMART report was unavailable. Doing some reading, I downloaded the current diagnostics zip, disabled auto start of VMs and auto start of array, and then shut down the system. I rebooted but no cigar. I shut down the server and disconnected the wires, I rebooted and logged into the portal on my laptop. I then reconnected the one problematic drive see see if it would pop up, after 5+ minutes it repopulated the array and I was able to run a smart test (although it may not have completed all the way, it was hard to tell). The only notable thing I noticed is that Current_Pending_Sector had a RAW_VALUE of 1. Attached is the SMART report. After reading the report everything seemed fine (to my inexperienced eye), however, upon reattaching everything and rebooting I am still unable to see or attach the problem drive. han1-smart-20210203-1134.zip

Update: After trying numerous things the only actual issue was that I had the Default Gateway (on unRAID) set to my old router's IP address (set by router). Solved

Basically my university has a system in place where you enter the MAC Address of your system for Ethernet access. Well, I added the Ethernet of both my router and my unRAID server machine. When running a Windows 10 virtual machine I have internet access within the VM, however my unRAID control panel and docker apps cannot access the internet. Any suggestions?

UPDATE: I tried a combination of various install methods along with some personal tinkering and I got macOS Sierra to boot correctly! I'll post information later, feel free to ask though.

Also, I tried booting up my previous config in safe mode, no luck.

What kind of output are you speaking of, onboard graphics? If so then yes, I have that assigned to unRAID's console and the server's BIOS.

Haha, getting close to doing that. I just have the 1 card.

Ah sorry, my unRAID machine does not have a BIOS resolution option, while my Clover / Sierra virtual "machine" does have the resolution option. I have the ability to do a new install, however this is my second attempt using a completely different method yet still having the exact same problem.