2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[jbarley]

I already tried the second Mac method but I cannot find the second boot.efi file because the usr folder is missing.

Missing or hidden?
Give this a try...
--------------------

• Open Finder.
• Press Command+Shift+G. A dialog box opens.
• Enter the path to the folder you want to access, for example /usr/.

 

[Machac]

No missing, it would be enough if someone could only upload all hidden folders.

 

[alphascorp]

Hi everybody,
I went galley like you all with the terminal to display the hidden files under mac but since I found this app I'm in the angel ...
I do not know where I found it but it worked very well under 10.7 and still works under 10.14 because I still use it ... and obviously under El captain with Mac Pro 2.1 ...

If you want to display the hidden files just click on the "show" button it restarts the Finder and displays the hidden files. conversely to go back and hide the hidden files restart the application and choose "hide" restarts the Finder and hides the hidden files.

 

[Machac]

I do not think it helps, have already tried to display hidden files via the terminal but the folders are simply missing.
Uploading a full backup or just the hidden files would help.

 

[alphascorp]

I do not think it helps, have already tried to display hidden files via the terminal but the folders are simply missing.
Uploading a full backup or just the hidden files would help.

I have never seen any hidden files missing ... without having manually erased them by mistake ... that said reinstalling El Capitan from a USB drive should solve the problem and restore the missing files (without deleting personal data or applications already installed), but for more precaution a backup of the personal data before re-installation is strongly advised ...
Even after a re-installation it can happen strange things, early last year after the first security update of January 2018 following a bootloop, I had to re-install El Capitan, yet the installation went through without errors but when I wanted to access my system disk, one of the internal disk was sytematically dismounted with an error message. The problem was resolved after a new re-installation...

 

[rthpjm]

I already tried the second Mac method but I cannot find the second boot.efi file because the usr folder is missing.

It’s hidden in the Finder.
You can go there in the Finder by hitting the key combination
SHIFT APPLE G
A go to the folder window appears
Type /usr then hit the Go button

Or from the Finder menus, select
Go > Go to folder...

Or use a Terminal

If it’s really missing then the install must have hit an error.

If your disk is still connected to the other Mac, remember to reference via /Volumes
cd /Volumes/your-El-Capitan-Volume/usr/standalone/i386

Even in the Finder Go to folder window use the /Volumes.... path

 

[LordeOurMother]

Yes. System Preferences, ICloud and then click the options button behind ‘iCloud Drive’

hey sorry, here is the preferences pane options. i'm unsure why it won't work.

 

[flygbuss]

hey sorry, here is the preferences pane options. i'm unsure why it won't work.

Does it change anything if you uncheck everything but let’s say weather and photos? The drive itself should still show up.

Sorry if you already mentioned it, but how exactly is it not working? Is it that you can’t see the drive itself I n the sidebar or is it not syncing with your other devices if you store something on it?

 

[pgriff]

I need a driver for m MP 2,1 running 10.11.6. I currently have an nVidia Quadro 4600 video card. I had a hard time dealing with nVidias web site and finally gave up. I'm hoping that somebody here can help.

 

[SuperMatt]

I am looking for a video card for my Mac Pro 1,2. I need boot screens and I don't have a lot of money to spend. Can anybody reccomend a card and a source for it?

Check out macvidcards.com as a good starting point.

Also, forum.netkas.org is a good source of info on flashing cards for Mac Pro use.

 

[jbarley]

I am looking for a video card for my Mac Pro 1,2. I need boot screens and I don't have a lot of money to spend. Can anybody reccomend a card and a source for it?

Something like this would fill the bill very nicely.
https://www.ebay.com/itm/Nvidia-Qua...=item283f2fcd4b:g:ypwAAOSwqSVZq4yn:rk:18:pf:0

 

[grimblegrumble]

Hi everyone.
for those who followed me above, I have news about my situation.
I redid the installation, with pikify method without usb,
passing first from firmware 1.1 to 2.1.
but unfortunately still does not see the external hard drives via USB (both from front doors and from rear doors) and I do not see the wifi card. leaving the USB problem, which I can fix, but if I changed wifi card I could solve according to you ? if so, what card do you recommend ?? thank you very much for your attention

 

