Inside Security (insert)
|
2017-11-08, 00:42
Post: #5
|
|||
|
|||
RE: Inside Security (insert)
I've changed it up just a few hours ago to reflect the following in menu.ipxe - which works great:
set 209:string http://###.###.###.4/knoppix-tftpboot/px...noppixboot set 210:string tftp://###.###.###.4/knoppix-tftpboot/ imgload knoppix-tftpboot/knoppix.0 boot knoppix.0 But now, I'm attempting to get iscsi to connect as a cache location for data recovery. Here's my code and the error messages: set iscsistuff iscsi:###.###.###.6::::iqn.2017-11.nnnn-iscsitrgt.nnnn.local:knoppix00 iqn.2017-11.nnnn-iscsitrgt.nnnn.local:knoppixstuff sanhook ${iscsistuff} && sanunhook || echo Unable to hook ${iscsistuff} set 209:string http://###.###.###.4/knoppix-tftpboot/px...noppixboot set 210:string tftp://###.###.###.4/knoppix-tftpboot/ imgload knoppix-tftpboot/knoppix.0 boot knoppix.0 The error is: Could not open SAN device: Input/ouput error (http://ipxe.org/1d0d6139) I can connect via Windows iscsi initiator using the initiator name: iqn.2017-11.nnnn-iscsitrgt.nnnn.local:knoppixstuff Once connected, I can delete, create, and format the filesystem and I can create directories and files. But when attempting via iPXE I get the above error. Any ideas? |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Inside Security (insert) - draugadrottinn - 2017-11-06, 17:19
RE: Inside Security (insert) - draugadrottinn - 2017-11-07, 03:16
RE: Inside Security (insert) - draugadrottinn - 2017-11-07, 19:57
RE: Inside Security (insert) - NiKiZe - 2017-11-08, 00:15
RE: Inside Security (insert) - draugadrottinn - 2017-11-08 00:42
|
User(s) browsing this thread: 1 Guest(s)