BTRFS hangs on nvme drive

[mr_raider]

BTRFS demi-gods, I Beseech thee...

I'm getting random freezes which, to the best of my knowledge, is due to btrfs and my drive. WHen it locks, I have to power cycle the laptop

system info:

[FONT=monospace][COLOR=#54FF54][B]mr_raider@HP-EliteBook-725-G3[/B][/COLOR]:[COLOR=#5454FF][B]~[/B][/COLOR]$ inxi -Fx
[COLOR=#5454FF][B]System:   [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Host:[/B][/COLOR][COLOR=#B2B2B2] HP-EliteBook-725-G3 [/COLOR][COLOR=#5454FF][B]Kernel:[/B][/COLOR][COLOR=#B2B2B2] 4.15.0-36-generic x86_64 [/COLOR][COLOR=#5454FF][B]bits:[/B][/COLOR][COLOR=#B2B2B2] 64 [/COLOR][COLOR=#5454FF][B]gcc:[/B][/COLOR][COLOR=#B2B2B2] 7.3.0[/COLOR]
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Desktop:[/B][/COLOR][COLOR=#B2B2B2] KDE Plasma 5.13.5 (Qt 5.11.1) [/COLOR][COLOR=#5454FF][B]Distro:[/B][/COLOR][COLOR=#B2B2B2] KDE neon User Edition 5.13                                     [/COLOR] 
[COLOR=#5454FF][B]Machine:  [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Device:[/B][/COLOR][COLOR=#B2B2B2] laptop [/COLOR][COLOR=#5454FF][B]System:[/B][/COLOR][COLOR=#B2B2B2] HP [/COLOR][COLOR=#5454FF][B]product:[/B][/COLOR][COLOR=#B2B2B2] HP EliteBook 725 G3 [/COLOR][COLOR=#5454FF][B]serial:[/B][/COLOR][COLOR=#B2B2B2] N/A                                            [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Mobo:[/B][/COLOR][COLOR=#B2B2B2] HP [/COLOR][COLOR=#5454FF][B]model:[/B][/COLOR][COLOR=#B2B2B2] 8084 [/COLOR][COLOR=#5454FF][B]v:[/B][/COLOR][COLOR=#B2B2B2] KBC Version 75.70 [/COLOR][COLOR=#5454FF][B]serial:[/B][/COLOR][COLOR=#B2B2B2] N/A [/COLOR][COLOR=#5454FF][B]UEFI:[/B][/COLOR][COLOR=#B2B2B2] HP [/COLOR][COLOR=#5454FF][B]v:[/B][/COLOR][COLOR=#B2B2B2] N73 Ver. 01.23 [/COLOR][COLOR=#5454FF][B]date:[/B][/COLOR][COLOR=#B2B2B2] 03/26/2018             [/COLOR] 
[COLOR=#5454FF][B]Battery   [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]BAT0:[/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]charge:[/B][/COLOR][COLOR=#B2B2B2] 31.4 Wh 81.8% [/COLOR][COLOR=#5454FF][B]condition:[/B][/COLOR][COLOR=#B2B2B2] 38.4/38.4 Wh (100%)                                                    [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]model:[/B][/COLOR][COLOR=#B2B2B2] Hewlett-Packard Primary [/COLOR][COLOR=#5454FF][B]status:[/B][/COLOR][COLOR=#B2B2B2] Discharging                                                            [/COLOR] 
[COLOR=#5454FF][B]CPU:      [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Quad core[/B][/COLOR][COLOR=#B2B2B2] AMD PRO A12-8800B R7 12 Compute Cores 4C+8G (-MCP-) [/COLOR][COLOR=#5454FF][B]arch:[/B][/COLOR][COLOR=#B2B2B2] Excavator rev.1 [/COLOR][COLOR=#5454FF][B]cache:[/B][/COLOR][COLOR=#B2B2B2] 4096 KB            [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]flags:[/B][/COLOR][COLOR=#B2B2B2] (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) [/COLOR][COLOR=#5454FF][B]bmips:[/B][/COLOR][COLOR=#B2B2B2] 16768                                       [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]clock speeds:[/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]max:[/B][/COLOR][COLOR=#B2B2B2] 2100 MHz [/COLOR][COLOR=#5454FF][B]1:[/B][/COLOR][COLOR=#B2B2B2] 1967 MHz [/COLOR][COLOR=#5454FF][B]2:[/B][/COLOR][COLOR=#B2B2B2] 2035 MHz [/COLOR][COLOR=#5454FF][B]3:[/B][/COLOR][COLOR=#B2B2B2] 1707 MHz [/COLOR][COLOR=#5454FF][B]4:[/B][/COLOR][COLOR=#B2B2B2] 1712 MHz                                   [/COLOR] 
[COLOR=#5454FF][B]Graphics: [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Card:[/B][/COLOR][COLOR=#B2B2B2] Advanced Micro Devices [AMD/ATI] Carrizo [/COLOR][COLOR=#5454FF][B]bus-ID:[/B][/COLOR][COLOR=#B2B2B2] 00:01.0                                                [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Display Server:[/B][/COLOR][COLOR=#B2B2B2] x11 (X.Org 1.19.6 ) [/COLOR][COLOR=#5454FF][B]drivers:[/B][/COLOR][COLOR=#B2B2B2] ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)             [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Resolution:[/B][/COLOR][COLOR=#B2B2B2] 1366x768@59.99hz                                                                                  [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]OpenGL: renderer:[/B][/COLOR][COLOR=#B2B2B2] AMD Radeon R7 Graphics (CARRIZO / DRM 3.23.0 / 4.15.0-36-generic, LLVM 6.0.0)               [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]version:[/B][/COLOR][COLOR=#B2B2B2] 4.5 Mesa 18.0.5 [/COLOR][COLOR=#5454FF][B]Direct Render:[/B][/COLOR][COLOR=#B2B2B2] Yes                                                                   [/COLOR] 
[COLOR=#5454FF][B]Audio:    [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Card-1[/B][/COLOR][COLOR=#B2B2B2] Advanced Micro Devices [AMD] Device 157a [/COLOR][COLOR=#5454FF][B]driver:[/B][/COLOR][COLOR=#B2B2B2] snd_hda_intel [/COLOR][COLOR=#5454FF][B]bus-ID:[/B][/COLOR][COLOR=#B2B2B2] 00:09.2                         [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Card-2[/B][/COLOR][COLOR=#B2B2B2] Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio [/COLOR][COLOR=#5454FF][B]driver:[/B][/COLOR][COLOR=#B2B2B2] snd_hda_intel [/COLOR][COLOR=#5454FF][B]bus-ID:[/B][/COLOR][COLOR=#B2B2B2] 00:01.1            [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Sound:[/B][/COLOR][COLOR=#B2B2B2] Advanced Linux Sound Architecture [/COLOR][COLOR=#5454FF][B]v:[/B][/COLOR][COLOR=#B2B2B2] k4.15.0-36-generic                                                [/COLOR] 
[COLOR=#5454FF][B]Network:  [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Card-1:[/B][/COLOR][COLOR=#B2B2B2] Broadcom Limited NetXtreme BCM5762 Gigabit Ethernet PCIe [/COLOR][COLOR=#5454FF][B]driver:[/B][/COLOR][COLOR=#B2B2B2] tg3 [/COLOR][COLOR=#5454FF][B]v:[/B][/COLOR][COLOR=#B2B2B2] 3.137 [/COLOR][COLOR=#5454FF][B]bus-ID:[/B][/COLOR][COLOR=#B2B2B2] 01:00.0         [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]IF:[/B][/COLOR][COLOR=#B2B2B2] enp1s0 [/COLOR][COLOR=#5454FF][B]state:[/B][/COLOR][COLOR=#B2B2B2] down [/COLOR][COLOR=#5454FF][B]mac:[/B][/COLOR][COLOR=#B2B2B2] ec:8e:b5:a4:33:ea                                                                 [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Card-2:[/B][/COLOR][COLOR=#B2B2B2] Intel Wireless 7265 [/COLOR][COLOR=#5454FF][B]driver:[/B][/COLOR][COLOR=#B2B2B2] iwlwifi [/COLOR][COLOR=#5454FF][B]bus-ID:[/B][/COLOR][COLOR=#B2B2B2] 02:00.0                                                   [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]IF:[/B][/COLOR][COLOR=#B2B2B2] wlp2s0 [/COLOR][COLOR=#5454FF][B]state:[/B][/COLOR][COLOR=#B2B2B2] up [/COLOR][COLOR=#5454FF][B]mac:[/B][/COLOR][COLOR=#B2B2B2] a4:02:b9:44:e6:61                                                                   [/COLOR] 
[COLOR=#5454FF][B]Drives:   [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]HDD Total Size:[/B][/COLOR][COLOR=#B2B2B2] 512.1GB (23.1% used)                                                                          [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]ID-1:[/B][/COLOR][COLOR=#B2B2B2] /dev/nvme0n1 [/COLOR][COLOR=#5454FF][B]model:[/B][/COLOR][COLOR=#B2B2B2] WDC_WDS512G1X0C [/COLOR][COLOR=#5454FF][B]size:[/B][/COLOR][COLOR=#B2B2B2] 512.1GB [/COLOR][COLOR=#5454FF][B]temp:[/B][/COLOR][COLOR=#B2B2B2] 50C                                             [/COLOR] 
[COLOR=#5454FF][B]Partition:[/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]ID-1:[/B][/COLOR][COLOR=#B2B2B2] / [/COLOR][COLOR=#5454FF][B]size:[/B][/COLOR][COLOR=#B2B2B2] 423G [/COLOR][COLOR=#5454FF][B]used:[/B][/COLOR][COLOR=#B2B2B2] 97G (23%) [/COLOR][COLOR=#5454FF][B]fs:[/B][/COLOR][COLOR=#B2B2B2] btrfs [/COLOR][COLOR=#5454FF][B]dev:[/B][/COLOR][COLOR=#B2B2B2] /dev/nvme0n1p3                                              [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]ID-2:[/B][/COLOR][COLOR=#B2B2B2] /home [/COLOR][COLOR=#5454FF][B]size:[/B][/COLOR][COLOR=#B2B2B2] 423G [/COLOR][COLOR=#5454FF][B]used:[/B][/COLOR][COLOR=#B2B2B2] 97G (23%) [/COLOR][COLOR=#5454FF][B]fs:[/B][/COLOR][COLOR=#B2B2B2] btrfs [/COLOR][COLOR=#5454FF][B]dev:[/B][/COLOR][COLOR=#B2B2B2] /dev/nvme0n1p3                                          [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]ID-3:[/B][/COLOR][COLOR=#B2B2B2] swap-1 [/COLOR][COLOR=#5454FF][B]size:[/B][/COLOR][COLOR=#B2B2B2] 15.99GB [/COLOR][COLOR=#5454FF][B]used:[/B][/COLOR][COLOR=#B2B2B2] 0.00GB (0%) [/COLOR][COLOR=#5454FF][B]fs:[/B][/COLOR][COLOR=#B2B2B2] swap [/COLOR][COLOR=#5454FF][B]dev:[/B][/COLOR][COLOR=#B2B2B2] /dev/nvme0n1p2                                     [/COLOR] 
[COLOR=#5454FF][B]RAID:     [/B][/COLOR][COLOR=#B2B2B2] No RAID devices: /proc/mdstat, md_mod kernel module present                                                   [/COLOR] 
[COLOR=#5454FF][B]Sensors:  [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]System Temperatures: cpu:[/B][/COLOR][COLOR=#B2B2B2] 52.6C [/COLOR][COLOR=#5454FF][B]mobo:[/B][/COLOR][COLOR=#B2B2B2] 0.0C [/COLOR][COLOR=#5454FF][B]gpu:[/B][/COLOR][COLOR=#B2B2B2] 52.0                                                          [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Fan Speeds (in rpm): cpu:[/B][/COLOR][COLOR=#B2B2B2] N/A                                                                                 [/COLOR] 
[COLOR=#5454FF][B]Info:     [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Processes:[/B][/COLOR][COLOR=#B2B2B2] 230 [/COLOR][COLOR=#5454FF][B]Uptime:[/B][/COLOR][COLOR=#B2B2B2] 13 min [/COLOR][COLOR=#5454FF][B]Memory:[/B][/COLOR][COLOR=#B2B2B2] 1289.1/7452.2MB [/COLOR][COLOR=#5454FF][B]Init:[/B][/COLOR][COLOR=#B2B2B2] systemd [/COLOR][COLOR=#5454FF][B]runlevel:[/B][/COLOR][COLOR=#B2B2B2] 5 [/COLOR][COLOR=#5454FF][B]Gcc sys:[/B][/COLOR][COLOR=#B2B2B2] 7.3.0                [/COLOR] 
[COLOR=#5454FF][B]          [/B][/COLOR][COLOR=#B2B2B2] [/COLOR][COLOR=#5454FF][B]Client:[/B][/COLOR][COLOR=#B2B2B2] Shell (bash 4.4.191) [/COLOR][COLOR=#5454FF][B]inxi:[/B][/COLOR][COLOR=#B2B2B2] 2.3.56                                     [/COLOR]
[/FONT]

dmesg:

[FONT=monospace]$ dmesg | grep nvme
[    2.035205] [COLOR=#FF5454][B]nvme[/B][/COLOR] [COLOR=#FF5454][B]nvme[/B][/COLOR]0: pci function 0000:04:00.0
[    2.263221]  [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1: p1 p2 p3
[    5.614491] BTRFS: device fsid d55dc8c1-28f2-4aaf-94cb-717a4ba5a56b devid 1 transid 214423 /dev/[COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3
[    5.615005] BTRFS info (device [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3): disk space caching is enabled
[    5.615007] BTRFS info (device [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3): has skinny extents
[    5.617866] BTRFS info (device [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3): bdev /dev/[COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3 errs: wr 39, rd 16, flush 0, corrupt 0, gen 0
[    5.660924] BTRFS info (device [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3): enabling ssd optimizations
[    6.114666] BTRFS info (device [COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p3): disk space caching is enabled
[    6.807895] Adding 15617020k swap on /dev/[COLOR=#FF5454][B]nvme[/B][/COLOR]0n1p2. Priority:-2 extents:1 across:15617020k SSFS

[/FONT]

Drive is a Wd black.

[Snowhog]

I'm going to ask; because I KNOW it will be mentioned: Why do you believe that btrfs is involved in the freezes?

An approach to maybe identifying what might be involved, would be to launch konsole and run top or htop (if it's installed) and leave it running and visible. When a freeze occurs, what processes are showing in top/htop?

[Thomas00]

Have you ever tried to switch to tty2 when the system hangs? I am asking because I am running btrfs on a nvme drive and experience crashes which up to now I haven't been able to narrow down to a root cause.
When I switch to tty2 I get lots of drive related errors. Like in your case the only way out is a power cycle.

https://www.kubuntuforums.net/showthread.php/74421-Frequent-OS-crashes-looking-for-troubleshooting-ideas

[mr_raider]

Have you ever tried to switch to tty2 when the system hangs? I am asking because I am running btrfs on a nvme drive and experience crashes which up to now I haven't been able to narrow down to a root cause.
When I switch to tty2 I get lots of drive related errors. Like in your case the only way out is a power cycle.

https://www.kubuntuforums.net/showthread.php/74421-Frequent-OS-crashes-looking-for-troubleshooting-ideas

Yes. I can switch to tty1 but I can't even log in. The only way out is to press ctrl-alt-del 7 times, and then I get btrfs i/o error.

It may not actually be btrfs, but the nvme driver also. I have two other PCs with NVME drives with no issue in Linux.

[Thomas00]

Same here, when the machine crashes I can't log in any longer but the error messages will nevertheless appear.

[oshunluvr]

It's easy to blame something not fully understood for issues that don't have a clear causes, but I have serious doubts that a file system would cause either problem. Simple enough to prove - stop using btrfs and see if your problem goes away.

There is one functionality of btrfs that may cause excessive CPU load which might appear to be a "hang" event - quotas. Disable quotas if you enabled it (it's off by default) and don't re-enable it until they fix the krenel problem associated with it.

Usually, random events - especially those that do not issue log reports, and I see none here - are hardware related, meaning mostly defective hardware but sometimes drivers. I would start by verifying your BIOS is up-to-date. NVME and it's interfaces are very new in the consumer world. Then I would check for driver errors, which should produce error logs. If the problem is new, try an older kernel. If you can, booting to a different drive and see if the problem stops. Also, run the drive though some testing.

[Thomas00]

I agree, at least for my case. I started to keep track of my crashes in the hope to find comunalities. My current suspicion is that it’s got to do with driver/hardware/kernel but not with btrfs. Actually btrfs has proven to be very resilient given the number of freezes I had up to now.

[mr_raider]

Well I loaded a live USB and btrfs check found errors. I repaired them and did a Balance so we'll see.

It might be the errors were due to nvme hangs. I disable the PCIe power saving states. We'll see if that helps.

I can always go back to plain Sata drives if I have to.

Sent from my ONEPLUS A5010 using Tapatalk

[jlittle]

I'm not sure if my experience is relevant to your situation, and so I didn't respond at first, but maybe it is.

I installed Kubuntu 16.04 on a new desktop in 2016 on btrfs and it ran really well. plasmashell crashed occasionally but it restarted automatically and had little effect. Then, early this year on 17.10 I started getting lock-ups and sometimes horrible boot errors, which gradually got worse until a lock-up usually occurred before I could log in, or within a second or two of logging in. Once in this state I got nearly three days up, but then not again. I installed an 18.04 beta in another subvolume in the same btrfs, and, other than repeating two years of configuration and installing had no further trouble.

• I never considered that btrfs was in any way the cause of the trouble, and since I'm still on the same file system, I've now concluded it wasn't
• a few days before I had trouble there was a big storm which took out the power while the computer was powered on but suspended; maybe that did something
• the cleaner unplugged the computer, also while it was suspended; I've learned to do a shutdown before she comes
• when I first had trouble I should have switched to a month old snapshot, or to a two month old backup of the OS; if that had solved things I would have saved much time and effort
• I've documented my set up much more carefully now, still not what I'd call good, but better

I think it's likely your OS is in a bad state, if not from the underlying problem then from all the power-offs, and you're in for a reinstall. Since you don't have confidence in btrfs, I suggest repartitioning to have a 25 GB or so ext4 file system for root, and do a fresh install to that. If that runs well, good, but if the trouble recurs you've isolated it somewhat.

[GreyGeek]

Do the problems in this link look familiar? https://github.com/spdk/spdk/issues/400

[mr_raider]

Do the problems in this link look familiar? https://github.com/spdk/spdk/issues/400

No. I ran an fstrim from the terminal and I'm getting a hang with I/0 page fault errors.

My guess is something is wrong with the nvme interface. I can't tell if it's the drive or the chipset. I have two other PC's (AMD and Intel) using nvme drives with no issues.

I'll try a secure erase and reinstall tomorrow.

Sent from my ONEPLUS A5010 using Tapatalk

[mr_raider]

Ok. DId some testing. This seems to be an issue with btrfs is handled by this controller. My guess is my hangs were happening during fstrim background operations.

I secure erased the whole drive and booted a live USB for testing.

If I configure the drive with a single ext4 partition, and then mount it, I can issue an fstrim command to the mounted filesystem and it completes after some time.

If I configure the drive with a single btrfs partition, and then mount it, I can issue an fstrim command to the mounted filesystem and it hangs and never completes. dmesg shows that the nvme controller just gives up after 2 minutes and teh drive disappears.

If I configure the drive with ext4 and btrfs partitions, I can fstrim the ext4 partition, but the btrfs partition gives the same hang.

I know btrfs TRIM actions take much longer than ext4. My guess is the drive is entering some kind of power saving mode during certain disk I/O operations. Or the AMD controller may be flaky, but I have other AMD PCs that use nvme just fine.

If anyone else has the same drive (WD Black M.2 pci-e 512GB) they can try it too.

For now I re-installed in ext4 format on this laptop.

[mr_raider]

Well switched out the WD black for an Intel 6000p and seems to have solved the issue. BTRFS is working again and fstrim is fine.

Moved teh WD Black into an Intel machine, and now it's running Neon 18.04 with no issues. Must be some compatibility thing with AMD's controller.

[GreyGeek]

Glad you got it resolved.
I wonder if there are hardware settings in the HD bios that could correct that WD Black M.2 pci-e 512GB problem?

https://support.wdc.com/knowledgebas...=17144&lang=en