Hi in tests we regularly create iscsi targets and mount them so it generally works. Thereby it is important how you exactly setup, create, pass and scan them. Only then can your specific issue be (hopefully) reproduced so that one can e.g. bisect on the changes to bisect on scripts/rescan-scsi-bus.sh
So it would be great to have 1. on Host to set up my iscsi disks I did ... 2. to make them available to the guest I did ... 3.1 then I resacn with ... but it fails like ... 3.2 if I use the script from git it works like ... For 3.1 and 3.2 it might be useful to track kernel events (dmesg -w) and udev ((sudo udevadm monitor) and providing those as log files for each of the two cases (3.1 and 3.2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750774 Title: Replace rescan_scsi_bus script with the latest one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1750774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
