locked
Low Disk Space on SYS drive RRS feed

  • General discussion

  • Just in case anyone has a problem with their whs SYS drive running low on space, check the following. Open explorer>

    C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs

    Look for any large *.log file and delete it.  Our entire household was trying to print stuff tonight and we kept getting spooling errors.  I started checking files starting with anything that shouldn’t be there and moved on to the log files.  I came across a log file (chkdsk_c_fs_p.log) which I had to look at several times as I could not believe the size of it (14 Gigs) yes that is right 14 gigabytes worth of text file/log file.  


    jd

    Saturday, November 8, 2008 5:55 AM

All replies

  • On the other side - if you get such huge log files, this is not normal in most configurations. So you should try to figure out, what is the root cause for that much logging.
    Best greetings from Germany
    Olaf
    Saturday, November 8, 2008 1:13 PM
    Moderator
  • a5_ACES said:

    Just in case anyone has a problem with their whs SYS drive running low on space, check the following. Open explorer>

    C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs

    Look for any large *.log file and delete it.  Our entire household was trying to print stuff tonight and we kept getting spooling errors.  I started checking files starting with anything that shouldn’t be there and moved on to the log files.  I came across a log file (chkdsk_c_fs_p.log) which I had to look at several times as I could not believe the size of it (14 Gigs) yes that is right 14 gigabytes worth of text file/log file.  


    jd



    Have you seen this error occur again?

    Thank you
    Lara Jones [MSFT] Windows Home Server Team
    Wednesday, November 12, 2008 8:57 PM
    Moderator
  • Hello,

    I'm having the same problem as mentioned above.

    All disk space on c is gone because of 14gb  wort of log files !

    I manually deleted them but they keep coming back after a couple of days.

    Any ideas on how to solve this would be much appriciated.

    Thanks in advance !

    Jos van Veen
    Tuesday, June 9, 2009 9:17 PM
  • Hello,

    I'm having the same problem as mentioned above.

    All disk space on c is gone because of 14gb  wort of log files !

    I manually deleted them but they keep coming back after a couple of days.

    Any ideas on how to solve this would be much appriciated.

    Thanks in advance !

    Jos van Veen
    Which log files are out of control i.e. large?

    Thanks!

    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Tuesday, June 9, 2009 9:23 PM
    Moderator
  • I just deleted most of them and I'm onlu left with one in the trash bin "DEUtil" and then date and numbers.

    Some of the lof files are 3Gb + ???.

    I've deleted some add-ins hope that solves it ?

    Any ideas of what it could be.

    Thanks for the quick reply.

    Jos van Veen
    Tuesday, June 9, 2009 9:53 PM
  • I'm currently trying to delete 32Gig of these files.  All the large ones are "DEUtilxxxxx.log".  They come in at 840,000KB each.

    Anyone have a clue as to what could be causing them?  None of my editors will open them due to size.

    Additional:
    I finally opened one of the log files (can you believe WordPad was able to open it!?!) and it is full of:

    [8/15/2009 5:20:34 PM c34] Audit Grace Period is set to: 1440

    [8/15/2009 5:20:34 PM c34] ***Starting Primary Pass

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\26a97ea9545ce47964520728ec3994

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\26a97ea9545ce47964520728ec3994\amd64

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\26a97ea9545ce47964520728ec3994\i386

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\d50ede359daaf07216f52d6ef6df

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\folders

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},\DE\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},1100000000acf5

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},1100000000acf5

    [8/15/2009 5:20:34 PM c34] Suppressing QSM error in backup folder

    [8/15/2009 5:20:34 PM c34] Info for D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Control.4096.dat

    [8/15/2009 5:20:34 PM c34] State = Migrated NumberOfShadows = 1

    [8/15/2009 5:20:34 PM c34] Shadow(0) Volume(81757893-04b0-40cc-9876-9b038b52734b) State(Unknown)

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},200000000ad18

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},200000000ad18

    [8/15/2009 5:20:34 PM c34] Suppressing QSM error in backup folder

    [8/15/2009 5:20:34 PM c34] Info for D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\CONVERT1.BackupSet.dat

    [8/15/2009 5:20:34 PM c34] State = Migrated NumberOfShadows = 1

    [8/15/2009 5:20:34 PM c34] Shadow(0) Volume(81757893-04b0-40cc-9876-9b038b52734b) State(Unknown)

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},1200000004830f

    [8/15/2009 5:20:34 PM ba0] DEFilter!DEOpenFile: Error c0000001 from LookupVolumeAndNameForGuid on 81757893-04b0-40cc-9876-9b038b52734b

    [8/15/2009 5:20:34 PM c34] OpenedFile::Open: Error 31 opening {81757893-04B0-40CC-9876-9B038B52734B},1200000004830f

    [8/15/2009 5:20:34 PM c34] Suppressing QSM error in backup folder

    [8/15/2009 5:20:34 PM c34] Info for D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\CONVERT1.C.FileRecordHash.4096.dat

    [8/15/2009 5:20:34 PM c34] State = Migrated NumberOfShadows = 1

    [8/15/2009 5:20:34 PM c34] Shadow(0) Volume(81757893-04b0-40cc-9876-9b038b52734b) State(Unknown)



    I don't know enough about these particular errors, but they may be pointing to why the files are growing so large and shutting down the system drive.  Anyone have any thoughts on this?

    ALG

    Monday, August 17, 2009 11:02 AM
  • Al, could you please post a separate question, rather than tagging your issue on to a post that may be only loosely related?

    And as an initial suggestion, try running chkdsk on all the drives in your server. After you delete all those log files that are currently clogging up your system partition, that is...

    I'm not on the WHS team, I just post a lot. :)
    Monday, August 17, 2009 3:53 PM
    Moderator