Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 
(연관된 글이 1개 있습니다.)

Hyper-V 서비스 시작 오류 - Not enough storage is available to complete this operation.

결론부터 말씀드리면 이 오류는 해결하지 못했습니다. 잘 되던 Hyper-V 서비스가 갑자기 다음과 같은 오류를 발생하며 "시작" 상태로 진입하지 못했습니다.

Windows could not start the Hyper-V Virtual Machine Management service on Local Computer.

Error 14: Not enough storage is available to complete this operation.

이벤트 로그에도 동일한 오류가 남을 뿐 그다지 별 도움이 되지 않았습니다.

Log Name:      System
Source:        Service Control Manager
Date:          2014-01-06 오전 9:20:01
Event ID:      7023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      testpc.testad.com
Description:
The Hyper-V Virtual Machine Management service terminated with the following error: 
Not enough storage is available to complete this operation.

검색해 보니 다음의 글이 그나마 관련이 있었는데요.

The Hyper-V Virtual Machine Management service terminated with the following error: Not enough storage is available to complete this operation. 
; http://social.technet.microsoft.com/Forums/windows/en-US/c137fe1a-e34d-469a-9e98-2a2c2199ced2/the-hyperv-virtual-machine-management-service-terminated-with-the-following-error-not-enough?forum=w8itprovirt

제 경우에 실제로 다음과 같은 결과를 보였고 하드 디스크의 일부 데이터가 손실된 듯 합니다.

c:\>chkdsk /scan

Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on C:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
                                                                                       
                                                                                       
  266496 file records processed.                                                         File verification completed.
                                                                                       
                                                                                       
  1925 large file records processed.                                                                                                                           
                                                                                       
  0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
