macOS 10.15 Catalina on Unsupported Macs

[wylhkg]

my photo app cannot be open

Process: Photos [1256]
Path: /System/Applications/Photos.app/Contents/MacOS/Photos
Identifier: com.apple.Photos
Version: 5.0 (101.11.103)
Build Info: Photos_Apps-101011103000000~1
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Photos [1256]
User ID: 501

Date/Time: 2019-07-27 08:54:31.823 +0800
OS Version: Mac OS X 10.15 (19A512f)
Report Version: 12
Anonymous UUID: 6FBF43BB-35E0-0EB3-2DA7-59A336152C62


Time Awake Since Boot: 40000 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [1256]

Application Specific Information:
dyld3 mode
Crashing on exception: Invalid parameter not satisfying: device != nil

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff3ae65cd3 __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff7101ab43 objc_exception_throw + 48
2 CoreFoundation 0x00007fff3ae816cc +[NSException raise:format:arguments:] + 88
3 Foundation 0x00007fff3d5c97c1 -[NSAssertionHandler handleFailureInMethodbject:file:lineNumber:description:] + 191
4 PhotosUICore 0x00007fff642b3396 -[PXGMetalTextureConverter initWithDevice:] + 437
5 PhotosUICore 0x00007fff6409bccb -[PXGMetalRenderer init] + 1012
6 PhotosUICore 0x00007fff642cef0f -[PXGEngine init] + 109
7 PhotosUICore 0x00007fff6436f1de -[PXGView initWithFrame:] + 695
8 AppKit 0x00007fff380e6982 -[NSView init] + 44
9 PhotosUICore 0x00007fff640b3db8 -[PXCuratedLibraryViewProvider initWithPhotoLibrary:extendedTraitCollection:] + 829
10 Photos 0x0000000102e19adf -[IPXCuratedLibraryViewController initWithPhotoLibrary:] + 174
11 Photos 0x0000000102ca5d4d -[IPXWorkspaceController _rootViewControllerProvidingViewControllersForNavigationDestination:] + 1513
12 UXKit 0x00007fff6c450a3e -[UXSourceController _navigateToDestination:animated:completion:] + 75
13 UXKit 0x00007fff6c454d6a __69-[UXSourceController _setRootViewControllers:destination:completion:]_block_invoke.465 + 622
14 libdispatch.dylib 0x00007fff722f1653 _dispatch_call_block_and_release + 12
15 libdispatch.dylib 0x00007fff722f25de _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff722fdcd3 _dispatch_main_queue_callback_4CF + 1105
17 CoreFoundation 0x00007fff3adb4e23 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
18 CoreFoundation 0x00007fff3adb455b __CFRunLoopRun + 2384
19 CoreFoundation 0x00007fff3adb3996 CFRunLoopRunSpecific + 503
20 HIToolbox 0x00007fff3996908d RunCurrentEventLoopInMode + 292
21 HIToolbox 0x00007fff39968dcd ReceiveNextEventCommon + 600
22 HIToolbox 0x00007fff39968b57 _BlockUntilNextEventMatchingListInModeWithFilter + 64
23 AppKit 0x00007fff380236b0 _DPSNextEvent + 990
24 AppKit 0x00007fff38022424 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
25 AppKit 0x00007fff3801cb82 -[NSApplication run] + 658
26 AppKit 0x00007fff3800ea4e NSApplicationMain + 777
27 libdyld.dylib 0x00007fff72342c35 start + 1
28 ??? 0x0000000000000001 0x0 + 1

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.AppKit 0x00007fff383d59e3 -[NSApplication _crashOnException:] + 106
1 com.apple.AppKit 0x00007fff383d58c9 -[NSApplication reportException:] + 908
2 com.apple.AppKit 0x00007fff3848befa uncaughtErrorProc + 145
3 com.apple.CoreFoundation 0x00007fff3aee89cc __handleUncaughtException + 726
4 libobjc.A.dylib 0x00007fff7101c9f6 _objc_terminate() + 90
5 libc++abi.dylib 0x00007fff6f541da7 std::__terminate(void (*)()) + 8
6 libc++abi.dylib 0x00007fff6f541d59 std::terminate() + 41
7 libdispatch.dylib 0x00007fff722f25f2 _dispatch_client_callout + 28
8 libdispatch.dylib 0x00007fff722fdcd3 _dispatch_main_queue_callback_4CF + 1105
9 com.apple.CoreFoundation 0x00007fff3adb4e23 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
10 com.apple.CoreFoundation 0x00007fff3adb455b __CFRunLoopRun + 2384
11 com.apple.CoreFoundation 0x00007fff3adb3996 CFRunLoopRunSpecific + 503
12 com.apple.HIToolbox 0x00007fff3996908d RunCurrentEventLoopInMode + 292
13 com.apple.HIToolbox 0x00007fff39968dcd ReceiveNextEventCommon + 600
14 com.apple.HIToolbox 0x00007fff39968b57 _BlockUntilNextEventMatchingListInModeWithFilter + 64
15 com.apple.AppKit 0x00007fff380236b0 _DPSNextEvent + 990
16 com.apple.AppKit 0x00007fff38022424 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
17 com.apple.AppKit 0x00007fff3801cb82 -[NSApplication run] + 658
18 com.apple.AppKit 0x00007fff3800ea4e NSApplicationMain + 777
19 libdyld.dylib 0x00007fff72342c35 start + 1

