Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The spare T5 that I have is 1TB, so certainly large enough.

The T5 now has bootable Monterey on it. I can use Migration Assistance to move everything from a CCC clone of the data volume.

But, I thought the point of this exercise was to boot from a drive that had nothing extra installed and only a single virgin user?
if its a software problem, you will move it across, if they are on the same system, but if its a (disk) hardware problem, then you are leaving it behind, although the internal drive is still there and might cause issues, but maybe not, if you dont use it, or unmount it while booted from the ssd.
 
Last edited:
if its a software problem, you will move it across, if they are on the same system, but if its a hardware problem, then you are leaving it behind, although the internal drive is still there and might cause issues, but maybe not, if you dont use it, or unmount it while booted from the ssd.
I can use fstab to keep it from mounting.
 
Still going strong!

Code:
Kernel-2022-07-10-080308.panic
Kernel-2022-07-10-102819.panic
Kernel-2022-07-10-104012.panic
Kernel-2022-07-10-180539.panic
Kernel-2022-07-10-181003.panic
Kernel-2022-07-10-181324.panic

Kernel-2022-07-11-082212.panic

Kernel-2022-07-17-091640.panic

Kernel-2022-07-18-191907.panic

Kernel-2022-07-19-192355.panic

Kernel-2022-07-20-120110.panic
Kernel-2022-07-20-120405.panic
Kernel-2022-07-20-122308.panic
Kernel-2022-07-20-123242.panic

Kernel-2022-07-21-060717.panic
Kernel-2022-07-21-061451.panic
Kernel-2022-07-21-153512.panic
Kernel-2022-07-21-154924.panic

Kernel-2022-07-24-160629.panic

Kernel-2022-07-25-093755.panic
Kernel-2022-07-25-133514.panic
Kernel-2022-07-25-163109.panic
Kernel-2022-07-25-163529.panic
Kernel-2022-07-25-163758.panic

Kernel-2022-07-27-045730.panic
Kernel-2022-07-27-050927.panic
Kernel-2022-07-27-111324.panic
Kernel-2022-07-27-161747.panic
Kernel-2022-07-27-194250.panic
Kernel-2022-07-27-195222.panic
Kernel-2022-07-27-195507.panic

Kernel-2022-07-28-042401.panic
Kernel-2022-07-28-231836.panic

Kernel-2022-07-29-020433.panic
Kernel-2022-07-29-051419.panic
Kernel-2022-07-29-051719.panic
Kernel-2022-07-29-051949.panic
Kernel-2022-07-29-052247.panic
Kernel-2022-07-29-065959.panic
Kernel-2022-07-29-070432.panic
Kernel-2022-07-29-074159.panic
Kernel-2022-07-29-103008.panic
Kernel-2022-07-29-104606.panic
Kernel-2022-07-29-120624.panic

Kernel-2022-07-30-043856.panic
Kernel-2022-07-30-044216.panic
Kernel-2022-07-30-044724.panic
Kernel-2022-07-30-045601.panic
Kernel-2022-07-30-045915.panic

Kernel-2022-07-31-051529.panic

Kernel-2022-08-01-052231.panic

Kernel-2022-08-03-205912.panic
Kernel-2022-08-03-210121.panic

Kernel-2022-08-04-012038.panic
Kernel-2022-08-04-114230.panic
Kernel-2022-08-04-114431.panic

Kernel-2022-08-10-043407.panic
Kernel-2022-08-10-043652.panic
Kernel-2022-08-10-082901.panic

Kernel-2022-08-11-042738.panic
Kernel-2022-08-11-043518.panic
Kernel-2022-08-11-043709.panic
Kernel-2022-08-11-043956.panic
Kernel-2022-08-11-045447.panic
Kernel-2022-08-11-161355.panic
Kernel-2022-08-11-162401.panic

Kernel-2022-08-17-180547.panic
Kernel-2022-08-17-204835.panic

