ERROR: resizing partition e2fsck failed with exit code 8

I had the same issue after updating Android SDK tools package to version 25.2.2. To fix the problem i've restarted Android SDK Manager and then created new virtual device instead of using the old one.

I know this is an "old" question, but the following command solved the problem for me:

./emulator -data /sdk/path/here/system-images/android-API/default/x86/userdata.img -avd your_avd_name

where API is the api level you want to use. I found that this is only needed for API<20

Note: I had that problem with libstdc++, so I had to use the LD_PRELOAD envvar. I removed it in the example, so for me, the complete command looks like this:

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./emulator -data /home/username/Android/Sdk/system-images/android-API/default/x86/userdata.img -avd Whatever

I ran into the same type of problem after installing an update to one the SDK platforms, except my output log contained more than complaints. It contained a possible solution to the problem. See the log below.

emulator: WARNING: userdata partition is resized from 769 M to 770 MERROR: resizing partition e2fsck failed with exit code 8Hax is enabledHax ram_size 0x40000000HAX is working and emulator runs in fast virt mode.emulator: Listening for console connections on port: 5554emulator: Serial number of this emulator (for ADB): emulator-5554Your emulator is out of date, please update by launching Android Studio: - Start Android Studio - Select menu "Tools > Android > SDK Manager" - Click "SDK Tools" tab - Check "Android SDK Tools" checkbox - Click "OK"Emulator Android_Accelerated_x86_Nougat is running.Waiting for emulator to be ready...

Solution 1: Update the SDK Tools

1. Open Android SDKs and Tools window.
2. Go to the Tools tab (the name of this tab has changed).
3. Expand the Android SDK Tools group and make sure you select thelatest available version.
4. Click Apply Changes.

Possible problem with this solution:

You may run into a new problem by following this solution. When you run the emulator it will do a cold boot and ask you for a decryption password. If you don't provide the right password, it will display a black screen and then tell you that the decryption failed.

So this did not work in my case, but your mileage may vary.

Solution 2: Factory reset the emulator

I don't use Android Studio. I use Xamarin with Visual Studio. Installing the Xamarin Device Manager and doing a factory reset of the emulator is what fixed the problem for me.

You should have a similar option if you are using Android Studio. But if you would like to, you can try downloading and installing the Xamarin Device Manager by Microsoft. It's an independent application that does not require installation of Visual Studio or Xamarin.