[Bug] SMB mounted volume IO error 1.2.80 "System.IO.FileNotFoundException" #554
Open
opened 2025-01-21 03:04:27 +00:00 by GiulioCDI
·
19 comments
No Branch/Tag Specified
No results found.
Canary-1.2.447
Canary-1.2.446
1.2.86
Canary-1.2.445
Canary-1.2.444
Canary-1.2.443
Canary-1.2.442
Canary-1.2.441
Canary-1.2.440
Canary-1.2.439
Canary-1.2.438
Canary-1.2.437
Canary-1.2.436
Canary-1.2.435
Canary-1.2.434
Canary-1.2.433
Canary-1.2.432
Canary-1.2.431
Canary-1.2.430
Canary-1.2.429
Canary-1.2.428
Canary-1.2.427
Canary-1.2.426
Canary-1.2.425
Canary-1.2.424
Canary-1.2.423
Canary-1.2.422
Canary-1.2.421
Canary-1.2.420
Canary-1.2.419
Canary-1.2.418
Canary-1.2.417
Canary-1.2.416
Canary-1.2.415
Canary-1.2.414
Canary-1.2.413
Canary-1.2.412
Canary-1.2.411
Canary-1.2.410
Canary-1.2.409
Canary-1.2.408
Canary-1.2.407
Canary-1.2.406
Canary-1.2.405
Canary-1.2.404
Canary-1.2.403
Canary-1.2.402
Canary-1.2.401
Canary-1.2.400
Canary-1.2.399
Canary-1.2.398
Canary-1.2.397
Canary-1.2.396
1.2.82
Canary-1.2.395
Canary-1.2.394
Canary-1.2.393
Canary-1.2.392
Canary-1.2.391
Canary-1.2.390
Canary-1.2.389
Canary-1.2.388
Canary-1.2.387
Canary-1.2.386
Canary-1.2.385
Canary-1.2.384
Canary-1.2.383
Canary-1.2.382
Canary-1.2.381
Canary-1.2.380
Canary-1.2.379
Canary-1.2.378
Canary-1.2.377
Canary-1.2.376
Canary-1.2.375
Canary-1.2.374
Canary-1.2.373
Canary-1.2.372
Canary-1.2.371
Canary-1.2.370
Canary-1.2.369
Canary-1.2.368
Canary-1.2.367
Canary-1.2.366
Canary-1.2.365
Canary-1.2.364
Canary-1.2.363
Canary-1.2.362
Canary-1.2.361
Canary-1.2.360
Canary-1.2.359
Canary-1.2.358
Canary-1.2.357
Canary-1.2.356
Canary-1.2.355
Canary-1.2.354
Canary-1.2.353
Canary-1.2.352
Canary-1.2.351
Canary-1.2.350
Canary-1.2.349
Canary-1.2.348
Canary-1.2.347
Canary-1.2.346
Canary-1.2.345
Canary-1.2.344
Canary-1.2.343
Canary-1.2.342
Canary-1.2.341
Canary-1.2.340
Canary-1.2.339
Canary-1.2.338
Canary-1.2.337
Canary-1.2.336
Canary-1.2.335
Canary-1.2.334
Canary-1.2.333
Canary-1.2.332
Canary-1.2.331
Canary-1.2.330
Canary-1.2.329
Canary-1.2.328
Canary-1.2.327
Canary-1.2.326
Canary-1.2.325
Canary-1.2.324
Canary-1.2.323
Canary-1.2.322
Canary-1.2.321
Canary-1.2.320
Canary-1.2.319
Canary-1.2.318
Canary-1.2.317
Canary-1.2.316
Canary-1.2.315
Canary-1.2.314
Canary-1.2.313
Canary-1.2.312
Canary-1.2.311
Canary-1.2.310
Canary-1.2.309
Canary-1.2.308
Canary-1.2.307
Canary-1.2.306
Canary-1.2.305
Canary-1.2.304
Canary-1.2.303
Canary-1.2.302
Canary-1.2.301
Canary-1.2.300
Canary-1.2.299
Canary-1.2.297
Canary-1.2.296
Canary-1.2.295
Canary-1.2.294
Canary-1.2.293
Canary-1.2.292
Canary-1.2.291
Canary-1.2.290
Canary-1.2.289
Canary-1.2.288
Canary-1.2.287
Canary-1.2.286
Canary-1.2.285
1.2.81
Canary-1.2.284
Canary-1.2.283
Canary-1.2.282
Canary-1.2.281
Canary-1.2.280
Canary-1.2.279
Canary-1.2.278
Canary-1.2.277
Canary-1.2.276
Canary-1.2.275
Canary-1.2.274
Canary-1.2.273
Canary-1.2.272
Canary-1.2.271
Canary-1.2.270
Canary-1.2.269
Canary-1.2.268
1.2.80
Canary-1.2.267
Canary-1.2.266
Canary-1.2.265
Canary-1.2.264
Canary-1.2.263
Canary-1.2.262
Canary-1.2.261
Canary-1.2.260
Canary-1.2.259
Canary-1.2.258
Canary-1.2.257
Canary-1.2.256
Canary-1.2.255
Canary-1.2.254
Canary-1.2.253
Canary-1.2.252
Canary-1.2.251
Canary-1.2.250
Canary-1.2.249
Canary-1.2.248
Canary-1.2.247
Canary-1.2.246
Canary-1.2.245
Canary-1.2.244
Canary-1.2.243
Canary-1.2.242
Canary-1.2.241
Canary-1.2.240
Canary-1.2.239
Canary-1.2.238
Canary-1.2.237
Canary-1.2.236
Canary-1.2.235
Canary-1.2.234
Canary-1.2.233
Canary-1.2.232
Canary-1.2.231
Canary-1.2.230
Canary-1.2.229
Canary-1.2.228
Canary-1.2.227
Canary-1.2.226
Canary-1.2.225
Canary-1.2.224
Canary-1.2.223
Canary-1.2.222
Canary-1.2.221
Canary-1.2.220
Canary-1.2.219
Canary-1.2.218
Canary-1.2.217
Canary-1.2.216
Canary-1.2.215
Canary-1.2.214
Canary-1.2.213
Canary-1.2.212
Canary-1.2.211
Canary-1.2.210
Canary-1.2.209
Canary-1.2.208
Canary-1.2.207
Canary-1.2.206
Canary-1.2.205
Canary-1.2.204
Canary-1.2.203
Canary-1.2.202
Canary-1.2.201
Canary-1.2.200
Canary-1.2.199
Canary-1.2.198
Canary-1.2.197
Canary-1.2.196
Canary-1.2.195
Canary-1.2.194
Canary-1.2.193
Canary-1.2.192
Canary-1.2.191
Canary-1.2.190
Canary-1.2.189
Canary-1.2.188
Canary-1.2.187
Canary-1.2.186
Canary-1.2.185
Canary-1.2.184
Canary-1.2.183
Canary-1.2.182
Canary-1.2.180
Canary-1.2.179
Canary-1.2.178
Canary-1.2.177
Canary-1.2.176
Canary-1.2.175
Canary-1.2.174
Canary-1.2.173
Canary-1.2.172
Canary-1.2.171
Canary-1.2.170
Canary-1.2.169
Canary-1.2.168
Canary-1.2.167
Canary-1.2.166
Canary-1.2.165
Canary-1.2.164
Canary-1.2.163
Canary-1.2.162
Canary-1.2.161
Canary-1.2.160
Canary-1.2.159
Canary-1.2.158
Canary-1.2.157
Canary-1.2.156
Canary-1.2.155
Canary-1.2.146
Canary-1.2.145
Canary-1.2.144
Canary-1.2.143
Canary-1.2.142
Canary-1.2.141
Canary-1.2.140
Canary-1.2.139
Canary-1.2.138
Canary-1.2.137
Canary-1.2.136
Canary-1.2.135
Canary-1.2.134
Canary-1.2.133
Canary-1.2.132
Canary-1.2.131
Canary-1.2.130
Canary-1.2.129
Canary-1.2.128
Canary-1.2.127
Canary-1.2.126
Canary-1.2.125
Canary-1.2.124
Canary-1.2.123
Canary-1.2.122
Canary-1.2.121
Canary-1.2.120
Canary-1.2.119
Canary-1.2.118
Canary-1.2.117
Canary-1.2.116
Canary-1.2.115
Canary-1.2.114
Canary-1.2.113
Canary-1.2.112
Canary-1.2.111
Canary-1.2.110
Canary-1.2.109
Canary-1.2.108
Canary-1.2.107
Canary-1.2.106
Canary-1.2.105
Canary-1.2.104
Canary-1.2.103
Canary-1.2.102
Canary-1.2.101
Canary-1.2.100
Canary-1.2.99
Canary-1.2.98
Canary-1.2.97
1.2.79
1.2.78
Canary-1.2.96
Canary-1.2.95
Canary-1.2.94
Canary-1.2.93
Canary-1.2.92
Canary-1.2.91
Canary-1.2.90
Canary-1.2.89
Canary-1.2.88
Canary-1.2.87
Canary-1.2.86
Canary-1.2.85
Canary-1.2.84
Canary-1.2.83
Canary-1.2.82
Canary-1.2.81
Canary-1.2.80
Canary-1.2.79
Canary-1.2.78
Canary-1.2.77
Canary-1.2.76
Canary-1.2.75
Canary-1.2.74
Canary-1.2.73
Canary-1.2.72
Canary-1.2.71
Canary-1.2.70
Canary-1.2.69
Canary-1.2.68
Canary-1.2.67
Canary-1.2.66
Canary-1.2.65
Canary-1.2.64
Canary-1.2.63
Canary-1.2.62
Canary-1.2.61
Canary-1.2.59
Canary-1.2.58
Canary-1.2.57
Canary-1.2.56
Canary-1.2.55
Canary-1.2.54
Canary-1.2.53
Canary-1.2.52
Canary-1.2.51
Canary-1.2.50
Canary-1.2.49
Canary-1.2.48
Canary-1.2.47
1.2.76
Canary-1.2.46
1.2.75
1.2.74
1.2.73
Canary-1.2.45
Canary-1.2.44
Canary-1.2.43
Canary-1.2.42
Canary-1.2.41
Canary-1.2.40
Canary-1.2.38
Canary-1.2.37
Canary-1.2.36
Canary-1.2.35
Canary-1.2.34
Canary-1.2.33
Canary-1.2.32
Canary-1.2.31
Canary-1.2.30
Canary-1.2.29
Canary-1.2.28
Canary-1.2.27
Canary-1.2.26
Canary-1.2.25
Canary-1.2.24
Canary-1.2.23
Canary-1.2.22
Canary-1.2.21
Canary-1.2.20
Canary-1.2.19
Canary-1.2.18
Canary-1.2.17
Canary-1.2.16
Canary-1.2.15
Canary-1.2.14
Canary-1.2.13
Canary-1.2.12
Canary-1.2.11
Canary-1.2.10
Canary-1.2.9
Canary-1.2.8
Canary-1.2.7
Canary-1.2.5
Canary-1.2.4
Canary-1.2.3
Canary-1.2.2
1.2.72
1.2.71
1.2.70
1.2.69
1.2.68
1.2.67
1.2.65
1.2.64
1.2.59
1.2.57
1.2.56
1.2.50
1.2.49
1.2.45
1.2.44
1.2.43
1.2.42
1.2.41
1.2.40
1.2.39
1.2.38
1.2.37
1.2.36
1.2.35
1.2.34
1.2.33
1.2.32
1.2.31
1.2.30
1.2.29
1.2.28
1.2.26
1.2.25
1.2.24
1.2.22
1.2.21
1.2.20
1.2.19
1.2.18
Labels
Clear labels
audio
Affects Audio playback during emulation
blocked on external progress
This cannot move forward without work on an external project or service.
bug
Something isn't working
cpu
An issue with ARMeilleure, the JIT, or Hypervisor
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good first issues to work on for new contributors
gpu
Affects GPU emulation
graphics-backend:metal
Affects the Metal Graphics backend
graphics-backend:opengl
Affects the OpenGL Graphics backend
graphics-backend:vulkan
Affects the Vulkan Graphics backend
gui
Affects the Avalonia UI or translations.
help wanted
Extra attention is needed
horizon
Affects the Horizon OS HLE components.
infra
Updates to dependencies
invalid
This doesn't seem right
kernel
Affects the kernel HLE components.
ldn
Affects the LDN functionality
linux
Linux only issue
macOS
macOS only issue
not planned but open to a PR
I do not intend on working on this myself, but I would not be opposed to an implementation.
question
Further information is requested
windows
Windows only issue
wontfix
This will not be worked on
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: MeloNX/Ryujinx-ryubing#554
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the issue
Update 1.2.80 has broken compatibility with mounted SMB shares. I believe the update to .NET 9 has caused this issue. Emulator will crash upon launching any software.
Emulator files and games are located on the network share. Previously emulator would detect the correct emulated system version in the bottom right corner.
After the update, the detected System version is NaN.
The previous version would also correctly list the mounted network path in console: D:\FOLDER_TO_EMULATOR...
After the update, folder path is listed as follows: \?\UNC\NETWORK_LOCATION...
Reproduction steps
Update to v1.2.80 and attempt to launch a game with the emulator running on an SMB network mounted disk.
Log file
Ryujinx_1.2.80_2025-01-20_21-49-27.log
OS
Windows 11 23H2
Ryujinx version
1.2.80
Game version
NA
CPU
AMD 7950X
GPU
NVIDIA RTX 4090
RAM
64 GB
List of applied mods
NA
Additional context?
No response
I have the same problem, with both 1.2.80 and 1.2.81... If i go back to 1.2.78 , all goes back to normal.
Use that version then. I'm not undoing the upgrade to .NET 9 because of a weird edge case with how some people decide to store their games.
@GreemDev We didnt tell you to reverse the .NET upgrade... But, more then anything to look up to fix the problem?
If before was working fine, but now it doesnt, i dont see why you cant fix. Obviously if the problem is with .NET 9 itself, there nothing we can do, we have to wait for a fix from Microsoft, i understand that.. in this case or we SMB users stick with 1.2.78 at the moment, or someone have to find a workaround to fix the Bug. Because "weird edge" or not, there are users that can and use a NAS to store anything and/or use SMB Share.
In my case I use a NAS, because for me its more convenient, and i can access those files whenever i am.
Dont cut off people only because they use a NAS/SMB Share. Please.
The .NET upgrade is realistically the only thing that caused this. I didn't make any changes to how anything is loaded.
I'm not asking for you to revert a change.
I'm asking if it would be possible to look into why this issue is occurring. It is possible the issue is related to .NET 9. But this may not be the case. If you could take a bit of time to look into the issue I believe both I and x7l7j8cc would appreciate it.
I understand this issue will effect a small subset of users but for us it would make a huge difference. Thank you.
Refer to the comment I just made.
I recently moved my emulator folders to my NAS, and used a symlink to bind it to my network path. Seems to work fine on my end.
How exactly did you manage this? I created a symlink to my emulator folder on my NAS but Ryujinx still refused to display firmware version and sees itself as installed on \UNC\SERVERNAME\Folder
@dxgldotorg @kftX
For me symlink doesnt work , as im on Windows.. and Windows doesnt allow to create a symlink to a NAS / SMB Share, you can only create a "Desktop Type Link".
mklink /d link target
@dxgldotorg I used that same command, but when used on a smb/nas it simply create a link on windows.
Yup, can confirm the same. I knew about mklink /d but the thing is that's a soft-link and doesn't work, I thought he'd done something different. Linux allows for hard linking folders but Windows does not. There is a junction option in Windows as well, but it can't point to non-local drives. So basically we keep the old version.
Maybe recent Canary builds of Windows handle the symlink redirection better, as that is what I'm running on.
Can't test at the very moment as my server is having issues, but it did work for me.Edit: Booted up TOTK 1.2.1 and could play and save fine.Here is a python script I created to create a .bat file with all the mklink commands for directories containing a mix of folders and files.
Change the extension of the file from .txt to .py in order to use it.
The python script asks for a network directory and a local directory and will create a .bat file containing the commands for a symlink from the network directory to the local directory.
Run the created .bat in order to create the symlink. Finally, you must delete the Ryujinx.exe from the local folder since it's a symlink file and replace it with a copy of the .exe from the network folder.
Symbolic Link Create.txt
@GiulioCDI
This are the results..."Impossibile trovare il percorso specificato." -> "The specified path could not be found."
EDIT: I needed to create manually the Folder.
@GiulioCDI Ok, after a bit, i can confirm that the method GiulioCDI wrote, works fine.
GiulioCDI, i changed a bit the python code, and ended up creating 2 methods...
Either two do their things Fully Automatically (just need the source and destination folder), so there is no need to manually copy or other things. Obviously if anyone is interested.
RyujiNX_SymLink_Generator.py.txt
RyujiNX_SymLink_Generator(with_BAT).py.txt
I tested the most recent Canary and the issue is still there. It does not detect or install any firmware as the path \UNC[...] is unavailable. Are you sure your Ryujinx itself is on the NAS? Because the dumps being located on the NAS/Server is fine, what breaks Ryujinx is the emulator itself (with a portable folder) being located on the NAS/Server.
Here is a screenshot of my local folder. All files and folder except for Ryujinx.exe are symlinks. The .exe is the only file that needs to actually be present in the local directory. I took a screenshot of my Ryujinx folder for easier understanding.
EDIT
When installing firmware use the symlink path and not the network path.Installing firmware from a network folder seems to work without a problem.
As a quick update, LaunchBox just recently updated to .NET 9 as well, and my network shares do not seem to suffer from the same issue: they are detected as Drive E, F, G, ect, rather than UNC\SERVERNAME\[...]
This seems to be abandoned, but just wanted to give that small piece of feedback.