Thread 1:
0 libsystem_pthread.dylib 0x00007fff7254f708 start_wqthread + 0

Thread 2:: Dispatch queue: com.apple.photos.preload-backgroundQueue
0 libsystem_kernel.dylib 0x00007fff7248dc46 __ulock_wait + 10
1 libdispatch.dylib 0x00007fff722f2da6 _dlock_wait + 44
2 libdispatch.dylib 0x00007fff722f2c35 _dispatch_thread_event_wait_slow + 36
3 libdispatch.dylib 0x00007fff722fe8cb __DISPATCH_WAIT_FOR_QUEUE__ + 287
4 libdispatch.dylib 0x00007fff722fe51d _dispatch_sync_f_slow + 171
5 com.apple.PhotosUICore 0x00007fff6422ad83 -[PXPreloadScheduler scheduleMainQueueTaskAndWait:] + 211
6 libdispatch.dylib 0x00007fff722f1653 _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff722f25de _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff722f7b9e _dispatch_lane_serial_drain + 597
9 libdispatch.dylib 0x00007fff722f8522 _dispatch_lane_invoke + 363
10 libdispatch.dylib 0x00007fff72301b91 _dispatch_workloop_worker_thread + 582
11 libsystem_pthread.dylib 0x00007fff725556d3 _pthread_wqthread.cold.1 + 125
12 libsystem_pthread.dylib 0x00007fff7254f856 _pthread_wqthread + 203
13 libsystem_pthread.dylib 0x00007fff7254f717 start_wqthread + 15

Thread 3:
0 libsystem_pthread.dylib 0x00007fff7254f708 start_wqthread + 0

Thread 4:
0 libsystem_pthread.dylib 0x00007fff7254f708 start_wqthread + 0