Read failure with status 0xc000000d at offset 0x1364119000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136417a000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364185000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452871000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x90 is invalid.
15 49 03 00 00 00 01 00 90 00 74 00 01 00 00 00  .I........t.....
2b e2 02 00 00 00 01 00 ea 83 56 70 34 9f ce 01  +.........Vp4...
ea 83 56 70 34 9f ce 01 77 b0 75 07 b4 af ce 01  ..Vp4...w.u.....
ea 83 56 70 34 9f ce 01 00 10 00 00 00 00 00 00  ..Vp4...........
70 0b 00 00 00 00 00 00 20 00 00 00 00 00 00 00  p....... .......
19 00 4c 00 53 00 41 00 2d 00 4c 00 69 00 63 00  ..L.S.A.-.L.i.c.
65 00 6e 00 73 00 65 00 2d 00 70 00 70 00 64 00  e.n.s.e.-.p.p.d.
6c 00 69 00 63 00 2e 00 78 00 72 00 6d 00 2d 00  l.i.c...x.r.m.-.
6d 00 73 00 00 00 00 00 ff ff ff ff ff ff ff ff  m.s.............
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136418b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136419d000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13641a0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0xa8 is invalid.
45 49 03 00 00 00 01 00 a8 00 8c 00 01 00 00 00  EI..............
2f e2 02 00 00 00 01 00 0b 5a 5b e6 51 9f ce 01  /........Z[.Q...
0b 5a 5b e6 51 9f ce 01 f1 94 a1 07 b4 af ce 01  .Z[.Q...........
0b 5a 5b e6 51 9f ce 01 00 30 00 00 00 00 00 00  .Z[.Q....0......
5f 2a 00 00 00 00 00 00 20 00 00 00 00 00 00 00  _*...... .......
25 00 53 00 65 00 72 00 76 00 65 00 72 00 53 00  %.S.e.r.v.e.r.S.
74 00 61 00 6e 00 64 00 61 00 72 00 64 00 2d 00  t.a.n.d.a.r.d.-.
52 00 65 00 74 00 61 00 69 00 6c 00 2d 00 31 00  R.e.t.a.i.l.-.1.
2d 00 70 00 6c 00 2d 00 72 00 74 00 6d 00 2e 00  -.p.l.-.r.t.m...
78 00 72 00 6d 00 2d 00 6d 00 73 00 00 00 00 00  x.r.m.-.m.s.....
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364206000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136427c000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452d7b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1b03e000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1360683000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x690d0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f982000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb45c7000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f98e000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f996000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13a6c52000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453603000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453605000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453607000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13643d8000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136719d000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x14311e2000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb0b06000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1455a56000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Win

하단에 "wbem" 관련 폴더도 눈에 띄는데요. WMI 관련 서비스에 의존하는 WindowSMART 프로그램을 실행하니 다음과 같은 오류 메시지만 출력할 뿐이었습니다.

WMI Failure Predicted: False
The Microsoft storage driver is reporting False over WMI for the flag "failure predicted." The storage driver is not detecting any problems.

윈도우 백업 서비스를 이용해 시스템 전체 백업이 되어 있었지만 지난 백업 날짜로 C 드라이브를 통째로 돌려도 마찬가지 문제가 발생했습니다. 가정을 해보자면, 지난번 부팅 이후로 파일 시스템이 깨진 곳이 있었고 백업도 그것을 포함해서 된 것 같습니다. (백업 하드 용량이 작은 관계로 백업이 2개 정도만 보관된 것도 문제였고. ^^;) 그러다가 이번에 재부팅이 되면서 wbem 관련 문제가 발생해 Hyper-V 서비스가 시작하지 못하게 된 것입니다.

어쩔 수 없이! Hyper-V 호스트 운영체제만 새로 설치를 하는 것으로 문제를 우회했습니다. (역시 VM으로 서비스들을 뽑아놓으니 복구가 빠르게 되는군요. ^^;) 해결책 찾는 것보다 새로 설치하는 것이 더 빨랐습니다.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]

[연관 글]






[최초 등록일: ]
[최종 수정일: 6/27/2021]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... 166  167  168  169  170  171  172  173  174  175  176  177  178  179  [180]  ...
NoWriterDateCnt.TitleFile(s)
483정성태3/17/200740801오류 유형: 30. x64 환경: .NET + COM 프로젝트 실행 시 오류 - 80040154 [2]
482정성태3/17/200730292Team Foundation Server: 17. 팀 프로젝트 접속 및 사용
481정성태3/17/200724215Team Foundation Server: 16. 팀 프로젝트 읽기 전용 사용자 등록
480정성태3/14/200722318.NET Framework: 86. GC(Garbage Collector)의 변화
479정성태3/14/200726351개발 환경 구성: 25. D820 - ReadyBoost 구동
478정성태3/14/200725679개발 환경 구성: 24. D820 고주파음 문제
477정성태3/14/200735000개발 환경 구성: 23. 비스타 x64 버전에서 서명되지 않은 드라이버 사용 [4]
476정성태3/9/200730375개발 환경 구성: 22. D820 노트북 - 설치 및 BitLocker 구성 [1]
475정성태3/6/200724756.NET Framework: 85. 공용 프로퍼티 자동 생성
474정성태3/5/200722958.NET Framework: 84. Lambda 표현식 응용 사례 [1]
473정성태3/4/200730097디버깅 기술: 14. TFS 오류 추적(TF53010, TF14105)
472정성태3/3/200729177디버깅 기술: 13. 예외 발생 시 Minidump 생성 - WinDBG [3]파일 다운로드1
471정성태3/1/200718379디버깅 기술: 12. Managed Method에 Break Point 걸기
469정성태2/28/200729904디버깅 기술: 11. (Managed) Main Method에 Break Point 걸기 [3]파일 다운로드1
470정성태3/1/200721275    답변글 디버깅 기술: 11.1. (Managed) Main Method에 Break Point 걸기 - 내용 보강
468정성태2/25/200731148COM 개체 관련: 20. 탭 브라우저의 윈도우 핸들 구하기 [3]
466정성태2/22/200722845Windows: 23. 롱혼 서버 코어 버전 [2]
465정성태2/21/200721819오류 유형: 29. TFS 관련 스케줄 작업 실패
464정성태2/25/200723000오류 유형: 28. TF10217, TF53010, TF14105 오류
463정성태2/21/200716033Team Foundation Server: 15. 포탈 사이트의 보고서 주소를 도메인 명으로 적용
462정성태2/13/200743333.NET Framework: 83. 라이브러리에 다국어 리소스 추가 방법 [4]파일 다운로드1
461정성태2/13/200721051오류 유형: 27. DLinq 예제 오류 : error: 26 - Error Locating Server/Instance Specified
460정성태2/13/200721249.NET Framework: 82. Orcas 1월 CTP에서 Linq 소스 컴파일 방법
459정성태2/17/200725253오류 유형: 26. "Automatic Updates" 서비스 CPU 100% 점유 현상 - 두 번째 이야기 [3]
458정성태2/12/200721712.NET Framework: 81. LINQ 개발 환경 설정 [1]
457정성태2/8/200726187.NET Framework: 80. LINQ 관련 용어 정리 및 리소스 소개 [2]
... 166  167  168  169  170  171  172  173  174  175  176  177  178  179  [180]  ...