- Remove From My Forums
-
Общие обсуждения
-
На сервере Windows Server 2012 в журнале событий несколько раз встречал такую ошибку.
Источник: Defrag
ID: 257
Том «(C:)» не был оптимизирован из-за ошибки: Ни оптимизация памяти, ни анализ слоев не будут выполняться, если слои менее 8 МБ. (0x8900002D)
Что это за проблема?
Все ответы
-
Сегодня столкнулся с аналогичной ошибкой.
-
https://support.microsoft.com/en-us/kb/2964429
Workaround
To temporarily work around this problem, either disable the Storage Optimizer «Optimize drives» service or exclude the thin provisioned LUNs from the scheduled task.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More information
There’s no need to run Storage Optimizer on thin provisioned LUNs that use an allocation size (also known as slab size) of less than 8 MB. Thin provisioned LUNs that have a smaller slab size manage space more efficiently,
and the benefits of defragmenting them are not as great.When you run the Storage Optimizer with the Analyze switch at a command prompt or a PowerShell prompt (for example, defrag
g: /a or Optimize-Volume -Analyze g –Verbose) on a thin provisioned LUN that’s using a small slab size, the command does not execute, and you receive the following error message:Neither Slab Consolidation nor Slab Analysis will run if slabs are less than 8 MB.
This is expected behavior because slab consolidation and slab analysis has been disabled on thin provisioned LUNs that have a slab size of less than 8 MB.
-
Изменено
Anton Istomov
20 июля 2015 г. 18:17
-
Изменено
-
Решение здесь — https://support.microsoft.com/en-us/kb/2964429
Для windows 8.1 & windows server R2 дополнительно должен быть установлен апдейт
https://support.microsoft.com/en-us/kb/2919355
-
Еще одна подобная ошибка.
Источник: Defrag
ID: 257
Том «Зарезервировано системой» не был оптимизирован из-за ошибки: Параметр задан неверно. (0x80070057)
- Remove From My Forums
-
Question
-
After upgrading to Windows 8.1, I keep getting Event id 257, Defrag: «The volume TI10664900J (C:) was not optimized because an error was encountered: The parameter is incorrect. (0x80070057)» in Event Viewer errors.
[
Name]Microsoft-Windows-Defrag Keywords 0x80000000000000 [
SystemTime]2013-11-12T16:21:45.000000000Z The parameter is
incorrect. (0x80070057)00000000A40500005105000000000000629468641336AAB85B55B1B5B038000000000000 Any help would be appreciated.
Answers
-
Hi,
This issue could be caused if Defragment take operation on SSD. And as we know SSD cannot be defragged.
To check if your SSD has been defragmented, please run following powershell command:
Get-EventLog -LogName Application -Source «microsoft-windows-defrag» | sort timegenerated -desc | fl timegenerated, message
Judging by the drive letter, you can easily see if your SSD drive gets defragmented. The SSD volume below has been correctly re-trimmed first, but then erroneously defragged.
You can try following steps to avoid defragmentation of your SSD:
Exclude SSD from automatic maintenance
Open the disk optimizer (dfrgui):
-
Press «Change Settings». -
Press «Choose» and remove checkboxes from SSD volumes.
In addition, I will document it and confirm with product team if it is by design.
Keep post.
Kate Li
TechNet Community Support-
Marked as answer by
Wednesday, November 20, 2013 4:46 AM
-
Event ID 257
The volume (C:) was not optimized because an error was encountered:
The parameter is incorrect. (0x80070057)
I have Windows 8.1 64 Bit (HDD) and lately I noticed the above event in my Event Viewer. I get every day 3 or 4 of these errors. Anyone found a solution to this ?
- SFC /SCANNNOW didn’t solve the problem: Resource Protection did not find any integrity violations.
Solutions that I did not try but might work
-
Basic steps to use diskpart to assign a drive letter to the system
partition-
Open an elevated command prompt.
-
Type diskpart and press Enter. You leave the standard command prompt and enter the diskpart utility. (Nothing exciting happens,
don’t worry.) -
Type list disk and press Enter to get a listing of the disks on the system. (More accurately, the disks visible to diskpart.) Figure
out
which disk contains the partition you want to assign a drive letter
to. -
Type select disk X, where X is the applicable disk number.
-
Type list partition and press Enter to get a listing of recognized partitions on disk X (from step 4). Your desired
partition will the
listed there. If not, go outside and enjoy nature. -
Type select partition Y, where Y is the applicable partition number.
-
Type assign letter=Z, where Z is the drive letter you wish to assign. Diskpart should reply: DiskPart successfully assigned the
drive letter or mount point.
Once the system recognizes the drive letter (a reboot may help; as I
mentioned, I did not reboot before the trim worked, but did have to
wait awhile), you should be able to defrag/trim.To unassign the drive letter:
A. Carry out steps 1 — 6 above.
B. Type remove and press Enter. Diskpart should reply: DiskPart
successfully removed the drive letter or mount point.I hope this helps.
-
-
I am not entirely sure why it helped, but after I had the same
issue (0x80070057 during defrag, chkdsk reports no errors) reseting
the journal seemed to fix it.Open an Administrator command prompt and make use of fsutil:
fsutil usn deletejournal /D volume pathname
fsutil usn createjournal m=max-value a=alloc-delta volume pathnameEg :
fsutil usn deletejournal /D C:
fsutil usn createjournal m=1000 a=100 C:Maybe it helps someone else as well.
The answers are from here
asked Jan 9, 2014 at 21:48
DevidDevid
6,26913 gold badges55 silver badges74 bronze badges
5
After doing some research, I found out that Microsoft released a Hotfix for this issue.
Symptoms
When you run the Disk Defragmenter (Defrag.exe) utility on a volume on a computer that’s running Windows 8.1 or Windows Server 2012 R2, the defrag operation fails. Additionally, event ID 257 is logged in the Application log. This event displays a «The parameter is incorrect» error message. In this case, you may be unable to optimize the volume for space efficiency.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
- Windows 8.1
- Windows Server 2012 R2
from KB Article Number: 2929874
B. Shea
1,2042 gold badges11 silver badges18 bronze badges
answered Apr 1, 2014 at 14:58
4
It often results from an ‘unusual’ (such as ^ & or $ ) character in a file or folder names. Therefore, suggest you use the System File Checker
sfc /scannow
Which will take some time to complete.
answered Jan 9, 2014 at 22:19
K7AAYK7AAY
9,4244 gold badges33 silver badges61 bronze badges
3
Solution by
Event Log Doctor
2016-05-31 14:44:40 UTC
Windows runs the defrag.exe utility via the Scheduled Tasks subsystem in an effort perform SSD maintenance and/or defrag drives automatically.
If the defrag.exe cannot defrag a volume, it will log event 257, even if other drives have been processed successfully.
In most cases (especially workstations) this event can be safely ignored and/or excluded from monitoring.
A bug fix appears to be available from Microsoft but does unfortunately not install on most systems.
I have got a strange issue that just begun on january 29th. I have a server that is getting a defrag error with the following details:
The volume (C:) was not optimized because an error was encountered: Neither Slab Consolidation nor Slab Analysis will run if slabs are less than 8 MB. (0x8900002D)
I have searched google up and down but can’t really understand what exactly this means. This is a virtual server running on VMware 6.5. When I go to the defag gui I can see that the hard drives are showing as «Thin Provisioned» but the strange thing is, other vm’s also with thin provision drives are showing in there respective gui as «Hard Disk Drives». Those machines are not getting this error. Can someone help me out here?
Following the installation of a new Veeam One platform on a Windows 2012 R2 server (now migrated to W2019), I encountered an issue with the deduplication and defragmentation of a partition on the HDD. An “Event 257 Slab Consolidation Not Optimized” appeared.
The volume (C:) was not optimized because an error was encountered: Neither Slab Consolidation nor Slab Analysis will run if slabs are less than 8 MB. (0x8900002D)
As a symptom, I found this message on Microsoft Support: “When you run the Disk Defragmenter utility (Defrag.exe) on a volume on a computer running Windows 8.1 or Windows Server 2012 R2, the defragmentation operation fails. In addition, event ID 257 is recorded in the application log. This event displays an error message “The setting is incorrect.”
Possible cause of Event 257 Defrag Slab Consolidation Not Optimized
There are several possible causes of the problem. But what we do know is that the problem occurs when defragmenting VM files, whether in Hyper-V or Netapp.
- What is your file system? NTFS, REFS? or Mon?
- the storage is shared ?
- Is it a RAID disk? (in my case yes)
- Are the disks SATA or is there SSD?
- As a reminder, SSDs don’t really like defragmentation
Using the Defrag.exe program or the ScheduledDefrag task we get this error message Event 257 Slab Consolidation Not Optimized. A first solution is to modify the task.
By default, if we go to the windows task explorer we call %windir%system32defrag.exe -c -h -k -g -$
1: How to resolve Event ID 257 Slab Consolidation Not Optimized
As in the previous picture, the first solution is to modify the task in the task scheduler.
- search for the ScheduledDefrag task in Microsoft –> Windows –> Defrag
- Right click and select “property”.
- Go to the “Action” tab
- Select the action and make it modify
- Remove the -k
- Save and run the task
The -k means “Perform section consolidation on specified volumes”. Here are all the options of the defrag.exe application (from microsoft)
/a | Perform an analysis on the specified volumes. |
/C | Perform the operation on all volumes. |
/d | Perform traditional defragmentation (this is the default). On a tiered volume, however, traditional defragmentation is performed only on the capacity level. |
/e | Perform the operation on all volumes except those specified. |
/g | Optimize storage levels on specified volumes. |
/h | Perform the operation with normal priority (the default value is Low). |
/i [n] | The level optimization would run for at most n seconds on each volume. |
/k | Perform section consolidation on the specified volumes. |
/l | Make a readjustment on the specified volumes. |
/m [n] | Run the operation on each volume in parallel in the background. At most n threads optimize the storage levels in parallel. |
/o | Perform the appropriate optimization for each media type. |
/t | Follows up an operation already in progress on the specified volume. |
/U | Print the progress of the operation on the screen. |
/v | Display the detailed output containing fragmentation statistics. |
/x | Perform a free space consolidation on the specified volumes. |
/? | Displays this help information. |
Now, either there are two cases, you have no more error messages and everything is ok, or you get a new error message “The volume (C:) was not optimized because an error was encountered: The operation requested is not supported by the hardware backing the volume (0x8900002A)”. In this case, I invite you to go to solution number 2. This is the most efficient one, thanks to powershell
2 : Powershell Defrag Optimize Volume
If the first solution to defragment and optimize your disk, especially for deduplication, did not work, you can switch to this much more efficient solution.
- Open a powershell console as administrator
- enter “Optimize-Volume -DriveLetter C -Defrag -Verbose
Normally, you should have solved your problem. If not, I invite you to leave a comment, I will answer it by trying to reproduce your system error. Also check this post on Microsoft Technet
Specialist in datacenter, powershell, virtualization, content creation and SEO is the founder of PeopleAreGeek. Passionate about video games when he was young, he was then taken by technology and knowledge sharing.