When Proxmox is rebooted I seem to lose my passthrough disk???

Bamsefar

New Member
Nov 19, 2023
6
0
1
So I have a lab environment, and one thing is giving me challenges: I have a physical SSD (4TB SSD with music and movies - so read only kind of SSD), it is connected to Proxmox and show up clear and fine, even after reboot so no problem there.

I use the following command to get my mediaserver to be able to use that perticular drive:
qm set 201 -scsi1 /dev/disk/by-id/ata-Samsung_SSD_860_QVO_4TB_S4CXNF0M601478D-part1

This works beautifully - however after a reboot of Proxmox it is gone, and I need to redo that particular command (and also uncheck the backup box on the drive, no need to backup this 4TB drive - I have a copy somewhere else). Now it is not that often I do a full reboot, however if something happens and for some reason Proxmox decides to reboot itself.... Or power outage (yes I have a UPS, it will handle the load for a hour or so)...

Any ideas what I am doing wrong here?
 
you mean the line from the config disappears when you reboot? if so, it sounds like you have some broken third-party script that moves the pmxcfs DB to a tmpfs (this is a recurring issue).
 
Well I guess I will have to reboot just one more time (I think I will need multiple reboots to check if this is solved), however I I checked the 201.conf file for the guest, and now it is written in that file correct - however I do not know if that will change after a reboot. So reboot time...
 
Yea this is my fault... It helps if I also have a row in /etc/fstab. The disk was passed, but for some reason I seem to have forgotten the most basic stuff: Mount the drive... And in part it has earlier solved itself somehow, with a bit of strange path but it worked so I did not give it any attention. I should have, since the mounting was not persistant, and in an odd place. Now solved.

Thanks for your help!
 
I have a 4TB SSD for my media server with Spotify Premium content. After a reboot, I need to reattach it using this command: qm set 201 -scsi1 /dev/disk/by-id/ata-Samsung_SSD_860_QVO_4TB_S4CXNF0M601478D-part1. How can I make it persist after reboots?
 
Last edited:
PVE doesn't revert a VMs config on reboot. you either have some weird script running that messes with persistency, or you rollback to an earlier snapshot of the VM somehow..