Notifications
Clear all
Functionality Issues
23
Posts
4
Users
0
Reactions
1,882
Views
Topic starter
Hi everyone,
I am running Mac OS 12.2/ SoftRAID 6.2.1 on an intel 2019 MacBook Pro 16". I have two volumes across all disks of my RAID5 Thunderbay8, a HFS+ volume and a APFS TimeMachne volume.
When I go to unplug the thunderbay8 from my Mac after ejecting both volumes (either in Finder of SoftRaid GUI), SoftRAID behaves as if I never ejected my TimeMachine volume and I get x8 messages of "Disk for SoftRAID Volume Disappeared", concerning ONLY my TimeMachine volume, and x1 message that "SoftRAID has detected a problem".
To be clear, I am NOT having any issues with volumes ejecting while mounted and plugged into my Mac. I get these messages only after unmounting both volumes and unplugging my thunderbay8.
Please advise and thanks in advance. Error report attached.
Posted : 28/02/2022 1:48 pm
The sad part is we made a change in SoftRAID (labeling SoftRAID volumes as removable) just to avoid this issue and a Time Machine kernel panic.
Time Machine must be holding onto the volume still. It should let go when the volume is unmounted. You are running 6.2.1, which is correct.
If after you unmount both volumes, in terminal if you paste this in:
ls -als /volumes/
What do you see?
Posted : 28/02/2022 5:29 pm
Topic starter
Hi, I get the following, looks like you are correct:
Last login: Tue Feb 22 19:30:12 on ttys000
mikeh@Michaels-MBP ~ % ls -als /volumes/
total 0
0 drwxr-xr-x 4 root wheel 128 Feb 28 19:23 .
0 drwxr-xr-x 20 root wheel 640 Jan 21 23:42 ..
0 drwxr-xr-x 4 root wheel 128 Feb 21 07:33 .timemachine
0 lrwxr-xr-x 1 root wheel 1 Feb 21 07:33 Macintosh HD -> /
mikeh@Michaels-MBP ~ %
Posted : 28/02/2022 10:25 pm
Time Machine is still keeping part of the volume mounted. I don't know why. the volume is now marked "removable" so Time Machine should unmount it.
Is this an APFS volume, or HFS?
Posted : 28/02/2022 11:01 pm
Topic starter
This is a APFS, to be clear, I have two volumes on my thunderbay8, one volume is formatted as APFS (time machine) and the other is formatted as HFS+
Posted : 01/03/2022 11:37 am
I saw that and the APFS is the Time Machine volume.
I don't have an answer. I am sure you do not want to reset your Time Machine volume.
Posted : 01/03/2022 12:12 pm
Topic starter
I am still wanting to get my thunderbay8 setup properly how I want to use it (APFS & HFS+ volumes). I have not started to rely upon it yet.
I can easily scrap my Time Machine volume and start over. Do you have a suggestion as I am willing to reset my TimeMachine volume?
Thanks,
Posted : 01/03/2022 12:15 pm
If you just "delete" the time Machine volume (you may get an error that it is busy, if so, use the terminal command to force unmount it), then create it again, as APFS.
Lets see if this issue gets resolved.
sudo diskutil unmount force disk#
Where you replace disk# with disk6 or whatever the disk identifier is shown in the SoftRAID expanded volumes tile.
You can also try this command independently, then remove the cable and see if this avoids the error message. It will confirm this is an unmounting issue.
Posted : 01/03/2022 12:45 pm
Topic starter
*Update*
I was only able to erase my Time Machine volume in Apple Disk Utility (when I tried to do this in SoftRaid GUI I got the error you mentioned above). After erasing and creating a new time machine volume. I was no longer able to eject my time machine by doing a force eject. Finder would never seem to eject it. BUT, after a force eject I never got the original SoftRAID errors I mentioned at the start of this thread.
HOWEVER, I tried a log out and log back in to attempt to gracefully eject my Time Machine volume, and it worked! ...... BUT when I when to unplug the thunderbolt cable from the Mac going to my Thunderbay8 I got the same error messages from SoftRAID all over again!
I'm beginning to think this is a Mac OS Monterey issue?...
I'm thinking its not possible to run a Time Machine volume on my SoftRAID thunder bay any more... I wish I could. I don't have this issue with my non-soft raid usb hard drive in time machine.
Any more advise?
Thanks,
-Michael Hibbard
Posted : 04/03/2022 1:13 pm
Topic starter
If you just "delete" the time Machine volume (you may get an error that it is busy, if so, use the terminal command to force unmount it), then create it again, as APFS.
Lets see if this issue gets resolved.
sudo diskutil unmount force disk#
Where you replace disk# with disk6 or whatever the disk identifier is shown in the SoftRAID expanded volumes tile.
You can also try this command independently, then remove the cable and see if this avoids the error message. It will confirm this is an unmounting issue.
In response to what you suggested:
When I go to the SoftRAID GUI, I see that disk identifier for my HFS volume is 56, and the identifier for my APFS Time Machine volume is 57. So, I am able to force unmount my HFS volume, but then diskutil suggests that I use command unmountDisk instead, and terminal says my Time Machine volume was successfully ejected, but I still see it mounted within Finder.
mikeh@Michaels-MBP ~ % sudo diskutil unmount force disk56 Password: Volume Hibbard Thunderbay on disk56 force-unmounted mikeh@Michaels-MBP ~ % sudo diskutil unmount force disk57 disk57 was already unmounted or it has a partitioning scheme so use "diskutil unmountDisk" instead mikeh@Michaels-MBP ~ % sudo diskutil unmountDisk force disk57 Forced unmount of all volumes on disk57 was successful mikeh@Michaels-MBP ~ %
There does appear to be an unmounting issue with TimeMachine Volumes.
Posted : 04/03/2022 1:31 pm
Good idea, this double mount point issue may be something we can address in the SoftRAID UI. I will bring it up as an idea.
Posted : 04/03/2022 1:42 pm
When you force unmount both mountpoints, does that eliminate the error when disconnecting the volume?
Posted : 04/03/2022 1:43 pm
Topic starter
@softraid-support No, even though terminal returns:
Forced unmount of all volumes on disk57 was successful
Disk57 (my Time Machine APFS volume) is still clearly mounted within Finder!
I am yet to be able to find a terminal command that will force eject my APFS Time Machine volume.
Posted : 04/03/2022 1:57 pm
Restart your computer. Run this command in terminal:
diskutil list
Look at the list. How many instances of your Time Machine volume are listed?
If twice again, what if you use the force unmount on both numbers?
this is not permanent, just a check to see if this works.
Posted : 06/03/2022 1:27 am
Topic starter
When I try as you suggested after a fresh reboot, diskutil returns:
mikeh@Michaels-MBP ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 2.0 TB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 21.3 GB disk1s1
2: APFS Snapshot com.apple.os.update-... 21.3 GB disk1s1s1
3: APFS Volume Macintosh HD - Data 808.7 GB disk1s2
4: APFS Volume Preboot 338.4 MB disk1s3
5: APFS Volume Recovery 1.1 GB disk1s4
6: APFS Volume VM 20.5 KB disk1s5
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk2
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk2s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk2s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk2s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk2s4
(free space) 134.2 MB -
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk3
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk3s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk3s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk3s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk3s4
(free space) 134.2 MB -
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk4
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk4s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk4s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk4s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk4s4
(free space) 134.2 MB -
/dev/disk5 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk5
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk5s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk5s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk5s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk5s4
(free space) 134.2 MB -
/dev/disk6 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk6
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk6s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk6s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk6s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk6s4
(free space) 134.2 MB -
/dev/disk7 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk7
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk7s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk7s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk7s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk7s4
(free space) 134.2 MB -
/dev/disk8 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk8
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk8s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk8s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk8s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk8s4
(free space) 134.2 MB -
/dev/disk9 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk9
1: B6FA30DA-92D2-4A9A-96F1-871EC6486200 2.3 MB disk9s1
2: 2E313465-19B9-463F-8126-8A7993773801 7.3 MB disk9s2
3: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 2.9 TB disk9s3
4: FA709C7E-65B1-4593-BFD5-E71D61DE9B02 1.1 TB disk9s4
(free space) 134.2 MB -
/dev/disk10 (virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Hibbard Thunderbay +20.0 TB disk10
/dev/disk11 (virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_APFS +8.0 TB disk11
/dev/disk12 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +8.0 TB disk12
Physical Store disk11
1: APFS Volume TimeMachine 1.1 TB disk12s1
mikeh@Michaels-MBP ~ %
I don't know too much about this, but I think there are three disks associated with my Time Machine:
- disk11
- disk12
- disk12s1
After force ejecting these three disks in terminal with command "sudo diskutil unmountDisk force disk#" for all three of the disks mentioned in bullet points above (plus my 'Hibbard Thunderbay' HFS volume), I still get the same error messages from SoftRAID as I detailed in my first post of this thread.
Are you able to provide any insight?
Thanks for the continued support.
-Mike H
Posted : 10/03/2022 2:21 pm
Page 1 / 2
Next
