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/technologies/components/uefi-iscsi/ Reviewers Guide: http://download.paragon-software.com/doc/uefi_iscsi_target_manual_eng.pdf Your feedback and suggestions are appreciated. As always, your Paragon Team
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
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.
'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.
I am trying to install Paragon uEFI iSCSI following the instructions given. I get errors when I run the escsicfg.bat --show. It gets as far as the first network connection. It does not show the subnet correctly (shows 0.0.0.0) I then try running the "escsicfg.bat --install" using the command "escsicfg.bat --install I: 2 0" i: being my thumb drive 2 = The target Hard drive 0 = My network adapter Again I get an error. It requests they I modify the "escsi.config" and then use the "escsicfg.bat --copy" function. No instructions have been given with respect to modifying the config file. I ended up modifying the config file based on the information available to me and used the "escsicfg.bat --copy" function. This ran to completion without error. I then tried to boot from the thumb drive but I get the message that the drive is not bootable. I trying to install on a Windows XP Professional SP3 computer running 2.6Ghz Petium Dual COre with a 1Gig of RAM. Any advice? Alex
Creating the USB stick worked fine on my machine, however I was unable to boot from this USB stick. I am getting the following error, directly from my UEFI BIOS I believe, when I try to boot the USB stick in the same machine in which I created it: "The system found unauthorized changes on the firmware, operating system or uEFI drivers. Press [N] to run the next boot device. or enter directly to BIOS setup if there are no other boot devices installed. Go to BIOS setup > Advanced >Boot and change the current boot device into other secured boot devices." I am using a ASUS Sabertooth Z87 Motherboard, BIOS version 1803 (1 short of current BIOS version). I have 32 GB memory, an Intel Core I7 4770K processor, and 4 USB plus the target memory stick drives plugged into the USB Ports on the Motherboard. I have only one machine with UEFI BIOS, and I am not sure what the result would be on any other ASUS uEFI based Motherboard. I am not sure how to proceed. Thanks Mike Yost
Hi I was initially very excited to see the news of your new product. Eagerly I signed up & downloaded the installer & quickstart guide. However upon reading said guide, I am now somewhat confused as to your product offering. The software must first be configured on the machine to host the target. Hopefully I remember to do this before my hard disk failure. Secondly, I have approximately 650 machines of varying configurations. SO I have to keep several hundred USB disks? I also want to access more than one drive. Lets say 3. Do I now need approximately 1950 USB drives to store the different configs And Finally, I would have thought, the purpose of a uEFI based iSCSI target was to bypass any operating system having to be loaded. It could be installed in the EFI partition itself, so no media being required at all (unless total disk failure/EFI partition removal). If I have to use media, wouldnt you simply load a linux live distribution or FreeNAS or OpenFiler Which you do not have to specify the exact network card and can also share multiple drives. Sorry if I come across a little blunt, but please clarify when you would use this instead of a linux live environment? THanks Mike
Because you might use the SCSI, I might not serve as a reference, but participated in "Paragon UEFI iSCSI Target (English) Early Adopter Program" now. "target name" to be necessary here wants you automatically to name it Will there be the method to try whether "traget IP" is usable before being connected?
When i try to run the bat file i get the following. config_app.exe has encountered a problem and needs to close, in the dos screen Code: C:\Paragon>escsicfg.bat --show Available Disks: --------- Available NICs: Adapter #0 Friendly name: Local Area Connection Description: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller - Packet Scheduler Miniport DHCP:on MAC:00:1a:92:16:89:e0 Ipv4: 192.168.1.52 Subnet mask: 255.255.255.255