[Macschrauber]

Unscrew the wifi card and pull it to double check.

Bcm94321mc is ok and the stock card. You should get it really cheap as people with newer Mac Pros get rid of it due incompatibility issues with Sierra and above. What shouldnt bother you with 1.1

 

[LordeOurMother]

Does it change anything if you uncheck everything but let’s say weather and photos? The drive itself should still show up.

Sorry if you already mentioned it, but how exactly is it not working? Is it that you can’t see the drive itself I n the sidebar or is it not syncing with your other devices if you store something on it?

The drive is visible but it does not sync with my other devices and I cannot view my files saved in the cloud on it.

 

[samrod]

rthpjm I've read through countless comments, but can't find the answer to my specific situation.

I'm running 10.7.5 off an internal HDD and followed the instructions on your video (

) exactly to install El Capitan on an SSD. But it either installed the recovery partition on the main volume or is only booting into recovery mode. Even when the 10.11.6 volume is selected as the startup disk or on option-boot, I end up in the recovery screen. I'd been running El Capitan just fine for a few years before I somehow screwed it up and must now reinstall without wiping my boot drive.

Please help!

Mac Pro 1,1 / 2.66 Ghz 8 Core / 28 GB RAM / 240 GB SSD / 320 GB HDD / 1.5 TB HDD / 3 TB HDD / 1GB ATI Radeon 5770 HD

 

[rthpjm]

rthpjm I've read through countless comments, but can't find the answer to my specific situation.

I'm running 10.7.5 off an internal HDD and followed the instructions on your video (

) exactly to install El Capitan on an SSD. But it either installed the recovery partition on the main volume or is only booting into recovery mode. Even when the 10.11.6 volume is selected as the startup disk or on option-boot, I end up in the recovery screen. I'd been running El Capitan just fine for a few years before I somehow screwed it up and must now reinstall without wiping my boot drive.

Please help!

Mac Pro 1,1 / 2.66 Ghz 8 Core / 28 GB RAM / 240 GB SSD / 320 GB HDD / 1.5 TB HDD / 3 TB HDD / 1GB ATI Radeon 5770 HD

Hi @samrod

Sorry to hear you’re having issues. You’re actually lucky, I’m not watching this thread much anymore. You could have been waiting a while, but as it happens... Onwards...

Are you using the script, or the app?
Can you paste the output from the following command please

diskutil list

What volume name did you give the SSD?
Have you formatted the SSD as HFS+ journaled with a GUID partition scheme? SSDs often come formatted for PCs with FAT/NTFS with an MBR partition scheme.

 

[samrod]

beyond those of us commenting on here

Hi @samrod

Sorry to hear you’re having issues. You’re actually lucky, I’m not watching this thread much anymore. You could have been waiting a while, but as it happens... Onwards...

Are you using the script, or the app?
Can you paste the output from the following command please

diskutil list

What volume name did you give the SSD?
Have you formatted the SSD as HFS+ journaled with a GUID partition scheme? SSDs often come formatted for PCs with FAT/NTFS with an MBR partition scheme.

The SSD is called "SuDDen" and already had El Capitan running before I screwed it up deleting /L/Caches, /S/L/Caches, ~/Caches, and some logs in /private/var/log/.

It's a journaled HFS+ volume.

I used the script.
My ~ is safely on Iwi.
10.7.5 is on the stock HDD Mahalo.
Manawa Mikini (Time Machine in Hawaiian) is my Time Machine volume.

Here's the diskutil output:

/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.5 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Iwi 1.5 TB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS SuDDen 239.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Mahalo 319.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_CoreStorage 3.0 TB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Manawa Mikini *3.0 TB disk4

I'd just like to say that you do a lot of good for many more people beyond those of us commenting on here. You're very much appreciated. Thank you!

 

[rthpjm]

beyond those of us commenting on here

