Log File Initialization Error Drive C
Support Guy, we highly recommend that you visit our Guide for New Members. Log File Initialization Error? Help, please? Discussion in 'All Other Software' started by mattbro75, Sep 16, 2004. Thread Status: Not open for further replies. Advertisement mattbro75 Thread Starter Joined: Jun 20, 2003 Messages: 76 When I reboot my system I get a pop-up error message from my Norton SystemWorks '03: header of pop-up window is: "Norton Protection: ATTENTION" The text in the box is: "Log File Initialization Error, Drive C:" If I X out of the window, or click ok approx 3/8 of the time I get the BSOD with a stop message referring to a driver for my Gravis Controller. I fail to see what the driver could have to do with a Log File error? This has me very nervous as I don't really wanna lose my drive. What's more, it's a very annoying little glitch. I've checked Symantec Consumer knowlegde base, and googled for fixes/info extensively. Please, any help/info would be GREATLY appreciated. mattbro75, Sep 16, 2004 #1 Sponsor mattbro75 Thread Starter Joined: Jun 20, 2003 Messages: 76 No one knows anything about this one? Help? mattbro75, Sep 16, 2004 #2 MFDnNC Joined: Sep 7, 2004 Messages: 49,014 Un-Install/Re-install or Dump NSW MFDnNC, Sep 16, 2004 #3 mattbro75 Thread Starter Joined: Jun 20, 2003 Messages: 76 So you think it's merely an issue with NSW and not with c:? mattbro75, Sep 17, 2004 #4 liufreeman Joined: Oct 18, 2004 Messages: 1 hi,i got the same problem. Whenever you restart the computer, a "Log file initialization error" appears. The message may also include the drives that are affected. To enhance the Recycle Bin's functions, Norton Utilities sets up a folder within the Recycled folder on the hard drives. If there is an error creating this folder, the "Log file initialization error" message appears. so you need to disable your norton protected re
RAM I have two physical Hardrives. My second hardrive is partitioned into D & E Just today, my computer starts up very slowly with a report 'Log File Initialization Error : Drive D' I can read Drive C and Drive E, can see directory of Drive D but cannot read the files. What could I do do to recover Drive D or do I have to reformat? Please help. TIA. Ron Guest, Feb 2, 2005 #1 Advertisements Mark L. Ferguson Guest Boot to the XP setup CD, and press 'r' for recovery console, run the command : CHKDSK /R -- Mark L. Ferguson (NOT an MS-MVP) FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.txt marfers notes for https://forums.techguy.org/threads/log-file-initialization-error-help-please.274522/ windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm .. "Dorado" <> wrote in message news:... >I am running Win XP, on P4 2.4GHz with 500MB RAM > > I have two physical Hardrives. My second hardrive is partitioned into > D & E > > Just today, my computer starts up very slowly with a report 'Log File > Initialization Error : Drive D' > > I can read Drive C and Drive E, can see directory of Drive D but cannot read > the files. http://www.pcreview.co.uk/threads/log-file-initialization-error-drive-d.137111/ > > What could I do do to recover Drive D or do I have to reformat? Please help. > TIA. > > Ron Mark L. Ferguson, Feb 2, 2005 #2 Advertisements Show Ignored Content Want to reply to this thread or ask your own question? It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum. Sign Up Now! Similar Threads Setup Initialization Error Paul, Nov 10, 2003, in forum: Windows XP Help Replies: 0 Views: 705 Paul Nov 10, 2003 Error Mssg: Windows Sockets Initialization Failed - Help Please!!!!!! Guest, Jan 29, 2004, in forum: Windows XP Help Replies: 3 Views: 1,300 roger Feb 1, 2004 Error msg: A temporary file needed for initialization....... Guest, Feb 16, 2004, in forum: Windows XP Help Replies: 4 Views: 11,258 roger Feb 19, 2004 Error reading setup initialization file Guest, May 28, 2004, in forum: Windows XP Help Replies: 0 Views: 370 Guest May 28, 2004 dwwin.exe error - dll initialization failed.... JS, Dec 1, 2004, in forum: Windows XP Help Replies: 3 Views: 545 Jatin Dec 4, 2004 temporary file needed/initialization/not found Guest, Feb 24, 2005, in forum: Windows XP Help Replies: 5 Views: 928 Guest Feb 25, 2005 A temporary file needed for initialization could not be created Guest, Mar 5, 2005, in forum: Windows XP Hel
Initialization ★★★★★★★★★★★★★★★ SQL Server Premier Field EngineeringDecember 22, 200915 Share 0 0 You may want to consider enabling Instant File Initialization (via SE_MANAGE_VOLUME_NAME a.k.a. "Perform volume maintenance tasks") for your SQL https://blogs.msdn.microsoft.com/sql_pfe_blog/2009/12/22/how-and-why-to-enable-instant-file-initialization/ Server startup/service account. This option allows for much faster data file allocations (CREATE AND ALTER FILE) but DOES NOT WORK FOR LOG FILE ALLOCATIONS. This is enabled for each instance via the "Perform volume maintenance tasks" local security policy. In a cluster you have to grant the right on all nodes. If there are multiple instances on a server or cluster, you should grant this right to each instance’s security group.
log file This permission keeps SQL Server from "zeroing out" new space when you create or expand a data file (it is not applied to log files). This helps performance for CREATE DATABASE, ALTER DATABASE, RESTORE, and AUTOGROW. It can have a significant positive impact on how long it takes to create or expand a data file, but there is a small security risk in doing so. That is because a file "delete" really just deallocates log file initialization the space and a new allocation can reuse that space which may still have data in it. When you do not zero out the existing space there is a possibility that someone could read data that you thought had been deleted. It is very common to turn Instant File Initialization on. Many shops consider the increased performance benefit to far outweigh the small security risk, but you must weigh the cost and benefits within your own environment. How to grant this right/permission (tested on Windows 2008) to each instance of SQL Server: · Run lusrmgr.msc on the server to find the appropriate group name for each instance of SQL Server. For example: SQLServer2005MSSQLUser$SERENITYHOME$KAYLEE (SQL 2005 named instance), SQLServerMSSQLUser$SerenityHome$WASH (SQL 2008 named instance), or SQLServerMSSQLUser$SerenityHome$MSSQLSERVER (SQL 2008 default instance). · Run secpol.msc on the server. · Under Security Settings on the left, go to Local Policies and under that to User Rights Assignment. · Under Policy on the right side, go to "Perform volume maintenance tasks" and double click on it · On the Local Security Setting tab click on the "Add User or Group" button · In "Select Users, Computers, or Group" o Click on "Locations" and choose either your local computer name (for local groups/standalone) or your domain (for domain groups/clusters) o Click on "Object Typ