In 2017 I began experiencing an annoying problem. When I put the
computer to sleep, sometimes the display would come back on in six
seconds, and the log wouldn't show that it had ever been asleep. It
didn't seem to be connected with anything in Activity Monitor. Sometimes
the second try would work, but I could go so far as to cycle it through
a safe startup. On the second startup, if I clicked "sleep" instead of logging on, it might still refuse to sleep.
A year later, the problem migrated to my new computer. It persists
although my hardware and software are almost entirely different from 2017.
Now I remember. The hard drive on my 2012 had become very slow, but a detailed report showed that it was in excellent shape. I suspected that defragmentation-on-the-fly wasn't working,
and there no longer seemed to
be defrag apps available.
Prior to 2012, I used to defrag by cloning,
which also provided redundancy. So I bought a USB SSD, cloned onto it
with CCC, booted with it, and cloned back to my HD.
It worked, but gradually the HD slowed down as if it were again becoming fragmented. I usually booted from the external SSD.
For my first few months with my 2018 Mini, I cloned back and forth
between the internal SSD and an external one because I liked redundancy.
Now I have a theory. A cloned OS will somehow conflict with Apple's
garbage collection, and this will persist even after a system upgrade.
If I tell the computer to sleep during a scheduled garbage collection, I think garbage collection vetos sleep about 6 seconds after the screen
goes black.
It's annoying, and there may be worse effects. Should I reinstall the
OS? Should I reinstall from Time Machine, or erase and get it from the internet?
Do I need to write down my Apple password?
In 2017 I began experiencing an annoying problem. When I put the
computer to sleep, sometimes the display would come back on in six
seconds, and the log wouldn't show that it had ever been asleep. It
didn't seem to be connected with anything in Activity Monitor.
Sometimes the second try would work, but I could go so far as to cycle
it through a safe startup. On the second startup, if I clicked "sleep" instead of logging on, it might still refuse to sleep.
A year later, the problem migrated to my new computer. It persists
although my hardware and software are almost entirely different from
2017.
Now I remember. The hard drive on my 2012 had become very slow, but a detailed report showed that it was in excellent shape. I suspected that defragmentation-on-the-fly wasn't working, and there no longer seemed
to be defrag apps available. Prior to 2012, I used to defrag by
cloning, which also provided redundancy. So I bought a USB SSD, cloned
onto it with CCC, booted with it, and cloned back to my HD.
It worked, but gradually the HD slowed down as if it were again
becoming fragmented. I usually booted from the external SSD.
For my first few months with my 2018 Mini, I cloned back and forth
between the internal SSD and an external one because I liked
redundancy. Now I have a theory. A cloned OS will somehow conflict with Apple's garbage collection, and this will persist even after a system upgrade. If I tell the computer to sleep during a scheduled garbage collection, I think garbage collection vetos sleep about 6 seconds
after the screen goes black.
It's annoying, and there may be worse effects. Should I reinstall the
OS? Should I reinstall from Time Machine, or erase and get it from the internet? Do I need to write down my Apple password?
Sometimes when I put my Mac to sleep, it will wake up almost instantly.
The cause for is likely the mouse moving slightly (maybe as I let go or
move the chair back under the desk) and reawakening it. It usually
works properly the second attempt though.
Another may be Spotlight indexing. Make sure the cloned drive is in the
list to be excluded. Also exclude it from Time Machine (there's little
point in also backing up a clone of the drive that's already backing up
- other than perhaps double-redundancy).
On 2021-11-11 20:25:17 +0000, J Burns said:
In 2017 I began experiencing an annoying problem. When I put the
computer to sleep, sometimes the display would come back on in six
seconds, and the log wouldn't show that it had ever been asleep. It
didn't seem to be connected with anything in Activity Monitor.
Sometimes the second try would work, but I could go so far as to cycle
it through a safe startup. On the second startup, if I clicked "sleep"
instead of logging on, it might still refuse to sleep.
A year later, the problem migrated to my new computer. It persists
although my hardware and software are almost entirely different from
2017.
Now I remember. The hard drive on my 2012 had become very slow, but a
detailed report showed that it was in excellent shape. I suspected
that defragmentation-on-the-fly wasn't working, and there no longer
seemed to be defrag apps available. Prior to 2012, I used to defrag by
cloning, which also provided redundancy. So I bought a USB SSD, cloned
onto it with CCC, booted with it, and cloned back to my HD.
It worked, but gradually the HD slowed down as if it were again
becoming fragmented. I usually booted from the external SSD.
For my first few months with my 2018 Mini, I cloned back and forth
between the internal SSD and an external one because I liked
redundancy. Now I have a theory. A cloned OS will somehow conflict
with Apple's garbage collection, and this will persist even after a
system upgrade. If I tell the computer to sleep during a scheduled
garbage collection, I think garbage collection vetos sleep about 6
seconds after the screen goes black.
It's annoying, and there may be worse effects. Should I reinstall the
OS? Should I reinstall from Time Machine, or erase and get it from the
internet? Do I need to write down my Apple password?
Two other possibilities ...
Sometimes when I put my Mac to sleep, it will wake up almost instantly.
The cause for is likely the mouse moving slightly (maybe as I let go or
move the chair back under the desk) and reawakening it. It usually works properly the second attempt though.
Another may be Spotlight indexing. Make sure the cloned drive is in the
list to be excluded. Also exclude it from Time Machine (there's little
point in also backing up a clone of the drive that's already backing up
- other than perhaps double-redundancy).
An OS may know the logical location of files but not their physical
location on an SSD. The SSD knows the physical location of data but not
what files it belongs to.
TRIM allows an OS to tell an SSD what data has
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data.
Perhaps Apple doesn't support TRIM for
third-party SSDs because it may not know where an unfamiliar SSD puts data.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can't
be aware of the physical location of the files on the SSD.
In effect,
cloning turns an OEM SSD into a third-party SSD,
and Apple won't enable
TRIM.
Without TRIM, I guess in the event of Sleep, it can't tell the SSD
to cease garbage collection. Would it be a calamity if the computer went
to sleep during garbage collection?
My theory is that sometimes my Mac won't sleep because the OS is waiting
for the SSD to finish garbage collection, a process the OS can't
interrupt without TRIM. If I erased my SSD to make a fresh install of OS
12, maybe I'd have TRIM.
In article <sml6f8$r36$1...@dont-email.me>, J Burns <bu...@nospam.com>
wrote:
An OS may know the logical location of files but not their physical location on an SSD. The SSD knows the physical location of data but not what files it belongs to.that is normal and not an issue whatsoever.
TRIM allows an OS to tell an SSD what data hasit does not.
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data.
Perhaps Apple doesn't support TRIM fornope, it's because some ssds have poor implementations of trim, which
third-party SSDs because it may not know where an unfamiliar SSD puts data.
can potentially cause data loss. apple does not want to test every
single ssd out there to be sure it works properly.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can'tthat does not matter at all.
be aware of the physical location of the files on the SSD.
In effect,no it doesn't.
cloning turns an OEM SSD into a third-party SSD,
and Apple won't enabletrim is not needed on modern ssds, however, it can be enabled if the
TRIM.
user really wants it.
Without TRIM, I guess in the event of Sleep, it can't tell the SSDnope. that makes absolutely no difference whatsoever. it will resume
to cease garbage collection. Would it be a calamity if the computer went
to sleep during garbage collection?
when the computer wakes, just as everything else does.
My theory is that sometimes my Mac won't sleep because the OS is waiting for the SSD to finish garbage collection, a process the OS can'tthat theory has no basis in reality.
interrupt without TRIM. If I erased my SSD to make a fresh install of OS 12, maybe I'd have TRIM.
In article <sml6f8$r36$1...@dont-email.me>, J Burns <bu...@nospam.com>
wrote:
An OS may know the logical location of files but not their physical location on an SSD. The SSD knows the physical location of data but not what files it belongs to.that is normal and not an issue whatsoever.
TRIM allows an OS to tell an SSD what data hasit does not.
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data.
Perhaps Apple doesn't support TRIM fornope, it's because some ssds have poor implementations of trim, which
third-party SSDs because it may not know where an unfamiliar SSD puts data.
can potentially cause data loss. apple does not want to test every
single ssd out there to be sure it works properly.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can'tthat does not matter at all.
be aware of the physical location of the files on the SSD.
In effect,no it doesn't.
cloning turns an OEM SSD into a third-party SSD,
and Apple won't enabletrim is not needed on modern ssds, however, it can be enabled if the
TRIM.
user really wants it.
Without TRIM, I guess in the event of Sleep, it can't tell the SSDnope. that makes absolutely no difference whatsoever. it will resume
to cease garbage collection. Would it be a calamity if the computer went
to sleep during garbage collection?
when the computer wakes, just as everything else does.
My theory is that sometimes my Mac won't sleep because the OS is waiting for the SSD to finish garbage collection, a process the OS can'tthat theory has no basis in reality.
interrupt without TRIM. If I erased my SSD to make a fresh install of OS 12, maybe I'd have TRIM.
On 11/11/21 6:24 PM, Your Name wrote:
On 2021-11-11 20:25:17 +0000, J Burns said:
In 2017 I began experiencing an annoying problem. When I put the
computer to sleep, sometimes the display would come back on in six
seconds, and the log wouldn't show that it had ever been asleep. It
didn't seem to be connected with anything in Activity Monitor.
Sometimes the second try would work, but I could go so far as to cycle
it through a safe startup. On the second startup, if I clicked "sleep"
instead of logging on, it might still refuse to sleep.
A year later, the problem migrated to my new computer. It persists
although my hardware and software are almost entirely different from
2017.
Now I remember. The hard drive on my 2012 had become very slow, but a
detailed report showed that it was in excellent shape. I suspected
that defragmentation-on-the-fly wasn't working, and there no longer
seemed to be defrag apps available. Prior to 2012, I used to defrag by
cloning, which also provided redundancy. So I bought a USB SSD, cloned
onto it with CCC, booted with it, and cloned back to my HD.
It worked, but gradually the HD slowed down as if it were again
becoming fragmented. I usually booted from the external SSD.
For my first few months with my 2018 Mini, I cloned back and forth
between the internal SSD and an external one because I liked
redundancy. Now I have a theory. A cloned OS will somehow conflict
with Apple's garbage collection, and this will persist even after a
system upgrade. If I tell the computer to sleep during a scheduled
garbage collection, I think garbage collection vetos sleep about 6
seconds after the screen goes black.
It's annoying, and there may be worse effects. Should I reinstall the
OS? Should I reinstall from Time Machine, or erase and get it from the
internet? Do I need to write down my Apple password?
Two other possibilities ...
Sometimes when I put my Mac to sleep, it will wake up almost instantly.
The cause for is likely the mouse moving slightly (maybe as I let go or move the chair back under the desk) and reawakening it. It usually works properly the second attempt though.
Another may be Spotlight indexing. Make sure the cloned drive is in the list to be excluded. Also exclude it from Time Machine (there's little point in also backing up a clone of the drive that's already backing up
- other than perhaps double-redundancy).
Thanks. Before 2017, if a Mac woke unexpectedly, it wouldn't necessarily
be 6 seconds after I told it to sleep, and the log would say it had been waked, usually by a USB device, probably the mouse. In the current
problem, the log never says it was waked, so I guess it wasn't asleep.
Naturally, I need Spotlight to keep my startup drive indexed. I quit
using clones as backups in 2019, so I also need Time Machine to keep my startup drive backed up. When I've had trouble, I've checked Activity
Monitor and haven't found backupd or a stored to be active.
There was a peculiarity under OS 11. When I had trouble, I would find
that when I clicked S[eep, suggestd had jumped to "175% CPU." If I
killed the process, clicking Sleep would wake it, so it was an effect,
not the cause. It doesn't happen under OS 12, and it didn't happen under
OS X.
An OS may know the logical location of files but not their physical
location on an SSD. The SSD knows the physical location of data but not
what files it belongs to. TRIM allows an OS to tell an SSD what data has
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data. Perhaps Apple doesn't support TRIM for
third-party SSDs because it may not know where an unfamiliar SSD puts data.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can't
be aware of the physical location of the files on the SSD. In effect,
cloning turns an OEM SSD into a third-party SSD, and Apple won't enable
TRIM. Without TRIM, I guess in the event of Sleep, it can't tell the SSD
to cease garbage collection. Would it be a calamity if the computer went
to sleep during garbage collection?
My theory is that sometimes my Mac won't sleep because the OS is waiting
for the SSD to finish garbage collection, a process the OS can't
interrupt without TRIM. If I erased my SSD to make a fresh install of OS
12, maybe I'd have TRIM.
On Friday, November 12, 2021 at 12:52:12 AM UTC-7, J Burns wrote:
On 11/11/21 6:24 PM, Your Name wrote:
On 2021-11-11 20:25:17 +0000, J Burns said:
In 2017 I began experiencing an annoying problem. When I put the
computer to sleep, sometimes the display would come back on in six
seconds, and the log wouldn't show that it had ever been asleep. It
didn't seem to be connected with anything in Activity Monitor.
Sometimes the second try would work, but I could go so far as to cycle >> it through a safe startup. On the second startup, if I clicked "sleep" >> instead of logging on, it might still refuse to sleep.
A year later, the problem migrated to my new computer. It persists
although my hardware and software are almost entirely different from
2017.
Now I remember. The hard drive on my 2012 had become very slow, but a
detailed report showed that it was in excellent shape. I suspected
that defragmentation-on-the-fly wasn't working, and there no longer
seemed to be defrag apps available. Prior to 2012, I used to defrag by >> cloning, which also provided redundancy. So I bought a USB SSD, cloned >> onto it with CCC, booted with it, and cloned back to my HD.
It worked, but gradually the HD slowed down as if it were again
becoming fragmented. I usually booted from the external SSD.
For my first few months with my 2018 Mini, I cloned back and forth
between the internal SSD and an external one because I liked
redundancy. Now I have a theory. A cloned OS will somehow conflict
with Apple's garbage collection, and this will persist even after a
system upgrade. If I tell the computer to sleep during a scheduled
garbage collection, I think garbage collection vetos sleep about 6
seconds after the screen goes black.
It's annoying, and there may be worse effects. Should I reinstall the
OS? Should I reinstall from Time Machine, or erase and get it from the >> internet? Do I need to write down my Apple password?
Two other possibilities ...
Sometimes when I put my Mac to sleep, it will wake up almost instantly. The cause for is likely the mouse moving slightly (maybe as I let go or move the chair back under the desk) and reawakening it. It usually works properly the second attempt though.
Another may be Spotlight indexing. Make sure the cloned drive is in the list to be excluded. Also exclude it from Time Machine (there's little point in also backing up a clone of the drive that's already backing up
- other than perhaps double-redundancy).
Thanks. Before 2017, if a Mac woke unexpectedly, it wouldn't necessarily
be 6 seconds after I told it to sleep, and the log would say it had been waked, usually by a USB device, probably the mouse. In the current
problem, the log never says it was waked, so I guess it wasn't asleep.
Naturally, I need Spotlight to keep my startup drive indexed. I quit
using clones as backups in 2019, so I also need Time Machine to keep my startup drive backed up. When I've had trouble, I've checked Activity Monitor and haven't found backupd or a stored to be active.
There was a peculiarity under OS 11. When I had trouble, I would find
that when I clicked S[eep, suggestd had jumped to "175% CPU." If I
killed the process, clicking Sleep would wake it, so it was an effect,
not the cause. It doesn't happen under OS 12, and it didn't happen under
OS X.
An OS may know the logical location of files but not their physical location on an SSD. The SSD knows the physical location of data but not what files it belongs to. TRIM allows an OS to tell an SSD what data has been deleted. It sounds as if in this case, the OS keeps track of the physical location of data. Perhaps Apple doesn't support TRIM for third-party SSDs because it may not know where an unfamiliar SSD puts data.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can't
be aware of the physical location of the files on the SSD. In effect, cloning turns an OEM SSD into a third-party SSD, and Apple won't enable TRIM. Without TRIM, I guess in the event of Sleep, it can't tell the SSD
to cease garbage collection. Would it be a calamity if the computer went
to sleep during garbage collection?
My theory is that sometimes my Mac won't sleep because the OS is waiting for the SSD to finish garbage collection, a process the OS can'tThis is something you merely pretend to understand.
interrupt without TRIM. If I erased my SSD to make a fresh install of OS 12, maybe I'd have TRIM.
Over and over, the surface request is Larry Washington wants to "talk
tech", but Larry Washington spends most of his time whining about "trolling".
Do you have a high school diploma?
The entire farce is brimming of unbelievable inconsistencies and counts heavily on Larry Washington's 'home made CMS' nonsense. How many more
chances does Larry Washington's stupid arse (a brick knows more than Larry Washington and is useful) need to prove their FromTheRafters sock accusation with evidence?
Larry Washington claimed the headers were entirely consistent with many
of the forgeries. Interesting, why is he having such a struggle backing
his assertion up when asked to do so? In other words, if his statement
was supportable, and not just a weak attempt to come to FromTheRafterss rescue? Larry Washington suffers from neurotic fantasies so, to him, everything,
even people ignoring him, are "slander". Who DOESN'T know this?
-
Eight things to never feed your cat! http://techrights.org/2011/07/24/gnu-linux-macosx-by-michael-glasser- roy-schestowitz-and-goblin-on-techbytes/ https://www.bing.com/search?q=Steve+Petruzzellis+the+narcissistic+bigot https://swisscows.com/web?query=dustin%20cook%20%22functionally%20illiterate%20fraud%22
Dustin Cook is a functionally illiterate fraud
On Friday, November 12, 2021 at 5:21:37 AM UTC-7, nospam wrote:
In article <sml6f8$r36$1...@dont-email.me>, J Burns <bu...@nospam.com> wrote:
The guy is as loved as a drunken karaoke singer -- and with good reason.An OS may know the logical location of files but not their physical location on an SSD. The SSD knows the physical location of data but not what files it belongs to.that is normal and not an issue whatsoever.
TRIM allows an OS to tell an SSD what data hasit does not.
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data.
Perhaps Apple doesn't support TRIM fornope, it's because some ssds have poor implementations of trim, which
third-party SSDs because it may not know where an unfamiliar SSD puts data.
can potentially cause data loss. apple does not want to test every
single ssd out there to be sure it works properly.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can't be aware of the physical location of the files on the SSD.that does not matter at all.
In effect,no it doesn't.
cloning turns an OEM SSD into a third-party SSD,
and Apple won't enabletrim is not needed on modern ssds, however, it can be enabled if the
TRIM.
user really wants it.
Without TRIM, I guess in the event of Sleep, it can't tell the SSDnope. that makes absolutely no difference whatsoever. it will resume
to cease garbage collection. Would it be a calamity if the computer went to sleep during garbage collection?
when the computer wakes, just as everything else does.
My theory is that sometimes my Mac won't sleep because the OS is waiting for the SSD to finish garbage collection, a process the OS can't interrupt without TRIM. If I erased my SSD to make a fresh install of OS 12, maybe I'd have TRIM.that theory has no basis in reality.
It was Snit sock HWSNBN who flooded RonB's site millions of times and
denied it. This forum is a puss-filled cyst.
Snit sock HWSNBN claims to be the programming master, let's see him
put up a variant minus the shipping/handling routines.
--
This Trick Gets Women Hot For You https://www.walmart.com/browse/books/family-kids-books/cary-fagan/3920_582053_585918/YnJhbmQ6Q2FyeSBGYWdhbgieie
<https://www.truepeoplesearch.com/results?name=4234911448&Diesel&Gremlin&Dustin_Cook>
https://swisscows.com/web?query=%22narcissistic%20bigot%22
Steve Carroll the Narcissistic Bigot
On Friday, November 12, 2021 at 5:21:37 AM UTC-7, nospam wrote:
In article <sml6f8$r36$1...@dont-email.me>, J Burns <bu...@nospam.com> wrote:
The guy is as loved as a drunken karaoke singer -- and with good reason.An OS may know the logical location of files but not their physical location on an SSD. The SSD knows the physical location of data but not what files it belongs to.that is normal and not an issue whatsoever.
TRIM allows an OS to tell an SSD what data hasit does not.
been deleted. It sounds as if in this case, the OS keeps track of the physical location of data.
Perhaps Apple doesn't support TRIM fornope, it's because some ssds have poor implementations of trim, which
third-party SSDs because it may not know where an unfamiliar SSD puts data.
can potentially cause data loss. apple does not want to test every
single ssd out there to be sure it works properly.
When CCC copies an OS onto an SSD, it seems that the OS on the SSD can't be aware of the physical location of the files on the SSD.that does not matter at all.
In effect,no it doesn't.
cloning turns an OEM SSD into a third-party SSD,
and Apple won't enabletrim is not needed on modern ssds, however, it can be enabled if the
TRIM.
user really wants it.
Without TRIM, I guess in the event of Sleep, it can't tell the SSDnope. that makes absolutely no difference whatsoever. it will resume
to cease garbage collection. Would it be a calamity if the computer went to sleep during garbage collection?
when the computer wakes, just as everything else does.
My theory is that sometimes my Mac won't sleep because the OS is waiting for the SSD to finish garbage collection, a process the OS can't interrupt without TRIM. If I erased my SSD to make a fresh install of OS 12, maybe I'd have TRIM.that theory has no basis in reality.
It was Snit sock HWSNBN who flooded RonB's site millions of times and
denied it. This forum is a puss-filled cyst.
Snit sock HWSNBN claims to be the programming master, let's see him
put up a variant minus the shipping/handling routines.
--
This Trick Gets Women Hot For You https://www.walmart.com/browse/books/family-kids-books/cary-fagan/3920_582053_585918/YnJhbmQ6Q2FyeSBGYWdhbgieie
<https://www.truepeoplesearch.com/results?name=4234911448&Diesel&Gremlin&Dustin_Cook>
https://swisscows.com/web?query=%22narcissistic%20bigot%22
Steve Carroll the Narcissistic Bigot
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 185 |
| Nodes: | 16 (1 / 15) |
| Uptime: | 04:30:11 |
| Calls: | 3,676 |
| Calls today: | 2 |
| Files: | 11,149 |
| Messages: | 3,447,353 |