The SSD is called "SuDDen" and already had El Capitan running before I screwed it up deleting /L/Caches, /S/L/Caches, ~/Caches, and some logs in /private/var/log/.

It's a journaled HFS+ volume.

I used the script.
My ~ is safely on Iwi.
10.7.5 is on the stock HDD Mahalo.
Manawa Mikini (Time Machine in Hawaiian) is my Time Machine volume.

Here's the diskutil output:

/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.5 TB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Iwi 1.5 TB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS SuDDen 239.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk2
1: EFI 209.7 MB disk2s1
2: Apple_HFS Mahalo 319.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_CoreStorage 3.0 TB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Manawa Mikini *3.0 TB disk4

I'd just like to say that you do a lot of good for many more people beyond those of us commenting on here. You're very much appreciated. Thank you!

Thanks for the kind words. I just like helping people, is all!

Okay so can you take a look at your SuDDen volume (Finder or Terminal) and let me know what folders you can see. From the Terminal..

ls -al /Volumes/SuDDen

Then paste the output of the following command

bless --info /Volumes/SuDDen

 

[samrod]

Samrods-Mac-Pro:samrod samrod$ ls -al /Volumes/SuDDen/
total 88
drwxr-xr-x@ 34 root wheel 1224 Mar 1 11:04 .
drwxrwxrwt@ 6 root admin 204 Feb 26 23:28 ..
-rw-rw-r--@ 1 root admin 15364 Mar 1 11:04 .DS_Store
d--x--x--x 8 root wheel 272 Feb 26 12:26 .DocumentRevisions-V100
-rw-r--r--@ 1 root wheel 2766 Feb 26 12:02 .OSInstallerMessages
drwx------ 5 root wheel 170 Jul 3 2014 .Spotlight-V100
-rw-rw-rw-@ 1 root 501 5192 Nov 1 2009 .SymAVx86QSFile
d-wx-wx-wt 5 root wheel 170 Feb 4 2018 .TemporaryItems
d-wx-wx-wt 4 root wheel 136 Feb 26 12:26 .Trashes
-rw-r--r--@ 1 samrod staff 0 Nov 25 2015 .com.apple.timemachine.donotpresent
srwxrwxrwx 1 root wheel 0 Nov 29 2014 .dbfseventsd
---------- 1 root admin 0 Feb 25 2016 .file
drwx------ 5 root wheel 170 Feb 26 12:44 .fseventsd
drwxr-xr-x@ 2 root wheel 68 Feb 26 11:46 .vol
drwxrwxr-x@ 114 root admin 3876 Feb 26 11:53 Applications
drwxr-xr-x@ 67 root wheel 2278 Feb 26 11:53 Library
drwxr-xr-x@ 2 root wheel 68 Feb 26 11:46 Network
drwxr-xr-x 9 root wheel 306 Feb 26 10:56 OS X Install Data
drwxr-xr-x@ 4 root wheel 136 Feb 26 11:20 System
drwxr-xr-x@ 6 root admin 204 Feb 26 11:46 Users
drwxrwxrwt@ 6 root admin 204 Feb 25 13:26 Volumes
drwxr-xr-x@ 39 root wheel 1326 Jul 8 2016 bin
drwxrwxr-t@ 2 root admin 68 Feb 26 11:46 cores
dr-xr-xr-x@ 2 root wheel 68 Feb 26 11:46 dev
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:40 etc -> private/etc
-rw-r--r--@ 1 root wheel 313 Aug 2 2015 installer.failurerequests
dr-xr-xr-x@ 2 root wheel 68 Dec 14 2014 net
drwxr-xr-x@ 6 root wheel 204 Feb 26 11:46 private
drwxr-xr-x@ 59 root wheel 2006 Feb 26 11:42 sbin
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:40 tmp -> private/tmp
drwxr-xr-x@ 11 root wheel 374 Feb 26 12:00 usr
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:42 var -> private/var

