@john-graham shouldn't be the case, they are 14TB Toshiba MG07ACA drives sold by OWC and are listed as CMR. Luckily it looks like they still sell them so I should be able to pick up a matching drive when I have a chance.
@dguisinger01
I am pretty sure the only "SMR" drives we ever sell are the low end 1-2TB drives, which are difficult to get at good price points with SMR. And performance is generally not a major factor for such disks. All the Toshiba and large drives we sell, we strictly avoid SMR.
@dguisinger01
I am pretty sure the only "SMR" drives we ever sell are the low end 1-2TB drives, which are difficult to get at good price points with SMR. And performance is generally not a major factor for such disks. All the Toshiba and large drives we sell, we strictly avoid SMR.
I asked the question because Western Digital got slammed for not labeling drives if they were SMR or CMR drives
@john-graham
SMR vs CMR is a scandal. Drive companies backtracked, but then started sneaking in SMR without labelling again. Its a confusing issue to consumers.
@stevebgb
Wish I knew. Engineering has its schedule. One thing I learned is good engineers do not go from project to project, they complete one item at a time. So the beta has to wait untl the current task/project is at a stopping point. Could be any time, my guess is friday earliest.
I tried to run the beta 5 but gut the same old error.
I need a SoftRAID support file. Did b2 work? if so, run it and save a support file and attach. B5 has different debug code.
If it did not, then paste this into terminal.app:
sudo softraidtool generatereport ~/Desktop/John.Graham.7.6.1.b5.11.19.23.sr_supt
I need a SoftRAID support file. Did b2 work? if so, run it and save a support file and attach. B5 has different debug code.
If it did not, then paste this into terminal.app:
sudo softraidtool generatereport ~/Desktop/John.Graham.7.6.1.b5.11.19.23.sr_supt
Attached is from b2 that works, b5 does not.
We released a 7.6.1 b5, but it is not a fix, we are working on a new beta. It collected additional debug info however, which we are reviewing to try to fix this, this week if possible.

