lsi sas - only first drive accessible - transport\_set\_identify() failure
i have the ga-7pesh2 motherboard which has built-in sas, and i’ve added an lsi sas 9207-8e card flashed to it mode for a das. however only the first drive on the new lsi card is accessible. if i disconnect the first drive and reboot, then the next drive is the only one accessible.

i currently have …
only thing i can think of is to maybe reflash the firmware.
it doesn;t make much sense to me; where did you get that instruction?

substitute mkdir for md and it might work but there is insufficient information. you're making a directory and naming it sd-card. then you're going into that directory and copying everything from the f:\ drive into that folder. that doesn't get it on to the other card.

if access is denied to the card, none of the above will work so you need to fix that first. it might be write protected. following cards have been verified

rcs\_r2ug-a2e16-a pcie switch

nvidia’a dgpu

intel82572ei nic

nec upd720200 usb3.0 card

asus usb3.1 card

moschip usb2.0 card

ocz ssd

ocz rvd400-22280-512g-a ssd

silicon image corp. 3132 sata controller

intel e10g42bt x520-t2 10gigabit nic card

sta… hi there floriann software,

first of all, i would say that it is always a better idea to open up a new thread, instead of engaging in an old one.

apart from that, as the drive is recognized on other systems except for the xp one, then it comes to drivers. make sure you go to the mobo's website and update the drivers.
is the drive initialized as mbr. in case it is initialized as gpt, i would advise you to back up all the data and initialize it as mbr. win xp has some limitations on that: https://support.microsoft.com/en-us/kb/2581408

cheers,
d\_know\_wd :) does the gateway have access to this mounted path/drive? <https://docs.inductiveautomation.com/display/doc80/mapping+a+network+drive> Ok, fought this problem for almost a week, and 20 minutes after i write this it is solved:

I repeated the Installation, and as a final step I "diskpart" - cleaned and reformatted the WD drive, and now it works.

I do not really understand what might have been wrong ( it was "GPT")…. Maybe something in the order I did the things.




[View solution in original post](/t5/Intel-Optane-Memory/A-classic-one-Optane-module-not-recognized-by-RST-App/m-p/645903#M4006) thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … try that drive with another computer. if it doesn't work, it's probably dead. yes you add second as a slave drive, boot from one that has os, second has data. access thru my computer for second one. please refer to following posts:

<https://devtalk.nvidia.com/default/topic/1021886/jetson-tx2/pcie-usb-lane-mapping/post/5203705/#5203705>
<https://devtalk.nvidia.com/default/topic/1013740/jetson-tx2/tx2-config-3-for-usb-lane-mapping/post/5207826/#5207826>
[https://devtalk.nvidia.com/default/topic/102…](https://devtalk.nvidia.com/default/topic/1023160/jetson-tx2/tx2-using-pcix1-instead-of-usb3-default-config-1-/post/5207785/#5207785) that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: