View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007056||Kali Linux||General Bug||public||2021-02-19 16:23||2023-10-10 12:25|
|Summary||0007056: Kali-live crashes during build - Message: Volume ID does not fit in 32 bit|
sorry to disturb you, but I believe, that something important might have changed, but I still can not find, what happened.
As usual as do regularly I wanted to build a kali-live , and as I always do is to get the latest git configs using the command
git pull origin master, then do the build with ./build.sh with my additional commands like "boot=live" keyboard=......." and so on.
This is working well since years.
But this time the build crashes with the message: "Volume ID does not fit in 32 bit" (see attached build.log).
Please note, that both builds (I built for amd64 and for i386) are crashing with the identical message. I also noticed, that the git command updated some files, one was build.sh (don't know if this matters).
So as I am not sure, if I myself did something wrong or if one of the new configs messed or one of the packages are causing this issue, I am looking for help here.
It would be nice, if someone could give me a clue (if it was my mistake) or take a look at this issue.
Thanks for any help and feel free for more information.
|Steps To Reproduce|
define path to the repository on your disk
download and install needed packages
execute any commands to fit your personal environment
prepare youre proxy and make sure, your local repo has ownership "apt-cacher-ng:apt-cacher-ng"
cp acng.conf /etc/apt-cacher-ng/
updating the git branch
git pull origin master
This is a test szenario, execite other scripts as needed
This suggestion calls my very own script.
Then second script:
Author Hans-J. Ullrich <[email protected]>
Set some variables, not active yet.
architecture: i386, amd64, arm
Distribution, you might not want to change it.
Your preferred window-manager: lxde, kde, xfce, gnome
Environmet for your local proxy
language, keyboard, locales everything you might not need to change
BOOTAPP="boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"
Clean your system, not really necessarey, as the latter "./build.sh" does
VERY IMPORTANT: Make sure, apt-cacher is started, even, if you are sure,
it is already running!
/etc/init.d/apt-cacher-ng stop && sleep 3 && /etc/init.d/apt-cacher-ng start
set your needed environment and preparations.
This command starts the actual build. All commands are in one line.
However, this script might be improved, to use variables for better
./build.sh --arch $ARCH --distribution $DISTRO --variant $VARIANT --verbose -- --apt-http-proxy $PROXY --bootappend-live "$BOOTAPP"
these options can be used for further commands after build
for example, if you want to burn a dvd, shutdown, whatever
Examples for my personal needs below
Suggestions for handling the built image.
cp /home/username/live-build-config/images/*.iso /home/user/
Some opportunities at unattended build run, what to do after the build succeeded.
shutdown -h now
build.log (1,402,727 bytes)
It's indeed a regression in i386.
I have pushed live-build 20210216kali1 with the fix, it should be soon available in kali-dev and a bit later in kali-rolling.
|2021-02-19 16:23||vanguard||New Issue|
|2021-02-19 16:23||vanguard||File Added: build.log|
|2021-02-23 09:20||rhertzog||Note Added: 0014241|
|2021-02-23 12:41||rhertzog||Assigned To||=> rhertzog|
|2021-02-23 12:41||rhertzog||Status||new => resolved|
|2021-02-23 12:41||rhertzog||Resolution||open => fixed|
|2021-02-23 12:41||rhertzog||Note Added: 0014243|
|2023-10-10 12:25||vanguard||Status||resolved => closed|