The server runs for several hours, after which errors appear. There is only one sda disk on the proxmox server

[SQWL]

pve kernel: [ 7348.425199] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.426099] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.427045] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.427781] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.428610] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.429508] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.430234] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.431015] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.432010] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.432547] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.433290] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7348.434169] sd 9:0:0:1: rejecting I/O to offline device
pve kernel: [ 7348.434817] sd 9:0:0:1: rejecting I/O to offline device
pve kernel: [ 7348.435513] sd 9:0:0:1: rejecting I/O to offline device
pve kernel: [ 7370.117104] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7370.117488] print_req_error: 20 callbacks suppressed
pve kernel: [ 7370.117490] blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
pve kernel: [ 7370.118252] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7370.118682] blk_update_request: I/O error, dev sdb, sector 3466844354 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
pve kernel: [ 7400.117163] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7400.117550] blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
pve kernel: [ 7400.118307] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7400.118740] blk_update_request: I/O error, dev sdb, sector 3406329130 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
pve kernel: [ 7400.119464] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7400.120088] blk_update_request: I/O error, dev sdb, sector 3438194093 op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
pve kernel: [ 7400.120801] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7400.121446] blk_update_request: I/O error, dev sdb, sector 3438194093 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
pve kernel: [ 7401.115324] sd 9:0:0:0: rejecting I/O to offline device
pve kernel: [ 7401.115688] blk_update_request: I/O error, dev sdb, sector 3466844354 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
pve kernel: [ 7430.117343] sd 9:0:0:0: rejecting I/O to offline device

 

[fschauer]

Check the SMART values of your drive

smartctl -a /dev/sdX

Does it show any errors?

 

[SQWL]

Check the SMART values of your drive

smartctl -a /dev/sdX

Does it show any errors?

Smartctl open device: /dev/sdb failed: No such device

 

[fschauer]

Does the drive maybe show up under a different name somewhere when you run

lsblk

 

[SQWL]

Does the drive maybe show up under a different name somewhere when you run

lsblk

proxmox server download log

sd 5:0:0:0: [sda] Write Protect is off
sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3

 

[SQWL]

Does the drive maybe show up under a different name somewhere when you run

lsblk

 

[fschauer]

The kernel seems to be trying to access a device that doesn't even exist...
What does your /etc/fstab file look like?

 

[SQWL]

The kernel seems to be trying to access a device that doesn't even exist...
What does your /etc/fstab file look like?

/dev/pve/root / ext4 errors=remount-ro 0 1

UUID=****-****/boot/efi vfat defaults 0 1

/dev/pve/swap none swap sw 0 0

proc /proc proc defaults 0 0

 

[bbgeek17]

What is the output of: journalctl -b -0 |grep 9:0:0:

and/or: dmesg|grep 9:0:0:

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[SQWL]

What is the output of: journalctl -b -0 |grep 9:0:0:

and/or: dmesg|grep 9:0:0:

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[bbgeek17]

That does not make sense. You can try "journalctl |grep 9:0:0:"
If there is no output, then perhaps you lost all prior logs. Its impossible for kernel to complain about a device that apparently it never saw before...
You can also try reboot and then grep again

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox