CHKDSK was started on new laptop. Is the harddrive broken?

electricity · 09 Jan 2013

Is my harddrive broken, although the computer is completely new?

I have bought a new Lenovo Thinkpad x230 (with a traditional harddrive). The first thing I did was going to Windows Update to download the available updates for Windows 7 professional 64 bit. (There were some problems with the installation of the updates, but I could solve them with the help of information from internet. One of the update files had to be installed separately first, otherwise it would block the whole package of update files from installing.)

During a reboot CHKDSK is started and gives me the message below. I am sorry that it is in Swedish, but if I translate a summary it says:
- the disk has to be controlled for inconsequences
- takes away the damaged attribute post (128, "")
- takes away a couple of index posts
- CHKDSK restores some unindexed files to

What does this mean? Is my harddrive broken? Should I return it to the shop immediately?

Kontrollerar filsystemet på C:
Filsystemet är av typen NTFS.
Volymetiketten är Windows7_OS.
En av diskarna behöver inkonsekvenskontrolleras. Du kan
avbryta diskkontrollen, men du rekommenderas att
låta den fortsätta.
Disken kommer nu att kontrolleras.
CHKDSK verifierar filer (steg 1 av 3)...
Attributposten av typen 0x80 med instanstaggen 0x4 är korslänkad
för 0x1 kluster (med start vid 0x3095c2).
En del kluster upptagna av attribut av typen 0x80 och med instans-ID 0x4
i filen 0x2b4a7 används redan.
Tar bort den skadade attributposten (128, "")
från filpostsegmentet 177319.
195584 filposter har behandlats.
Filverifieringen är klar.
477 stora filposter har behandlats.
0 skadade filposter har behandlats.
2 EA-poster har behandlats.
46 referensposter har behandlats.
CHKDSK verifierar index (steg 2 av 3)...
Filreferensen 0xd00000002b4a7 för indexposten CR6210~1.175 för indexet $I30
med det överordnade objektet 0x1b8 är inte identisk med 0x900000002b4a7.
Tar bort indexposten CR6210~1.175 i indexet $I30 i filen 440.
Filreferensen 0xd00000002b4a7 för indexposten Critical_6.1.7601.17592_80af4d447d799450f85daf4cb60beddda3e33e3_05bdb99d för indexet $I30
med det överordnade objektet 0x1b8 är inte identisk med 0x900000002b4a7.
Tar bort indexposten Critical_6.1.7601.17592_80af4d447d799450f85daf4cb60beddda3e33e3_05bdb99d i indexet $I30 i filen 440.
Filreferensen 0x1400000002b4a4 för indexposten Report.wer för indexet $I30
med det överordnade objektet 0x2b4a3 är inte identisk med 0x1300000002b4a4.
Tar bort indexposten Report.wer i indexet $I30 i filen 177315.
271024 indexposter har behandlats.
Indexverifieringen är klar.
CHKDSK läser oindexerade filer för återanslutning till den ursprungliga katalogen.
Återställer den överblivna filen 304CAD~1.XML (177316) till katalogfilen 3036.
Återställer den överblivna filen 30273180_2679573209.back.xml (177316) till katalogfilen 3036.
Återställer den överblivna filen 302FE4~1.XML (177319) till katalogfilen 3036.
Återställer den överblivna filen 30273180_2679573229.xml (177319) till katalogfilen 3036.
4 oindexerade filer har genomsökts.
Återställer den överblivna filen 30D6DB~1.XML (177476) till katalogfilen 3036.
Återställer den överblivna filen 30273180_2679573228.back.xml (177476) till katalogfilen 3036.
CHKDSK återställer återstående oindexerade filer.
1 oindexerade filer har återställts.
CHKDSK verifierar säkerhetsbeskrivare (steg 3 av 3)...
195584 fil-SD/SID-poster har behandlats.
Rensar upp 364 oanvända indexposter från indexet $SII i filen 0x9.
Rensar upp 364 oanvända indexposter från indexet $SDH i filen 0x9.
Rensar upp 364 oanvända säkerhetsbeskrivare.
Verifieringen av säkerhetsbeskrivare är klar.
Infogar dataattribut i filen 177319.
37722 datafiler har behandlats.
CHKDSK verifierar USN-journalen...
37102736 USN-byte har behandlats.
Verifieringen av USN-journalen är klar.
Korrigerar fel i BITMAP-attributen för MFT.
CHKDSK hittade ledigt diskutrymme markerat som allokerat i volymbitmappen.
Korrigeringar har gjorts i filsystemet.
468416511 kB diskutrymme totalt.
44033272 kB i 143579 filer.
100812 kB i 37723 index.
0 kB i skadade sektorer.
313159 kB används av operativsystemet.
65536 kB hårddisksutrymme används av loggfilen.
423969268 kB ledigt utrymme.
4096 byte i varje allokeringsenhet.
117104127 allokeringsenheter finns totalt på disken.
105992317 allokeringsenheter är tillgängliga på disken.
Intern information:
00 fc 02 00 40 c4 02 00 a0 88 05 00 00 00 00 00 ....@...........
7e 00 00 00 2e 00 00 00 00 00 00 00 00 00 00 00 ~...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Kontrollen av disken har slutförts.
Vänta medan datorn startas om.

