Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
troubleshooting [2023/11/17 23:23] – [x86/x86_64] Legacy boot "Boot error" recovery maximumentropytroubleshooting [2026/03/28 18:41] (current) – ↷ Links adapted because of a move operation 92.184.108.195
Line 1: Line 1:
 ====== System Troubleshooting ====== ====== System Troubleshooting ======
 +
 +If going to our [[https://discord.gg/ndyUKA5|Discord]] for help, gather the relevant logs (as described below) and upload them along with your message. This will help us help you better.
  
 ===== Emulators not launching/EmulationStation logs ===== ===== Emulators not launching/EmulationStation logs =====
Line 49: Line 51:
   * [[systems:fpinball|Future Pinball]]   * [[systems:fpinball|Future Pinball]]
   * [[systems:jaguar|Jaguar]] (BigPEmu)   * [[systems:jaguar|Jaguar]] (BigPEmu)
-  * [[systems:xash3d_fwgs|xash3d_fwgs]]+  * [[systems:halflife|xash3d_fwgs]]
  
-If you want to continue using your NAS for the majority of your games, but to use your internal storage for these affected systems so they can continue to work (not being on your NAS, obviously), save the following script as ''/userdata/system/custom.sh'': 
  
-<file bash custom.sh>+If you want to continue using your NAS for the majority of your games, but to use your internal storage for these affected systems so they can continue to work (not being on your NAS, obviously), save the following file as a [[scripting_services_rules_examples#batocera_services|service]] in ''/userdata/system/services/nas_workaround'' (no extension): 
 + 
 +<file bash nas_workaround>
 #!/bin/bash #!/bin/bash
 # This allows you to still use Windows/Flatpaks even while using a NAS. # This allows you to still use Windows/Flatpaks even while using a NAS.
Line 71: Line 74:
  
 </file> </file>
 +
 +After uploading or creating the file, run ''batocera-services enable nas_workaround'' to activate the service at boot. Rebooting or running ''batocera-services start nas_workaround'' should create all the nescessary mountpoints in /media/.
  
 <WRAP center round info> <WRAP center round info>
Line 359: Line 364:
 ==== I can see the drive but still can't access it! ==== ==== I can see the drive but still can't access it! ====
  
-Maybe you have Bitlocker drive encryption enabled? This is a feature of Windows that allows you to encrypt your drive's data such that only Windows can see it. It is not enabled by default, but it could have been unintentionally activated.+Maybe you have Bitlocker drive encryption enabled? This is a feature of Windows that allows you to encrypt your drive's data such that only Windows can see it. It is enabled by default since around 2024.
  
 First, type "bitlocker drive encryption" into the Start menu and select the identically named option. Make sure your hard-drive says "Off" in its Bitlocker encryption status. First, type "bitlocker drive encryption" into the Start menu and select the identically named option. Make sure your hard-drive says "Off" in its Bitlocker encryption status.
Line 379: Line 384:
 ===== Create a Batocera support file ===== ===== Create a Batocera support file =====
  
-In case you want to share a snapshot of your system log files to [[:report_issue|help developers diagnose your machine]] you can use the menu **SYSTEM SETTINGS** -> **FRONTEND DEVELOPER OPTIONS** -> **CREATE A SUPPORT FILE**. It will generate a tarball in ''/userdata/saves/'' named ''batocera-support-YYYYMMDDHHMMSS.tar.gz'' (with year/date/time of creation in the filename). You could also create this by running ''batocera-support'' from [[:access_the_batocera_via_ssh|SSH]]. This tarball might contain sensitive data such as your Wi-Fi/RetroAchievements password in plain-text, so be careful of where you share it to. Your:+In case you want to share a snapshot of your system log files to [[:report_issue|help developers diagnose your machine]] you can use the menu **SYSTEM SETTINGS** -> **FRONTEND DEVELOPER OPTIONS** -> **CREATE A SUPPORT FILE**. It will generate a tarball in ''/userdata/saves/'' named ''batocera-support-YYYYMMDDHHMMSS.tar.gz'' (with year/date/time of creation in the filename). You could also create this by running ''batocera-support'' from [[:access_the_batocera_via_ssh|SSH]].  
 +<WRAP center round important> 
 +This tarball might contain sensitive data such as your Wi-Fi/RetroAchievements password in plain-text, so be careful of where you share it to. Your:
   * Wi-Fi SSID and password is in ''system/batocera.conf'' and ''system/batocera-boot.conf''   * Wi-Fi SSID and password is in ''system/batocera.conf'' and ''system/batocera-boot.conf''
   * RetroAcheivements username and password are in ''system/batocera.conf''   * RetroAcheivements username and password are in ''system/batocera.conf''
Line 386: Line 393:
 You could also just use a freshly installed Batocera that contains no such information instead to create the support file. You could also just use a freshly installed Batocera that contains no such information instead to create the support file.
  
 +In Batocera **39** or later, most sensitive data will be scrubbed from the support file automatically.  Please file a Github issue report if any sensitive data is found in support files from recent versions.
 +</WRAP>
 ===== Factory reset ===== ===== Factory reset =====
  
  • troubleshooting.1700263426.txt.gz
  • Last modified: 3 years ago
  • by maximumentropy