The drive is assigned a letter in Windows Explorer However when I install the software and try and access a XFS disk from my unEAID system on my Windows 10 setup: The software is not free but is very modestly priced so not really a big issue to consider purchasing it. Then insert the card and see if it shows up at the correct mount point.īottom line: Always format all your microSD cards the exact same way (and if you use a volume name, always use the same one), and you shouldn’t have issues.I have just noticed that Paragon software have extended their Linux file system support on Windows to include read-only handling of XFS and BTRFS format disks (in addition to the EXT2/3/4 read/write support they have had for ages) which is potentially of great interest to unRAID users. Try removing the card and rebooting your Deck. Sometimes, even when you format the card without a volume name, the Deck will mount it in another location with a similar series of letters – but since your installed software is expecting the content at mmcblk0p1? It won’t run right. When you do this, Deck will mount the card by that name instead of the normal mmcblk0p1 location. This can happen in one of two ways most likely it is because you gave the volume a name when you formatted it with LFS. The microSD card isn’t mounted the same when formatting outside the Deck and it is causing my installed stuff like EmuDeck to stop working. This should restore the ability to write/install new games.Īs of V0.6b, DDM can export the above command (customized for your drive) to a text file to the root of the drive which you can open, cut and paste and execute in konsole to change ownership on the drive to behave with the Deck. Run this command from konsole and replace the with the name of your Deck’s SD card. Unfortunately, writing to the root of a LFS formatted drive requires a bit of fixing while on the Deck itself. If the steamapps folder is already made under a different set of permissions, the command below will also clear the issue. This is commonly an issue when a new microSD card is prepped for the Deck and the steamapps folder isn’t already created by the Deck. This will make all subsequent folders created to be accessible by the Deck. Fortunately, they are pretty easy to work around.įirst, always mount the drive in LFS as User 1000 and Group 1000 while manually setting permissions to 777. There are some permissions quirks between LFS and the Deck. I get a DISK ERROR when installing Steam games, I cannot write to the root of the drive or folders created when using LFS. Windows 11) appears to cause corruption, blue screens of death and other undesirable events)Īfter using LFS to work with my drive, it appears to be write protected when using it on the deck. * Note: Using the free Windows BRTFS driver in versions of Windows higher than 10 (e.g.
0 Comments
Leave a Reply. |