v. 6.3, driver 6.3 ...
 
Notifications
Clear all

v. 6.3, driver 6.3 on BigSur - Error Notice

Page 1 / 2
(@guitarflex)
Eminent Member

Checked the Known Issues link to not waste anyone's time, and the only description I found of this same notice applied to 10.14 and earlier. Finally updated the macOS from Catalina 10.15.7 to BigSur (which is already not off to smooth sailing with Adobe/Photoshop) and in the process got current on SoftRaid 6.3 with the 6.3 driver. 

Is this error notice a concern/problem/or known issue? I was sorting out something on the computer, used Dock Ejector to eject all of my volumes, and proceeded to pull the cable only after the volumes were safely ejected. When I did, I got this error notice. I recreated the issue 3 times in a row, and went into Disk Utility to confirm that, yes, the volumes were ejected prior to disconnecting the ThunderBay. 

 

error notice
Quote
Topic starter Posted : 18/08/2022 9:13 pm
(@softraid-support)
Member Admin

There was a bug in 5.x that was fixed in 6.0 and Big Sur, where when the app was open a long time, it would generate this.

Are you on Big Sur now? Are you getting this every launch, or when the app is open and sitting for a while?

ReplyQuote
Posted : 18/08/2022 10:49 pm
(@guitarflex)
Eminent Member
Posted by: @softraid-support

There was a bug in 5.x that was fixed in 6.0 and Big Sur, where when the app was open a long time, it would generate this.

Are you on Big Sur now? Are you getting this every launch, or when the app is open and sitting for a while?

Thanks for the reply. To keep the answers short, yes, I am on Big Sur as of earlier this afternoon. I didn't get that error upon launch, and hadn't had the app open and sitting long enough to receive the message. That message only came up (repeatably and consistently) when I would (1) Eject Volumes, with OWC Dock Ejector, and looked to see that all volumes in SoftRaid said "Unmounted." At that exact moment, (2) if I disconnect the device (in my case just disconnecting the TB3 cable), that exact error message appears in the SoftRaid app as soon as the device (ThunderBay) is disconnected. There's no error in Finder or indication that a volume was not ejected properly, and I confirmed in Disk Utility that all volumes were properly ejected. But in SoftRaid, at that specific moment in time under those exact conditions, I get the error every time. 

This post was modified 3 months ago by GuitarFlex
ReplyQuote
Topic starter Posted : 19/08/2022 12:24 am
(@softraid-support)
Member Admin

@guitarflex 

I will investigate this. Possible this is a bug, rather than something unique to your system.

ReplyQuote
Posted : 19/08/2022 12:29 am
(@guitarflex)
Eminent Member

@softraid-support 

Thank you. Due to some Adobe Creative Cloud issues anyhow, I am contemplating a clean/fresh install of Big Sur, as I made the switch from Catalina the standard way directly from Finder, without starting over from scratch. If I take the leap and clean install, I will update to let you know if it's still an issue. Or if you find something out before then, vice versa. We'll figure it out somehow. I appreciate it and thanks again.

ReplyQuote
Topic starter Posted : 19/08/2022 2:31 pm
(@softraid-support)
Member Admin

@guitarflex 

Sure. I have seen Apple's Migration assistant import completely non-functional, and unsigned extensions from as far back as 2007. i.e, there is no protection from importing problem extensions at all.

So yes, this could help. let us know

ReplyQuote
Posted : 19/08/2022 2:35 pm
(@guitarflex)
Eminent Member
Posted by: @softraid-support

@guitarflex 

Sure. I have seen Apple's Migration assistant import completely non-functional, and unsigned extensions from as far back as 2007. i.e, there is no protection from importing problem extensions at all.

So yes, this could help. let us know

