mirror of
https://github.com/hacks-guide/Guide_3DS.git
synced 2025-08-26 01:44:20 +02:00
d84cb07e29
Things that happen in this shameless squash:
- Removed 404 page
- It doesn't work in VitePress and making it work in VitePress needs
some invasive hack in the theme that I'm not willing to do
- The default is more than enough, though
- Moved consoleVersionSelect include to another directory
- This avoids being uploaded to Crowdin for translation
- Inline all SafeB9SInstaller includes
- Not only do parameterized includes not work, but if/else statements
don't work at all
- The sysupdate include parameter hasn't been used since MSET9, so it
actually works just fine without any parameters. Hooray(?)
- Move mset9-chorus to an include, that logic doesn't work in VitePress
- Removed Get Started button from homepage, it breaks translations
- Tables in get-started are now shown by default; it seems VitePress really does
not want us to use inline script. So we cannot enable it upon
realizing that the browser is JS capable
- Include parameters are now in frontmatter to allow translation
- Hacked in a bunch of CSS values kanged from the old theme to make it
look not stupid
- Drop headers down one level to make table of contents work
72 lines
1.8 KiB
Markdown
72 lines
1.8 KiB
Markdown
# F3 (Linux)
|
|
|
|
## Required Reading
|
|
|
|
This is an add-on section for checking your SD card for errors using F3.
|
|
|
|
Depending on the size of your SD card and the speed of your computer, this process can take up to several hours!
|
|
|
|
This page is for Linux users only. If you are not on Linux, check out the [H2testw (Windows)](h2testw-(windows)) or [F3XSwift (Mac)](f3xswift-(mac)) pages.
|
|
|
|
## What You Need
|
|
|
|
* The latest version of [F3](https://github.com/AltraMayor/f3/releases/tag/v8.0)
|
|
|
|
## Instructions
|
|
|
|
1. Unzip the f3 `.zip` file
|
|
1. `cd` into the f3 directory
|
|
1. Run `make` to compile F3
|
|
1. Insert your SD card into your computer
|
|
1. Mount your SD card
|
|
1. Run `./f3write <your sd card mount point>`
|
|
1. Wait until the process is complete. See below for an example output.
|
|
|
|
~~~ bash
|
|
$ ./f3write /media/michel/6135-3363/
|
|
Free space: 29.71 GB
|
|
Creating file 1.h2w ... OK!
|
|
...
|
|
Creating file 30.h2w ... OK!
|
|
Free space: 0.00 Byte
|
|
Average Writing speed: 4.90 MB/s
|
|
~~~
|
|
|
|
1. Run `./f3read <your sd card mount point>`
|
|
1. Wait until the process is complete. See below for an example output.
|
|
|
|
~~~ bash
|
|
$ ./f3read /media/michel/6135-3363/
|
|
SECTORS ok/corrupted/changed/overwritten
|
|
Validating file 1.h2w ... 2097152/ 0/ 0/ 0
|
|
...
|
|
Validating file 30.h2w ... 1491904/ 0/ 0/ 0
|
|
|
|
Data OK: 29.71 GB (62309312 sectors)
|
|
Data LOST: 0.00 Byte (0 sectors)
|
|
Corrupted: 0.00 Byte (0 sectors)
|
|
Slightly changed: 0.00 Byte (0 sectors)
|
|
Overwritten: 0.00 Byte (0 sectors)
|
|
Average Reading speed: 9.42 MB/s
|
|
~~~
|
|
|
|
___
|
|
|
|
::: tip
|
|
|
|
If the test shows the result `Data LOST: 0.00 Byte (0 sectors)`, your SD card is good and you can delete all `.h2w` files on your SD card.
|
|
|
|
:::
|
|
|
|
::: danger
|
|
|
|
If the test shows any other results, your SD card may be corrupted or damaged and you may have to replace it!
|
|
|
|
:::
|
|
|
|
::: tip
|
|
|
|
Return to [Get Started](get-started)
|
|
|
|
:::
|