Thread 5:: Dispatch queue: NSOperationQueue 0x7faa1a6439d0 (QOS: USER_INITIATED)
0 libsystem_kernel.dylib 0x00007fff7248dc46 __ulock_wait + 10
1 libdispatch.dylib 0x00007fff722f2da6 _dlock_wait + 44
2 libdispatch.dylib 0x00007fff722f3031 _dispatch_group_wait_slow + 43
3 libdispatch.dylib 0x00007fff722f5119 dispatch_block_wait + 212
4 com.apple.swe.UXKit 0x00007fff6c4549b2 __68-[UXSourceController setRootViewControllers:destination:completion:]_block_invoke_2 + 220
5 com.apple.Foundation 0x00007fff3d4fa0bd __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
6 com.apple.Foundation 0x00007fff3d4f9fb5 -[NSBlockOperation main] + 98
7 com.apple.Foundation 0x00007fff3d66a3c0 __NSOPERATION_IS_INVOKING_MAIN__ + 17
8 com.apple.Foundation 0x00007fff3d4d09b4 -[NSOperation start] + 731
9 com.apple.Foundation 0x00007fff3d66a7ce __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 17
10 com.apple.Foundation 0x00007fff3d4f9d88 __NSOQSchedule_f + 182
11 libdispatch.dylib 0x00007fff722fe243 _dispatch_block_async_invoke2 + 83
12 libdispatch.dylib 0x00007fff722f25de _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff722f4790 _dispatch_continuation_pop + 414
14 libdispatch.dylib 0x00007fff722f3e8e _dispatch_async_redirect_invoke + 703
15 libdispatch.dylib 0x00007fff723008e5 _dispatch_root_queue_drain + 326
16 libdispatch.dylib 0x00007fff72301025 _dispatch_worker_thread2 + 92
17 libsystem_pthread.dylib 0x00007fff72555699 _pthread_wqthread.cold.1 + 67
18 libsystem_pthread.dylib 0x00007fff7254f856 _pthread_wqthread + 203
19 libsystem_pthread.dylib 0x00007fff7254f717 start_wqthread + 15

 

[avl-code-r]

There are a couple things you can do. My best recommendation would be to create a second, APFS partition on your SSD, and install Catalina on that (as it is a beta OS after all). To perform the installation, you can use Catalina Patcher to either create a bootable USB installer drive to use for the installation, or install directly without using a USB drive at all. Just select the second partition when performing the installation. If you'd rather convert your main partition to APFS and do an upgrade, make a bootable USB installer with Catalina Patcher, boot from that, open Disk Utility, select your main partition, and select "Unmount". Then in the Edit menu of Disk Utility in the Menu Bar, select "Convert to APFS". Be aware that this is a one way operation, and cannot be undone. Once finished, close Disk Utility, and proceed with the Catalina installation on that volume. All post-install patches are handled for you automatically, so just go through the installer and you're done.

Slightly different situation, but thought I would share what worked and didn't work for me.
MacBookPro8,1
16GB Ram
1TB SSD formate APFS with several 'containers'
Mojave installed

What did not work:
- Using Catalina Patcher did not work installing onto my last empty container.
- Creating another partition and using Catalina Patcher to install directly on that partition.
? Both of those resulted in booting to the Circle with a line thru it .

What did work:
- Using Catalina Patcher to create an installer on 16GB SDXC card with a GUID portion map. It previously had my Mojave installer on it. I then booted onto that card, selected reinstall and selected the 'new partition' I had created before.

Hope that helps someone.
Thanks dosdude1 and everyone else


Also, How do I delete the installer disk that shows up when I hold the option key down? Is that in a /tmp folder somewhere? Pretty sure it showed up when I tried to install directly from the Catalina Patcher.

 

[dosdude1]

Slightly different situation, but thought I would share what worked and didn't work for me.
MacBookPro8,1
16GB Ram
1TB SSD formate APFS with several 'containers'
Mojave installed

What did not work:
- Using Catalina Patcher did not work installing onto my last empty container.
- Creating another partition and using Catalina Patcher to install directly on that partition.
? Both of those resulted in booting to the Circle with a line thru it .

What did work:
- Using Catalina Patcher to create an installer on 16GB SDXC card with a GUID portion map. It previously had my Mojave installer on it. I then booted onto that card, selected reinstall and selected the 'new partition' I had created before.

Hope that helps someone.
Thanks dosdude1 and everyone else


Also, How do I delete the installer disk that shows up when I hold the option key down? Is that in a /tmp folder somewhere? Pretty sure it showed up when I tried to install directly from the Catalina Patcher.

Hmm, ok, thanks for the feedback. What version of macOS were you running Catalina Patcher under? I tested doing so under Mojave, but other changes may be needed for it to work properly from older OS versions. You were using Catalina Patcher version 1.0.2?

