Frank McLean
Senior Member
- Joined
- Mar 10, 2017
I keep getting Disk Busy error from my Crucial MX500 2TB 3D NAND SATA 2.5 Inch Internal SSD - CT2000MX500SSD1 . Can anyone shed any light on this?
Thank you in advance.
Thank you in advance.
Hey Frank, Happy New Year...
I can tell you are running a notebook of some sorts because your Crucial SSD drive is 2.5", but that is it...
Your notebook what are its specs, please?
The "busy signal" does that mean you cannot access the drive under what? Windows 10, Home/Pro?
Can that notebook handle a SATA III drive, if so, you might need to update your SATA I (or II) cable to the class III SATA cable.
Sometimes there might be a setting under the computer's BIOS that needs addressing.
Also, when was the last time you updated your firmware for your notebook/laptop? Especially your BIOS. The latest firmware install might correct your "busy signal".
Next, all Solid State Drives (SSDs), depending upon how long they have been sitting at the warehouse could need a firmware update themselves, did you know that some SSD drives REQUIRE FIRMWARE UPDATES?
Let us know...
Cheers!
Sent from my SM-G965U using Tapatalk
Take a look here: HP and Compaq Desktop PCs - About SATA Hard Drives and Controller Modes | HP® Customer Support.Can you please explain about AHCI in the Bios. What is the significance of this? What does it do? How might if affect the Crucial SSD?
Also can someone please answer my previous question about whether my PC will still reboot if in devmgmt.msc I highlight my Crucial SSD drive and reboot will my PC still Start?
Have you tried to do a chkdsk?Just got a freeze that lasted about 30 seconds.
Sorry to hear that it didn't help.Hi GDany, I ran from cmd chkdsk /f /r /x, it took only about one hours to run. I still had a brief free since then.
Oh, yes, you already sent us your results after the chkdsk test. What i suggested now is something else related to your computer bios. You did not read my previous message.Sorry, I thought I had responded to that. Yes I ran chkdsk /f /r /x it took just a little more than an hour to run. The short 30 second freeze occurred after running the check disk. I haven't used the PC much since then. I'll have to watch for a awhile to see if it fixed the problem. But the freezes are related to the Disk Busy phenom-en.