Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Issues with NVME disks

Dennusb
in General Support

Featured Replies

Hi,

I have a Ugreen DXP4800 Plus running for two weeks now with 2 brand new Samsung_SSD_990_PRO_1TB_S7HDNJ0Y913248M NVME disks in a pool (for fast storage).
After a while i see this in the logs

Jan 10 12:35:30 Server01 kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x11

Jan 10 12:35:30 Server01 kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?

Jan 10 12:35:30 Server01 kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug

Jan 10 12:35:30 Server01 kernel: nvme nvme0: D3 entry latency set to 10 seconds

Jan 10 12:36:33 Server01 kernel: nvme nvme0: I/O tag 16 (7010) QID 0 timeout, disable controller

Jan 10 12:36:33 Server01 kernel: nvme nvme0: Disabling device after reset failure: -4

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488758304 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 969960336 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175902, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175903, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488692992 op 0x1:(WRITE) flags 0x101000 phys_seg 8 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175904, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 3759688 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175905, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175906, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488693248 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175907, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488693568 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175908, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488693888 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175909, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488698816 op 0x1:(WRITE) flags 0x101000 phys_seg 3 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175910, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488699296 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 175911, rd 1372, flush 955, corrupt 0, gen 0

Jan 10 12:36:33 Server01 kernel: I/O error, dev nvme0n1, sector 488699392 op 0x1:(WRITE) flags 0x101000 phys_seg 3 prio class 2

Jan 10 12:36:33 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:36:33 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:36:33 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:36:33 Server01 kernel: BTRFS error (device nvme2n1p1): error writing primary super block to device 2

Jan 10 12:37:03 Server01 kernel: btrfs_dev_stat_inc_and_print: 422 callbacks suppressed

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176333, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176334, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176335, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176336, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176337, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176338, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176339, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176340, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176341, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): bdev /dev/nvme0n1p1 errs: wr 176342, rd 1372, flush 956, corrupt 0, gen 0

Jan 10 12:37:03 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:37:03 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:37:03 Server01 kernel: BTRFS warning (device nvme2n1p1): lost super block write due to IO error on /dev/nvme0n1p1 (-5)

Jan 10 12:37:03 Server01 kernel: BTRFS error (device nvme2n1p1): error writing primary super block to device 2

Jan 10 12:37:08 Server01 kernel: btrfs_dev_stat_inc_and_print: 83 callbacks suppressed

After which the secondary NVME drive goes offline in the Unraid GUI. I already checked if they are installed properly, they are.

What could this be? A bad NVME drive? Or something else totally?

  • Quote
    • Community Expert
    18 hours ago, Dennusb said:

    Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug

    Try adding this to syslinux cfg, it helps sometimes.

    on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

    nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

    e.g.:

    append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

    Power cycle the server and see if it makes a difference.

  • Quote

    • 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.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.