To remove the installer partition, just look for a volume containing a directory named "macOS Install Data", and then erase that volume using Disk Utility.

 

[avl-code-r]

Hmm, ok, thanks for the feedback. What version of macOS were you running Catalina Patcher under? I tested doing so under Mojave, but other changes may be needed for it to work properly from older OS versions. You were using Catalina Patcher version 1.0.2?

To remove the installer partition, just look for a volume containing a directory named "macOS Install Data", and then erase that volume using Disk Utility.

I ran it from my internal SSD formatted APFS running
macOS Mojave 10.14.5 (18F203)
macOS Catalina Patcher version: 1.0.2

Let me know if you need anything else.

Not sure what the issues are, could be user error, but figured I'd through the feedback out there for you and anyone else trying. If it doesn't work one way, try another.

 

[anthonysmith93]

Is photos app ever gonna work? I wonder if this is a beta issue, or if it's an unsupported mac issue?

 

[0134168]

I tried this first of course. Was not working here. I had do it via terminal, so that download from anywhere is enabled. This option was abandoned in high sierra times, iirc.

You are wrong.

 

[TimothyR734]

Is photos app ever gonna work? I wonder if this is a beta issue, or if it's an unsupported mac issue?

The Photos app as well as Maps and the new drift screensaver rely on GPU's the support Metal this may or may not be resolved but you can access your photo's go to the pictures folder right click on Photo's Library-Show Package contents your picture are in the Originals folder you can view them with the Preview app this is the only work around I know.

 

[Vyzantion]

@0403979 I have performed a boot with F2 on Clover, to collect information. In here the content of the EFI, with the test, in case it is relevant.

 

[avl-code-r]

The Photos app as well as Maps and the new drift screensaver rely on GPU's the support Metal this may or may not be resolved but you can access your photo's go to the pictures folder right click on Photo's Library-Show Package contents your picture are in the Originals folder you can view them with the Preview app this is the only work around I know.

I agree.

I think the main driving force is Apple streamlining the codebase so apps and OSs can run on different hardware and OSs easily. So the focus is the future pipeline of hardware and the codebase that can utilize that hardware, and the agility to switch it all out seamlessly. Going back and looking at previous hardware and codebase transitions, I think they have learned from their mistakes and are planning ahead. I expect the next transitions to be seamless and Apple to have more options than ever.

That leaves the old hardware in need of an updated codebase. Sometimes it's doable, other times it's just not going to be performant enough. The main reason is usually something that exists in the newer chips, like a codec for encoding / decoding video, that makes certain tasks/features undoable on old hardware.


Over all, I'll still take the latest OS I can run on hardware, just to keep all the feature set and nerfed features in sync, even if have to run the photos app on a different machine (though if it's my only machine, I may not do the upgrade).

The maps launched and ran on my machine. I switched it to lite mode so I could see things better, zoomed in some, noticed most of the 'labels' were missing, but the roads were there. Then it crashed. I haven't tried Photos yet.

Now, If anyone could tell me why features keep getting nerfed over time... I mean why remove features? And then there's the 'only works with iCloud' features that shouldn't need iCloud... I'd be happier keeping more computers on different OSs if all of that didn't change as much.

 

[joelw135]

It sounds like post-install patches were not applied correctly for some reason. Which method did you use for installation?

I used the patcher from you.

 

[avz]

Better security and app supported, even for those that do not require metal. Besides, if a macOS version is succeeded by another macOS version that has the same system requirements, it is pretty clear that the first needs to dumped and replaced with the second, since the first shall not receive any real security and performance updates, since, according to the Apple logic, the next macOS is the security and stability update of the old one. Only a macOS version that is the end of the line for some older hardware can get some security and stability updates, but they are pretty unreliable, I shall say.

Would you say that the older hardware is actually more secure? For instance the lack of multi-threading makes the system more secure? Do you have any other tips for improved security?

 

[echophilon]

You are wrong.

I'm okay with your judgement. At least it works using the cl.

 

[DuncanGarp]

* post deleted

 

