Toshiba Crack Bios Hard Drive Password Utility [REPACK]
Yvette Burkhammer
Hi guys, i have a 500GB NVMe and want to upgrade to 2TB. Any easy way to migrate the contents (including windows) of the old to new? Only 1 m.2 slot on my mobo. Or should i get a case for the new nvme and slot it instead?
^ this. You actually don't even have to do that, if you have any external drive handy that is accessible over USB and that has nothing important on it, clone your existing NVMe to it and then swap the M.2 over and then clone it back.
It's not in a power saving mode, and my Crucial P2, SK Hynix P31, Samsung 960 Pro, Samsung 970 Evo Plus and Kingston KC2500 all count power on hours correctly. Both the KC2500 and P2 have been in this slot, in this role and counted wall clock hours. So it's not that.
I have x2 MX500 1TB SSD's, and on rare occasions, specifically when restarting multiple times in short intervals (restarting into safe mode and using DDU for example then restarting again) the end MX500 drive will fail to detect and thus dissappear and in extremely rare cases can be both (when restarting again instead of shutting down the other disappears then).
I then shut the PC down, and then turn it on to fix it, it's an odd issue that isn't make or break anything, but it is an annoyance when it occurs and troubling if it's a bad sign of possible future troubles?
Planning to backup my stuff on it just in case things get worse over time, so far it's remained the same since I've had it, just really annoying when on the second restart it dissappears and so you have to shut down again and then start the PC, perhaps I'll just stop using the restart function as it could be to do with that?
1st thing I did when it happened, didn't really change anything, tried a different cable and then purchased a whole 3 pack brand new set, which are used there now, also tried different SATA slots and replaced the power cord to them too.
Either it's the SSD itself, which I hope not, and if so doesn't get worse (it's been like this for many months now, I think since when I got it but can't recall exactly, rarely occurs and I haven't noticed it getting any worse, just an annoyance if I'm restarting multiple times in short intervals) or it's something to do with my BIOS on restarting multiple times, perhaps even the PSU?
I just restarted my PC 4 times in short intervals a few moments ago (Restarted to safe mode, DDU, Restarted to normal, Restarted to disable driver signature verification and restarted when finished setting everything up again from using DDU and applying driver signature verification again after reinstalling the monitor driver) and it didn't occur once (surprisingly), but sometimes it will in this process of multiple restarting, and then I have to shut down the PC and leave it off for about 1 minute and then startup again to fix it.
Nope. Perhaps because mine are all 24/7 and Linux, they never drop into that bottom power state that stops them counting. I've noted there's a post on Servethehome that comments on the 980 Pro with the 5x firmware not counting properly, so it's not just mine.
Very odd. I mean if you've got another PSU to test you could try that, it might also be potentially a UEFI/BIOS option related to SATA link power saving perhaps. Without testing the SSDs across reboots in another PC to see if they do the same thing, you ultimately can't eliminate something else being the cause. But this would be a quick way to test if it's something to do with your PC and the PSU at the same time, since another PC would be using a separate PSU.
Yes, using Crucial Storage Executive it says there is a firmware update available for both of them, however when I selected to install it, it fails? I'll try again and give you a detailed description of the error.
Error while checking for firmware updates.
Connection failed because of socket exception when trying to access the firmware web service host. Please try again later or use the manual firmware update process.
And If I read this correctly, I will try updating to Version M3CR023 which should be compatible with my M3CR043 version, I'm also downloading a new Storage Executive to make sure it's function correctly and I'll update through that, I haven't backed up any of my files though, perhaps I should do that.
Running M3CR023 here and SA says 33 is the goto. This flavor had known issues and was pulled upon release, perhaps sorted since. Crucial did pull ALL versions of code from there site upon discovery bitd.
Storage Executive is very bloated and runs like crap, partially because it's basically a web server running entirely on top of Java, but functionally it has worked fine for me in the past when I've used it. It's just slow.
While I'm at it, I don't really need to, but for convenience sake, I'll also figure out Macrium Reflect and do a backup of my OS, as that'll save me some time if I have to reinstall Windows again at any stage. :)
Not sure, I don't feel very confident with that method, but if there is a good tutorial you've seen on youtube or somewhere I can watch or read, I might be more confident in that approach. Otherwise, I'm fine if Crucial Storage Executive is slow or whatever, what would most worry me is if it's prone to failure during the process.
I have two of the older (much, much older) Crucial m4 drives that had that bug that once you hit about 5000 hours on it, it basically stops working after being in use for one hour, every hour. Had to go through that manual firmware update process as described above, though I did it with bootable DVDs I think.
I'm not saying you're wrong, I've already said the software is bloated. As have you, multiple times. We get it. I had no issues using it to update the firmware on tens, likely more than a hundred SATA drives used in system builds where I used to work.
First of all, the M3CR023 firmware doesn't work on it ... I got it to boot and all, it says it is applying the firmware update, but on reboot, the original M3CR043 was still shown as the current firmware version.
However, there is a M3CR045 firmware available for drives with N3CR043 firmware. To get Crucial Storage Executive to download and apply it, since there is no standalone download for it, you need to initiate a high workload on the drive (copy a big directory to a network or USB storage device) ... then Crucial Storage Executive won't crap out, it will then be able to apply the firmware update.
To get Crucial Storage Executive to download and apply it, since there is no standalone download for it, you need to initiate a high workload on the drive (copy a big directory to a network or USB storage device) ... then Crucial Storage Executive won't crap out, it will then be able to apply the firmware update.
So even with the new firmware M3CR046, one of the MX500's didn't appear on startup, only I didn't notice for a while because the MX500 SSD that normally does it being Drive 0, was instead Drive 1 this time, so it's like they switched places, anyway, could be just a random one off, I'll see how it goes, a quick restart fixed it.
If you've updated firmware and tried different SATA cables and it's still happening, your next two steps IMO would be to try powering the drive differently (just use a dedicated PSU's SATA power connectors or try a Molex -> SATA off your current PSU) or try the drive in another system.
SSD's and NAND in general are very simple devices. There's a PCB, NAND flash on said PCB, and a controller. At most in addition to those, a slab of DRAM. Excluding an issue with the chips on the PCB of the SSD itself, it's pretty hard for something to go wrong. Your system either isn't detecting all the drives properly on a cold boot (perhaps apply a small boot delay or play with settings in your UEFI e.g. disabling Fast Boot) or the drives aren't getting powered on boot (could be too many devices off the one rail on the PSU, or any other plethora of PSU-related factors).
If the drives function fine in another system, then that eliminates the drives themselves as the cause. You're then back to either your PSU, or your system/platform. If you can, a cheap Molex -> SATA adapter is a quick way to test powering the drives on cold boot. If the drives have the same issue on a wholly separate system, pull the data off them and warranty them.
I disabled fast boot both in BIOS and in the Windows Environment, not sure how to do a 'boot delay', as the POST screen is extremely fast for me and not sure where to change it either, I checked all the settings in the BIOS and couldn't seem to find it unless I need to delve into the 'secure boot' section of the BIOS?
Provided the firmware on the motherboard does a cascading pass (read: attempts to load from each drive, and on failure continues), you'll have the drive initialised because otherwise the system can't attempt to boot from it. It's an ugly hack from early UEFI boot days.
So I named both drives with the Identical name "Crucial MX500 SSD" so both named exactly the same, and I suspect it may be getting confused or conflicted on startup occasionally hence one of them on rare occasions disappearing, so I've since changed them to "Crucial MX500 1 SSD" and "Crucial MX500 2 SSD" and so far it hasn't happened again, but I'll keep an eye on it. :)
7fc3f7cf58