[SOLVED] HDD Passthrough from Proxmox host to VM no longer syncing like it used to?

[sabidawg]

Hi all, I was hoping someone was able to point out what change has happened to my small home-lab setup.
For quite sometime I have had 2 HDD's (one for downloads the other for plex media) passthrough to a VM.
I have just recently purchased a new HDD for my plex media and migrated the data across.
In the past when downloading from the VM or making any changes to the HDD from the VM side, the files would be visible on every other container/VM that had the drives passed through and mounted and as-well as the host OS pretty much immediately.
Now for some reason since I have migrated the data across to the new HDD and passed it through to the VM, I can no longer see the data appear on the hdd from another container, VM or the host server until I reset the server. Same is true the other way, If I create a folder on the HDD from the Host OS, that folder does not appear visible until I reboot. It is like it is taking a snapshot of the data but not allowing the changes to be present until reboot?


I am using this guide https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM) which is the same guide I used last time.

The only changes I can think of is the last HDD was MBR where as I had to format this one as GPT due to size.
If someone would be willing to provide some input as to what is going on that would be greatly appreciated.
Please also let me know what config files or logs I should post.
Thank you.

 

[Dunuin]

But I hope you never mount that HDD at the same time to multiple machines (host/LXC/VM)? If you do you will corrupt your data.

 

[sabidawg]

But I hope you never mount that HDD at the same time to multiple machines (host/LXC/VM)? If you do you will corrupt your data.

Yes I did... But I have just been on a learning journey today about not mounting a HDD on 2 separate OS's simultaneously.. I may have corrupted my data now which is no real biggie for as most of it is just plex media which can be redownloaded if needed.

So now I am trying to figure out the best way to set up my system.
Ideally I want to pass through the HDD to a VM and then allow a separate container to access it.

 

[Dunuin]

Easiest would be to setup NAS VM (for example OpenMediaVault 6 would be a simple and not demanding NAS OS), then use disk passthrough to bring your HDD into the VM. Then use that NAS VM as a SMB/NFS server to share the folders on your passthroughed HDD. You can then mount the NFS/SMB shares inside your other VMs, privileged LXCs or even on your PVE host. With that all of them can access the folders in parallel. For unprivileged LXCs it is more complex, as you can't directly mount NFS/SMB share inside them. As a workaround you would need to mount the SMB/NFS shares on your PVE host and then use bind-mounts with manual user remapping to bring them from the host into that unprivileged LXC.

 

[sabidawg]

Easiest would be to setup NAS VM (for example OpenMediaVault 6 would be a simple and not demanding NAS OS), then use disk passthrough to bring your HDD into the VM. Then use that NAS VM as a SMB/NFS server to share the folders on your passthroughed HDD. You can then mount the NFS/SMB shares inside your other VMs, privileged LXCs or even on your PVE host. With that all of them can access the folders in parallel. For unprivileged LXCs it is more complex, as you can't directly mount NFS/SMB share inside them. As a workaround you would need to mount the SMB/NFS shares on your PVE host and then use bind-mounts with manual user remapping to bring them from the host into that unprivileged LXC.

Excellent. Thankyou very much. This is the type of stuff I am looking for. I started looking at SMB but could only access a share on the priv container in which I was considering just using instead. However this will be a fun learning so I will give this one a go.

Thank you again.

 

[sabidawg]

Ok so now my setup has been modified to have OMV as a VM which I have passed through disks from proxmox and created share directories I have then mounted the SAMBA/CIFS share onto another VM and an un-priv container. Everything seems to be accessible, The VM with the share mount can modify delete and add things and the container can naturally read only which is perfect. However on the booting of the OMV I am getting an error.
Now I am assuming this due to when I had mounted it simultaneously but I am wondering if this indicates a hdd failure or just data corruption?

