EGOvoruhk

Hopefully this news means Unraid 7 is going to come with some regularly added features/upgrades to justify the increase? Seems all the good stuff the past few years has come directly from the community, and Unraid itself has just been in maintenance/security mode. My (non-internet connected) server has been on 6.11 for a year and half and I don't feel like I'm missing out on anything yet Would love to actually see "unlimited" devices apply to the main array, bcachefs when it's "ready", a simple way to deal with bit-rot detection (and healing), 3+ parity drive support, etc

Are there any issues for older MacOS versions? I'm trying to follow the YouTube video (though it seems outdated, in regards to the settings shown), but get "stuck" on the notify script. It just hangs forever. I'm trying to install Mojave within Unraid 6.10.3, and it creates a "Macinabox Mojave" folder in the VM share, with OpenCore and a vDisk, and also downloads a (roughly) 2GB "Mojave-install.img" file to the ISO location, and that's about it, the script just sits there running in User Scripts

Those drives were sitting physically untouched in a rackmount server for days (Disk0 never actually being physically touched at all, as that was the 8TB parity that was left intact), and went through 2 full checks. I'm curious why both would fail at the exact same time (within 3 seconds, per the log). Could it be indicative of a different issue? They're connected via SFF-8087 fanout cables, and the controller/SFF-8087 end was never unplugged, and hasn't been for over a year, so it shouldn't be any seating issues. They also passed SMART tests after the failure without ever being touched, so obviously not a cabling issue Just wondering where I should be focusing my attention. One drive would make sense, both simultaneously throws me for a loop

Upgraded to 6.8, and about 8 hours later, both my parity drives popped up as disabled simultaneously after some normal usage. Curious if there's anything in the logs that may hint as to why they would both drop at the same time Note: Prior to the 6.8 upgrade I had ran a full parity check with zero errors, then I upgraded my 2x8GB dual parity with a new 10GB drive (now 1x8GB, 1x10GB) and parity sync passed with zero errors, then I upgraded a 4GB data drive with the retired 8TB parity drive, and that sync also passed with zero errors. Then I made a backup of my flash, and upgraded to 6.8 without issues. All my VMs and Dockers were running, and everything seemed normal until later when both parity drives popped up with red Xs I shutdown all VMs/Dockers, ran a SMART test on both parity drives and they came back fine, grabbed my diagnostics, stopped the array, and powered down void-diagnostics-20191228-1756.zip

I'd love iSCSI support for ESXi Datastore use