This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Upon looking at event viewer under Error title:
The storage optimiser couldn't complete re-trim on (G:) because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)
Under Windows Logs it says that : The storage optimiser successfully completed defragmentation on (G:)
It says this for E, F , G drive which are all Hard drives. (In my system I have C drive which is operating system Samsung 980 PRO M.2 SSD, E Drive , F Drive and G Drive are all Hard drives
For C Drive my M.2 SSD it says : The storage optimiser successfully completed analysis on (C:) (Im guessing this is normal since it didnt do anything but analyse it right? I think the bug of it being not recognise by optimisation has been fixed since what was it ver 2004?)
From my understanding I thought this was a bug in ver 2004 with the whole Scheduled Optimisation? I guess it must be fixed for SSD's However in my case, I do believe that the re:trim is not available on hard drives right? So why is it trying to retrim a HDD? Is this still a bug and can I ignore it? Rather if not how do I fix it? (I have tried from another thread the winsat formal command but doing that didnt help or rather it gave a black screen and disappeared, tried DISM check health everything went ok, sfc scannow also came back good)
Currently on Windows 10 Pro Version 22H2 (OS Build 19045.2364)
As a further question, by these errors coming up like it trying to retrim and then defrag afterwards does this bug or error should we say wear down my drives faster because of this?
Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIL%3C/text%3E%3C/svg%3E)
Seagate IronWolfs do not have a TRIM, you are correct. There are two technologies of SMR, and many Seagate SMR drives do not use TRIM. There are pro and contras for a both technologies. WD mainly use a technology with TRIM support.
I recommend you ignore these events; they are typical for your hardware. They are similar to 10016 events that are a part of normal Windows operation.
Sorry, this is not a bug, this is expected behavior, even if it seems strange. The analogy: each car has a gas tank. Tesla does not have a gas tank. Obviously, this is Tesla bug, isn't it? ;)
Yes, this defrag is safe and should be considered as normal. If you'll see an SSD defragmentation, it is normal too, because it is needed for normal Windows operation.
The " SSD does not need defragmentation" words are half-truth unfortunately. But this is a long enough story.
An analogy again: car engine does not need gearbox for its operation. But a cars have a gearbox because the CAR needs it. Similarly, Windows needs a defragmentation even SSD itself does not need it.
Seagate IronWolfs do not have a TRIM, you are correct. There are two technologies of SMR, and many Seagate SMR drives do not use TRIM. There are pro and contras for a both technologies. WD mainly use a technology with TRIM support.
I recommend you ignore these events; they are typical for your hardware. They are similar to 10016 events that are a part of normal Windows operation.
Ah right, so it's like a bug then I can safely ignore, thanks Igor.
Is it safe for it defrag my drives on a weekly basis / automatic is this considered normal or should I turn it off / extend it?
> Im guessing this is normal since it didnt do anything but analyse it right?
Sorry, but this is not correct. Windows may need to defragment system drive regardless of its type. I see defragmentation of my SSD monthly. Please check 258 events in the application journal.> I do believe that the re:trim is not available on hard drives right?
Sorry, but this is not correct too. Many modern hard drives with SMR technology support TRIM. Western Digital's document with a description of the drives supporting TRIM is dated by 2016.So, there is no bugs with disk optimizing. Since 2004 version Windows tries to trim HDDs too, so if hard drive does not support TRIM, 0x8900002A error is registered and 264 event appears in Application journal. This is just a statement of the fact of the TRIM absence.
Please ask other questions if you have them.
I've checked for 258 and it says so far only I could find C drive Analysis and defrag E F G as mentioned above.
I don't believe I have TRIM on any hard drives as I looked on CrystalDiskInfo and it only shows my M.2 SSD with TRIM. ST8000NE001, ST16000NE000, ST8000DM004 are the hard drives
So how do I go about fixing this? - Is it ok to ignore these events or?
Upon research I believe the ST8000NE001 and ST16000NE000 are both CMR and ST8000DM004 is SMR? Although I don't think the SMR one has Trim?
> Im guessing this is normal since it didnt do anything but analyse it right?
Sorry, but this is not correct. Windows may need to defragment system drive regardless of its type. I see defragmentation of my SSD monthly. Please check 258 events in the application journal.
> I do believe that the re:trim is not available on hard drives right?
Sorry, but this is not correct too. Many modern hard drives with SMR technology support TRIM. Western Digital's document with a description of the drives supporting TRIM is dated by 2016.
So, there is no bugs with disk optimizing. Since 2004 version Windows tries to trim HDDs too, so if hard drive does not support TRIM, 0x8900002A error is registered and 264 event appears in Application journal. This is just a statement of the fact of the TRIM absence.
Please ask other questions if you have them.
