Also widely installed in (guessing 30+) PC's I've updated for friends and family over the last few years, again with no reported failures or issues. I have around 10 MX500's around the house (PC, Xbox, PS4, Set Top Box) as they are one of the SSD's that still has some DRAM and while some of these are up to 4 years old with 24/7 running, I'm yet to have an issue with any one of them. My main array uses a deliberate mix of drive models and purchase dates. I'd alway recommend spitting the risk in a pool in such a way. The other (mirror) cache drive is a different brand to split the risk of any systemic failure. so just the way the drive reports rather than any indication of reliabilty or pending failure. When I look at the smart data, no sectors or nand blocks have actually been reallocated etc. My 500GB drive in the cache is over 2 years old, no issues apart from the nusiance alerts for 'pending sector' which I disabled. Perhaps an issue with a specific firmware version that only showed up, as they say in an 'edge case'. Useful information and a data point but without a clear trend of failures it may be excessive to write off the MX500 so completely. I will never buy Crucial SSDs again, and am looking to replace these with a more reliable brand.įeb 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). 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. 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. 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: Avoid using Crucial SSDs in your Unraid system. Posting this here in case anyone else runs into these issues, hopefully it will save some time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |