mxsnapshot isohybrid: Warning: more than 1024 cylinders: 13663 [Solved]

[Vanitarium]

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 info: latte-dock wm: kwin_x11 dm: SDDM Distro: MX-19.4_kde_x64 patito feo March 31  2021 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TUXEDO product: TUXEDO Aura 15 Gen1 v: N/A serial: <filter> Chassis: Notebook type: 10 
           serial: <filter> 
           Mobo: TUXEDO s model: AURA1501 serial: <filter> UEFI: INSYDE v: 1.07.03RTR2 date: 11/13/2020 
Battery:   ID-1: BAT0 charge: 38.0 Wh condition: 46.3/48.3 Wh (96%) volts: 15.5/15.2 model: Notebook BAT type: Li-ion 
           serial: <filter> status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP arch: Zen family: 17 (23) 
           model-id: 60 (96) stepping: 1 microcode: 8600106 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31942 
           Speed: 1382 MHz min/max: 1400/2000 MHz boost: enabled Core speeds (MHz): 1: 1382 2: 1433 3: 1446 4: 1453 5: 1707 
           6: 1530 7: 1837 8: 1416 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: CLEVO/KAPOK driver: amdgpu v: kernel bus ID: 05:00.0 
           chip ID: 1002:1636 
           Display: x11 server: X.Org 1.20.10 driver: amdgpu compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.0-5mx-amd64 LLVM 11.0.1) v: 4.6 Mesa 20.3.4 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor vendor: CLEVO/KAPOK 
           driver: N/A bus ID: 05:00.5 chip ID: 1022:15e2 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel 
           bus ID: 05:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel 
           port: 2000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 bus ID: 03:00.0 chip ID: 8086:2723 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 599.94 GiB used: 72.34 GiB (12.1%) 
           ID-1: /dev/mmcblk0 model: ED4QT size: 119.25 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
           scheme: GPT 
           ID-2: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 500GB size: 465.76 GiB block size: physical: 512 B 
           logical: 512 B speed: 63.2 Gb/s lanes: 4 serial: <filter> rev: 1B2QGXA7 scheme: GPT 
           ID-3: /dev/sda type: USB vendor: Verbatim model: STORE N GO size: 14.92 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: 463.48 GiB size: 455.21 GiB (98.21%) used: 58.89 GiB (12.9%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 2.00 GiB used: 3.5 MiB (0.2%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 39.1 C mobo: N/A gpu: amdgpu temp: 37 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirrors.ukfast.co.uk/sites/MX_antiX_packages/mx/repo/ buster main non-free
           2: deb https://mirrors.ukfast.co.uk/sites/MX_antiX_packages/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 266 Uptime: 34m Memory: 15.57 GiB used: 1.94 GiB (12.5%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

Hiya,
I have created an USB from a snapshot for my whole system. When MXsnapshot completes it gives me a warning as shown below.

Code: Select all

isohybrid: Warning: more than 1024 cylinders: 13663
isohybrid: Not all BIOSes will be able to boot this device

... and true enough my BIOS does not boot it but I have to use 'boot from file' option in my Insyde BIOS ...
I have researched in the forum but no results came up with non-booting snapshots! I am sorry if this is a well known issue with MX snapshots and it due to an error of oversight.

[dolphin_oracle]

the cylinders issue is an old warning from the days when PC's booted CDs and DVDs. typically the insyde bios shouldn't have an issue with it. Likely its actually an issue with boot device order. or maybe the method used to make the live-usb (our live-usb-maker tool would be the preferred and most reliable option).

[Huckleberry Finn]

@dolphin_oracle @Adrian Just on this opportunity: Is it possible to remove that warning in next versions ? ... Or at least replace with something softer for the daily user, i.e. " ... finished successfully, just some very old computers may not be able to boot this iso for it's ... in size (blah blah) ... "

[Vanitarium]

Thanks for replies and help.
I have actually used MX live-usb-maker but the BIOS tells me Booting from LINPUS failed.
So, any thoughts about that?
I shall try and use Etcher on my other machine and see boots.
Will report back here.

[dolphin_oracle]

Thanks for replies and help.
I have actually used MX live-usb-maker but the BIOS tells me Booting from LINPUS failed.
So, any thoughts about that?
I shall try and use Etcher on my other machine and see boots.
Will report back here.

ooo I've got a old lenovo that does that LINPUS message. I think it has something to do with some kind of security keys in the UEFI setup. I got around it on the old lenovo by using legacy booting instead of UEFI, but I'm not sure that's an option with the insyde UEFI setup.

the grub/uefi gurus around here may be able to help.

[Adrian]

@dolphin_oracle @Adrian Just on this opportunity: Is it possible to remove that warning in next versions ? ... Or at least replace with something softer for the daily user, i.e. " ... finished successfully, just some very old computers may not be able to boot this iso for it's ... in size (blah blah) ... "

That message is part of the mkisofs (or isohybrid) program, it's not something we control.

[fehlix]

Thanks for replies and help.
I have actually used MX live-usb-maker but the BIOS tells me Booting from LINPUS failed.
So, any thoughts about that?
I shall try and use Etcher on my other machine and see boots.
Will report back here.

I would also try to click on GPT when you create the LiveUSB with Live-USB-maker. The one you created was done using MBR indicated with the Quick-System-Info.
The Linpus thing is probably somewhere hardcoded with the UEFI-firmware.

[Vanitarium]

Great this is now solved!
I had not seen the Advanced>>EFI GPT tickbox and I have now made a new USB live and it worked in spite of that obscure warning.

Thank you all you gurus!!!

[JayM]

If this is solved to your satisfaction, could you please mark the topic as solved by clicking the button with a checkmark icon next to the post containing the solution? Instructions are here. This will make it easier for others when they search the forum looking for a solution to the same problem. Thanks.

[Vanitarium]

Sorry I had checked wrong post.....