Samrods-Mac-Pro:samrod samrod$ bless --info /Volumes/SuDDen/
finderinfo[0]: 38617997 => Blessed System Folder is /Volumes/SuDDen/System/Library/CoreServices
finderinfo[1]: 39042898 => Blessed System File is /Volumes/SuDDen/System/Library/CoreServices/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 38617997 => OS X blessed folder is /Volumes/SuDDen/System/Library/CoreServices
64-bit VSDB volume id: 0xD63B406787E5DFAC

 

[rthpjm]

Samrods-Mac-Pro:samrod samrod$ ls -al /Volumes/SuDDen/
total 88
drwxr-xr-x@ 34 root wheel 1224 Mar 1 11:04 .
drwxrwxrwt@ 6 root admin 204 Feb 26 23:28 ..
-rw-rw-r--@ 1 root admin 15364 Mar 1 11:04 .DS_Store
d--x--x--x 8 root wheel 272 Feb 26 12:26 .DocumentRevisions-V100
-rw-r--r--@ 1 root wheel 2766 Feb 26 12:02 .OSInstallerMessages
drwx------ 5 root wheel 170 Jul 3 2014 .Spotlight-V100
-rw-rw-rw-@ 1 root 501 5192 Nov 1 2009 .SymAVx86QSFile
d-wx-wx-wt 5 root wheel 170 Feb 4 2018 .TemporaryItems
d-wx-wx-wt 4 root wheel 136 Feb 26 12:26 .Trashes
-rw-r--r--@ 1 samrod staff 0 Nov 25 2015 .com.apple.timemachine.donotpresent
srwxrwxrwx 1 root wheel 0 Nov 29 2014 .dbfseventsd
---------- 1 root admin 0 Feb 25 2016 .file
drwx------ 5 root wheel 170 Feb 26 12:44 .fseventsd
drwxr-xr-x@ 2 root wheel 68 Feb 26 11:46 .vol
drwxrwxr-x@ 114 root admin 3876 Feb 26 11:53 Applications
drwxr-xr-x@ 67 root wheel 2278 Feb 26 11:53 Library
drwxr-xr-x@ 2 root wheel 68 Feb 26 11:46 Network
drwxr-xr-x 9 root wheel 306 Feb 26 10:56 OS X Install Data
drwxr-xr-x@ 4 root wheel 136 Feb 26 11:20 System
drwxr-xr-x@ 6 root admin 204 Feb 26 11:46 Users
drwxrwxrwt@ 6 root admin 204 Feb 25 13:26 Volumes
drwxr-xr-x@ 39 root wheel 1326 Jul 8 2016 bin
drwxrwxr-t@ 2 root admin 68 Feb 26 11:46 cores
dr-xr-xr-x@ 2 root wheel 68 Feb 26 11:46 dev
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:40 etc -> private/etc
-rw-r--r--@ 1 root wheel 313 Aug 2 2015 installer.failurerequests
dr-xr-xr-x@ 2 root wheel 68 Dec 14 2014 net
drwxr-xr-x@ 6 root wheel 204 Feb 26 11:46 private
drwxr-xr-x@ 59 root wheel 2006 Feb 26 11:42 sbin
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:40 tmp -> private/tmp
drwxr-xr-x@ 11 root wheel 374 Feb 26 12:00 usr
lrwxr-xr-x@ 1 root wheel 11 Feb 26 11:42 var -> private/var

Samrods-Mac-Pro:samrod samrod$ bless --info /Volumes/SuDDen/
finderinfo[0]: 38617997 => Blessed System Folder is /Volumes/SuDDen/System/Library/CoreServices
finderinfo[1]: 39042898 => Blessed System File is /Volumes/SuDDen/System/Library/CoreServices/boot.efi
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 0 => No alternate OS blessed file/folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 38617997 => OS X blessed folder is /Volumes/SuDDen/System/Library/CoreServices
64-bit VSDB volume id: 0xD63B406787E5DFAC

Hi Samrod

So it looks like you have a full installation of El Capitan, and the “OS X Install Data” folder (Pikify usually creates this, although the Apple tools will also create this).

The installer seems to have been run on Feb 26. There are also older files/folders, therefore I assume that you performed an “in-place upgrade” rather than a “clean install”.

