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.

"Critical Media Error" in ubuntu linux as VM passthrough

Featured Replies

I have a NVME drive being passed through unraid as a VM to an ubuntu VM. I am currently getting random errors such as errors below. Does this actually indicate an error, or is this a setting or such? Also posted the smartctl below.

 

[Jul17 16:11] print_req_error: 14 callbacks suppressed
[  +0.000003] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  +0.074604] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074383] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.068966] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  +0.074432] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074535] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074392] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.021549] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  +0.074414] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074332] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +4.419550] print_req_error: 59 callbacks suppressed
[  +0.000009] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074354] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074440] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074299] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074701] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074286] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074340] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.075307] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074317] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  +0.074543] blk_update_request: critical medium error, dev nvme0n1, sector 2597378592 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

 

=== START OF INFORMATION SECTION ===
Model Number:                       SPCC M.2 PCIe SSD
Serial Number:                      230155785140024
Firmware Version:                   VB421D65
PCI Vendor/Subsystem ID:            0x10ec
IEEE OUI Identifier:                0x00e04c
Controller ID:                      1
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,048,408,248,320 [2.04 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            500e04 c91e050719
Local Time is:                      Sat Jul 22 08:17:04 2023 EDT
Firmware Updates (0x02):            1 Slot
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0014):     DS_Mngmt Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         32 Pages
Warning  Comp. Temp. Threshold:     100 Celsius
Critical Comp. Temp. Threshold:     110 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0   230000   50000
 1 +     4.00W       -        -    1  1  1  1     4000   50000
 2 +     3.00W       -        -    2  2  2  2     4000  250000
 3 -     0.50W       -        -    3  3  3  3     4000    8000
 4 -   0.0090W       -        -    4  4  4  4     8000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        43 Celsius
Available Spare:                    100%
Available Spare Threshold:          32%
Percentage Used:                    0%
Data Units Read:                    40,869,455 [20.9 TB]
Data Units Written:                 55,079,426 [28.2 TB]
Host Read Commands:                 873,033,683
Host Write Commands:                288,842,365
Controller Busy Time:               0
Power Cycles:                       2
Power On Hours:                     745
Unsafe Shutdowns:                   1
Media and Data Integrity Errors:    952
Error Information Log Entries:      8,627
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 8 of 8 entries)
No Errors Logged

 

  • 2 weeks later...

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

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.