To be continued sometime. I'm a bit traumatized at the moment but probably for no good reason and certainly not your fault! I just resolved an Adobe disaster that lasted 27 hours upon the "dirty install" of Big Sur, but once I loaded the bootable Catalina backup, I think I misjudged that it was Big Sur's causing, when it wasn't after all. 3 hours of conversations and 2 agents later, my Creative Cloud suite actually works again and from what he had to do to solve the issue (which involved a ton of manual uninstalling and trashing folders), it's clear to me a fresh install would have rectified whatever went wrong along the way. At this stage, I'm frazzled enough to be sensitized all over again to irrational fears of screwing it all up if I fresh install after all of that and finally getting a resolution, but......

 

I kind of wonder if something didn't go as planned during the OS update all the same. When Big Sur loaded after installing, I got a "your computer restarted because of a problem" notice but all else seemed well. Applications were working fine until the Photoshop disaster which evidently was still a disaster when I loaded the Catalina backup (so I can't blame that one on Big Sur in the end. I *am* wondering if an Apple security update did it, since the other Mac that had not been updated was fine with Photoshop, but not to ramble on 3rd party apps that are irrelevant to SoftRaid).

 

I'm sure I'll work the nerve up to do whatever needs to be done over the weekend but if the SoftRaid notice can be confirmed to be a bug, great, I'll probably leave my system as-is unless something really crazy happens. But if there's no good reason for it or can't be explained by a bug, a fresh install may still be in store after all of this!!! I'd almost be getting annoyed and frustrated if the whole thing wasn't hilarious to me by this stage. I've been at this 9 days now, building up to and finally migrating from Catalina. There has to be some comedy to that at least and the comedy keeps me sane. At least I'm learning enough that this will never be as stressful to me ever again for the experiences. 

 

If you find out it is a S.R. bug though, please definitely let me know! 

This post was modified 3 months ago by GuitarFlex
ReplyQuote
Topic starter Posted : 19/08/2022 9:05 pm
(@guitarflex)
Eminent Member

 

SoftRaid Window

Three highly specific questions about this issue in the OP, but I'm not sure if it belongs in this Known Issues sub-forum or in the Big Sur sub-forum, since the questions straddle the line between the error notice mentioned previously and general questions to disk management. In lieu of posting twice, I'll update here but feel free to move it if need be.

 

1. (Preface) -- stayed up half the night (again) reading & researching. When I finally had Big Sur on my machine and attached a Mercury Pro Elite (16TB) to my ThunderBay Flex 8, the volume did not mount. Thinking it was a fluke, I tried the other port to no avail. Beginning to worry if the ThunderBay could be faulty, I tried a different approach, connecting directly to the Thunderbolt 3 Pro Dock. Drive still did not mount (which was ironically comforting, as it ruled out concerns over the ThunderBay enclosure). Eventually, restarting the computer and drive did the trick and my volume mounted. Since then (two days ago), the Elite Pro normally mounts, but once in a while I have to try twice. 

1-MAIN Question: Had not given this a whole lot of thought since Thursday, but in the middle of last night found this RocketYard blog: https://eshop.macsales.com/blog/67909-big-sur-problems-macbook-pro/ Even though I'm on a late 2019 model and the main body of the article did not apply, as I began scrolling through comments it came to my attention that people had been experiencing major issues with mounting hard drives after updating to Big Sur. Which leads to SPECIFIC question #1:  Should OWC Dock Ejector eject everything connected to the computer, or only volumes attached to OWC hardware?

1-Context: As you can see in the first attached screen shot of my SoftRaid window, after using Dock Ejector "Eject All," (and yes, I updated Dock Ejector to the latest version too), five drives clearly say "unmounted," but the bottom volume "Video Computer Clone" was not unmounted. That volume is on a (fairly cheap, Costco) external SanDisk Extreme SSD 1TB drive connected to my computer through a different USB-C port (in other words not connected to the ThunderBay). Having said that.....

IF I connect the SanDisk directly to the ThunderBay USB-C port OR if I connect it to the Thunderbolt 3 Pro Dock, Disk Ejector then ejects to the disk.

 

