O HDD torna-se RAW e NTFS novamente?

Question

O problema começou hoje depois que eu reiniciei o meu computador, eu comecei a receber muitos erros de programas que estão instalados no E: / e D: / partições (mesma unidade), ele começa ok e de repente a unidade se torna um sistema de arquivos RAW (é o que eu recebo de uma execução do chkdsk). Depois de um longo tempo, a unidade se torna novamente NTFS (apenas por alguns minutos).

Além disso, recebo um BSOD com o seguinte erro: KERNEL DATA_INPAGE_ERROR

Meu inglês é ruim, então peço desculpas; O que devo fazer para resolver este problema? Talvez o HDD esteja danificado?

edit: eu também recebo isso do chkdsk

Stage 4: Looking for bad clusters in user file data ...
Read failure with status 0xc0000483 at offset 0x25777000 for 0x8000 bytes.

A disk read error occurredc0000483
Read failure with status 0xc0000483 at offset 0xcc4400 for 0x400 bytes.
The disk does not have enough space to replace bad clusters
detected in file 238 of name .
Read failure with status 0xc0000483 at offset 0x41185000 for 0x10000 bytes.

A disk read error occurredc0000483
Read failure with status 0xc0000483 at offset 0xc69800 for 0x400 bytes.
The disk does not have enough space to replace bad clusters
detected in file 239 of name .
Read failure with status 0xc0000483 at offset 0x40000 for 0x400 bytes.
An unspecified error occurred (6e74667363686b2e b10).

    

Answer 1

Como eu esperava que o HDD estivesse danificado. Os Dados SMART mostram um grande problema com Reallocated Sectors Count :

Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as "reallocated" and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called "remaps". The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future. While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. If sequential access speed is critical, the remapped sectors can be manually marked as bad blocks in the file system in order to prevent their use.

Além disso, o alto Current Pending Sector Count é uma coisa ruim:

Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written. However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.

Se este for um laptop novo , faça o backup de todos os dados possíveis e traga-o de volta para a loja, para que eles substituam o disco rígido defeituoso.