Paragon uEFI iSCSI Target

[Paragon_MA]

Paragon Software Group proudly announces its latest technology for remote connection to any uEFI system even if it is not bootable.
Join the early adoption testing today and get your free copy. Paragon uEFI iSCSI Target.

Product web page: http://www.paragon-software.com/tech...ts/uefi-iscsi/
Reviewers Guide: http://download.paragon-software.com...manual_eng.pdf

Your feedback and suggestions are appreciated.
As always, your Paragon Team

[ocker]

I have not used Paragon uEFI iSCSI Target because even though I am an experienced PC user I find the whole process ridiculously complex and the manual badly written. One absolutely essential change to make the manual a bit useable is when you give a screen capture showing the information to insert in the escsicfg.bat parameters is to snow an example where those parameters are used because it is not clear what information from the screen capture you have used. i.e. which drive letter, disk number and NIC was used.
With the complexity and state of the instructions at the moment I figure that I am better off formatting my 3TB HDD as 2TB than going through the pain of using Paragon uEFI iSCSI to format it as 3TB

[deep13]

I just tried to get this working on a Thinkpad T530 I was able to finally get the config file correct and see it get an address via DHCP and start listening. however I was unable to ping the IP address it claimed it got form DHCP and was unable to connect to the iSCSI target.

I have a feeling this thing hasn't been tested much outside of VirtualBox or VMWare. I was hoping to use this as a sort of poor man's target mode (similar to the Apple firmware's start in target mode feature)

If you have newer versions of the software for me to try I would be glad to give it another go.

Another thing that might be useful for setting up the escsi.config manually is not requring the model/serial number to match the exact number of spaces. I'm not sure where the spaces come from but I ended up counting the spaces between the brackets when it lists the detected disks and then editing escsi.config inside the EFI shell until it worked. It did seem to detect all the disks and display them when it didn't match up. It would be very nice to have it export all of the disks (assuming it's possible to do so)

If I can get this fully working I would like to add it to my main EFI partition as a recovery tool.

[feoff]

'Ping' feature is not supported by iSCSI target.

Windows iSCSI initiator dumps it's error messages to Windows System Log (My Computer (right-click)->Manage->Diagnostics->Event Viewer->Windows Logs->System). Save error message created by 'MSiSCSI' source by selecting them, right-click and save selected events.

More info on iSCSI initiator failures might clarify the issue and help improving the solution.