2. When I dismount the SanDisk (either via "Unmount" in the SoftRaid window, or via Disk Utility), and pull/disconnect the drive, the identical error message pops up: "An internal part of the SoftRaid application has stopped working." So I don't think this is related to improper disk ejection, but this leads to my third and most important question.....

 

3. Very importantly, once the volume is ejected, it's safe to dismount regardless of the above error message, correct? After reading the comments on the RocketYard blog, the second screen cap accompanies my question. I can have all of my SoftRaid volumes unmounted (attachment two; recalling the bottom volume was unmounted manually...not with Dock Ejector), and when I go into Disk Utility, I see the volumes are indeed all grey/unmounted, but the top level/disks in the ThunderBay enclosure are not greyed out, nor appear ejected. I actually tried hitting "Eject" on some of the SATA disks but there was no volume to dismount and so it appeared to be irrelevant. In any event, I just want to confirm that this is perfectly acceptable and normal behavior, and that as long as the volumes themselves are dismounted, there's not an issue or concern here to resolve. 

 

I may load from the SanDisk backup into Catalina this afternoon, take a look around and see if things look and behave the same. If I can't figure anything out from that, I may try rolling back to SoftRaid 6.03 since I kept the installer, and at least see if the "An internal part of the SoftRaid application has stopped working" goes away. If none of those things reveal a change or answer anything, maybe all of this is leading towards a clean install of Big Sur. But as long as I know I'm not jeopardizing the drives, it's no big deal to put up with an inconsequential SoftRaid error notice....as long as it really is inconsequential.

Disk Utility Window
softraid volumes unmounted
SoftRaid Window

 

This post was modified 3 months ago by GuitarFlex
ReplyQuote
Topic starter Posted : 20/08/2022 3:00 pm
(@guitarflex)
Eminent Member

