Re: OT: Is there any size limit for ISO's?
Hi all, so, the problem is 90 percent solved. It was indeed the problem with the graphic mode, just as Stefan's crytal ball told. Orinially the kernel driver should automatically detect, which mode is possible and then switch to it. But it doesn't. So the screen went blank. The fix was easy: I added the parm "vga=791" to the kernel and the screen went to the required solution. Everything is working now, when I boot the stick on another computer. Thus I can say: generally it is working! However: When I boot this stick on the same computer, where I built the iso, it hangs at boot. I suppose, this is related to, that I am using encrypted filesystems on the harddrive. It appears (although the ISO is working completely in RAM), it wants the encryption password. This is strange. In the past I gor a solution for it: Before building and creating the ISO, I moved /etc/crypttab away and then created the ISO. This was working well in the past. You should know, that I have written a little script, which prepares the system (by deleting history and other unnecessary things or moving some things away), then build and at last move everything back. This is working like a charm. Oh, and maybe the issues I described might appear with a newer kernel, because KALI linux was running 6.1 but now it is running 6.5. However, this might not matter, just want to mention it, if someone else is interested and fell into the same issue as me. As I said: the problem is 90 percent solved, now I am just try to solve the (very!) little thing with the password issue. Stay tuned, I'll be back. Best Hans
Re: OT: Is there any size limit for ISO's?
Am Montag, 22. Januar 2024, 23:35:23 CET schrieb Stefan Monnier: Hi Stefan, I think your crystal ball is clever. The same idea came in my mind, and I believe, the screen goes blank, when the graphics card wants to switch into vesa mode. Please note, that I start the livefile on the sam computer, where I have built it from. So of course, all graphic drivers are existent. The next days I will try some kernel settings, as far as I rembeer, I can force some vga modes at boot (something I used in the old times like "vga=691 or so, can't exactly remember). I will inform you! Best Hans > > Last message is, that a new USB device is found, then the screen goes > > blank. I can make some snapshots of a video, by interest. > > My crystal ball blames the video driver (presuming that the DRM module > for your video card is loaded around the same time as that USB device is > found). > > > Stefan
Re: OT: Is there any size limit for ISO's?
On 1/22/24 16:30, Hans wrote: Hi Thomas, Anyways, 32 GB of size should not be a problem. Ok. size does not matter When the stick is booting, first appear the usual text messages, The first message is the boot prompt. Then the usual messages· PCI found and so on. Last message is, that a new USB device is found, then the screen goes blank. I can make some snapshots of a video, by interest. From a C.E.T., probably not needed. If the found usb hub has something plugged in, the port power will be enabled in order to investigate what it might be, and if its usb bus powered, might draw too much, triggering an under voltage protective shutdown, test by externally powering whatever is plugged in, or unplugging it to remove that load. If nothing is/was plugged in, its likely something else unrelated. Can you determine the origin of the last visible messages ? Yes, see above. BIOS/EFI ? The BIOS is without EFI. Boot loader (GRUB or ISOLINUX/SYSLINUX) ? Bootloader is grub, the image is an image from kali linux. The big size comes from a virtualbox image inside for windows 10. (the vmdk is smaller than 4GB, so bootcdwrite got not into problems). Linux ? Yes, KALI Linux, which is Debian based. Debian installation software ? vers close to. Is Virtualbox using the same BIOS type as the real machine ? I mean EFI versus Legacy BIOS aka CSM mode. Yes, it uses legacy bios. Is the USB stick large enough for the image ? Yes, it is. The image is about 32 GB big, the USB-stick is 64GB. Should fit very well. The last ISO working was baout 12GB and fit on a 32GB stick. Can dd read the whole image back from the USB stick ? Yes, it can. I tried also dd with option bs=1, so to install bitwise, just to make clear everything is copied. # Set variable blocks to image file size divided by 2048 blocks=... # Set variable stick to device file address of the USB stick stick=... dd if="$stick" bs=2048 count="$blocks" | md5sum I already tried thzis, too. 1024, 2048 and 4096, and of course 1. If no i/o error is reported by dd, compute the MD5 sum of the image file and compare both. Already did, comarision was ok. It's not impossible. Especially if the stick hardware has problems. But depending on the origin of the last visible message there is also a chance that boot loader or Linux derail because of buggy file content in the elsewise healthy ISO. This stick is new. However, the stck I used before, was another distributor. I changed the stick, because the former stick I used before, died after about 10th or 12th installing of the iso. Have a nice day :) Same to you! Best Hans Thomas . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: OT: Is there any size limit for ISO's?
> Last message is, that a new USB device is found, then the screen goes > blank. I can make some snapshots of a video, by interest. My crystal ball blames the video driver (presuming that the DRM module for your video card is loaded around the same time as that USB device is found). Stefan
Re: OT: Is there any size limit for ISO's?
Hi Thomas, > Anyways, 32 GB of size should not be a problem. Ok. size does not matter > > > When the stick is booting, first appear the usual text messages, > The first message is the boot prompt. Then the usual messages· PCI found and so on. Last message is, that a new USB device is found, then the screen goes blank. I can make some snapshots of a video, by interest. > Can you determine the origin of the last visible messages ? Yes, see above. > BIOS/EFI ? The BIOS is without EFI. > Boot loader (GRUB or ISOLINUX/SYSLINUX) ? Bootloader is grub, the image is an image from kali linux. The big size comes from a virtualbox image inside for windows 10. (the vmdk is smaller than 4GB, so bootcdwrite got not into problems). > Linux ? Yes, KALI Linux, which is Debian based. > Debian installation software ? vers close to. > > Is Virtualbox using the same BIOS type as the real machine ? > I mean EFI versus Legacy BIOS aka CSM mode. > Yes, it uses legacy bios. > > Is the USB stick large enough for the image ? Yes, it is. The image is about 32 GB big, the USB-stick is 64GB. Should fit very well. The last ISO working was baout 12GB and fit on a 32GB stick. > > Can dd read the whole image back from the USB stick ? > Yes, it can. I tried also dd with option bs=1, so to install bitwise, just to make clear everything is copied. > # Set variable blocks to image file size divided by 2048 > blocks=... > # Set variable stick to device file address of the USB stick > stick=... > > dd if="$stick" bs=2048 count="$blocks" | md5sum I already tried thzis, too. 1024, 2048 and 4096, and of course 1. > > If no i/o error is reported by dd, compute the MD5 sum of the image file > and compare both. > Already did, comarision was ok. > It's not impossible. Especially if the stick hardware has problems. > But depending on the origin of the last visible message there is also > a chance that boot loader or Linux derail because of buggy file content > in the elsewise healthy ISO. > This stick is new. However, the stck I used before, was another distributor. I changed the stick, because the former stick I used before, died after about 10th or 12th installing of the iso. > > Have a nice day :) > Same to you! Best Hans > Thomas
Re: OT: Is there any size limit for ISO's?
Hi, Hans wrote: > does anyone know, if there is a limit of the size an iso may have? With xorriso: 4 TiB = 4096 GiB. An ISO 9660 filesystem may have 2 exp 32 data blocks. The usual block size is 2 exp 11 = 2048 bytes. That would be 2 exp 43 = 8 TiB in total. But xorriso uses libburn for writing and a poor design decision of about 20 years ago lets it use signed int for block addresses. So only 2 exp 31 blocks = 4 TiB are possible with libburn and xorriso. > Background: I have a selfmade lifefile iso image, which was created by > bootcdwrite. The size of the imagefile is about 32GB. Looks like bootcd uses genisoimage for producing the ISO, (https://tracker.debian.org/media/packages/b/bootcd/control-6.7) Anyways, 32 GB of size should not be a problem. > When the stick is booting, first appear the usual text messages, Can you determine the origin of the last visible messages ? BIOS/EFI ? Boot loader (GRUB or ISOLINUX/SYSLINUX) ? Linux ? Debian installation software ? > but then the screen goes blank and the further boot hangs. > However, when I am booting this file (this iso-image) with Virtualbox, > everything is working well. Is Virtualbox using the same BIOS type as the real machine ? I mean EFI versus Legacy BIOS aka CSM mode. > Note: In earlier times I had a smaller image (about 8 GB), which booted > perfectly. Is the USB stick large enough for the image ? Can dd read the whole image back from the USB stick ? # Set variable blocks to image file size divided by 2048 blocks=... # Set variable stick to device file address of the USB stick stick=... dd if="$stick" bs=2048 count="$blocks" | md5sum If no i/o error is reported by dd, compute the MD5 sum of the image file and compare both. > So I believe, the size of the image is, what matters. But maybe I am wrong. It's not impossible. Especially if the stick hardware has problems. But depending on the origin of the last visible message there is also a chance that boot loader or Linux derail because of buggy file content in the elsewise healthy ISO. Have a nice day :) Thomas
Re: OT: Is there any size limit for ISO's?
Am 22.01.2024 um 21:07:55 Uhr schrieb Hans: > I copied the file using dd to an usb stick, but it does crash at boot. Is the USB stick equal or bigger than the ISO? If not, the writing process will just stop at the end of the device and the stick data will be corrupted because they are incomplete.
OT: Is there any size limit for ISO's?
Hi folks, does anyone know, if there is a limit of the size an iso may have? Background: I have a selfmade lifefile iso image, which was created by bootcdwrite. The size of the imagefile is about 32GB. I copied the file using dd to an usb stick, but it does crash at boot. When the stick is booting, first appear the usual text messages, but then the screen goes blank and the further boot hangs. However, when I am booting this file (this iso-image) with Virtualbox, everything is working well. As it is a livefile and goes blank, I can not see, why it hangs. Note: In earlier times I had a smaller image (about 8 GB), which booted perfectly. So I believe, the size of the image is, what matters. But maybe I am wrong. Be happy for all hints. Best regards Hans
