-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot make filesystem #67
Comments
That's strange. Are you using a USB boot or live image? People have mentioned an incompatibility in the past with Kali. |
Hi, I'm having issues along these lines as well. I am using an ESX vm. I have tried changing Here's the contents of my
and the output of
|
What's the output of |
I‘ve met the same question with U. Querying database for architecture... Password for user firmadyne: I've checked the qemu.initial.serial.log and there isnt any '__inet_insert_ifa' as well. |
You should create a separate issue. Have you checked https://github.com/firmadyne/firmadyne#runsh-is-not-generated ? |
thank you,i've solved this problem. Below is the output of run.sh Starting firmware emulation... use Ctrl-a + x to exit |
Somehow, the init binaries is missing or not executable. You'll need to check /sbin/init, and if it doesn't exist, find the proper name of the init binary for this firmware and move it there. |
When inputting sudo ./scripts/makeImage.sh, the output is /dev/mapper/loop0p1 is mounted; will not make a filesystem here!. I have do it again using your FAQ,but it has no effect. Looking forward to your answer
The text was updated successfully, but these errors were encountered: