-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxmox 7 - VM TrueNAS Core vs Scale #108
Comments
Please check issue #87 to see if this maybe you issue. |
No I do not think this is the same issue. The ssl redirect is unchecked in TrueNAS-Scale and all my settings in Proxmox are the same when I use the same pool in a different VM TrueNAS-Core which works fine. I noticed the generated command below is wrong: This should have a "/" not a "-" : OmegaPool/oscuzzy/vm-113-disk-0 Is anyone else successfully running Proxmox 7.0 and TrueNAS-Scale? I realize scale is only in a release candidate state. |
I believe so. I have a couple that have it running. I have not yet. I had a bad HDD drive that I need to install to get the Scale up and running. Someone had to do two targets between colons (e.g. - iqn.org.something:taget1:another-target). I believe it is in one of the issues. Possible you can provide me the syslog output from this? I remember having to do something with a character on the TrueNAS-SCALE in the very beginning. |
Look at Issue #75 and why the slash (/) was turned into a dash (-). |
Can you tell me what two targets accomplishes? How would I set that up in Truenas? Here is my storage.cfg:
I can successfully create a new disk for an existing VM and it shows up in TN-Scale, but when I delete it on Proxmox it is not removed in TN-Scale. Those logs are not terribly interesting as they appear successful in Proxmox. Here is the syslog that captures a failure when cloning VM-113 to 106:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have two Proxmox servers and have been using your deb install for a few months now. All TrueNAS installs are VMs on each Proxmox host with HBA passthrough. On the new second server I thought I would try the Scale RC1 as it would behave better as a VM being Linux and with QEMU guest agent. Below are the errors I received while cloning a random VM to the new Scale with ZFS over ISCSI. I shutdown the Scale VM and created a 2nd TrueNAS Core VM, after importing the zfs pool and settings it worked with no errors. For now I will continue using TrueNAS Core. Let me know if you need more info or would like me to try something as I can switch back fairly easy.
Notes:
Output:
create full clone of drive sata0 (zScuzzy:vm-106-disk-0)
Warning: volblocksize (4096) is less than the default minimum block size (8192).
To reduce wasted space a volblocksize of 16384 is recommended.
iscsiadm: No session found.
iscsiadm: No session found.
transferred 0.0 B of 52.0 MiB (0.00%)
...
transferred 52.0 MiB of 52.0 MiB (100.00%)
cannot open 'OmegaPool-oscuzzy/vm-113-disk-0': dataset does not exist
create full clone of drive sata1 (zScuzzy:vm-106-disk-1)
cannot open 'OmegaPool-oscuzzy': no such pool
Could not find lu_name for zvol vm-113-disk-0 at /usr/share/perl5/PVE/Storage/ZFSPlugin.pm line 118.
TASK ERROR: clone failed: command '/usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/192.168.XX.XX_id_rsa root@192.168.XX.XX zfs create -s -b 4k -V 8388608k OmegaPool-oscuzzy/vm-113-disk-0' failed: exit code 1
The text was updated successfully, but these errors were encountered: