[Sticky] Monterey Other issues

@sithu 

I believe Time Machine is hanging on to the volume, even if you remove it. One idea is if you remove all disks from the computer except the disks for this volume, then "uninstall SoftRAID" from utlitiies menu. Restart, use Disk Utility to erase the disk(s). then you can reinstall the SoftRAID driver. (remember to "Allow" OWC as an identified developer.)

@softraid-support 

Just to be sure I understand, so that I don't accidentally wipe all my data:   I have 8 drives, and 4 volumes. Every one of the 4 volumes is spread across the 8 drives in RAID5. If I uninstall SoftRaid, reboot, then use Apple's Disk Utility to erase only the time machine volume, will it mess up any of the other 3 volumes? Thanks!

@sithu 

This is more difficult then, I thought you had a pair of disks with a Time Machine volume.

You can do it this way:

remove all the disks and restart.

Insert just two disks.

Delete the one volume.

Pull them, and delete the volume on the next two.

repeat until all 8 are finished.

This will remove just the one volume, by not allowing enough disks present to mount the volume.

@softraid-support 

I don't have a backup of the files on this RAID so didn't feel comfortable with removing the disks and deleting the volume piece by piece like you suggested, just in case something bad happened.

But I was able to delete the time machine volume. Here's what I did:

Found out that even though I stopped using the disk in Time Machine and removed it, it kept holding onto the volume like you suggested, as seen in the logs. Spotlight MDS processes and time machine.

sudo lsof /Volumes/TimeMachine/

printf '\e[3J' && log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 6h | grep -F 'eMac' | grep -Fv 'etat' | awk -F']' '{print substr($0,1,19), $NF}'

Opened my time machine drive in Finder and deleted all the backups, emptied trash. Later I found out in terminal this doesn't really remove the files, but moves them into a hidden folder.

went into system preferences, enabled Full Disk Access for Terminal

cd /Volumes/TimeMachine  (TimeMachine is the name of my timemachine volume)

ls -lae  (this shows all hidden folders on the time machine drive)

sudo rm -Rf .Spotlight-V100  (use with extreme caution)
repeated for each hidden file+folder except .Trashes

tmutil destinationinfo
(I first added back the drive to time machine settings and disabled automatic backup)

tmutil removedestination destination_id  (this is the long ID code from desitnationinfo)

Unmounted

Erased the disk in Softraid and Remounted. Time Machine now pops up and asks if I want to use the new disk as a backup destination. Clicked now.

Unmounted it, and Delete Volume which now worked.

It seems it's a really bad idea to have an APFS Time Machine volume in SoftRaid at this time, as it never really unmounts. 

Now after ejecting the remaining volumes in Finder, when I unplug it no longer gives me the pop up saying a RAID volume was suddenly removed. I'll report back to see if this fixes the kernel panics I've been having.

@sithu 

Good work figuring out why Time Machine is hanging onto the volume. I will bring this up in engineering to see if A) this is an Apple bug, and B) if we can create a workaround.

Let me know on the panics.

@softraid-support 

No more Kernel panics since fixing this!

Cheers

Greetings from Oz.

Just upgrade an iMac 2017 27" with a new internal SSD and successfully migrated all data from a Time Machine back up.

After the migration all my SoftRaid RAID 5 & RAID 1 enclosures mount on the desktop without any icons, just the volume name.

Did a search on the SoftRaid forums and the last report of this issue was 2 years ago.

Is there a PROPER fix? Not simply copying and pasting icons to the Get Info dialog box?

@apple-answers-au 

I believe this is an Acronis bug. Do you have Acronis installed? if so, I think if you give it "Full Disk Access", it would fix this issue.

There is also a less common, macOS issue that causes this. generally it fixes itself with a macOS update.

Ever since updating to Monterey 12.2, my enclosure keeps spinning the disks down and up non-stop when the machine goes to sleep. All is lates (driver is 6.2, auto updates are on). No effect from tweaking power settings (put disks to sleep).

I'm afraid this spinning the disks up and down non-stop is going to kill my drives inside. Is there a way to check/fix this behavior? My disks used to go to sleep and didn't wake up constantly. I need my drives connected for time machine daily backups.

@vic-tor 

This seems like a Monterey issue, I do not know a workaround yet. It does not kill the drives, but is extremely annoying.

Since installing the latest driver and app I've started getting this after I've unmounted all drives. I have a 5 disc RAID 5, and two single drive one being Time Machine. The other two eject fine but when I turn the OWC 8B off this pops up. I currently have TM set to off so it shouldn't be even in use, plus it does eject fine.

@cell-666 

What is the reply to lsof on your volume(s)?

sudo lsof /Volumes/myVolumename

(If there is a space in your volume name, you must enter it like this Macintosh\ HD)

@softraid-support Forgot the attachment in the previous post, doesn't accept png :(  

It’s the default Time Machine named drive.

@cell-666 

I am not sure when you see this dialog box.

Is this after you first unmount the volume, wait a while, then disconnect?

Or are you getting this randomly when using the computer?
(indicates the enclosure is losing contact with the system momentarily)

Posted by: @softraid-support

@cell-666 

I am not sure when you see this dialog box.

 

Is this after you first unmount the volume, wait a while, then disconnect?

Or are you getting this randomly when using the computer?
(indicates the enclosure is losing contact with the system momentarily)

I get this at the end of the day when shutting down the OWC. I normally unmount in the same order, this TM drive, a single drive, then the 6 drive RAID. I then flick the power off to the OWC box at the rear. This TM drive is the only one which throws this popup warning.