Kernel-2022-08-18-092355.panic
Kernel-2022-08-18-103716.panic
Kernel-2022-08-18-165841.panic
Kernel-2022-08-18-170051.panic
Kernel-2022-08-18-170308.panic
Kernel-2022-08-18-170539.panic

Kernel-2022-08-19-031918.panic
Kernel-2022-08-19-054210.panic
Kernel-2022-08-19-054714.panic
Kernel-2022-08-19-102630.panic
Kernel-2022-08-19-150515.panic
Kernel-2022-08-19-165145.panic

Kernel-2022-08-23-124859.panic

Kernel-2022-08-29-150535.panic
Kernel-2022-08-29-151108.panic

Kernel-2022-09-05-063713.panic
Kernel-2022-09-05-071654.panic
Kernel-2022-09-05-072245.panic
Kernel-2022-09-05-074719.panic
Kernel-2022-09-05-084830.panic
Kernel-2022-09-05-091951.panic
Kernel-2022-09-05-153516.panic
Kernel-2022-09-05-153943.panic
Kernel-2022-09-05-154429.panic
Kernel-2022-09-05-201623.panic

Kernel-2022-09-06-074533.panic
Kernel-2022-09-06-110439.panic
Kernel-2022-09-06-110906.panic

Kernel-2022-09-07-071334.panic
Kernel-2022-09-07-071640.panic
Kernel-2022-09-07-080625.panic
Kernel-2022-09-07-080800.panic
Kernel-2022-09-07-081255.panic
Kernel-2022-09-07-081457.panic
Kernel-2022-09-07-081735.panic

Kernel-2022-09-08-053202.panic
Kernel-2022-09-08-103101.panic
Kernel-2022-09-08-103229.panic
Kernel-2022-09-08-185421.panic

Kernel-2022-09-09-042710.panic
Kernel-2022-09-09-042952.panic
Kernel-2022-09-09-044114.panic
Kernel-2022-09-09-044403.panic
Kernel-2022-09-09-071448.panic
 
Yes, still running of the internal disk. I decided that the project to run off of an external drive would be valid only if the external drive contained a pristine system and a virgin user with nothing additional installed. I'd have to run it that way for at least two weeks to be reasonably certain about the outcome.

Unfortunately, I can't go without a computer for two weeks, so I've been spending a lot of time putting together stuff on my wife's M1 iMac so I could use that while running the old iMac on the pristine installation.

Turns out that setting myself up on my wife's machine is more time consuming than I thought. For example, I have a bunch of shell scripts that need binaries available via MacPorts. But, to install MacPorts you need to install Xcode and the Xcode command line tools. Then I need to install all the necessary binaries ver MacPorts.

Also, I needed an SMTP client. Because of an early mistake on my part, that took several days to install, configure and get working.

Right now I'm in the midst of installing a Plex Media Server on the machine.

To be honest, I remain unconvinced that this test will prove anything very useful, so I haven't devoted a lot of time to my wife's machine. And, we were on a dive boat for six days and spent another week at our condo; so no work at all during that period.

I did have to use the spare T5 as a media drive for Plex, so I'll have to find something else to boot the old iMac from.

I'll get there.

In the mean time, I'm having a good time with the Kernel Panics.

Now, whenever the machine boots after a panic there is no Menu Bar, the Dock is only partially functional and the UI sometimes doesn't handle keystrokes or window clicks. In those cases I need to log in remotely (usually from my iPad) and issue the following command:

Code:
sudo killall -KILL WindowServer

That brings the Menu Bar back, returns the Dock to full functionality and makes keystroke appear where wanted. I think what I've learned from that is that the Kernel Panics may have something to do with the WindowServer process. Perhaps when I'm able to install MacOS Ventura that problem will disappear.

I'm in no hurry. (I guess that must be obvious.)
 
I finally got around to setting up my wife's M1 iMac so I could use it as my main machine; perhaps spurred on by the fact that this old iMac is now having kernel panics 25+ times per day.

I created an external boot drive with Monterey and a virgin user. I migrated nothing from the existing internal drive.