Oct 23 18:39:15 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:15 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:15 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:15 pve kernel: ata4.00: cmd c8/00:00:30:18:00/00:00:00:00:00/e0 tag 0 dma 131072 in res 51/40:00:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:15 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:15 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:16 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:16 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:16 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:16 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:16 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 30 00 00 01 00 00 00
Oct 23 18:39:16 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x200000 phys_seg 1 prio class 0
Oct 23 18:39:16 pve kernel: ata4: EH complete
Oct 23 18:39:19 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:19 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:19 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:19 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:19 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:19 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:19 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:19 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:19 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:19 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:19 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:19 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x200000 phys_seg 1 prio class 0
Oct 23 18:39:19 pve kernel: ata4: EH complete
Oct 23 18:39:23 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:23 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:23 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:23 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:23 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:23 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:23 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:23 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:23 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:23 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:23 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:23 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x200000 phys_seg 1 prio class 0
Oct 23 18:39:23 pve kernel: ata4: EH complete
Oct 23 18:39:27 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:27 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:27 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:27 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:27 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:27 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:27 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:27 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:27 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:27 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:27 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:27 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:27 pve kernel: ata4: EH complete
Oct 23 18:39:31 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:31 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:31 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:31 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:31 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:31 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:31 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:31 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:31 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:31 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:31 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:31 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:31 pve kernel: ata4: EH complete
Oct 23 18:39:35 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:35 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:35 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:35 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:35 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:35 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:35 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:35 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:35 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:35 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:35 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:35 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:35 pve kernel: ata4: EH complete
Oct 23 18:39:39 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:39 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:39 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:39 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:39 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:39 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:39 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:39 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:39 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:39 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:39 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:39 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:39 pve kernel: ata4: EH complete
Oct 23 18:39:43 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:43 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:43 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:43 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:43 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:43 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:43 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:43 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:43 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:43 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:43 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:43 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:43 pve kernel: ata4: EH complete
Oct 23 18:39:46 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:46 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:46 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:46 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:46 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:46 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:47 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:47 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:47 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:47 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:47 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:47 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:47 pve kernel: ata4: EH complete
Oct 23 18:39:50 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:50 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:50 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:50 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:50 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:50 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:50 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:50 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:50 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:50 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:50 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:50 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:50 pve kernel: ata4: EH complete
Oct 23 18:39:54 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:54 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:54 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:54 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:54 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:54 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:54 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:54 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:54 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:54 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:54 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:54 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Oct 23 18:39:54 pve kernel: ata4: EH complete
Oct 23 18:39:58 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:39:58 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:39:58 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:39:58 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:39:58 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:39:58 pve kernel: ata4.00: error: { UNC }
Oct 23 18:39:58 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:39:58 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:39:58 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:39:58 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:39:58 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:39:58 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x200000 phys_seg 1 prio class 0
Oct 23 18:39:58 pve kernel: ata4: EH complete
Oct 23 18:40:02 pve kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Oct 23 18:40:02 pve kernel: ata4.00: BMDMA stat 0x25
Oct 23 18:40:02 pve kernel: ata4.00: failed command: READ DMA
Oct 23 18:40:02 pve kernel: ata4.00: cmd c8/00:08:e8:18:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 51/40:08:e8:18:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Oct 23 18:40:02 pve kernel: ata4.00: status: { DRDY ERR }
Oct 23 18:40:02 pve kernel: ata4.00: error: { UNC }
Oct 23 18:40:02 pve kernel: ata4.00: configured for UDMA/133
Oct 23 18:40:02 pve kernel: sd 3:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
Oct 23 18:40:02 pve kernel: sd 3:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
Oct 23 18:40:02 pve kernel: sd 3:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 23 18:40:02 pve kernel: sd 3:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 18 e8 00 00 00 08 00 00
Oct 23 18:40:02 pve kernel: blk_update_request: I/O error, dev sdc, sector 6376 op 0x0READ) flags 0x200000 phys_seg 1 prio class 0
Oct 23 18:40:02 pve kernel: ata4: EH complete

 

[leesteken]

Now I am assuming this due to when I had mounted it simultaneously but I am wondering if this indicates a hdd failure or just data corruption?

