iSCSI target clean-up (removal)

HPmoss

Member
May 8, 2023
61
8
13
Online
www.google.co.uk
I was experimenting with iSCSI target and while trying to move I made a rookie mistake of deleting the folder first instead of gracefully cleaning it. I had tgt installed on the system that I have uninstalled. Can some please help me fix the issue, just trying to clean up the mess. I am not an expert in tgt/iSCSI targets. Logs from Proxmox listed below:

:
:

:
Jul 03 13:34:56 pve01 systemd[1]: Unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve...
Jul 03 13:34:56 pve01 umount[5056]: umount: /mnt/pve/HS-iSCSI: target is busy.
Jul 03 13:34:56 pve01 systemd[1]: mnt-pve-HS\x2diSCSI.mount: Mount process exited, code=exited, status=32/n/a
Jul 03 13:34:56 pve01 systemd[1]: Failed unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve.
Jul 03 13:35:42 pve01 systemd[1]: Unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve...
Jul 03 13:35:42 pve01 systemd[1]: mnt-pve-HS\x2diSCSI.mount: Mount process exited, code=exited, status=32/n/a
Jul 03 13:35:42 pve01 umount[5186]: umount: /mnt/pve/HS-iSCSI: target is busy.
Jul 03 13:35:42 pve01 systemd[1]: Failed unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve.
Jul 03 13:37:11 pve01 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Jul 03 13:37:11 pve01 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Jul 03 13:37:11 pve01 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Jul 03 13:37:11 pve01 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Jul 03 13:40:33 pve01 pvedaemon[1301]: <root@pam> starting task UPID:pve01:00001816:0001C05B:68667A41:dirremove:HS-iSCSI:root@pam:
Jul 03 13:40:33 pve01 systemd[1]: Unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve...
Jul 03 13:40:33 pve01 umount[6173]: umount: /mnt/pve/HS-iSCSI: target is busy.
Jul 03 13:40:33 pve01 systemd[1]: mnt-pve-HS\x2diSCSI.mount: Mount process exited, code=exited, status=32/n/a
Jul 03 13:40:33 pve01 systemd[1]: Failed unmounting mnt-pve-HS\x2diSCSI.mount - Mount storage 'HS-iSCSI' under /mnt/pve.
Jul 03 13:40:33 pve01 pvedaemon[6166]: command 'systemctl stop 'mnt-pve-HS\x2diSCSI.mount'' failed: exit code 1
Jul 03 13:40:33 pve01 pvedaemon[1301]: <root@pam> end task UPID:pve01:00001816:0001C05B:68667A41:dirremove:HS-iSCSI:root@pam: command 'systemctl stop 'mnt-pve-HS\x2diSCSI.mount'' failed: exit code 1
 
Hi @HPmoss , its not quite clear to me what you did or the state you are in.

In general, you should:
- check your mount points: mount
- check iscsi sessions and nodes: iscsiadm -m session && iscsiadm -m node
- check storage config : cat /etc/pve/storage.cfg
- check storage status: pvesm status
- the mount point that is being unmounted is busy, this could be due to running VMs. You can a) reboot the system b) find out why its busy "linux open files" in google

There is nothing in your log that would indicate an iSCSI error, except the names of your mount-moints, which could be completely arbitrary. Frankly, if this is not a critical production system - reboot it.


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