The volume appears to be “blessed” correctly for a regular reboot.

Let’s check if the installation completed cleanly. There should be a file located at /Volumes/SuDDen/var/log/install.log. You can use a Terminal or the Console app to take a look. Look for any error messages, you could upload a copy here and I will take a look.

The other obvious thing to check is whether you have allowed Software Update to run at any point?
Did you successfully reboot after installing? Did you then allow SU to run?

Let’s check some of the key files

ls -lh /Volumes/SuDDen/System/Library/CoreServices/boot.efi /Volumes/SuDDen/usr/standalone/i386/boot.efi

Both files should have the same size, just over 300k bytes. If one or both are larger, approx 600k bytes, then you have the Apple versions of the boot files. Replace them with the Pike version.

Let’s see if you have allowed the 2018 Security Updates to be installed. The 2018 SUs have a new kernel file which causes the original MacPro to crash on startup, often described as a boot loop...

md5 /Volumes/SuDDen/System/Library/Kernels/kernel

 

[samrod]

So it looks like you have a full installation of El Capitan, and the “OS X Install Data” folder (Pikify usually creates this, although the Apple tools will also create this).

The installer seems to have been run on Feb 26. There are also older files/folders, therefore I assume that you performed an “in-place upgrade” rather than a “clean install”.

Yup, I have a ton of apps and that I'd rather avoid having to reinstall from scratch.

Let’s check if the installation completed cleanly. There should be a file located at /Volumes/SuDDen/var/log/install.log. You can use a Terminal or the Console app to take a look. Look for any error messages, you could upload a copy here and I will take a look.

The first part completed successfully:

./createpikeinstallmedia /Volumes/SuDDEN/

Then I restarted after "DONE PIKIFYING", the El Capitan installer ran for about a half hour and completed successfully. When I clicked "Restart", it booted into the El Capitan recovery mode and here we are. The install log is attached and contains a single error.

The other obvious thing to check is whether you have allowed Software Update to run at any point?
Did you successfully reboot after installing? Did you then allow SU to run?

Have not run any updates or security updates and both boot.efi files are 309kb.

"/Volumes/SuDDen/System/Library/Kernels/" doesn't exist.

 

[rthpjm]

Yup, I have a ton of apps and that I'd rather avoid having to reinstall from scratch.



The first part completed successfully:

./createpikeinstallmedia /Volumes/SuDDEN/

Then I restarted after "DONE PIKIFYING", the El Capitan installer ran for about a half hour and completed successfully. When I clicked "Restart", it booted into the El Capitan recovery mode and here we are. The install log is attached and contains a single error.



Have not run any updates or security updates and both boot.efi files are 309kb.

"/Volumes/SuDDen/System/Library/Kernels/" doesn't exist.

Hi samrod,

Can I ask you to list (in detail) the steps you went through to install with pikify? The install log clearly shows that you have not used pikify in the way it was designed to operate.

It looks like you have tried to install the pikify.pkg on its own. The package is not designed to be installed independently, it will only be successful when it is called from the main installer (whilst installing OS X El Capitan).

Q1. How did you install El Capitan onto SuDDen?
Q2. Did you "try" to install pikify.pkg on it's own?

Ah, ha!

When I clicked "Restart", it booted into the El Capitan recovery mode and here we are.

After the pikify script has run, and after you hit restart, the machine will boot (not into the recovery partition) into the "modified" installer. You seem to have then chosen not to "install".

Go through the procedure again, but keep going, you need to install! (Pikify builds a modified installer).

1. run the createpikeinstallmedia script again
2. reboot
3. you should enter the installer, install onto SuDDen. This will be an in-place install, it will simply install the MacOSX elements whilst preserving your Apps, settings, and files (of course make sure you have a backup, just in case).
4. At the end of the install it should reboot into El Capitan hosted on SuDDen

 

[samrod]

Hi rthpjm,

Hi samrod,
Q1. How did you install El Capitan onto SuDDen?
Q2. Did you "try" to install pikify.pkg on it's own?