Did you do pysical disk passsthrough or did you do PCIe passthrough a drive controller?
Either way, if you are getting media errors in the logs on the Proxmox host (as it looks like you do), it usually indicates physical disk, cable or controller problems.
Does the drive SMART information show any problem? Drives do fail without SMART warnings.

 

[sabidawg]

I did the physical disk passthrough. SMART information is showing a log of issues "Error: UNC 8 sectors at LBA = 0x000018e8 = 6376" being predominantly the error. (see quote below) which is a read error I am assuming?
I did some reading on the attributes and it looks like there is some signs of it failing? It is a brand new disk, but like I said I did attempt to mount it simultaneously.
However I did the same thing with a drive that has over 4k power_on_hours and that one seems to have no issue at this stage.
If I mount the drive on the PVE host I get no errors, or at least I can't see any. It seems to be only when mounting it to the open media vault VM.

=== START OF INFORMATION SECTION ===
Device Model:
Serial Number:
LU WWN Device Id:
Firmware Version: 81.00B81
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Oct 23 21:26:17 2022 ACDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled

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

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (41160) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 437) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 190 135 051 - 327
3 Spin_Up_Time POS--K 225 224 021 - 3750
4 Start_Stop_Count -O--CK 100 100 000 - 49
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 100 100 000 - 115
10 Spin_Retry_Count -O--CK 100 253 000 - 0
11 Calibration_Retry_Count -O--CK 100 253 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 49
192 Power-Off_Retract_Count -O--CK 200 200 000 - 39
193 Load_Cycle_Count -O--CK 200 200 000 - 81
194 Temperature_Celsius -O---K 103 103 000 - 47
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 1
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 6 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb6 GPL,SL VS 1 Device vendor specific log
0xb7 GPL,SL VS 78 Device vendor specific log
0xbd GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 93 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 326 (device log contains only the most recent 24 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 326 [13] occurred at disk power-on lifetime: 113 hours (4 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 08 00 00 00 00 18 e8 e0 00 Error: UNC 8 sectors at LBA = 0x000018e8 = 6376

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 18 e8 e0 08 00:07:34.750 READ DMA
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:07:34.730 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 08 00:07:34.730 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:07:34.665 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 18 e8 e0 08 00:07:30.852 READ DMA

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 114 6376

Selective Self-tests/Logging not supported

SCT Status Version: 3
SCT Version (vendor specific): 258 (0x0102)
Device State: Active (0)
Current Temperature: 47 Celsius
Power Cycle Min/Max Temperature: 44/47 Celsius
Lifetime Min/Max Temperature: 20/47 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/65 Celsius
Min/Max Temperature Limit: -41/85 Celsius
Temperature History Size (Index): 478 (249)

SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 49 --- Lifetime Power-On Resets
0x01 0x010 4 115 --- Power-on Hours
0x01 0x018 6 3044123020 --- Logical Sectors Written
0x01 0x020 6 2002350 --- Number of Write Commands
0x01 0x028 6 198609121 --- Logical Sectors Read
0x01 0x030 6 6972200 --- Number of Read Commands
0x01 0x038 6 414000000 --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 115 --- Spindle Motor Power-on Hours
0x03 0x010 4 29 --- Head Flying Hours
0x03 0x018 4 121 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 507 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 8 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 39 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 326 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 2 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 47 --- Current Temperature
0x05 0x010 1 40 --- Average Short Term Temperature
0x05 0x018 1 - --- Average Long Term Temperature
0x05 0x020 1 47 --- Highest Temperature
0x05 0x028 1 25 --- Lowest Temperature
0x05 0x030 1 42 --- Highest Average Short Term Temperature
0x05 0x038 1 38 --- Lowest Average Short Term Temperature
0x05 0x040 1 - --- Highest Average Long Term Temperature
0x05 0x048 1 - --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 65 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 0 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 328 --- Number of Hardware Resets
0x06 0x010 4 172 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0008 2 0 Device-to-host non-data FIS retries
0x0009 2 2 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 4 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x8000 4 7848 Vendor specific