SHOULD I USE CRUCIAL STORAGE EXECUTIVE UPDATE
SHOULD I USE CRUCIAL STORAGE EXECUTIVE DOWNLOAD
SHOULD I USE CRUCIAL STORAGE EXECUTIVE WINDOWS

SHOULD I USE CRUCIAL STORAGE EXECUTIVE UPDATE

Went through chkdsk, SMART, different sata ports on the motherboard, different power supplies, locations to mount the drive (static discharge?) etc until finally tried the firmware update which has solved it! I even built up multiples of the exact same PC build and they ALL had the same issue! How weird! Totally replicatable. The SSD wouldn't be accessible again until I powered off, unplugged, flushed the bits by holding the power button down, and then re-powering on the PC, at which point, it was totally fine. I just started speccing these drives out for our studio's workstation's local repositories for SVN version control, and I kept having issues where after about 120GB or 1-2hrs of writing, the checkout would crash and render the local repo malformed. Of the many years I've spent troubleshooting PC issues, this is the first time I felt cornered, since not even switching cables, ports or anything had worked. 'This is an optional update which repairs a hang condition occurring under corner-case workloads.'ĭo you think that my issue could've been related to the problem you describe on your original post? It would happen completely randomly while playing intensive games installed on it, and again, only started happening after I got the brand new GPU.Ī minute before I found this post, I discovered Crucial Storage Executive and used it to update the firmware.

SHOULD I USE CRUCIAL STORAGE EXECUTIVE WINDOWS

If I Shut down and powered on again, BIOS would show it properly and Windows would recognize it just fine. If I Restarted the PC, BIOS would show it the same way. Right after getting a new GPU (RX 6700 XT), my MX500 would randomly dissapear from Windows and on Disk Management it would show as a 1GB generic unmounted drive with a random name. I hope you have 3 minutes of your time to read this :) I just found your post after endless hours searching for people having issues with their MX500 randomly dissapearing on Windows. Most Windows desktop and notebook users will be unaffected by this change. Release Notes: This is an optional update which repairs a hang condition occurring under corner-case workloads. Feb 7 01:20:52 darktower kernel: I/O error, dev loop2, sector 887200 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0įeb 7 01:21:10 darktower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 13, rd 1644, flush 0, corrupt 0, gen 0įeb 7 01:21:10 darktower kernel: BTRFS warning (device sdc1: state EA): direct IO failed ino 109014 rw 0,0 sector 0x578abf30 len 0 err no 10įeb 7 01:21:10 darktower kernel: BTRFS warning (device sdc1: state EA): direct IO failed ino 109014 rw 0,0 sector 0x578abf38 len 0 err no 10įeb 7 04:40:04 darktower root: Fix Common Problems: Error: Unable to write to Docker Imageįeb 7 08:39:38 darktower kernel: I/O error, dev sdc, sector 212606944 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0įeb 7 08:39:38 darktower kernel: I/O error, dev loop3, sector 78080 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 so this required mounting BTRFS in Windows using WinBtrfs, and writing to the filesystem while you execute the firmware update in the crucial software. Also the firmware update only works if you are actively writing to the disk ( lol).

SHOULD I USE CRUCIAL STORAGE EXECUTIVE DOWNLOAD

This update is not available for direct download through the Crucial support site, you must use crucial storage executive software which only runs on Windows. Specific log message examples below.Īfter lots of troubleshooting and process of elimination, the only thing that ended up resolving this and stabilizing my cache pool was updating the SSDs firmware to the latest version available, M3CR046 at the time of this post. Also the drives will seemingly randomly disappear from BIOS and take several reboots before they reappeared. They worked fine for about a year, but this past week I suddenly started getting all kinds of BTRFS errors and other storage related write errors messages in the syslog. I had a cache pool using 2x Crucial MX500 1TB SSDs.

If you are using them, backup all the data immediately, consider replacing them, or at the very least check your firmware version and update to the latest (M3CR046) ASAP. TLDR: You may want to update Crucial SSD firmware if using them in your Unraid system. Posting this here in case anyone else runs into these issues, hopefully it will save some time.

Should i use crucial storage executive