Write caching

When using Windows, enabling or not write caching for an EHD may be important. Is write caching a consideration for EHDs when running OS X?
If so, where is the setting selected? I can't find anything about write caching in Disk Utility.
Thanks.

Try checking "enchanced productivity" (or kind of - I've got russian Vista, not english ) checkbox in HDD properties in Device Manager.
Message Edited by skripatch on 07-14-2008 10:37 AM
//help will save the world

Similar Messages

Disk write cache corruption on an external hard disk

Recently I purchased an external hard disk, to put all of my pictures of my baby due to space limitations on my internal laptop drive. Since my Canon camera 10 megapixel pictures take up a ton of space this was occurring at an alarming rate. My intention was also to back up to DVD but never got to it. This is both a comment and a question.
Now said baby, is getting really good at pulling cords etc. He managed to do this on the external drive firewire cable. As far as i know the drive was not in the process of actually writing. However, after a few minutes and trying to re-plug the drive the OS crashed with a Grey Screen of Death hardware error that tells you that you need to push the power button..
This apparently corrupted the drive's directory. Upon reboot the drive would not mount. Since there were time machine backups on the drive too Diskwarrior was not able to reconstruct the drive in the built in memory available on the computer. Time machine stores millions of files and Diskwarrior apparently wants to keep it all in memory at once. Since my computer has 2GB you would hope that would be enough but apparently not. So that failed. Other utilities seemed to be able to find the files but not restore the directory. I also took it to the apple store they were not able to recover it.
I have to say this is extremely distressing, and hard to believe that a simple accident like this could cost the loss of thousands of pictures. I did send it to a rescue company but that was expensive but I think apple needs to do something about this situation.
On Windows there is a way to disable the write cache for external drives. This is not available for Mac OS X. This would prevent this rather common occurrence of a plug accidentally becoming disengaged when the drive is not in the process of writing. This reduces the odds but I still think apple, in order to become clearly superior, needs a better solution.
I know Apple has experimented with ZFS would this not eliminate this possibility of this kind of disaster? Is this in Snow Leopard desktop? I know they are thinking this is a business customer focused technology but clearly if it can eliminate this kind of thing then I think it is extremely useful to their non server customers. Perhaps there are other ways of dealing with this issue but ZFS is designed to deal with these issues. HFS+ is extremely fragile to disk corruption.
I know my situation is not that uncommon and this is not the first time this has happened to me with an external drive. You would think I had learned. I hate to think of how many other people have had the same thing happen to them.

Disabling a write cache would not help you with the problem you are having. Besides the write cache is on the hard drive and operates independently of the operating system. But nothing can protect you from disconnected an external drive improperly, and if the drive is in the process of being written to, and the problem comes from directory corruption, not file corruption, as in the case you have described, disabling a write cache would not have made any difference.
For the future the magic word is: Backups.
< Edited by Host >

Can't write cache file for while creating domain in soa 11.1.1.5 on HP-UX

Hi,
Installing SOA 11.1.1.5 on HP-UX and during domain creation/configuration I am getting the below errors
**sys-package-mgr: can't write cache file for**
and have lots of cache file errors for different packages
Any idea what might be wrong and whats the cause of these errors and is it safe to ignore these errors if not what is the work arround. As I already looked at the below post but I don't find */var/tmp/wlstTemp* on my machine as suggested in the post below.
SOA 11.1.1.5 install got can't write cache file
So wondering if there's anything else I can do i.e. while creating or configuring a Domain pass some parameter to config.sh etc.
Thanks

Hi,
I don't see python.cachedir in config.sh. Here is config.sh
#!/bin/sh
mypwd="`pwd`"
# Determine the location of this script...
# Note: this will not work if the script is sourced (. ./config.sh)
SCRIPTNAME=$0
case ${SCRIPTNAME} in
/*) SCRIPTPATH=`dirname "${SCRIPTNAME}"` ;;
*) SCRIPTPATH=`dirname "${mypwd}/${SCRIPTNAME}"` ;;
esac
# Set the ORACLE_HOME relative to this script...
ORACLE_HOME=`cd "${SCRIPTPATH}/../.." ; pwd`
export ORACLE_HOME
# Set the MW_HOME relative to the ORACLE_HOME...
MW_HOME=`cd "${ORACLE_HOME}/.." ; pwd`
export MW_HOME
# Set the home directories...
. "${SCRIPTPATH}/setHomeDirs.sh"
# Set the config jvm args...
CONFIG_JVM_ARGS="${CONFIG_JVM_ARGS} -DCOMMON_COMPONENTS_HOME='${COMMON_COMPONENTS_HOME}'"
export CONFIG_JVM_ARGS
# Delegate to the main script...
"${WL_HOME}/common/bin/config.sh" "$@"Thanks

Is there a way to turn off using ram as intermediary when transfering files between 2 internal hdds? (write cache is off on all drives)

right forum? first time here. none of the options seem perfect. so i guess this applies to 'setup.' i tried to describe what's happening verbosely from the start of a file transfer to completion of writing file to 2nd hard drive.
win 7 64bit home - i2600k 3.4ghz - 8gb of ram - 2hdd 1 ssd
I have this problem when transferring files between 2 internal hard drives. one is unhealthy (slow write speeds but not looking for advice to replace it because it serves its unimportant purpose). so, the unhealthy drive drops into PIO mode - that's acceptable.
however, a little over 1gb of any file transfer is cached in RAM during the file transfer. after the file transfer window closes, indicating the transfer is "complete" (HA!), it still has 1gb to write from RAM which takes about 30minutes. This would
not be a problem if it did not also earmark an additional 5gb of ram (never in use), leaving 1gb or less 'free' for programs. this needlessly causes my pc to be sluggish - moreso than a typical file transfer file between 2 healthy drives. i have windows write
caching turned off on all drives. so this is a different setting i can't figure out nor find after 2 hours of google searches.
info from taskmanager and resource monitor.
idle estimates: total 8175, cached 532, available 7218, free 6771 and the graph in taskman shows about 1gb memory in use.
at the start of a file transfer: 8175, 2661, 6070, 4511free and ~2gb of ram used in graph. No problems, yet.
however, as the transfer goes on, the free ram value drops to less than 1gb (1gb normal +1gb temporary transfer cache +5gb of unused earmarked space = ~7gb), cached value increases, but the amount of used ram remains relatively unchanged (2gb
during transfer and slowly drops to idle values as remaining bits are written to the 2nd hard drive). the free value is even slower to return to idle norms after the transfer completes writing data to 2nd hard drive from RAM. so, it's earmarking an addition
5gb of ram that are completely unused during this process. *****This is my problem*****
Is there any way to turn this function off or limit its maximum size. in addition to sluggishness, it poses risk to data integrity from system errors/power loss, and it's difficult to discern the actual time of transfer completion, which makes it difficult
to know when it's safe to shutdown my pc (any data left in ram is lost, and the file transfer is ruined - as of now i have to use resmon and look through what's writing to disk2 -> sometimes easy to forget about it when the transfer window closed 20-30minutes
ago and the file is still in the process of writing to the 2nd disk).
Any solution would be nice, and a little extra info like whether it can be applied to only 1 hard drive would be excellent.

Thanks for the reply.
(Although i have an undergrad degeee in computers, it's been 15years and my vocab is terrible. so, i will try my best. keep an open mind. it's not my occupation, so i rarely have to communicate ideas regarding PCs)
It operates the same way regardless of the write-cache option being enabled. It's not using the 5gb for read/write buffer - it's merely bloating standby memory during the transfer process at a rate similar to the write speed of destination (for my situation).
at this point i don't expect a solution. i've tried to look through lists of known memory leaks but i dont have the vocabulary to be 100% certain this problem is not documented. as of now it can't affect many people - NAS's with low bandwidth networks, usb
attached storage etc. do bugs get forwarded from these forums? below i can outline the consistent and repeatable nature not only on my pc but on others' pcs as well (2012 forum post i found).
I've been testing and paying a little more attention and i can describe it better:
Just the Facts
Resmon Memory Info: "In Use" stays consistent ~1gb (idle amount and roughly the same when nothing else is running during file transfer)
"Modified" contains file transfer
data (meta data?) which remains consistent at little over 1gb (minor fluctuations due to working as a buffer). After the file transfer window closes "Modified" slowly diminishes as it finishes lazy writing (i believe that's the term). I forget idle
pc amount, but after transfer this is ony 58mb)
"Standby" as the transfer starts it immediately rises to ~2gb. I'm sure this initial jump is normal. However, it will bloat well over 5gb over time with a large enough transfer increasing at a consistent rate during the entire transfer
process. the crux of the matter.
"Free" will drop as far as 35-50megabytes over time.
as the transfer starts, the "Standby" increases by an immediate chunk then at a slow rate throughout entire transfer process(~1mb/s). once writing metadata to RAM no longer occurs, the "Modified" ram slowly (@500kb/s matching resmon disk
activity for that file write) diminishes as it finishes lazy writing, After file is 100% written to destination drive, "Standby" remains a bloated figure long after.
a 1.4gb transfer filled 3677MB of "Standby" by the time writing finished and modified ram cleared. after 20minutes, it's still bloated at 3696MB. after 30-40mins it's down to 2300mb - this is about what it jumps immediately to when transfer starts
- it now remains at this level until i reboot.
I notice the "standby" is available to programs. but they do not operate well. e.g. a 480p trailer on IMDB.com will stop-and-go every 2-3seconds (stream buffers fine/fast) - this would be during the worst case scenario of 35-50mb "Free"
ram. my pc isn't and never was the latest and greatest, but choppy video never happens even with 1 or 2 resource hogs running (video processing/encoding, games, etc).
Conjecture Below
i think it's a problem when one device is significantly slower at writing than the source device - this is the factor that i share with others having this problem. when data is written to modified ram then sent to destination, standby memory is expanded
until it completely or nearly fills all available RAM - If the transfer size is large enough relative to how slow the write speed of destination device is. otherwise it fills it up as much as the file size/write speed issue allows. the term "memory leak"
is used below but may not technically be one, but it's an apt description in layman's terms.
i saw a similar post in these forums (link at end). My problem is repeatable and consistent with others' reports. I wasn't sure if i should revive it with a reply. some of these online message boards (maybe not this one) are extremely picky
and sensitive, lol.the world will end if an old thread revives - even if for a good reason.
i can answer some of the ancillary issues. one person (Friday, September 21, 2012 8:33 PM) mentions not being able to shutdown, i asume he means stuck on the shutdown screen - this is because lazy writing has not completed - his nas write speed is significantly
slower than reading from source - the last bits of data left in ram still needs to be writen to the destination. shutdown will stall for as long as needed until the data finishes writing to destination to prevent data loss.
another person (Monday, September 24, 2012 6:31 PM) mentions the rate of the leak, but the rate is more likely a function of read speed from source relative to write speed of destination. which explains why my standby expands closer to a 1:1 ratio compared
to his 1:100 (he said 10mb per 1000mb)
we all have the same exact results/behaviour, but slightly different rates of bloating/leaking. as the file is written from from the ram to the destination, standby increases during this time - not a problem if read and write speeds are roughly equal (unless
your transfering a terabytes then i bet the problem could rear its head). when writing lags, it gives the opportunity for standby ram to bloat with no maximum except the amount of installed ram. slower the write speed, the worse the problem.
The reply on Wednesday, September 26, 2012 3:04 AM has before and after pictures of exactly what i described in
"Just the Facts". Specifically the resmon image showing the Memory Tab.
The kb2647452 hotfix seems to do some weird things relative to this problem. in the posts that mention they've applied it: after file completes it looks like the "standby" bloat is now "in use" bloat. as per info from Tuesday, October
09, 2012 10:36 PM - bobmtl in an earlier post applies the patch. compare images from earlier posts to his post on this date. seems like a worse problem. Also, his process list indicates it's very unlikely they add up to ~4gb as listed in the color coded bar.
wheres the extra gb's coming from? likely the same culprit of what filled up "standby" memory for me and others. it looks like this patch relative to this problem merely recategorizes the bloat - just changes the title it falls under.
Link:
https://social.technet.microsoft.com/Forums/windows/en-US/955b600f-976d-4c09-86dc-2ff19e726baf/memory-leak-in-windows-7-64bit-when-writing-to-a-network-shared-disk?forum=w7itpronetworking

Can't Enable write cache on disk with event ID 34

One of our clients has a performance issue similar this one:
Performance issue on TS as VM - Resolution with screenshots
After monitoring it we found the problem is write cache. We improve the
... I
checked all other VMs, the Enable advanced performance is unchecked. Do you
... A: To improve the performance for the disk, here are some proactively action
plans:.
www.chicagotech.net/remoteissues/tsperformance1.htm
However, when we follow the resolution to Enable write cache, it doesn't take it with this event:
Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 34
Description:
The driver disabled the write cache on device \Device\Harddisk0\DR0.
How to fix it?
Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Hi,
By default, write caching is disabled on a disk that contains the Active Directory database (Ntds.dit). Also, write caching is disabled on a disk that contains the Active Directory log files. By doing this, you enhance the reliability of the Active
Directory files.
Thus if it is a DC, try to move the Active Directory database and the Active Directory log files off of a disk in which you need to enable write caching.
If you have any feedback on our support, please send to [email protected]

How to disable hard disk write caching?

How to disable hard disk write caching?
Is there something similar to Windows: http://support.microsoft.com/kb/259716/en

Manually mount the disk, disabling the cache. With the default mount mechanisms, no. Details.

Query performance problem - events 2505-read cache and 2510-write cache

Hi,
I am experiencing severe performance problems with a query, specifically with events 2505 (Read Cache) and 2510 (Write Cache) which went up to 11000 seconds on some executions. Data Manager (400 s), OLAP data selection (90 s) and OLAP user exit (250 s) are other the other event with noticeable times. All other events are very quick.
The query settings (RSRT) are
persistent cache across each app server -> cluster table,
update cache in delta process is checked ->group on infoprovider type
use cache despite virtual characteristics/key figs checked (one info-cube has1 virtual key figure which should have a static result for a day)
=>Do you know how I can get more details than what's in 0TCT_C02 to break down the read and write cache events time or do you have any recommandation?
I have checked and no dataloads were in progres on the info-providers and no master data loads (change run). Overall system performance was acceptable for other queries.
Thanks

Hi,
Looks like you're using BDB, not BDB JE, and this is the BDB JE forum. Could you please repost here?:
Berkeley DB
Thanks,
mark

SOA 11.1.1.5 install got can't write cache file

Hi,
I installed 2 node cluster of SOA 11.1.1.5 on linux and during domain configuration I got errors i.e.
**sys-package-mgr: can't write cache file for**
Installation was done and all the servers start/stop fine am able to deploy the processes, am able to access all the urls fine everything coming up fine BAM, SOA, OSB etc . Just wondering if the error above have any effect on the installation or any piece that might not work. As I have already did the installation and ignored those errors above so just wanted to see if anything I need to look for.
Thanks

Hi,
It's a cluster install and took sometime to do the full install so it will be a pain to re-install everything over. Currently have tested the processes and seems to be working fine.
Also I don't find
/var/tmp/wlstTemp
I do see wlstTemp appended with linux users who did Oracle SOA install.
Also in-future when creating a new environment besides the above chmod 777 on /var/tmp/wlstTemp is there any parameter we can supply when running config.sh. I read some where that in-order to get by these errors at the time of domain creation we can also pass some parameter.
Thanks

Getting "Unable to write cache file" message in DW CS4

I was having some issues with a Javascript message, so looking for possible solutions, I came across “Deleting a Corrupted Cache File” in the Index to Dreamweaver FAQ located on this forum. I decided to give it a shot and carefully followed the instructions on my Windows XP, deleting the suggested cache file in my Configuration folder. That didn’t help make my Javascript message go away, though I did eventually find a work-around for that issue.
However, after deleting this cache file, I began to get the following message every time I close my program or change sites in local files, “Unable to write cache file ‘C:\Documents and Settings\...” the message ends with the site name and the extension .dws. If I go to Manage Sites and turn off the Enable Cache button for that particular site, I no longer get the message. But if I turn the Enable Cache Button back on, I get the message again. It gives this same message for all the sites.
I’m hoping others have had this issue and there is a simple fix. I can’t say for sure that deleting the cache file in the configuration folder caused this, but it was only after that I began noticing the problem, so it would make sense the two are likely related.
Also, I wonder how important the cache is. I could just turn off the Enable Cache Button for all the sites as a work-around if there's no quick fix and if it’s no big deal.
-Steve

I was having some issues with a Javascript message, so looking for possible solutions, I came across “Deleting a Corrupted Cache File” in the Index to Dreamweaver FAQ located on this forum. I decided to give it a shot and carefully followed the instructions on my Windows XP, deleting the suggested cache file in my Configuration folder. That didn’t help make my Javascript message go away, though I did eventually find a work-around for that issue.
However, after deleting this cache file, I began to get the following message every time I close my program or change sites in local files, “Unable to write cache file ‘C:\Documents and Settings\...” the message ends with the site name and the extension .dws. If I go to Manage Sites and turn off the Enable Cache button for that particular site, I no longer get the message. But if I turn the Enable Cache Button back on, I get the message again. It gives this same message for all the sites.
I’m hoping others have had this issue and there is a simple fix. I can’t say for sure that deleting the cache file in the configuration folder caused this, but it was only after that I began noticing the problem, so it would make sense the two are likely related.
Also, I wonder how important the cache is. I could just turn off the Enable Cache Button for all the sites as a work-around if there's no quick fix and if it’s no big deal.
First of all, only delete cache files when DW is shutdown.
Also, there are a few different caches. That article only addresses 1 of them. Take a look at this TechNote to be able to find the Site .dws cache files:
http://kb2.adobe.com/cps/598/5989f7f4.html
HTH,
Randy

Check/Turn on Disk write cache

Dear all,
I read one of the Oracle metalink, and it said, we need to turn on the 'disk write cache' for better file writing throughput, but I am not very sure, whether currently, my newly installed Solaris 9 system have the 'disk write cache' turned on. Please advise,
- Whichcommand, I can use to check the current setting?
- How can I turn the 'disk write cache' if it is current off
Thanks
Regards,
Eddie

There are so many things that this could be, particularly when Oracle is brought into play, that I wouldn't know where to really start.
For example:
* Are you using parallel directories? If so, are all of the directories on separate hard drives? Better yet, are they on separate SCSI chains?
* Are you using UFS or VxFS?
* Did you run an iostat and vxstat to isolate where the slowness is occurring?
* Are you using any kind of software RAID?
* What's the speed of your drives?
* Are your boot disks mirrored? (Yes, boot disk performance can kill an entire server even if the applications and data are not on the boot disk.)
* Do you have inode access time enabled or disabled?
* Have you fine-tuned your kernel settings for better disk utilization?
Unfortunately, disk optimization is hell to diagnose. I know because I just went through weeks tuning the I/O of our production server. It's NOT fun.

Write cache not utilized for a LUN

I am running into this test result that I can't explain, please help. the test is running 5 thread of file creation at 5G each.
This is on 7420, testing is done within the same pool that uses a pair of mirrored log at 76G each.
one LDOM has 64G of memory, LUN is 1T, the "Write Cache Enabled" check box doesn't make hardly any difference, I can see that the log disks are being used, is that because the pool was created using the logs?
the other LDOM has 96G of memory, LUN is 3.5T, when the "Write Cache Enabled" is checked, I clearly see the log disks are hardly used, the other disks are getting a lot more actions than the log disks. But when the "Write Cache Enabled" is not checked, I see the log disks are used, they would have more activities on them. However the test results show that without using the log disks, I get faster throughput. So disk logzilla used, but faster; while logzilla used, I get slower results. What am I missing here?
I attached a pic for show what I saw, the highlighted is one of the log disks.
thanks for your help!

Dear Arun,
You wrote
=============
Cache is first in first out... if you exceute too many queries then cache might force out the first query for want of memory. Check the cache immediately after the query is ruin once then you should also check the cache settings for the query in RSRT to see if cache is enabled for the query. Ideally the option for cache should be " Main memory cache with swapping " in RSRT.
==============
I executed my query in question as the first query but no cache was created. The options for the cache mode was 'H Query reads data upon navigation' and 'main memory without swapping' along with a tick in the 'Query cache added to Delta' checkbox.
Just to check, i went on removing formulaes and calculated key figures and free characteristics from the query one by one and in the end the cache did get created for the same query. But I still could not pinpoint the exact reason for the query not producing cahce in its original form.
It only makes me think that there may be a particular scenarios or a peculiarity pertaining to the design of a query, that would prevent its cache being generated.
regards,
Kulmohan

Write-caching policy not restored after reboot.

The problem I've been experiencing is very similar to this old one from server 2000:
http://support.microsoft.com/kb/290757
After a system restart, the write-caching policy is not being saved on the server and the settings are not persistent.
The system hardware is an Intel RST express chipset, and the Intel Raid 5 Volume (Microsoft version) driver is 6.2.9200.16384 (win3_rtm.120725-1247)
are there any hotfixes available for this driver to correct the problem on server 2012?

ya, I can give that a try.. why not.
Do you have any hints on the registry paths for those values, or is there a quick cmdlet for the cache policy?
Of course you can. See:
Enable or Disable Disk Cache
http://blogs.msdn.com/b/winsdk/archive/2009/10/09/enable-or-disable-enable-write-caching-on-disk-behavior-on-disk.aspx
You can write a tiny app in C or C# enabling / disabling disk cache settings and use PowerShell to spawn it, handle scripting and scheduling.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

EventId: 32, disk - The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled

Virtualized 2012 R2 Domain Controller running on hyper-V. Every boot lists the following error three times:
EventId: 32, disk - The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled.
Data corruption may occur.
Having checked the virtual SCSI disks all have their write cache enabled, is this correct or do I need to take some action to prevent these events?

Hi,
This is normal and you can't change it. This tells AD that write caching is enabled so it uses a different method to store information.
http://www.hyper-v.nu/archives/hvredevoort/2013/07/keeping-your-virtual-active-directory-domain-controllers-safe/
More information there.
Thanks
Denis
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
Blog: http://www.windows-support.co.uk
Twitter: LinkedIn:

Raid Utility. Write cache disable due to insufficient battery charge

Is it the baterry? It gaves me the message every day at star.

The write cache is a performance-enhancing technique that improves write performance.
Ordinarily (without the cache), the host system sends data to the RAID to be stored. The RAID controller works out where the data should be written (based on the RAID parameters of the array), spins the disks, writes the data, verifies the write and then signals back to the host that the write was performed succesfully.
Sounds like a lot - and it is - but it all happens in a few milliseconds so you don't really notice too much - especially at low load.
At higher loads, though, it may take longer to queue the incoming requests - work out where to write the data, spin the disks, wait for other data to be written, etc.
That's where the cache comes in. With the write cache enabled, the host sends data to be written to the array. The controller stores this data in cache and immediately sends a confirmation back to the host. This lets the host get on with other tasks (possibly including sending more data to write), without waiting for the (slower) disks.
Writing to cache, since it's really just RAM, can be orders of magnitude faster than writing to disk, so the host gets a confirmation quicker, and it's not stuck waiting for other tasks to write to the disks, too.
There is a risk, though - if the power goes out, for example, there's a risk that any data in the (volatile) cache doesn't get written to disk in time and data loss/corruption occurs. That's where the battery comes in. It ensures the RAID can maintain that cache data (for up to 72 hours), so that it can be written to disk when the power is restored.
If the XServe RAID can't rely on the battery it disables the write cache to avoid the potential data loss.
As for whether you'll notice, that depends on your use pattern. Small writes won't have much of an impact, and it doesn't significantly affect read performance, so it's up to you.
Personally, I'd look to fix the issue, but that's me.

Can't enable HDD write caching

I recently upgraded my PC. I am using Vista x64 on a MSI P35 mobo and a Seagate SATA II 250GB drive and a 36GB Raptor (SATA I). It has the newest 1.8 BIOS and newest Intel AHCI drivers.
The problem is this: I can't enable write caching on either hard drive in the Device Manager. It is there to check but below it it says something like "This device does not support write caching."
Now I am not dumb, and the Raptor used to have write caching enabled on my old nForce4 mobo in Vista. I have AHCI enabled in the mobo BIOS too. Does anybody kno what is causing this?
Also, does anybody knw of any good utilities that will tell me the fatures that are enabled (NCQ, SATA 3.0, etc..) that doesn't require an install? I just like to execute utilities and get results without installing stuff (like CPU-Z and GPU-Z).

Hi,
By default, write caching is disabled on a disk that contains the Active Directory database (Ntds.dit). Also, write caching is disabled on a disk that contains the Active Directory log files. By doing this, you enhance the reliability of the Active
Directory files.
Thus if it is a DC, try to move the Active Directory database and the Active Directory log files off of a disk in which you need to enable write caching.
If you have any feedback on our support, please send to [email protected]

Write caching

Similar Messages

Maybe you are looking for