Comments (23)
Can you try the mirror “kali.mirror.globo.tech” ? I just checked and that’s the mirror that the build system gets as the round robin from http.kali.org
As to the second failed build - that’s because you disabled it installing raspi3-firmware - that package installs the rpi3 firmware and puts it in /boot/firmware and since we use a different layout (we have the first partition as /boot to mirror raspbian to be closer to what their scripts and all the instructions out there use) it’s failing to copy them.
Interestingly enough, your failure of nmap, is a 403 forbidden, not a 404 not found.
I should move the raspi3-firmware to a different line to be sure it’s installed since it is important and required, without it, an image won’t boot unless someone modified the script to clone the upstream firmware repo and move the files into /boot.
from kali-arm-build-scripts.
That seems odd, the script downloads that file and puts it where it needs to be - are you maybe running out of space on the drive your running the script from? That’s the only thing I could think may be doing it.
The computer this script is running on has a 10GB of unused disk space so there should be plenty of room spare. Is there anything else that might be interfering the script completing?
from kali-arm-build-scripts.
Perhaps a flakey internet connection?
If you could run the build again, and redirect the output to a file and paste it, I could see - I cannot reproduce the issue at all here, either running it manually nor through my automated builds (in fact, the automated build just completed a run 1 minute ago.)
Simply doing something like ./rpi3-nexmon.sh test 2>&1 | tee failing-build.log
and then paste the outputs into a comment here so I can see what your system is doing? If you've modified the file at all, it would be nice to see the changes as well.
from kali-arm-build-scripts.
That seems odd, the script downloads that file and puts it where it needs to be - are you maybe running out of space on the drive your running the script from? That’s the only thing I could think may be doing it.
from kali-arm-build-scripts.
The changes I made are from the Kali official walk-through: https://kali.training/topic/exercise-4-4-custom-kali-linux-arm-install/
The changes I made are:
`#desktop="fonts-croscore fonts-crosextra-caladea fonts-crosextra-carlito gnome-theme-kali gtk3-engines-xfce kali-desktop-xfce kali-root-login lightdm network-manager network-manager-gnome xfce4 xserver-xorg-video-fbdev xserver-xorg-input-evdev xserver-xorg-input-synaptics"
#tools="aircrack-ng ethtool hydra john libnfc-bin mfoc nmap passing-the-hash sqlmap usbutils winexe wireshark net-tools"
tools="aircrack-ng nmap hostapd"
#services="apache2 openssh-server"
services="openssh-server"
#extras="iceweasel xfce4-terminal wpasupplicant python-smbus i2c-tools python-requests python-configobj python-pip"
#packages="${arm} ${base} ${desktop} ${tools} ${services} ${extras}"
packages="${arm} ${base} ${tools} ${services}"`
Then under the WiFi section:
auto eth0 iface eth0 inet static address 192.168.1.12 netmask 255.255.255.0 gateway 192.168.1.1 EOF
The Log:
failing-build.log
from kali-arm-build-scripts.
Based on that log file, there was an isssue downloading nmap, not the kernel, or anything kernel related.
Either the mirror was in the middle of updating, or the mirror you got has a few out of date files - can you try hardcoding a different mirror? The “mirror=http.kali.org” line is the one to change.
Also please be sure you didn’t accidentally remove the beginning slash for the dpkg line for the kernel - you can quickly see your changes by doing “git diff” in the kali-arm-build-scripts checkout
from kali-arm-build-scripts.
I switched the mirror and it still wasn't working, so I decided to remove nmap from the installation. Also the dpkg line wasn't changed since I didn't see anything related to a line like that when I typed "git diff".
The newer installation without nmap seemed to work better, however still ran into a problem with inability to access a file. Will update further on Monday. Thank you all for the help thus far.
from kali-arm-build-scripts.
failing-build.log
I've changed the mirror and removed the installation of tools just in case. Now however, it cannot find the firmware folder to get the stats off of. I've scanned through the rest of the log file and there weren't any other errors as far as I could see.
from kali-arm-build-scripts.
Also to address the mention of sshd_config in your previous comment - because there’s an issue installing nmap, the packages fail to install and because openssh-server didn’t install (due to the nmap package failing), the /etc/ssh/sshd_config file doesn’t exist.
I have the script failing due to that because previously, I didn’t have it fail, and since the packages aren’t installed, the build was succeeding but (obviously) not working properly
from kali-arm-build-scripts.
failing-build.log
I tried the mirror that you mentioned and was able to install nmap with it, and I made sure the rpi3 firmware was installed as well this time. I believe that the script ran properly this time as I ended up with an .img file, however, based on the Kali Revealed, there should be a zipped .img file. Which is correct? The .img.xz or just a plain .img, or is something else up?
from kali-arm-build-scripts.
It’s img.xz - the image (img file) is compressed with xz because it compresses a bit better than a zip, but it doesn’t roll off the tongue as well as “zipped” which is often used synonymously as a compressed file. Although I don’t see anything on the page about a zipped file.
The only time you won’t have an img.xz file, is if you do it on 32bit, as 32bit will run out of memory compressing. The big change from when that was written until now is that it writes the image into the directory you run the script from so you don’t have to look in the folder to see it.
from kali-arm-build-scripts.
(^ the output of the script, clicking it will turn it right side up)
My apologies, to clarify: After the script stopped running, the files that were in the rpi3-nexmon-1.0 folder were the file system (kali-armhf), the image, nexmon folder, and the root folder. Nothing in the log file jumped out at me as saying something went wrong for it to just stop before compressing the image.
Edit: My OS is 64 bit.
from kali-arm-build-scripts.
i'm not sure what would cause that, aside from it not fully running correctly - do you have the output of the build? I run automated builds of all the rpi scripts and get a notification if something fails pretty quick, so the only thing i can think is another issue with downloading somewhere. You can run the script with something like ./rpi3-nexmon.sh 1.0 2>&1| tee rpibuild.log
and it would produce a file with the output that I could look through.
from kali-arm-build-scripts.
build.log
Here's the output from the build. I've only changed the mirror to what was suggested above and removed the desktop in the included packages and changed how the network interface will be setup, which I wouldn't think would change anything.
from kali-arm-build-scripts.
Can you try to add a sleep 10
after the sync
and before the umount -l ${bootp}
(line 459). I wonder if your cache isn't actually finished writing - it's not unmounting the boot partition yet even though it's unmounting the second partition.
from kali-arm-build-scripts.
build.log
Adding sleep 10
did slightly change the end result, it changed which loop was still running and wouldn't unmount. I increased the sleep time by 10 but it had the same result.
from kali-arm-build-scripts.
Okay, I'm not entirely certain but this may be my fault in not noticing that the size of the install was increasing - Can you set the size (line 21) to 5000 instead of 4500 and see if that works? I started running into a similar issue last night/today with the automated builds but it was throwing an error that it was running out of space not that it couldn't unmount.
I need to go through that walkthrough and see about getting modifications in to match the latest scripts, it's possible that we're still installing things even though you're not adding them (due to dependencies).
from kali-arm-build-scripts.
No, I'm wrong - your build script log output even shows you're only using 1.6GB of space.
What kind of hardware is being used here? The script should be lazily unmounting, so the loop device shouldn't be in use still.
from kali-arm-build-scripts.
I'm using a virtual machine that's running Kali which I made sure to give more than enough RAM and hard drive space. Otherwise, I have a i5 processor and 6GB of RAM.
from kali-arm-build-scripts.
from kali-arm-build-scripts.
I'm using virtualbox and my hard drive has 7,000 RPM and 6Gb/s.
from kali-arm-build-scripts.
I can't seem to replicate this here, are you still having issues with it?
from kali-arm-build-scripts.
Yes I am unfortunately. I've tried increasing the sleep time to no avail and trying to run the scrip on another Linux machine I had lying around but that died part way through, so I've been out of luck.
from kali-arm-build-scripts.
Related Issues (20)
- FriendlyArm NanoPC-T4 HOT 6
- Default Password toor for root Doesn't work on Fresh Image for Odroid C2? HOT 12
- Simple Kali arm build script for Raspberry pi 3 b+ HOT 3
- Container fails with error code 1 HOT 3
- rpi3-nexmon.sh fails with error code 1 HOT 8
- Create a arm64 script for the rapi 3b and 3b+? HOT 2
- [P4wnP1 + Nexmon] Unable to connect to the AP HOT 1
- `apt-get update` reports "Release file not valid yet." HOT 3
- HP Chromebook 13 G1 m7 variant HOT 1
- Can't Install raspi3-firmware HOT 3
- Fixed errors of pi-bluetooth for Pi Zero W HOT 3
- Need build scripts and images for ARM64 SBBR systems and Always Connected PCs HOT 1
- GPIO not working on Kali Linux RaspberryPi 3 64bit 2018.4a HOT 11
- PINE64 Pinebook 1080p HOT 1
- rpi0: g_serial and /dev/ttyGS0 HOT 2
- Odroid U2 image does not include "u2" in image name HOT 3
- Odroid image: read outside partition HOT 2
- rpi3-nexmon.sh couldn't download package bash HOT 2
- Suggestion for README.md
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kali-arm-build-scripts.