To update after some somewhat-promised experiments in the previous message. I booted Catalina from one (I'm a little paranoid; operative words: one of) of my SSD bootable backups. I was going to unmount all volumes but the startup volume and I did. No errors. But I couldn't immediately attribute that to Big Sur vs. Catalina because....

 

I noticed that my SoftRaid was old prior to the OS update. I still had v. 6.03 installed, so I went back to the main startup drive/Big Sur, proceeded to uninstall SoftRaid 6.3 entirely, restarted, re-installed the application and driver to SoftRaid v. 6.05 (because I had it and it was slightly more recent than 6.03, and I can't get 6.1 or 6.2 installers from the website) on Big Sur. And.....

 

No error notice. 

 

(Also, it turns out I answered my own question 3 (above) about disks vs. volumes appearing in Disk Utility. It's the same on my bootable backup and the same with my SoftRaid downgrade to 6.05, so unless corrected, this appears to not be a concern in the end. My volumes unmount so at that point they're totally safe to disconnect a cable, power off an enclosure, etc., and seeing other blank disks without a volume in disk utility is ultimately inconsequential, correct? Furthermore, SoftRaid would alert if a drive had been degraded anyhow).

 

I think also answered my 1st question above and have confirmed now that Dock Ejector only ejects OWC connected drives but if I am mistaken, please don't be shy to tell me "you're wrong."

 

So I'm on SoftRaid 6.05 again but on Big Sur. Would all of this point to a bug in 6.3 on Big Sur?

 

The last thing I could do is the clean install but at that point I'm going nuclear just to answer if this is a system issue on my end or an actual bug in SR 6.3 on Big Sur, and as long as my computer is stable, at some point I should probably quit trying to become a computer repairman and get back to work. Anyone else have 6.3 on Big Sur who can test this out to see if it's the software or just my system?

 

Last, now on 6.05, the only glitchy/weird thing is that whenever I start the software, I get prompted to enter my computer password because "Soft Raid 6.0.5 wants to make changes" and a new copy of the driver is installed upon launch. This is with Startup Security Utility set to "No Security" on my Mac. 

 

Obviously you'd probably prefer for me to be on version 6.3 anyhow and I'll happily go back once the error I was getting is confirmed to be a benign bug that does no harm upon disconnecting my devices

ReplyQuote
Topic starter Posted : 20/08/2022 5:01 pm
(@guitarflex)
Eminent Member

Forgive me for utterly beating up this thread with another wall of text over this afternoon. If I could keep it any shorter I would but issues just continue to come up. 

 

So now what appears to be happening is distinct from my initial concern over Big Sur itself when the 16TB Elite Pro didn't mount at first. This is markedly different because that I can see as a potential Big Sur issue that doesn't seem to be too repetitive so far (am I just going to get forced onto worse and worse operating systems as the years go by? Did I like Catalina because it was preinstalled on the computer when I bought it new, or was it because it actually was more stable?)

 

In this case, on SoftRaid 6.05 on Big Sur, I have a situation where the disk will connect to the computer. I can see the drive present in SoftRaid under "Disks" and also in Disk Utility. However, the volume doesn't mount and I'm pretty sure in this case it's because I'm on a rolled back version of 6.05. What happens is the volume appears connected to the disk but, it comes up as "unmounted" WITH "safeguard disabled" shown on the screen (which is of course bogus, I never disabled safeguard). Disk Utility confirms the disk is connected but the volume is not mounted. 

 

Guess I'll uninstall again, go back to 6.3, and see what we can figure out about the rest. 

 

It's perfectly okay with me if this is shown to be a system issue instead of a bug, but after 27 hours to resolve issues with Adobe, if there's something else going on where my library or cache files or something else is causing all of this and it's confirmed to not be a Soft Raid bug, maybe a clean install is in order. I just want to know it's worth the energy (and for me, still a bit of stress, because my confidence is still variable) to do that. Here's a pertinent question...are there any hidden folders I can trash to do a full and complete manual uninstall, or is the Uninstall function really uninstalling everything for sure (speaking specifically of SoftRaid and only SR)? I may also try setting up a new User account and make yet another update but it's probably simpler to just get back on 6.3 and sort the rest out as we go

ReplyQuote
Topic starter Posted : 20/08/2022 5:20 pm
(@guitarflex)
Eminent Member

Wish I didn't have to keep adding to this novel with a War & Peace length thread so please forgive me if any of this has not been imperative information. Just created a new user account. Deactivated before I logged out of the main administrator account. Anyhow....

 

No changes on the test account side. I don't know exactly how this works but I had to put in my admin account user name and password anyhow, even on the test user side (I only tried this at all since it helped sort out the issue with Adobe yesterday preceded by 2 hours with support). Everything was the same to the letter. "Safeguard Disabled" which I never disabled, and the drive labeled "unmounted" and unable to mount, although the disk is shown as connected.

 

Right now I'm just going back to version 6.3 - along with the rest, hopefully then it doesn't keep prompting me for my password to reinstall the driver every time with Secure Boot turned off. The original error message that started this thread, we'll sort out after you're able to get back to me with ideas/advice/direction. I don't need that error notice gone in order to use it the software happily but it would help to confirm this is a bug and not anything on my end. 

Thanks as always,

 

Sean 

ReplyQuote
Topic starter Posted : 20/08/2022 5:40 pm
(@guitarflex)
Eminent Member

Final (I think) update of the day. Uninstalled experiment with 6.05 and got current 6.3 re-installed. Pretty sure the prompt for my password and reinstallation of the driver every time was on account of not having granted permission in Security upon installation, but didn't address that until reading the 6.3 documentation .pdf after installation of 6.3 again. Anyhow, with Startup Security disabled and permission granted, the application now opens like normal, as expected with no snags. The Elite Pro issue that was present in the rolled back version didn't appear upon reinstallation of 6.3, and the disk connected with volume mounted. That said (and this cannot be a S.R. issue). I'm still questioning Big Sur with what it's done to me so far without even getting going yet and the RocketYard comments on external drives. If it had not happened with the Elite Pro connected to the TB3 dock I'd probably start being concerned about the ThunderBay. So 2-3 times now in the past 4-5 minutes here's the exact rundown. ElitePro connected to front of ThunderBay over USB. If everything is on upon a computer restart that all appears to be fine and well so far, but if I have unmounted the Elite Pro and it's powered off but still connected, when I turn the drive back on, the Mac itself is not connecting to the drive. Can't be a SR issue since the disk doesn't show in Disk Utility either. If I disconnect and reconnect the cable, that seems to trigger things to become recognized and then the drive shows and the volume mounts. Just checked both USB ports on the front of the ThunderBay and confirmed, it's not one or the other. Connected up but powered off and then switched on, the Mac is not seeing the disk at all. Then switched to TB3 Pro Dock. Strange to say but, thankfully, the drive doesn't connect either when connected up but switched from off to on. Is this Big Sur? It's clearly not SoftRaid and, thankfully, I've clearly ruled out the ThunderBay as a source of concern, because it's repeatable and across different devices. However, from this state of the disk not connecting, if I unplug the cable to and reconnect, the disk appears and the volume mounts (just did that this second with the cable into the dock...perfection now). Then, I (deliberately) unmounted the volume, pulled the cable (with the drive enclosure still powered on), and re-connected back up to the ThunderBay. Disk recognized and volume mounted. 

 

I'm afraid I may have thrown too many questions, statements, stories, and experiences out there another 4 hour troubleshooting session today. I guess for now the takeaway and my main question is if that error notice that began this whole thread is just a 6.3 bug. 

 

Any ideas on the disk connection issues would also be useful. Maybe it's all been rectified in Monterey but I'm not ready yet. Just getting to Big Sur has rolled into day 10 but I've still got my sense of humor and the rest can be dealt with 

ReplyQuote
Topic starter Posted : 20/08/2022 6:21 pm
(@guitarflex)
Eminent Member

I'm not reneging on the "last post of the day" statement above because now it's 1 A.M. so it's a new day! How's this for another piece of the puzzle. Just now was getting ready to call it a day/night, and after unmounting the Elite Pro connected to the ThunderBay, I flipped the power switch to the Elite Pro off. The volume and drive exited the Soft Raid window but.....there was no error message. Almost thought for a second that maybe things were all of a sudden solved. Powered the drive back up, seated the cable in again, the volume mounted, then I dismounted again and pulled the cable without powering the enclosure down. No error message. Now my curiosity was piqued so I connected it up to the TB3 Dock instead, repeated, and no error. But.....

 

When I unmounted the SanDisk SSD over USB-C connection, the error flashed on the screen. And from experience yesterday (which I don't want to repeat just because I'm paranoid), when I had unmounted all ThunderBay drives and disconnected the TB3 cable, the error certainly flashed on the screen. So....

 

This seems to only be triggered by USB-C and Thunderbolt connected drives.

 

Strange days 

ReplyQuote
Topic starter Posted : 21/08/2022 1:11 am
(@softraid-support)
Member Admin

@guitarflex 

The internal part of the SoftRAID application quit does not affect your volume. It is unmounted. I have seen that bug occasionally, but it is not fixed at this time

ReplyQuote
Posted : 21/08/2022 9:44 am
(@softraid-support)
Member Admin

@guitarflex 

Dock Ejector is supposed to eject all drives, so you can disconnect your devices. If it is leaving any mounted, it is a bug. (specifically if connected through an OWC dock, which is what Dock Ejector is for)

Once you have 6.3 reinstalled, it should not put up the driver install dialog box, unless it is a known bug in macOS that did not update the extensions cache.

ReplyQuote
Posted : 21/08/2022 9:48 am
Page 1 / 2
Share:
close
open