Code d'erreur

Discussions about using Windows guests in VirtualBox.
Post Reply
lucferi
Posts: 3
Joined: 19. May 2016, 13:32

Code d'erreur

Post by lucferi »

Bonjour,

Lorsque je démarre Windows 10 installé dans VirtualBox 4.3.20.r100309 sur Windows 7, j'obtiens le message d'erreur suivant:
ID de l'erreur :
BLKCACHE_IOERR
Sévérité :
Erreur non Fatale
Que faire pour réparer cette erreur ?
Merci pour vos réponses, Luc

When I start Windows 10 in VirtualBox installed 4.3.20.r100309 on Windows 7, I get the following error message:
Error ID:
BLKCACHE_IOERR
severity:
Non Fatal Error
What to do to fix this error?
Thank you for your answers, Luke
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Code d'erreur

Post by mpack »

Please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.
lucferi
Posts: 3
Joined: 19. May 2016, 13:32

Re: Code d'erreur

Post by lucferi »

Bonjour,

J'ai réussi à faire un zip du journal VMLogs mais je ne sais pas comment le poster ici. Pourriez-vous m'expliquer comment faire ?
Merci
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Code d'erreur

Post by socratis »

Seulement le dernier VBox.log, pas tous.
Image
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
lucferi
Posts: 3
Joined: 19. May 2016, 13:32

Re: Code d'erreur

Post by lucferi »

Bonjour,

En pièce jointe, les logs de VM.

Luc
Attachments
Win 10 pro-2016-05-19-13-51-13.7z
Ci-joint le log de VM.
Attached is the log VM.
(33.8 KiB) Downloaded 4 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Code d'erreur

Post by mpack »

You have a great many of these in the log (below is just a selection) :-
00:00:57.127166 I/O cache: Error while writing entry at offset 22124904448 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.151561 I/O cache: Error while writing entry at offset 22124920832 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.152995 I/O cache: Error while writing entry at offset 22124937216 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.153956 I/O cache: Error while writing entry at offset 22124953600 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.154914 I/O cache: Error while writing entry at offset 22124969984 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.155871 I/O cache: Error while writing entry at offset 22124986368 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.156866 I/O cache: Error while writing entry at offset 22125002752 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.157849 I/O cache: Error while writing entry at offset 22125019136 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.158835 I/O cache: Error while writing entry at offset 22125035520 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.159942 I/O cache: Error while writing entry at offset 22125051904 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.160924 I/O cache: Error while writing entry at offset 22125068288 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.161915 I/O cache: Error while writing entry at offset 22125084672 (32768 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
00:00:57.162907 I/O cache: Error while writing entry at offset 22125117440 (16384 bytes) to medium "ahci-0-0" (rc=VERR_UNRESOLVED_ERROR)
I'd say that you have a faulty host drive. Try running chkdsk on it - it will need to be a thorough overnight scan, not a quick filesystem integrity check.
Post Reply