Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Can't initialize fully new SSD

Apr 2, 2017 8:27AM PDT

After one of the two SSD drives in my laptop failed, I replaced it with a new one. i simply replaced the hard drive and have not tried to rebuild it or access any of the data. After replacing the failing SSD, I tried to do a clean installment of windows (8.1). I could not install windows on the new SSD, so I installed it on the old one instead (that is, of course, the other SSD in the computer, not the failed one).

However, when I try to initialize the drive in Disk Manager, I get the error message "Data error (cyclic redundance check)". The SSD is completely new from the store. Also, I don't understand why the disk manager shows 477 GB unallocated when the drive is only on 240 GB. The SSD drive I bought was this and since it comes in 480 GB as well, I guess there's a small chance that they gave me the wrong one but I highly doubt it.

Screenshots:

Disk Manager

List of disks from Disk Part, don't know if it's of any help since the non-initialized disk is not there:

Adding to this, it seems like my computer is working harder which should have something to do with the reinstallation as well. I can't test this since I don't have any numbers from how it was before, but since my laptop (MSI GS70 2QE) has two modes depending on intensivity in usage, shown by the light on the power button, it's easy to tell. Now the red light is always on and the fans are sounding a lot, before this only happened when I used demanding software or games. (I understand that "Red light" is very nonsensical terminology only relevant to this specific model, but you get the point.)

Discussion is locked

- Collapse -
Answer
UPDATE
Apr 2, 2017 9:01AM PDT
- Collapse -
Please be more specific?
Apr 2, 2017 9:27AM PDT

Hi, thanks for your answer. However, I'm not fully clear what you are referring to? "Right at top" is the following answer:

"In Disk Management, right-click the disk you want to initialize, and then click Initialize Disk.
In the Initialize Disk dialog box, select the disk(s) to initialize. You can select whether to use the master boot record (MBR) or GUID partition table (GPT) partition style."

I assume you read my thread and saw that this method was not working for me, hence my question. The second google hit refers to an initialized disk which has to be allocated. This solution does not work for me, since my disk is not initialized. Of course I have tried to google the question, so if you are referring to anything specific, please let me know.

- Collapse -
If the drives seem to be working, time to CHKDSK them.
Apr 2, 2017 9:24AM PDT

Use CHKDSK /F on all drive letters. Will take some time but mods here are seeing odd problems vanish after this. We don't know what's causing this.

- Collapse -
Thanks
Apr 2, 2017 9:35AM PDT

Hi, thanks for your answer. I've done this for C: and D:, but the problem is that I don't know how to do CHKDSK on the non-initialized drive? As you can see in the printscreen here, disk 1 = C:, Disk 2=D: but Disk 0 (the disk in question) does not have any letter assigned to it?

- Collapse -
Ahh
Apr 2, 2017 9:39AM PDT

I read the above as if you got the OS installed on the new drive.

Some of these laptops have a non-standard (compared to years ago) driver and things may go weird.

If I was there I'd get the latest GPARTED to partition this one. If that failed I would remove the drive to try it on another PC or that drive in an USB case.

- Collapse -
Solved!
Apr 2, 2017 10:11AM PDT

Just to let you know (and if case anyone else encounters the same problem and finds this thread), I got a response from another forum. I might have been unclear in my statement of the problem but however, this was the solution.

"You have installed windows on new drive (240GB).
That 476GB - is your old RAID volume. It is invalid since you have only one drive in RAID 0 array.

Yo have to go to RAID management screen (Intel Rapid Storage Configuration Utility) and delete old RAID. Only after that you'll be able to use your old SSD."

Anyhow, thanks for your help!

- Collapse -
ditto, use GParted
Apr 2, 2017 10:23AM PDT

It's a lot easier I think.