This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
RAIDar 6.5.0 for Mac OS Catalina was already fixed so you should be able to install it now on that version. We just tested it before we were able to use RAIDar on Catalina.
Well, when I open the System Report showing the Applications installed on my MacBook Pro running OSX 10.14.6 Mojave, it does show up as a 32-bit App. Apple and others say that these will not run under Catalina. I realize that the Web page interface will Probably still work, but RAIDar will not, so it says. (BTW: My Canon Printer/Scanner is in the same boat, alas)
Well, when I open the System Report showing the Applications installed on my MacBook Pro running OSX 10.14.6 Mojave, it does show up as a 32-bit App. Apple and others say that these will not run under Catalina.
Yes, 6.5. Not trying to argue, but the System Display says it is 32-bit. NetGear ReadyNAS 6.10.1 is probably going to be fine. The locator software in RAIDar says no good. Not implying it is a driver, just that the code that runs in the OS is not 64-bit. This is not a deal-breaker for Catalina, but the Canon and Logitech's Harmony One software give me cause for concern. I can always use my wife's older MacBook, as it cannot be upgraded to Mojave, much less Catalina.
Thank you very much. Not for RAIDar, but there are far too many reasons to hold off on Catalina for the time being. God, look at all the posts at MacRumors and OSX Daily!
RAIDar 6.5.0 for Mac OS Catalina was already fixed so you should be able to install it now on that version. We just tested it before we were able to use RAIDar on Catalina.
Thank you, oddly yesterday, the .dmg file did not install a new executable, but today it successfully installed 6.5.0. Now only if the resync would finish so I can replace disk4. I have gone from redundant to degraded.
As I said, yes I am resyncing, and yes, I am making a backup. Concurrently they are both active. That was the jist of my concern.
If disk 4 is the disk that is resyncing, then you could simply pull it. That would probably speed the backup, and it would also eliminate any chance that the resync will uncover a problem with one of the other disks.
However, if it's not about disk 4, then you probably should leave it alone and hope that the backup completes successfully.
It is disk 4. If I replace it, won't that start the resync over again? And, is that a bad thing if it is already degraded? Very confused.
Normally with XRAID/RAID-5 you have protection from a single disk failure. When the system is resyncing, that protection is lost - so the volume is described as "degraded".
Disk 4 was already not in the array (the resync was trying to add it back). The risk you were running is that another disk might have some errors. If that were to happen, the volume itself would fail, and you'd lose all the data.
Pulling disk 4 actually reduces the odds of that happening. The resync needs to read or write every sector on all four disks. The backup doesn't require that - for instance, it doesn't need to read free space at all. In any event, you were going to replace disk 4 anyway. So there's no point in trying to add a failing disk back into the array - it just was increasing the odds of losing your data, and slowing down the backup speed.
The best strategy is to have a backup plan in place, so you are always prepared for a volume failure. RAID protection is nice to have, but it isn't enough to keep your data safe.
