View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003762 | Kali Linux | General Bug | public | 2016-12-07 18:29 | 2023-10-10 12:27 |
Reporter | vanguard | Assigned To | rhertzog | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0003762: Self builf kali crashes at boot | ||||
Description | Der developers, I am building a kali linux lived image fron time to time with live-build. Please note: The build iso image is booting from a DVD perfectly, but I am using XBOOT (a multiboot tool) to get kali-linux livefile among other linuces onto an usb stick. This worked for many years now, as I said. But the latest boot crashes, when the livefile is unpacking and mounting the squashfs filesystem. The boot process wants also to mount also my ntfs (windows) filesystems, cannot succeed and ends in endless tries to mount these filesystems. Something must have changed, since the last 6 weeks either in live-build (I use the one from kali) or in kali itself. I hope, someone can help me and can give me some hints. Thank you for reading this. Best regards Hans | ||||
Steps To Reproduce |
| ||||
The endless messages, where it hangs are like the following: --- snip ---- --- snap ---- Both named filesystems above are really not on /dev/sdb but on /dev/sda. How can I fix it? Thanks Hans |
|
CORRECTION: The endless messages, where it hangs are like the following: --- snip ---- --- snap ---- Whilst /dev/sdb is the sd-card (where the correct filesystem.squashfs resides and should be found), /dev/sda11 is the harddrive, which should not be accessed. It looks, like the sd-card can not be mounted, and so filesystem.squashfs cannot be found. Am I correct? Any ideas, how can I fix it? Thanks Hans |
|
Ok, i checked it out. Kali starts from the sd drive (or usb-drive as well), but at the point, when the filesystem.squashfs should be mounted, it hangs. So it is surely a kali bug, and NOT a bug of xboot! I also checked the other livesystems, which are also debian based and are also started by xboot: All of them are working fine. Also checked the kali startup command of grub: It is identical to the other livesystems on this card. This all is telling me: It is really a problem by the build. FYI here is the grub command of kali: .linux /live/vmlinuz acpi_osi=Linux boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys live-media-path=/images/kalilinuxlxderollingi386/live initrd=/live/initrd.img This is the same syntax as all livesystems! As I cannot use kali-linux-live any more at all, please set the priority to "crash". If needed, I can send relevant files from the filesystem.squashfs up here. Thank you for any help. Best regards Hans |
|
Hi Hans, I tested a live-build ISO this morning, and had no issues at all. I am not familiar with XBOOT and would therefore suspect an issue with that, or something else in your build process. As of now, your bug report doesn't seem actionable on our part. If you can point out a specific bug with live-build, please feel free to re-open this report. |
|
Sorry, that is too easy for me! Please check my problem and use XBOOT then with the built ISO. When you build an ISO and burn it on DVD, then it is booting correctly, but when you boot from an SD-card or USB-stick using XBOOT, it crashes. And I repeat: For years it worked well with XBOOT! So do not blame it, because that what changed is kali NOT XBOOT! Do NOT use the downloadable version version 2016.2 for testing, but build a new one. The downloadable version 2016.2 is too old for the test. Please use a fresh build! I suppose, the problem might be easy to fix, but I am really stuck now. I do not know, where to look any more. Maybe it is a kernel problem? Don't know. But there IS a bug, something very important has changed. Please help! Thank you very much! Best Hans |
|
Hi Hans, We are not familiar with XBOOT and do not support it. If you want to try to narrow down your bug, i recommend you use the supported method of getting your ISO onto usb, which is using the "dd" utility. If this still brings up the issue, we can confirm it's a Kali bug. |
|
Hi @ muts And please add support for LZ4 squashfs "CONFIG_SQUASHFS_LZ4=y" (it's very fast),maybe also CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y ,or CONFIG_SQUASHFS_DECOMP_MULTI=y Regards |
|
Hi emil4o1, So the solution would be, that the maintainers will create a new package with a kernel compiled with CONFIG_FAT_DEFAULT_IOCHARSET="utf8" built in. And of course make a new package in the repo. I hope, they will read this here! :) I checked for any differences between a working build and a none working build, but I could not discover a difference. However, the latest git changed a path in the config of latest live-build for kali. They put includes.chroot/lib/live I found no changelog for the git. Is there any one at all? At next build I will try to use your hints and compress squashfs. My target machine is an EEEPC with a single core (two cores with hypertheading), let's see, if the ****MULTI_PERCPU=y will speed up things. Best regards Hans |
|
Ok.. the problem is that live-boot-initramfs-tools don't add module "nls_ascii" to initrd. |
|
Nice, but that is a workaround. But this should be fixed in the live-build-git of kali, so everybody got the benefits of t, don't you think so? Best regards Hans |
|
Same problem here. kali-linux-2016-W36-amd64.iso was working fine, kali-linux-2016-W49-amd64.iso is not working on FAT32. The official dd method is not user friendly, I want to use the rest of the USB drive for other data and a multiboot. Why carry multiple USB drives, if you have a 32GB with all you need? On USB only 'live' and 'isolinux' folder are needed. Rename isolinux.cfg to syslinux.cfg. The W36 version booted using syslinux on FAT32, the w49 only works from a EXT2 partition and extlinux bootloader. I'm trying the suggestion: manual edit inird and add module nls_ascii |
|
Can we not change something in the live-build environment? IMO thius should be the better way. If someone knows, how to do this, I will be pleased to test it. Hans |
|
I'll handle a live-boot update soonish. |
|
Hi Raphael, thank you for working on it! I am looking forward to the patch. As soon it will be implemented, I will build a new ISO and report, if it is working again. Thanks a lot and happy 2017! Hans |
|
This should be fixed with live-boot 20170112. I just uploaded it to Debian and I'll sync to kali once it's built and available in Debian unstable. |
|
New live-boot is now in kali-rolling. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2016-12-07 18:29 | vanguard | New Issue | |
2016-12-13 12:01 | vanguard | Note Added: 0006157 | |
2016-12-13 12:07 | vanguard | Note Added: 0006158 | |
2016-12-16 18:54 | vanguard | Note Added: 0006163 | |
2016-12-16 19:00 | muts | Assigned To | => muts |
2016-12-16 19:00 | muts | Status | new => closed |
2016-12-16 19:00 | muts | Resolution | open => unable to reproduce |
2016-12-16 19:00 | muts | Note Added: 0006164 | |
2016-12-16 19:19 | vanguard | Status | closed => feedback |
2016-12-16 19:19 | vanguard | Resolution | unable to reproduce => reopened |
2016-12-16 19:19 | vanguard | Note Added: 0006167 | |
2016-12-16 20:10 | muts | Note Added: 0006168 | |
2016-12-16 20:10 | muts | Note Edited: 0006168 | |
2016-12-18 10:46 | emil4o1 | Note Added: 0006170 | |
2016-12-18 11:26 | vanguard | Note Added: 0006171 | |
2016-12-18 11:26 | vanguard | Status | feedback => assigned |
2016-12-18 20:51 | emil4o1 | Note Added: 0006174 | |
2016-12-19 08:49 | vanguard | Note Added: 0006176 | |
2016-12-19 09:32 | qwik | Note Added: 0006177 | |
2016-12-19 10:14 | vanguard | Note Added: 0006178 | |
2016-12-19 10:28 | rhertzog | Assigned To | muts => rhertzog |
2016-12-19 10:29 | rhertzog | Note Added: 0006179 | |
2017-01-11 21:28 | vanguard | Note Added: 0006236 | |
2017-01-12 18:16 | rhertzog | Note Added: 0006244 | |
2017-01-14 14:59 | rhertzog | Status | assigned => resolved |
2017-01-14 14:59 | rhertzog | Resolution | reopened => fixed |
2017-01-14 14:59 | rhertzog | Note Added: 0006248 | |
2023-10-10 12:27 | vanguard | Status | resolved => closed |