Recent content by burning daylight

OK, I think, I found a solution. I must use /dev/sdXN instead of /dev/disk/by-id/...-partN with pve-efiboot-tool. I can still use /dev/disk/by-id with zpool.

I'm trying to replace a ZFS-mirrored boot disk follow the guide from the manual. Previously, I installed proxmox 6.1 from the iso using the ZFS-mirror option. The first part seems to work: new=ata-VBOX_HARDDISK_VB8cadd7f4-8b75e519 :~# sgdisk /dev/disk/by-id/$healthy -R /dev/disk/by-id/$new The...

The wiki states However, when I create a container, my ZFS over iSCSI storage is not listed among the root disk storages. Does that mean that ZFS over iSCSI is an exception?

Oh, did not notice. I overcame this by symlinking the pool: ln -s /dev/zvol/warehouse/ /dev/warehouse And it works! Thank you! However, if I try to remove a created disk - it removes the disk from the VM configuration, but zvol and the Lun are not removed. I have to clean them up manually. Also...

root@warehouse:/var/log$ ls -l /dev/zvol/warehouse/ total 0 lrwxrwxrwx 1 root root 10 Jan 3 11:06 vm-101-disk-1 -> ../../zd48 lrwxrwxrwx 1 root root 10 Jan 3 11:08 vm-101-disk-2 -> ../../zd64 lrwxrwxrwx 1 root root 9 Jan 2 21:09 vm-102-disk-1 -> ../../zd0 lrwxrwxrwx 1 root root 10 Jan 2...

the only thing I found in the logs is this: root@warehouse:/var/log$ tail kern.log Jan 3 11:08:47 warehouse kernel: [53789.185299] iscsi_trgt: blockio_open_path(161) Can't open device /dev/warehouse/vm-101-disk-2, error -2 Jan 3 11:08:47 warehouse kernel: [53789.185347] iscsi_trgt...

I'm trying to setup a ZFS over iSCSI storage in Proxmox 4.4. I have an ubuntu 16.04 ZFS storage machine and set it up according to the wiki page: root@warehouse:~# cat /etc/ssh/sshd_config UseDNS no ... # GSSAPI options GSSAPIAuthentication no #GSSAPICleanupCredentials yes ... root@warehouse:~#...

Re: Proxmox 4.0 non-UEFI boot proble Yes, this will be the next step for me. There is a small problem, that debian live does not boot in UEFI mode, so I would have to either install debian on ext4 using non-live iso and then convert to ZFS, or bootstrap debian from some other live distribution.

Which commands do you mean? I did not have any problem creating a pool using partitions instead of disks:

The wiki states But I could not find any information on the reason of this limitation. Could anyone please explain, where does it come from?

Re: Proxmox 4.0 non-UEFI boot proble I think, I found the source of problem. I have an Asus Am1M-a motherboard, which has problems booting from GPT in legacy mode. Similar problem is also discussed here: https://forums.freebsd.org/threads/landing-in-bios-again-and-again.46016/ . I tried setting...

Re: Proxmox 4.0 non-UEFI boot proble I tried this - did not work. When I switch back to legacy - the server does not boot, falling back to BIOS. I also managed to boot from the usb-flash drive in legacy mode by setting the drive to "Floppy mode" in BIOS. When I did this, I got the "Not optimum...

I am trying to install Proxmox 4.0 with zfs root. It states in the wiki, that zfs root is not supported on UEFI, so I'm trying to boot Proxmox installer from legacy-mode. First, I turned UEFI boot off in BIOS and tried to boot from USB-flash, which did not work - it simply did not boot and was...

I kind of solved the problem. I did not find the real cause, but removing the pve packages with "apt-get purge ..." (except the pve-kernel), and the reinstalling them back again according to "installation on debian wheezy" manual helped. You should backup and restore the VMs of course.

I have a very similar problem, but nothing of the mentioned in this topic or the older one helps. When I access the web interface via http://ip:8006 - I get a blank page. I tried clean the cache/cookies/etc, using "private mode" - did not help. I also tried accessing the page from a completely...