1

Topic: We install Linux on iscsi target...

Connection to a disk hardware,  HBA adapter Broadcom BCM5709, it Nextreme II, it QLogic. Adjustments  are registered in , at once on end of initialization UEFI I see successful connection HBA to a disk (both on the client, and on ). The installation machine real, not . Windows (normal 10, and it is enough Home): - HBA recognizes as 4 devices: two  the network boards, two SCSI Storage the controler - it is willingly launched, being  with SSD on iSCSI a disk - in the installer sees SCSI a disk and as it is willingly installed on it Ubuntu 17.10: - the installer does not see SCSI a disk. To Sootv Th it is not installed. - HBA recognizes only as 2 network boards. - in lspci shows the driver bnx2 for this the network. Storage controlers are not present, not recognized devices are not present. - lshw-c storage produces "Segmentation fault" Fedora 27: - All as well as in Ubuntu, except for absence of a command "lshw" and presence of an irritating every second exhaust in the console about impossibility to include USB2.0 port and the immediate second message on impossibility it to ungear. "Maybe USB cable is bad?" Questions silly . Though in USB2.0 only the mouse is thrust. And Windows,  problems with USB it is noted. - after start UI of the installer in the upper middle of the screen, it is literally for a second, appears constraining  "OOPS! We're sorry, it looks BOOTIMAGE crashed <...>". And there and then disappears. - on a step of a choice of disks to a help there is a description of adjustment of the program initiator (though it and more simple, not my case) - but it, unfortunately, does not fight with actual UI: button Add promised by a help iSCSI Target is not present, is only Add FCoE SAN that, certainly, at all that. (But I just in case tried - does not work). - Quit from the installer actually not Quit, and an output in any similarity of the desktop extremely similar on Ubuntu CentOS 7 Everything, 1708: - The load menu to a toothache reminds Fedora - the absolute leader on time of initialization of devices, more 2 minutes (against units of seconds at predecessors) - in 32 minutes (THIRTY TWO) the installer wrote "Not asking for VNC because we do not have a network" that, unconditionally, lies. Since on the computer there is still the built in Realtek receiving adjustments on DHCP. To a word - in Ubuntu and Fedora was both a network, and the Internet. (This Internet even in UEFI is! It is possible to check up presence of updates). -  the installer I and did not wait

2

Re: We install Linux on iscsi target...

Hello, IID, you wrote about  about  and Windows. And what about , , ,  ? Or did not reach yet by that moment? How many years in Windows? ? ? Why lshw? Whether read it? On what thoughts directs it?

3

Re: We install Linux on iscsi target...

Hello, IID, you wrote: IID> Connection to a disk hardware,  HBA adapter Broadcom BCM5709, it Nextreme II, it QLogic. IID> adjustments  are registered in , at once on end of initialization UEFI I see successful connection HBA to a disk (both on the client, and on ). Put unbutnu 14.04 LTS https://www.dell.com/support/home/ru/ru … erId=PX6V4

4

Re: We install Linux on iscsi target...

Hello, Sheridan, you wrote: S> Hello, IID, you wrote about  about  and Windows. S> and what about , , ,  ? Or did not reach yet by that moment? There is a hope that  appears better? Why? I . Remaining from the list does not interest. S> how many years in Windows? ? ? What it matters? S> why lshw? Whether  on "show unknown pci devices" S> Read it? On what thoughts I direct With software initiator and without HBA I will boot. Hanging up all handling on dead , and  parameters, instead of their floppy distribution on DHCP and usages of hardware resources of the device. S it? By, as network cards the device works.

5

Re: We install Linux on iscsi target...

Hello, IID, you wrote: IID> With software initiator I and without HBA will boot. Hanging up all handling on dead , and  parameters, instead of their floppy distribution on DHCP and usages of hardware resources of the device. And, understood. I will not prompt, in such modes did not work never...

6

Re: We install Linux on iscsi target...

Hello, kov_serg, you wrote: _> Put unbutnu 14.04 LTS _> https://www.dell.com/support/home/ru/ru … erId=PX6V4 you Hint at officially declared support? Well so win10 home edition in the list too is not present. And declared commercial  besides that expensive, besides that for downloading demand the questionnaire to fill,  also  not to taste, corporate ! But it is amusing that  the Windows in a complete set "" outrode powerful server , and on  and completely not new piece of iron, with open drivers.

7

Re: We install Linux on iscsi target...

Hello, IID, you wrote: IID> Hello, kov_serg, you wrote: _>> Put unbutnu 14.04 LTS _>> https://www.dell.com/support/home/ru/ru … erId=PX6V4 IID> you Hint at officially declared support? IID> well so win10 home edition in the list too is not present. IID> And declared commercial  besides that expensive, besides that for downloading demand the questionnaire to fill,  also  not to taste, corporate ! IID> But it is amusing that  the Windows in a complete set "" outrode powerful server , and on  and completely not new piece of iron, with open drivers. I hint at that that it is necessary firmware to update

8

Re: We install Linux on iscsi target...

Hello, IID, you wrote: IID> And declared commercial  besides that expensive, besides that for downloading demand the questionnaire to fill,  also  not to taste, corporate ! And  does not descend for the corporate?

9

Re: We install Linux on iscsi target...

Hello, Ops, you wrote: Ops> And  does not descend for the corporate? Perfectly rolls

10

Re: We install Linux on iscsi target...

Hello, kov_serg, you wrote: _> I hint at that that it is necessary firmware to update Firmvar fresh enough, 7.10. from 2014 () year. , I will try to update, we look that turns out.