May 2, 20242 yr Hello, I'm having issues with my NVME. I recently replaced it and it's been stable for a bit and now it seems I have a new issue. I'm getting the above error and then it no longer works. Currently this drive is accessed via docker and via a VM. It appears that the issue happens each time I put it under a small load via the VM (windows). I tried scrubbing/balancing the drive and it appears to still be having the issue. I checked the firmware in the `identity` tab and it's the latest. It's a Samsung 980 Pro 2tb. Once it goes down I have to reboot the server for it to be usable again. I'm not sure what is going on. I have also added `nvme_core.default_ps_max_latency_us=0 pcie_aspm=off`, based on google searches and I'm still having the issues. Relevant errors: May 1 20:21:57 jlw-unRaid kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 May 1 20:21:57 jlw-unRaid kernel: nvme nvme1: Does your device have a faulty power saving mode enabled? May 1 20:21:57 jlw-unRaid kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758874424, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758874424 op 0x0:(READ) flags 0x84700 phys_seg 9 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758875448, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758875448 op 0x0:(READ) flags 0x84700 phys_seg 5 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758876472, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758876472 op 0x0:(READ) flags 0x84700 phys_seg 4 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758877496, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758877496 op 0x0:(READ) flags 0x84700 phys_seg 3 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758878520, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758878520 op 0x0:(READ) flags 0x84700 phys_seg 3 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758879544, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758879544 op 0x0:(READ) flags 0x84700 phys_seg 3 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758880568, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758880568 op 0x0:(READ) flags 0x84700 phys_seg 3 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758881592, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758881592 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758871352, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758871352 op 0x0:(READ) flags 0x84700 phys_seg 5 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 758872376, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 20:21:57 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 758872376 op 0x0:(READ) flags 0x84700 phys_seg 5 prio class 2 May 1 20:21:57 jlw-unRaid kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002) May 1 20:21:57 jlw-unRaid kernel: nvme nvme1: Removing after probe failure status: -19 May 1 20:21:57 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 May 1 20:21:57 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 May 1 20:21:57 jlw-unRaid kernel: nvme1n1: detected capacity change from 3907029168 to 0 May 1 20:21:57 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0 May 1 20:21:57 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 2, rd 2, flush 0, corrupt 0, gen 0 May 1 20:21:57 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 3, rd 2, flush 0, corrupt 0, gen 0 May 1 20:21:57 jlw-unRaid kernel: BTRFS: error (device nvme1n1p1) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) May 1 20:21:57 jlw-unRaid kernel: BTRFS info (device nvme1n1p1: state E): forced readonly May 1 20:21:57 jlw-unRaid kernel: BTRFS warning (device nvme1n1p1: state E): Skipping commit of aborted transaction. May 1 20:21:57 jlw-unRaid kernel: BTRFS: error (device nvme1n1p1: state EA) in cleanup_transaction:1992: errno=-5 IO failure Adding my diagnostics to the post. jlw-unraid-diagnostics-20240501-2030.zip EDIT: I did notice I had a new line instead of a space, i'll try it with just a space. EDIT 2: Didn't make a difference EDIT 3: Updated BIOS no difference, seems to be triggered solely by the VM. I stress tested it in UnRaid and in BIOS and both passed their checks. EDIT 4: Updated VirtIO drivers in UnRaid and in Windows, no difference. With all the above edits I'm still getting this error here May 1 23:20:30 jlw-unRaid kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 May 1 23:20:30 jlw-unRaid kernel: nvme nvme1: Does your device have a faulty power saving mode enabled? May 1 23:20:30 jlw-unRaid kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405191872, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405191872 op 0x0:(READ) flags 0x84700 phys_seg 5 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405192896, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405192896 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405193920, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405193920 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405194944, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405194944 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405195968, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405195968 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405196992, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405196992 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405198016, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405198016 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405199040, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405199040 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405185728, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405185728 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: I/O Cmd(0x2) @ LBA 405186752, 1024 blocks, I/O Error (sct 0x3 / sc 0x71) May 1 23:20:30 jlw-unRaid kernel: I/O error, dev nvme1n1, sector 405186752 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 May 1 23:20:30 jlw-unRaid kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002) May 1 23:20:30 jlw-unRaid kernel: nvme nvme1: Removing after probe failure status: -19 May 1 23:20:30 jlw-unRaid kernel: nvme1n1: detected capacity change from 3907029168 to 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 1, rd 3, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 2, rd 3, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 2, rd 4, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1): failed to run delayed ref for logical 3302726057984 num_bytes 16384 type 176 action 1 ref_mod 1: -5 May 1 23:20:30 jlw-unRaid kernel: BTRFS: error (device nvme1n1p1: state A) in btrfs_run_delayed_refs:2150: errno=-5 IO failure May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1: state A): bdev /dev/nvme1n1p1 errs: wr 2, rd 5, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS info (device nvme1n1p1: state EA): forced readonly May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 2, rd 6, flush 0, corrupt 0, gen 0 May 1 23:20:30 jlw-unRaid kernel: BTRFS error (device nvme1n1p1: state EA): bdev /dev/nvme1n1p1 errs: wr 2, rd 7, flush 0, corrupt 0, gen 0 Edited May 2, 20242 yr by jlw_4049
May 2, 20242 yr Community Expert If adding that line to syslinux doesn't help I would recommend trying with a different brand/model device if possible, or a different board
May 3, 20242 yr Author 12 hours ago, JorgeB said: If adding that line to syslinux doesn't help I would recommend trying with a different brand/model device if possible, or a different board I took the drive out for now, I'll send off for an RMA. System is stable otherwise. I'll post back and let everyone know regardless. Thanks for the help!
May 24, 20242 yr Author So update, I RMA'd the drive. They said it passed all QA tests, reflashed it, formatted it and sent it back to me. I put it back in my UnRaid machine, it ran good for a bit but it's now doing the same thing under a small load being accessed through the VM. Any other suggestions? I did notice that I didn't have `pcie_aspm=off` on my boot command. I'm going to add it in and run test things out again in the mean time and I'll report back. EDIT: Instant fail when i put load on it EDIT 2: Sending the drive back to Samsung for an actual replacement this time jlw-unraid-diagnostics-20240524-1933.zip Edited May 25, 20242 yr by jlw_4049
May 25, 20242 yr Community Expert Solution I don't think it's a device problem, it's usually a compatibility issue between the board/device and kernel, that's why I recommended: On 5/2/2024 at 2:03 PM, JorgeB said: trying with a different brand/model device if possible, or a different board
May 25, 20242 yr Author Unfortunately, I am past return period to get a different drive. Do you think just putting it into a USB enclosure would resolve this issue? https://bugzilla.kernel.org/show_bug.cgi?id=218455 The issue for this was resolved in kernel 6.9, UnRaid's kernel is far behind. I know there isn't anything that can be done about this, but I appreciate the help. I might try the USB enclosure as a way to use the drive for now. Edited May 25, 20242 yr by jlw_4049
May 26, 20242 yr Community Expert 16 hours ago, jlw_4049 said: Do you think just putting it into a USB enclosure would resolve this issue? It may help with that error but cause others, since USB can be flaky, though some USB bridges work OK. 16 hours ago, jlw_4049 said: The issue for this was resolved in kernel 6.9, UnRaid's kernel is far behind. v6.13 is expected to be released with kernel 6.8, and switch to 6.9 once openzfs supports it.
May 26, 20242 yr Author Quote It may help with that error but cause others, since USB can be flaky, though some USB bridges work OK. My buddy has a similar setup to mine and he has a Samsung 990 Pro, I think I have Samsung talked into trading out since i provided error messages and stuff again. Quote v6.13 is expected to be released with kernel 6.8, and switch to 6.9 once openzfs supports it. Thanks for the information on this! I'll report back here when I get the new drive and let everyone know if things are stable.
June 12, 20242 yr Author Update: replaced it for a Samsung 990 Pro 2TB. It initially did really well, but I just got the same error. I will reboot and try to apply the line `nvme_core.default_ps_max_latency_us=0 pcie_aspm=off` and report my findings. Edit: Update, made no difference. Seems like the issue happens when the drive gets > 1gb of files on it. EDIT 2: So I swapped the NVME's around. In M.2_1 I had another NVME (different brand), this was directly connected to the CPU lanes. In M.2_2 I had the Samsung NVME, this is connected via AMD's chipset. It appears that it might have resolved the issue. I'll report back. EDIT 3: Looks like this resolved the issue. So I assume it has to do with the linux kernel, samsung drives (tested 2), and AMD's chipset. The same drives that was failing in the top slot of the motherboard directly connected to the CPU lanes, is working perfectly in all tests. Edited June 12, 20242 yr by jlw_4049
June 17, 20242 yr In case it's relevant/ helpful, I've been having similar troubles. Fitted a 4tb 990 Pro with factory heatsink into M2_1 (hadn't used that slot before as I was saving it for a fast drive). Same deal with my motherboard, although it's Intel; M2_1 is tied directly to the Raptor Lake 1700 socket. The other 3 run via the chipset. Moved my appdata and Immich libraries onto it to get the best performance I could. It ran fine for more than a month, then about 3 weeks ago I had the system lock up. Had to hard-reset to get it back. Then it happened again a week or so later. Figured out that the 990 had disappeared, checked the BIOS after rebooting and it wasn't there. But if I powered down and left it for a bit, it would reappear and work fine. Did so for a week, then during the night last night it happened again. Been searching around today and found a fair few posts from folk having similar issues. In this one, they said they resolved the issue by switching the 2 NVMes. So today I've moved mine from M2_1 to M2_4 (I already had a 1tb WD Black in M.2_2 & 3, which have been fine for the 18 months since I built the server). I'm not sure if mine's dying due to high load, but probably. Most of my server's heavy lifting (backups, snapshots, mover) are running in the night, and each time the drive has died it's been overnight. Looking like this could be an issue with 990 NVMes.
June 19, 20242 yr Author Ultimately my issue was solved by swapping the drives around on the board. Looking at the bug tracker for the kernel (I posted above) there is simply just a bug causing this. UnRaid is several kernels behind and the fix won't be in UnRaid for a while. I can confirm I tested this solution with both a Samsung 980 Pro and a Samsung 990 PRO (2 TB). Since making the change I've ran about 150+ hours of encoding off of the drive and it's been rock solid.
July 15, 20241 yr Community Expert Encounterd similar problem, my hardware is maxsun w680 motherboard+intel 13500+samsung 980pro 1tb. " nvme_core.default_ps_max_latency_us=0 pcie_aspm=off " works well for 4 months on unraid 6.12.10, and it crashed several minutes age. Seems there's nothing i can do except waiting for unraid7 with newer linux kernel?
July 15, 20241 yr Author 6 minutes ago, Wizard_ said: Encounterd similar problem, my hardware is maxsun w680 motherboard+intel 13500+samsung 980pro 1tb. " nvme_core.default_ps_max_latency_us=0 pcie_aspm=off " works well for 4 months on unraid 6.12.10, and it crashed several minutes age. Seems there's nothing i can do except waiting for unraid7 with newer linux kernel? Perhaps you could buy a reputable usb 3.1 adapter to install it in and see if that can get you by in the mean time. I was going to do this but ended up finding a solution that worked for me.
July 17, 20241 yr Author Update: after nearly a month of running well the same error came back with the new drive (Samsung 990 Pro 2TB) in the 2nd slot of my motherboard. I'm going to grab this enclosure to try to use a work around until a newer kernel. I will update everyone when I get it and to see if it solves the issue as a work around for now.
July 17, 20241 yr Community Expert I'v read the post again, it seems the author didn't precisely located the bug. He just updated his linux kernel version from 6.8 (for unraid 6.12.10, linux 6.1.79) to 6.9 and the problem disappeared. I really doubt that the problem is caused by kernel bug and it will be fixed in unraid7.0 :-( By the way, i decided to unplug the 980pro until the final solution comes out. Fortunately the optane 900p aic still works well.
July 17, 20241 yr Author 2 hours ago, Wizard_ said: I'v read the post again, it seems the author didn't precisely located the bug. He just updated his linux kernel version from 6.8 (for unraid 6.12.10, linux 6.1.79) to 6.9 and the problem disappeared. I really doubt that the problem is caused by kernel bug and it will be fixed in unraid7.0 :-( By the way, i decided to unplug the 980pro until the final solution comes out. Fortunately the optane 900p aic still works well. Both of my problem drives worked great in Windows and even testing on Ubuntu. So it has something to do with the hardware/kernel/unraid. I am not 100% sure what this might be. Tomorrow my USB 3.1 NVME enclosure comes in, I'll report back and let you know it it resolves the solution for now. EDIT: I am updating UnRaid to 6.12.11 to see if the kernel fixes might have any relevance to this issue. EDIT 2: Job failed with same bug. I'll report back with results of the USB 3.1 NVME Enclosure. Edited July 17, 20241 yr by jlw_4049
July 18, 20241 yr Author I'll make a new post in case anyone was following the above issue... I ordered the above dongle and put my Samsung 990 Pro 2TB and ran the same work flow as before that was making the error happen and everything appears to be working great. It has completed a long long version of that work flow. I went ahead and tested the previous drive Samsung 980 Pro 2TB (in the dongle) and did the same work flow where it would have crashed on the motherboard. On this dongle both drives are working flawlessly. Speed testing this dongle I'm getting around 3GB's read and 1.5ish GB's write speed (it could just be the test I am doing that is limiting them), so it's plenty fast and good enough for me. I'll report back if I have any more of those errors at all with this configuration. EDIT: 27 hour job completed with that drive on the dongle. EDIT2: Another 12 hours of jobs completed. Appears stable to me. Edited July 20, 20241 yr by jlw_4049
July 22, 20241 yr I've just bought a Samsung 990 Pro /w heat shield and also had the same error this afternoon. I'm on unRAID 7 beta2 btw. Did you try update the firmware?
July 22, 20241 yr Community Expert 52 minutes ago, chrisgtl said: I've just bought a Samsung 990 Pro /w heat shield and also had the same error this afternoon. I'm on unRAID 7 beta2 btw. Did you try update the firmware? latest firmware doesn't seems helpful for my 980pro
July 22, 20241 yr Looks like my 990 Pro is already on the latest firmware too..... Can you induce this error or do you just have to wait to see if it bums out randomly?
July 24, 20241 yr Author Firmware doesn't matter in this case. I tried different variants of the drive, they simply don't work well with UnRaid/Kernel/HW we have. I have a buddy that just has to use the command and it fixes his. On 7/22/2024 at 2:05 PM, chrisgtl said: Looks like my 990 Pro is already on the latest firmware too..... Can you induce this error or do you just have to wait to see if it bums out randomly? Once I get to a file or something that causes the error, it can be reproduced. However, it's random when it hits a file like that. Also update for the dongle. The dongle was stable for along time, but I ended up having a failure today. It was a different error but I have no doubt it was related to this. So there is no actual good work around for this. Grab yourselves a WD drive for UnRaid I guess. Today I took the secondary storage drive out of my general use/game/work pc (was a WD black 1tb) and just slotted the 980 Pro 2 TB in it's place. I'll just take the storage amount loss on the drive and quit worrying about it. Edited July 24, 20241 yr by jlw_4049
July 26, 20241 yr Well I'm on day 5 after my 990 Pro first showed an error. No problems since. I'm wondering if this is something to do with C-states, as I used a guide on here to allow better power saving. After my first 990 Pro error I ran through the guide again and I'm onto day 5 without any more occurrences. I'll update again once I've given it more time.
July 26, 20241 yr Author 6 hours ago, chrisgtl said: Well I'm on day 5 after my 990 Pro first showed an error. No problems since. I'm wondering if this is something to do with C-states, as I used a guide on here to allow better power saving. After my first 990 Pro error I ran through the guide again and I'm onto day 5 without any more occurrences. I'll update again once I've given it more time. Fingers crossed, but it is inevitable and random. I went for days to weeks and ever over a month with no failures with it coming back always.
July 29, 20241 yr Just happened again, so looks like it's over to WD for my next drive. Returned the 990 Pro back to Amazon. Bought a WD 770 instead, and saved myself 50 quid in the process. Edited July 29, 20241 yr by chrisgtl
July 30, 20241 yr Author On 7/29/2024 at 2:15 AM, chrisgtl said: Just happened again, so looks like it's over to WD for my next drive. Returned the 990 Pro back to Amazon. Bought a WD 770 instead, and saved myself 50 quid in the process. Sorry to hear that. Maybe one day this will be resolved, but I wouldn't count on it very soon it appears.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.