Search results

Nice to hear it still works :)

I don't use any RAID. Yes, my LUN is bootable and the network card is set correctly, grub menu is showing. No, I don't use ipxe, I am booting directly over my NIC. I am trying to achieve the same objective as my tutorial, but with debian, not proxmox.

I still not achieved the working install of debian over iSCSI. How do you install debian directly on iSCSI target with installer ? I can only connect to target manually with shell during install, tried to install but system don't boot with following message : mdadm : no array found by...

Hello, The best way to boot over iSCSI is a iSCSI-capable NIC, like intel X520 based adapters. About installing OS, I wrote a tutorial here. Best regards

To be sure to get a reliable system, it's recommanded to have the same hardware on you multiple hosts. I recommand to get some intel X520-based copy in china shop.

It is possible the iSCSI kernel module cannot communicate with this particular NIC fw to get IP at boot. I dont have same hw config as yours and when we do some tricks like this, the results can change a lot depending of hardware. I I think you should install the same NIC on all hosts.

Is your iSCSI NIC the same on all your pve hosts ? With my Intel NIC's I have no issues, but I never try with others brands/models.

Hi ! This is normal, when you click apply, ifupdown stops all links and restart them. By this way the iSCSI connection is interrupted. I think you can set the same IP as you set in your NIC's iSCSI BIOS but don't apply settings online, just reboot the host to take settings. It will prevent...

According to open-iscsi package help file, you can try to fill manually iscsi credentials int the config file. ISCSI_INITIATOR="iqn.1993-08.org.debian:01:9b3e5634fdb9" ISCSI_TARGET_NAME=iqn.2008-01.com.example:storage.foo ISCSI_TARGET_IP=192.168.1.1 ISCSI_TARGET_PORT=3160...

When I use the kernel v5.13, I get the same error, "could not setup fw entries". Did you use the kernel 5.15 ?

The OS get iSCSI information with the kernel module iscsi-ibft. That is the reason for adding ISCSI_AUTO=true In my case, no need to configure the NIC, after boot, when I check, the card has the same IP as I configured in the iscsi boot option rom.

Hi ! Like I wrote on the top of the howto, I use BIOS boot, because my adapter fail to boot on UEFI. Did you use the 5.15 kernel ? (At the time I wrote the post, 5.13 fails to iSCSI boot) Step 16 is very important, and you must update initramfs after this !

Yes, iscsiadm needs systemd, which is not running at install. I am actually out of ideas about your issue, tell me the results of your debootstrap.

Hi ! I see you have the same issue with Debian and Proxmox, maybe you shall check the HDD/iSCSI connection. What filer do you use ? Did you do a S.M.A.R.T test on your disks ? When you said in you other post It is on the same LUN with same iSCSI connection as now ?

When I see about adding the support for iSCSI install with the official ISO is actually not planned I searched some ideas to make this possible. I found a workaround with the official PVE 7.1 ISO and I want to share, maybe it can help someone. Only the iSCSI workaround will be explained, I...

I still not found what is the issue, but installing the new pve-kernel-5.15 solved the problem. Best regards

Hi there ! After two weeks of testing a lot of solutions, I come here to maybe get an answer about my issue. I use proxmox from v4 and now I have two Synology rs2421+ in HA mode for storage and I want to make my new three hypervisors boot over iSCSI. MY stuff : Hosts : - MB Asrock Rack...