Ah, ha!

Q1. I ran "./createpikeinstallmedia /Volumes/SuDDEN/" waited until it was completely done, selected restart, then the El Capitan installer took over for about a half hour until it was done and restarted itself.

Q2. Yes I ran pikify.pkg first before I found your YouTube video instructions. Is this the culprit?

After the pikify script has run, and after you hit restart, the machine will boot (not into the recovery partition) into the "modified" installer. You seem to have then chosen not to "install".

Go through the procedure again, but keep going, you need to install! (Pikify builds a modified installer).

1. run the createpikeinstallmedia script again
2. reboot
3. you should enter the installer, install onto SuDDen. This will be an in-place install, it will simply install the MacOSX elements whilst preserving your Apps, settings, and files (of course make sure you have a backup, just in case).
4. At the end of the install it should reboot into El Capitan hosted on SuDDen

All that is exactly what I did, only after having run pikify.pkg first. How do I uninstall pikify.pkg before trying again?

 

[rthpjm]

Hi rthpjm,



Q1. I ran "./createpikeinstallmedia /Volumes/SuDDEN/" waited until it was completely done, selected restart, then the El Capitan installer took over for about a half hour until it was done and restarted itself.

Q2. Yes I ran pikify.pkg first before I found your YouTube video instructions. Is this the culprit?



All that is exactly what I did, only after having run pikify.pkg first. How do I uninstall pikify.pkg before trying again?

Okay, hiwever the install.log does not show the “full” installation. It doesn’t look like the installation was performed on SuDDen.

Let’s assume that’s an anomaly. Therefore let’s try simple things first.

When booted in 10.7, go to the System Preferences app. Select the Startup Disk panel. Can you see SuDDen listed (as 10.11.x)? If so, select it and then hit the Restart... Does the Mac restart into El Capitan?

If not, try restarting in verbose mode, after you hear the boot chime hold down APPLE V

I’m assuming that you have a graphics card that shows the boot screens. When rebooting in verbose mode you should see text-based progress. Watch it, looking for any indication of an issue...

If there’s nothing obvious, try a PRAM reset. Reboot, when you hear the chime hold down APPLE ALT P R, keep them held down until you hear a second chime then release. It might boot into 10.7 after you clear the PRAM. Go back to System Prefs and select the Startup Disk again, reboot.

If there is still no joy, then run through the whole install procedure a second time. Make sure you createpikeinstallmedia on /Volumes/SuDDen, and when you get to the Apple Install also target SuDDen.

If you still have issues resend the install.log...

 

[samrod]

Okay, hiwever the install.log does not show the “full” installation. It doesn’t look like the installation was performed on SuDDen.

Let’s assume that’s an anomaly. Therefore let’s try simple things first.

When booted in 10.7, go to the System Preferences app. Select the Startup Disk panel. Can you see SuDDen listed (as 10.11.x)? If so, select it and then hit the Restart... Does the Mac restart into El Capitan?

If not, try restarting in verbose mode, after you hear the boot chime hold down APPLE V

I’m assuming that you have a graphics card that shows the boot screens. When rebooting in verbose mode you should see text-based progress. Watch it, looking for any indication of an issue...

If there’s nothing obvious, try a PRAM reset. Reboot, when you hear the chime hold down APPLE ALT P R, keep them held down until you hear a second chime then release. It might boot into 10.7 after you clear the PRAM. Go back to System Prefs and select the Startup Disk again, reboot.

If there is still no joy, then run through the whole install procedure a second time. Make sure you createpikeinstallmedia on /Volumes/SuDDen, and when you get to the Apple Install also target SuDDen.

If you still have issues resend the install.log...

Yes, Startup Disk was showing 10.11.6, but GOOD NEWS! I did exactly as you suggested and repeated the same steps again and BOOM, it installed and finally booted right back into El Capitan on my own account with everything intact. I was scared that I may have needed to do a clean install and reinstall all my apps.

Thank you SO MUCH for your help. I noticed some people upgraded their MacPro1,1 to report MacPro1,2. Should I do this?