mac android studio: emulator: process finished with exit code 134 (interrupted by signal 6: sigabrt

Since that didn't work, I finally tried e2fsck.

Since v gave no errors, I confirmed the write with w. I ran gdisk with r to get to recovery options and then with b and c to read and recover the partition table from the secondary table. Since I planned on using e2fsck, I didn't worry about that too much, since I had to use an unmounted disk anyway. I tried what was suggest here and run sudo blockdev -rereadpt on both disks, but it ran without any feedback and the mount was still not possible. Special device /dev/sdb1/ does not exist (a path prefix is not a directory). This morning I tried to continue after a reboot and suddenly I couldn't mount either disk:

I did that.Īlthough when checking afterwards with df -h the original disk showed 981G used and the copy only showed 80K in use. The first recommendation was to make a dd backup of the entire disk. I plugged in the drive into the original Ubuntu machine, only to see the same results. Some files were readable other folders threw an error or appeared empty. (Second mistake) I tried to use DiskInternals LinuxReader to be able to read the ext4 format. To use the data I plugged in the drive into a Windows machine. Since the drive is new and the SMART values all looked good, I didn't worry too much about it, but maybe I should have? The HDD was making noises when I moved the data. Here is what I did to make the problem occur: I moved all my data to a new drive and it seems to be lost.

Mac android studio: emulator: process finished with exit code 134 (interrupted by signal 6: sigabrt