marsmimar · 10 Jan 2013

Hello electricity and welcome to Seven Forums.

Others may disagree because it's a challenge to diagnose and repair problems. But in my opinion a new computer should not be running CHKDSK after installing Windows Updates and rebooting. I would take the computer back to the shop immediately. Otherwise they might try to blame you for damaging the laptop and not honor the warranty.

Google Translate:
Andra kan inte komma överens eftersom det är en utmaning att diagnostisera och reparera problem. Men enligt min mening en ny dator bör inte köra CHKDSK efter installation Windows-uppdateringar och starta om. Jag skulle ta datorn tillbaka till butiken direkt. Annars butiken kan klandra dig för att skada den bärbara datorn och inte hedra garantin.

bobafetthotmail · 10 Jan 2013

Unless it says there are "bad sectors" (in swedish) the disk should be fine. With google translate, the report above I see
0 kB i skadade sektorer. which is "0 KB in bad sectors.". which should mean it's ok.

From your summary and a Google translate it seems like you turned it off incorrectly (pressed power button until it powers everything down, not waiting the time to close things), and that could happen when installing critical updates like Service Pack 1 as well.

It just did some housekeeping, sometimes Windows 7 makes a mistake or is shut down incorrectly and that leaves errors in the filesystem (like saying it placed stuff in the wrong place or lost some indexes that have to be rebuilt/restored), that chkdsk fixes.

That said, if you can have it checked it's always better.

electricity · 11 Jan 2013

Thanks very much both of you!

This gives me something to think about. The CHKDSK behaviour made me nervous, and I don't want to start using the computer for important work until I know it is in good shape. Probably I will try to talk to Lenovo on Monday to hear what they are going to say.

No, I did not turn the computer off by pushing the power button. But, as I wrote, at first there were problems with the Windows update files (which in itself seems worrying to me) - and Windows made many reboots where it at start-up told me that changes are being made, only to stop at 35% through the process and changing the message to "the changes could not be performed" (or something similar), "the computer is restored to its previous state". Maybe all these reboots with changes and restored changes caused some problems with the file system? (I sadly don't know much about how Windows works on a detail level.)

All the best,

Martin

whs · 11 Jan 2013

I think too that your disk should be OK. But for safety, it is always recommended to make frequent images of the system and the data to an external disk. Then you can always bail yourself out when a disk breaks.
Imaging with free Macrium

bobafetthotmail · 12 Jan 2013

electricity said:

Maybe all these reboots with changes and restored changes caused some problems with the file system? (I sadly don't know much about how Windows works on a detail level.

Well, if it did that, then it's likely the cause of this fuss. Anyway "file system errors" sounds much worse than it is.

Would be interesting to know why it did screwup the updates. Did you manage to install everything in the end?

electricity · 13 Jan 2013

Yes, I could install all the updates. There was one critical update that had to be installed separately. I read about other Lenovo people on the web with update problems, but I also recognized the problem since I faced exactly the same situation on another Windows 7 machine around a year ago. So I found out the number of the critical update (the KB22244whatever), installed all the updates with lower numbers as a package of files, then in the next round installed the chosen one separately, and then the remaining 40-or-so updates would install as a package. I don't know why, but the mad-and-bad update cannot make its registry changes if it is not left alone. (Last year I read an explanation for this behaviour but I have now sadly forgotten why some other process was blocking the registry.)

Martin