[alphascorp]

Hi everybody,
MP5.1 updated to 10.15 PB3 with @dosdude1 v1.0.2 Patcher
All seems to work properly.

 

[Thomas tech enthusiast]

Hey @dosdude1 I still can not download Catalina even with your latest patcher tool. It still says error there was a problem downloading macOS please check your internet connection and try again later. Is there a way I can download macOS Catalina installer on my windows Pc then copy the files to my Mac? If you or anyone can think of any ideas that can help me solve my problem that would be greatly appreciated!

@dosdude1 I found in my download folder macOS Catalina.zip or something like that can’t remember the name exactly but, I moved it to trash then tried to use your patcher tool but, I still can’t download Catalina please help! I was able to download and install macOS Mojave three or four months ago with your Mojave patcher and the mac is running Mojave now so do not know why there is a problem with Catalina. The Mac is an iMac 12,2. Please help!

@dosdude1 I still can’t download macOS Catalina with your patcher please help!!

 

[LuisN]

@dosdude1 I still can’t download macOS Catalina with your patcher please help!!

It's clearly a problem with your internet connection. Is your internet traffic capped in anyway? Did you try changing dns servers? Maybe you have a friend who let you download Catalina in his house?

 

[0134168]

@dosdude1 I still can’t download macOS Catalina with your patcher please help!!

It´s a problem from your network. Do you want me to send you a link to my Wetransfer?

 

[Thomas tech enthusiast]

It´s a problem from your network. Do you want me to send you a link to my Wetransfer?

@******* Sure that would be great thanks so much! If you can send me the MacOS Catalina files then I can just use @dosdude1 Catalina patcher to install it!

 

[0134168]

@******* Sure that would be great thanks so much! If you can send me the MacOS Catalina files then I can just use @dosdude1 Catalina patcher to install it!

My pleasure. Give a few minutes.

 

[stevecc]

This is so cool!..Os Catalina on a 2008 24" iMac.Sure..a few bugs..But overall..Because its in developer mode..The more I use it.example..full screen to small screen..Bamm..No twich..Spell check..Graphics etc..Its better than Mojave..Looking forward to the progress in patcher updater..Im struggling a bit money wise lately..But I figure I owe dos...50$...serria..high serria.Mojave etc...Tks Man all pay that!

 

[anthonysmith93]

The Photos app as well as Maps and the new drift screensaver rely on GPU's the support Metal this may or may not be resolved but you can access your photo's go to the pictures folder right click on Photo's Library-Show Package contents your picture are in the Originals folder you can view them with the Preview app this is the only work around I know.

Dang, I may have to downgrade back to Mojave then. All apps worked flawlessly in Mojave, even tho I don't have metal capable hardware.

 

[Vyzantion]

Would you say that the older hardware is actually more secure? For instance the lack of multi-threading makes the system more secure? Do you have any other tips for improved security?

El Capitan, from a security stand-point, at the time of High Sierra, was preferable to Sierra, regardless of the age of the hardware. High Sierra was preferable to both, of course, not just because of the security. It is similar to LTS versions of Ubuntu Linux (one every two years, with intermediary versions every six mouths between them) or LTSC redstones of Windows 10 every two-tree years (with intermediary red stones between them on non-LTSC editions every six months) This is not officially, of course, from Apple but, if we look at the pattern, we see that this the case. If High Sierra comes free for all hardware that supported High Sierra, Sierra shall receive no real security updates, since High Sierra shall get them anyway. It is a form of pragmatism from Apple, to save some resources (financial or human) in software maintenance. If an edition of macOS is made to be the end of the line for some Macs, it is clear that they shall still receive some minimal security maintenance from Apple, like in the case of El Capitan.

 

[jhowarth]

