[Proxmox/Debian 12] Drives randomly disconnect an unmount

[Proxmox/Debian 12] Drives randomly disconnect an unmount
from ohshit604@sh.itjust.works to linux@lemmy.ml on 31 Jul 11:18
https://sh.itjust.works/post/43154253

Hey y’all

I’ve been running into this issue on my home’s server, the host OS is Proxmox while i have a Debian 12 VM running within it as a VM i have two external HDD’s (1tb, 5tb) running in a drive bay which are randomly disconnecting from the server and i can’t seem to make heads or tails of the error in my journalctl, i don’t think there is corruption on the drives but i’m hesitant to run any checks as i cannot back these up given how full they are.

The drives typically get recogniced under a different device name/ID right away. for example, /dev/sdb1 will now be /dev/sdd1, and that cycle just repeats every time they disconnect

This is kinda frustrating having to re-mount and re-add these to the VM, is there any way i could simply automate the re-mount of these drives and have the VM pick it up right away?

Jul 30 21:00:53 proxmox kernel:  sdb: sdb1
Jul 30 21:00:53 proxmox kernel:  sdc: sdc1
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159851824 op 0x0:(READ) flags 0x200000 phys_seg 5 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438525440 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=30s
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED to get lock err -19
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED err -19
Jul 30 21:00:52 proxmox kernel: usb 4-1: device firmware changed
Jul 30 21:00:52 proxmox kernel: usb 4-1: reset SuperSpeed USB device number 7 using xhci_hcd
Jul 30 21:00:52 proxmox kernel: scsi host4: uas_eh_device_reset_handler start
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Jul 30 20:59:59 proxmox kernel: critical medium error, dev sdd, sector 6653857080 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
Jul 30 20:59:59 proxmox kernel: blk_print_req_error: 47 callbacks suppressed
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cd 38 00 00 04 00 00 00
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Add. Sense: Unrecovered read error
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Sense Key : Medium Error [current] 
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jul 30 20:56:01 proxmox postfix/smtp[3945942]: 2F670200A1A: to=<proxmox.snowcap946@passmail.net>, relay=mx2.simplelogin.co[176.119.200.136]:25, delay=330448, delays=330369/0.01/79/0, dsn=4.4.2, status=deferred (l>
Jul 30 20:55:42 proxmox postfix/smtp[3945942]: 2F670200A1A: lost connection with mx2.simplelogin.co[185.205.70.136] while receiving the initial server greeting

#linux

threaded - newest

Strit@lemmy.linuxuserspace.show on 31 Jul 11:25 next collapse

I/O errosr usually indicate that the drives are about to fail. I’d start looking for new drives and transfer data as soon as possible.

ohshit604@sh.itjust.works on 31 Jul 11:43 collapse

Well that’s worrisome, I suppose this is where I start looking for replacements. Thank you!

Broadfern@lemmy.world on 31 Jul 12:19 next collapse

Echoing the other user; I just worked on a data recovery job with your symptoms near identical. Back up your important files while you still have them and get new ones ASAP; preferably some form of SSD.

This is hardware failure, not driver error. Your files will start to corrupt if you wait too long.

ohshit604@sh.itjust.works on 31 Jul 15:45 collapse

Back up your important files while you still have them and get new ones ASAP; preferably some form of SSD

Unfortunately I’m going to have to until pay day for me to replace the drives, and I currently don’t have 6tb to back up to, I was thinking of getting a 10tb western digital NAS drive as it is significantly cheaper than a 10tb SSD.

Granted an SSD would be ideal if I can find one relatively ”cheap” that still has a NAND chip for caching.

just_another_person@lemmy.world on 31 Jul 13:07 next collapse

Do they BOTH disconnect at the same time?
Is this connected over USB?

Edit: nevermind, looked closer at the logs. You USB device is resetting as it says right there in the logs. Either that carrier is on the fritz, or you have power saving features on the USB port it’s connected to, and it’s shutting the port down when it thinks it’s inactive.

If you don’t have another way to connect these drives to your machine, then do this: danielbrennand.com/…/proxmox-fix-usb-disconnect/#…

ohshit604@sh.itjust.works on 31 Jul 17:13 collapse

Do they BOTH disconnect at the same time?

Is this connected over USB?

Yup they disconnect at the same time, it uses USB for data transfer however, the dock does have its own power supply.

If you don’t have another way to connect these drives to your machine, then do this: danielbrennand.com/…/proxmox-fix-usb-disconnect/#…

I’ll give this a shot when I get home, I have an 2.5” SSD that is connected to a regular USB 3.0 port that isn’t shutting off like the HDD’s so I’m skeptical to think that a power saving feature is causing this.

Thank you!

just_another_person@lemmy.world on 31 Jul 18:58 collapse

If the 2.5" draws power from that USB port, then that port will always be seen as “in-use” by your machine. If your carrier has its own power source, then it could be seen as idle from time to time.

ohshit604@sh.itjust.works on 31 Jul 19:43 collapse

That’s fair, I’ve updated my grub to reflect the changes you linked earlier, I’ll give the machine a good ol fashioned reboot once I get home.

Thanks again.

just_another_person@lemmy.world on 01 Aug 00:30 collapse

👍

Eggymatrix@sh.itjust.works on 31 Jul 21:18 next collapse

Usb is weird, it works for external drives to put or retrieve the odd file from an external HDD, but feature creep made it unusable for VMs unless you tweak it to hell and back.

Stowaway@midwest.social on 01 Aug 03:32 collapse

I had a similar issue with a SAS drive In the backplane of a dell server. I thought for sure the drive was failing. Reseated it, cleaned the ports, ran some tests, just kept failing without any obvious signs why it was. Replaced it with a spare and same issue. That seemed very unlikely, so I put the old drive in another slot and its still running just fine going on 2 years without an issue. If you have another toaster give it a try.

The market is rife with cheapo junk tech. Ive seen several crapo off brand drive toasters fail, so thats possible. I don’t know the brand of yours so I can’t speak to them.

It could also just be the power supply for the toaster is crapping out, or doesn’t provide enough amperage. Those power supplies dont always keep providing the same amount of power forever, sometimes it drops over time, and that could be the cause too. Or they could be poorly made, meaning they probably drop in even short time periods.

If you have another power supply with the same voltage and higher amperage, you could try that. You could also try running only one drive in there and see if it keeps failing, if no issues, you could try the other drive and see if that one has issues. If that one doesn’t have issues either it could indicate power issues.