Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Operating System
Failing reinstall of El Capitan on formatted HD - no Disk Utility (2012 iMac, white screen of death)
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CrossyTM" data-source="post: 1874926" data-attributes="member: 406955"><p>Hi, All</p><p>Installation of El Capitan on either a (formatted) USB stick or on the formatted iMac HD (via Target Disk mode and Thunderbolt cable) is obviously <u>excluded</u>: The installer says "OS X can't be installed on this disk. macOS isn't installed" (in both cases).</p><p>I decided to reinstall the disk image on the iMac HD. And now? Again via Target Disk mode and Thunderbolt cable, the El Capitan installer (downloaded by and onto my MacBook Pro) made possible to choose the iMac HD (! - yes!) and accomplished the OS installation "successfully" (!!). - However, shutting down the iMac and restarting it did not let the iMac start up as it should, but the <u>original error persists</u> (white screen after abot 60% of the status bar). Only novelty: after some minutes, the white screen vanishes, and the iMac restarts by itself...</p><p>Thus: not very much gained...</p><p></p><p>But:</p><p>I looked at the output from the verbose-mode startup; and I had further diagnosis (hardware test):</p><p></p><p>There are two points I am wondering about...</p><p></p><p>1. I looked at the lines which show up in verbose mode (CMD-V at startup). And there is something in the iMac's file system which makes me wonder, whether a former OS installation / update went wrong, such that (in a way) two systems are installed in parallel which again creates a problem...</p><p>In the <strong>verbose</strong> output, I have these lines:</p><p></p><p>> LibBootCache: Unable to open: /var/db/BootCache.playlist: 2 No such file or directory</p><p>> Warning: kextd unavailable; proceeding w/o lock for <unknown></p><p>> Warning: couldn't block sleep during cache update</p><p>> Warning: proceeding w/o DiskArb</p><p>(later: )</p><p>> tzinit: <strong>New update not compatible or older version: 2020a.1.0 vs 2020a.1.0: No such file or directory</strong></p><p>> Sun Jan 31 <em>(more stuff here)</em> Early Boot complete. Continuing system boot.</p><p>(later: )</p><p>> Notice - new kext com.apple.driver.KextExcludedList, v13.2.1 matches prelinked kext but can't determine if <strong>executables are the same </strong>(noUUIDs).</p><p>(later: )</p><p>> unsupported CPU</p><p>> unsupported CPU</p><p>> unsupported PCH</p><p>> HID: Legacy shim 2</p><p>> BCM5701UserClient::clientClose</p><p>> BCM5701UserClient::terminate</p><p>(later: )</p><p>> promiscuous mode enable succeeded</p><p></p><p>In the <u>file system</u> of the iMac, as visible in the Finder, I have the <strong>folders</strong></p><p>Applications / Library / System / Users</p><p>Within "Library", there are about 60 subfolders.</p><p>But within "System", there is <em>another</em> folder named "Library" which contains about 97 subfolders - most of them seem to correspond to the subfolders in the upper-level "Library" folder... Is that the way it's supposed to be?? Is it rather a source of the problem? Help by simply deleting a number of files / folders from the HD...?</p><p></p><p>2. I had the diagnosis (hardware test) run (option-D at startup), and once it (again) showed a <strong>memory error</strong>: 4MEM/62/40000000: 0x88e61518 . (I suppose this is clearly a RAM error...) Only sometimes this (or a similar) error is diagnosed (in the extended test only, anyway). I am wondering whether one can tell <strong>which one</strong> of the four RAM modules is the (occasionally) faulty one?</p><p>If one cannot tell, I shall go ahead and carry out some dozens of tests, I think, with the one or the other pair of RAM modules removed... (would there be something to be watched out for while doing this, such as at the first restart after a change of RAM?)</p><p></p><p>I don't know whether the two (potential) problems are independent from one another or whether perhaps the memory problem (2.) caused the OS system problem (1.)...?!</p><p>To me it seems best to firstly investigate and solve the memory problem (2.) (which apparently is present)? Or am I heading a wrong way?</p><p></p><p>Further comments & advice most welcome!</p></blockquote><p></p>
[QUOTE="CrossyTM, post: 1874926, member: 406955"] Hi, All Installation of El Capitan on either a (formatted) USB stick or on the formatted iMac HD (via Target Disk mode and Thunderbolt cable) is obviously [U]excluded[/U]: The installer says "OS X can't be installed on this disk. macOS isn't installed" (in both cases). I decided to reinstall the disk image on the iMac HD. And now? Again via Target Disk mode and Thunderbolt cable, the El Capitan installer (downloaded by and onto my MacBook Pro) made possible to choose the iMac HD (! - yes!) and accomplished the OS installation "successfully" (!!). - However, shutting down the iMac and restarting it did not let the iMac start up as it should, but the [U]original error persists[/U] (white screen after abot 60% of the status bar). Only novelty: after some minutes, the white screen vanishes, and the iMac restarts by itself... Thus: not very much gained... But: I looked at the output from the verbose-mode startup; and I had further diagnosis (hardware test): There are two points I am wondering about... 1. I looked at the lines which show up in verbose mode (CMD-V at startup). And there is something in the iMac's file system which makes me wonder, whether a former OS installation / update went wrong, such that (in a way) two systems are installed in parallel which again creates a problem... In the [B]verbose[/B] output, I have these lines: > LibBootCache: Unable to open: /var/db/BootCache.playlist: 2 No such file or directory > Warning: kextd unavailable; proceeding w/o lock for <unknown> > Warning: couldn't block sleep during cache update > Warning: proceeding w/o DiskArb (later: ) > tzinit: [B]New update not compatible or older version: 2020a.1.0 vs 2020a.1.0: No such file or directory[/B] > Sun Jan 31 [I](more stuff here)[/I] Early Boot complete. Continuing system boot. (later: ) > Notice - new kext com.apple.driver.KextExcludedList, v13.2.1 matches prelinked kext but can't determine if [B]executables are the same [/B](noUUIDs). (later: ) > unsupported CPU > unsupported CPU > unsupported PCH > HID: Legacy shim 2 > BCM5701UserClient::clientClose > BCM5701UserClient::terminate (later: ) > promiscuous mode enable succeeded In the [U]file system[/U] of the iMac, as visible in the Finder, I have the [B]folders[/B] Applications / Library / System / Users Within "Library", there are about 60 subfolders. But within "System", there is [I]another[/I] folder named "Library" which contains about 97 subfolders - most of them seem to correspond to the subfolders in the upper-level "Library" folder... Is that the way it's supposed to be?? Is it rather a source of the problem? Help by simply deleting a number of files / folders from the HD...? 2. I had the diagnosis (hardware test) run (option-D at startup), and once it (again) showed a [B]memory error[/B]: 4MEM/62/40000000: 0x88e61518 . (I suppose this is clearly a RAM error...) Only sometimes this (or a similar) error is diagnosed (in the extended test only, anyway). I am wondering whether one can tell [B]which one[/B] of the four RAM modules is the (occasionally) faulty one? If one cannot tell, I shall go ahead and carry out some dozens of tests, I think, with the one or the other pair of RAM modules removed... (would there be something to be watched out for while doing this, such as at the first restart after a change of RAM?) I don't know whether the two (potential) problems are independent from one another or whether perhaps the memory problem (2.) caused the OS system problem (1.)...?! To me it seems best to firstly investigate and solve the memory problem (2.) (which apparently is present)? Or am I heading a wrong way? Further comments & advice most welcome! [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
Apple Computing Products:
macOS - Operating System
Failing reinstall of El Capitan on formatted HD - no Disk Utility (2012 iMac, white screen of death)
Top
