Critical Medium Error

[parv811]

I have installed Proxmox on my nvme and it's been working fine for 4 months but all of a sudden I am getting this error.Can anyone help me this?

class 0
[
27.7710531 blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 28.9407901 blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 30.0958341 blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[
31.1806111 blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 32.3283591 blk_update_request: critical medium error, dev numeon1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 33.594595] blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 34.7797451 blk_update_request: critical medium error, dev numeon1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 36.0147371 blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 37.1690981 blk_update_request: critical medium error, dev nume@n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 38.3575101 blk_update_request: critical medium error, dev numeon1, sector 951753264 op 0x0: (READ) flags 0x0 phys seg 1 prio
class 0
[ 39.634102] blk_update_request: critical medium error, dev nume0n1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class
[ 40.811247] blk_update_request: critical medium error, dev numeon1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
[ 42.067124] blk_update_request: critical medium error, dev numeon1, sector 951753264 op 0x0: (READ) flags 0x0 phys_seg 1 prio
class 0
2 logical volume(s) in volume group "pue" now active
/dev/mapper/pve-root: One or more block group descriptor checksums are invalid. FIXED.
/dev/mapper/pve-root: Group descriptor 576 checksum is 0x2367, should be Oxbf99.
/dev/mapper/pve-root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/mapper/pve-root requires a manual fsck
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
(initramfs)
(initramfs)
(initramfs) ..

 

[alexskysilk]

yes. your nvme manufacturer's rma department can.

 

[leesteken]

Unless Proxmox has worn out your drive beyond the number of writes guaranteed by the manufacturer, I expect that you can get it replaced.

EDIT: Have a look at the output of smartctl -a /dev/nvme0n1 and lookup the specifications for the drive, and see if it was worn out or had some kind of error.
(Did your copy all the messages manually? "numeon1" should probably be nvme0n1.)

 

[parv811]

Unless Proxmox has worn out your drive beyond the number of writes guaranteed by the manufacturer, I expect that you can get it replaced.

EDIT: Have a look at the output of smartctl -a /dev/nvme0n1 and lookup the specifications for the drive, and see if it was worn out or had some kind of error.
(Did your copy all the messages manually? "numeon1" should probably be nvme0n1.)

I have copied it through Apple but here disk looks good in SMART