El Capitan, from a security stand-point, at the time of High Sierra, was preferable to Sierra, regardless of the age of the hardware. High Sierra was preferable to both, of course, not just because of the security. It is similar to LTS versions of Ubuntu Linux (one every two years, with intermediary versions every six mouths between them) or LTSC redstones of Windows 10 every two-tree years (with intermediary red stones between them on non-LTSC editions every six months) This is not officially, of course, from Apple but, if we look at the pattern, we see that this the case. If High Sierra comes free for all hardware that supported High Sierra, Sierra shall receive no real security updates, since High Sierra shall get them anyway. It is a form of pragmatism from Apple, to save some resources (financial or human) in software maintenance. If an edition of macOS is made to be the end of the line for some Macs, it is clear that they shall still receive some minimal security maintenance from Apple, like in the case of El Capitan.

IMHO, the weak point for unsupported machines at the moment is that none of them are getting any microcode fixes from Intel to address the speculative related vulnerabilities. This is the exact reason the MacPro 5,1 got dropped at the last moment from the supported hardware list for Catalina (as Intel EOL'd those processors for future microcode updates). At least on the MacPro 3,1, I don't have to worry about the hyper threading attacks and, the further back you go, the less aggressive Intel was with their speculative optimizations.

 

[42towels]

I’m reposting this question here in the hopes the right set of eyes sees it (previously posted as a separate thread, but got no responses). Really hoping to get some more life out of my early-2009 Mac Pro. Hopefully doing a repost is kosher.

———-
I’m wondering if anybody can provide some insight into getting Catalina working on my early-2009 Mac Pro. My machine has two internal SSD drives. One has Mojave installed, and that works fine. I flashed the firmware to 5,1 some time ago. I have a metal compatible Radeon RX 580 video card.

I have tried multiple versions of dosdude’s catalina patcher, including the latest 1.0.2 version. The installation all seems to go fine, it installs onto the second SSD drive, and the post install patches seem to work fine. I’ve tried both with and without the APFS patch. The problem is that I cannot get it to boot.

If I boot into Mojave, and open the startup disk under settings, it shows the Catalina disk as an option. If I choose that and restart, it just boots back into Mojave.

If I remove the Radeon video card and put the original gt120 back in, and boot into the boot drive selection screen (hold opt key down during boot), the Catalina disk is not shown as an option.

If I boot into Mojave and use the bless command to check the disks, it shows the Mojave disk as bootable, but gives an error about the Catalina disk being an APFS partition. Seems like the Catalina install forces the disk to APFS even if I initially format it as Mac OS journaled.

Anybody have any ideas what is going wrong? Thanks!

Maybe this is helpful as well, from the machine's system report:

Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 GHz
Number of Processors: 2
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: MP51.007F.B03
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

 

[0134168]

I’m reposting this question here in the hopes the right set of eyes sees it (previously posted as a separate thread, but got no responses). Really hoping to get some more life out of my early-2009 Mac Pro. Hopefully doing a repost is kosher.

———-
I’m wondering if anybody can provide some insight into getting Catalina working on my early-2009 Mac Pro. My machine has two internal SSD drives. One has Mojave installed, and that works fine. I flashed the firmware to 5,1 some time ago. I have a metal compatible Radeon RX 580 video card.

I have tried multiple versions of dosdude’s catalina patcher, including the latest 1.0.2 version. The installation all seems to go fine, it installs onto the second SSD drive, and the post install patches seem to work fine. I’ve tried both with and without the APFS patch. The problem is that I cannot get it to boot.

If I boot into Mojave, and open the startup disk under settings, it shows the Catalina disk as an option. If I choose that and restart, it just boots back into Mojave.

If I remove the Radeon video card and put the original gt120 back in, and boot into the boot drive selection screen (hold opt key down during boot), the Catalina disk is not shown as an option.

If I boot into Mojave and use the bless command to check the disks, it shows the Mojave disk as bootable, but gives an error about the Catalina disk being an APFS partition. Seems like the Catalina install forces the disk to APFS even if I initially format it as Mac OS journaled.

Anybody have any ideas what is going wrong? Thanks!

Maybe this is helpful as well, from the machine's system report:

Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 GHz
Number of Processors: 2
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: MP51.007F.B03
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

Of course Catalaina force the APFS. As Mojave.