There were three panics overnight and one when I sat down to type this.

I guess that proves that the panics are not cause by the internal SSD or by any software I installed.

So, must be a different hardware problem. Not worth fixing, so time for a new machine.
 
BTW, I'm now running the Ventura public beta on the old iMac. That made the odd WindowServer error go away. No need to kill that process to get the machine functioning.
 
I finally got around to setting up my wife's M1 iMac so I could use it as my main machine; perhaps spurred on by the fact that this old iMac is now having kernel panics 25+ times per day.

I created an external boot drive with Monterey and a virgin user. I migrated nothing from the existing internal drive.

There were three panics overnight and one when I sat down to type this.

I guess that proves that the panics are not cause by the internal SSD or by any software I installed.

So, must be a different hardware problem. Not worth fixing, so time for a new machine.
Its great that you know its a motherboard/cpu issue by the sound of it so not worth fixing when you have another machine .... you would need to be pretty serious about hardware to change the cpu, and it might not fix it anyways. I did one a few months ago, and got lucky (it works) but I think you are doing the right thing ....
 
  • Like
Reactions: Buadhai
Sharing the one machine is not too bad. My wife is at her office all day weekdays, so the M1 is mine. Weekends is a bit harder so I have a 2010 MBA running Screen Sharing on an ancient Samsung monitor. It's ugly, but it works.

tempImageU1qifo.png
 
Since the last post I've made a rather odd discovery. I've posted about it here:

https://forums.macrumors.com/thread...prevent-kernel-panics-on-my-old-imac.2368037/

Just by chance I downloaded Rember, the GUI for the memory testing utility memtest. I set Rember to test all memory and do 255 loops, the maximum. There were no kernel panics while Rember was running memtest.

After lots of experimenting I've found that if I keep Rember running constantly, the machine never panics.

The downside is that memtest consumes lots of CPU. I can mitigate that somewhat by using renice to set the nice level to 20 (the max). I really don't notice any machine sluggishness, even when editing photos.

So, now I have a machine that no longer panics. I just have to remember to keep Rember running.

Oddly, running memtest from the command line doesn't have the same effect. The machine still panics now and then if I run memtest directly.

I don't really understand any of this.

Anyway, it is now November 27th and I haven't had a panic since starting Rember up on November 23rd. After four days it is on test loop number 201 out of 255.

Here are the last panics before running Rember:

Code:
Kernel-2022-11-21-102123.panic
Kernel-2022-11-22-135602.panic
Kernel-2022-11-22-140004.panic
Kernel-2022-11-22-141123.panic
Kernel-2022-11-22-141602.panic
Kernel-2022-11-22-164929.panic
Kernel-2022-11-23-104343.panic
Kernel-2022-11-23-135139.panic
Kernel-2022-11-23-164137.panic
Kernel-2022-11-23-164324.panic
Kernel-2022-11-23-164844.panic
Kernel-2022-11-23-165430.panic
 
I took the iMac to the only shop in this city (Nakhon Ratchasima, Thailand) willing to look at it. When I dropped it off there were several other iMacs on their workbench in various states of repair. So, I guess they do attempt to repair Mac computers.

At first they thought it was either the SSD or power supply. It was neither. Now they've had it a week and seem to have no idea what's wrong.

Time for a new machine, I guess.
 
I took the iMac to the only shop in this city (Nakhon Ratchasima, Thailand) willing to look at it. When I dropped it off there were several other iMacs on their workbench in various states of repair. So, I guess they do attempt to repair Mac computers.

At first they thought it was either the SSD or power supply. It was neither. Now they've had it a week and seem to have no idea what's wrong.

Time for a new machine, I guess.
good idea
 
After having the machine for over six weeks they finally called to say that they are unable to repair it. I guess that's it.
 
You asked me this before and I asked how is it possible to convert a 21" Retina 4K display into 5K monitor. Please explain.

Sorry, already forgot it. 21.5in monitor is not worth converting, is it?


 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.