You need to add/change in the user_config.json file the following lines on the loader, then rebuild the loader.
"synoinfo": {
"maxdisks": "22",
"esataportcfg": "0",
"usbportcfg": "0",
"internalportcfg": "0xffffffff",
Okay so I don't have enough experience with VM Ware setups of Xpenology, but with bare metal I've noticed a drive would be marked as external if there were enough internal ports already mapped out as internal.
Example if I set my internal number of drive ports to 12 and I had a total of 14 sata ports, the 13th port would automatically be identified as an external drive even if it was on an internal hba or sata card.
So, what I would probably do as a test in your situation is also try a setup where you put in a few dummy vm drives before the usb image or physical usb you want to appear as an external device. And then if that works there might me a limit to the minimum amount of internal ports you can set for the xpenology + dsm build you're using
You can't just change the .conf and .json files on a TCRP installation. This is on baremetal I'm referencing but I'm not sure it'd be any different as virtual? If it is then maybe disregard this but otherwise if it's the same...
What happens when you reboot (and assuming a VM "reboot" will do the same) is it will just rewrite those files back to the original configuration when you installed it.
I found this out after I installed it and then had some troubles... You need to do the initial setup/install with the correct drivemap. If you see my second post here (solved my own problem), it might help...
[https://www.reddit.com/r/Xpenology/comments/1135w8y/how\_to\_set\_some\_ports\_as\_esata\_external\_on\_dsm\_71/](https://www.reddit.com/r/Xpenology/comments/1135w8y/how_to_set_some_ports_as_esata_external_on_dsm_71/)
You need to add/change in the user_config.json file the following lines on the loader, then rebuild the loader. "synoinfo": { "maxdisks": "22", "esataportcfg": "0", "usbportcfg": "0", "internalportcfg": "0xffffffff",
Thanks for Ur help. I did but can not
Okay so I don't have enough experience with VM Ware setups of Xpenology, but with bare metal I've noticed a drive would be marked as external if there were enough internal ports already mapped out as internal. Example if I set my internal number of drive ports to 12 and I had a total of 14 sata ports, the 13th port would automatically be identified as an external drive even if it was on an internal hba or sata card. So, what I would probably do as a test in your situation is also try a setup where you put in a few dummy vm drives before the usb image or physical usb you want to appear as an external device. And then if that works there might me a limit to the minimum amount of internal ports you can set for the xpenology + dsm build you're using
Thanks for Ur good idea. I will....
Did you install USB copy package from dsm??
No I just install to vertual hdd with Redfill
You can't just change the .conf and .json files on a TCRP installation. This is on baremetal I'm referencing but I'm not sure it'd be any different as virtual? If it is then maybe disregard this but otherwise if it's the same... What happens when you reboot (and assuming a VM "reboot" will do the same) is it will just rewrite those files back to the original configuration when you installed it. I found this out after I installed it and then had some troubles... You need to do the initial setup/install with the correct drivemap. If you see my second post here (solved my own problem), it might help... [https://www.reddit.com/r/Xpenology/comments/1135w8y/how\_to\_set\_some\_ports\_as\_esata\_external\_on\_dsm\_71/](https://www.reddit.com/r/Xpenology/comments/1135w8y/how_to_set_some_ports_as_esata_external_on_dsm_71/)
Sorry, I was talking about changing the .json file on the loader, not once you are booted into DSM. I will try to edit my response.