A problem caused by ISCSI of Steam Deck

[jASON_ME]

Hello, ladies and gentlemen. As we all know, the steam game library is too large. Even the largest steam deck and TF card are not enough to fit it. Therefore, I try to use local NAS to provide additional network storage for it, and use ISCSI for connection. After everything is ready, it works well in desktop mode. However, when I return to Steamos, I cannot find the expanded library in the storage space (even though I just added it in desktop mode). At the same time, the command to start and mount has not been executed normally after restart. At the same time, the screen is not completely closed after I press the power button. In fact, after playing the sleep animation, the whole machine is stuck, Only restart. I am sure it is caused by ISCSI, because after I shut down the service, the system is normal. I hope the authorities can fix this problem. Thank you. Or tell me other ways to use networked storage.
PS.steamos：3.4.4，ISCSI：open-iscsi，NAS：truenas

[Modern Retro Gamer (UK)]

How are you mounting the network drive? Desktop and Game modes are two separate environments. One session is closed to start the other. Any volume mounting needs to occur at a lower level than the graphical display manager.

If your wireless connection is up when fstab is processed then in theory you should be able to add an entry there.

Not sure how the immutable file system setup will effect these changes long term.

[jASON_ME]

I mount the network device from ssh to deck in the graphical interface. In fact, because some software can view the file directory, I do see the remote file under the corresponding mount directory.

[jASON_ME]

When I view in desktop mode, the settings in steam are consistent with the OS, and they are not very like an independent set of file systems. I used to change the game file through ssh in the OS mode to get the language support I expected. He just needs to start the game directly after the file is replaced to apply it immediately. Moreover, since the mount directory is created in advance, whether ISCSI works or not, and whether the remote disk is mounted to the target path, it still exists. The only difference is that the content is different, so my settings have not been erased. In desktop mode, it is still one of the download libraries.