During boot, after grub selection screen, it appears "error: sparse file not allowed - Aborted. Press any key to exit."

Bug #2065476 reported by vimo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

After updating Xubuntu 23.10 to version 24.04, during boot, after selecting the Xubuntu version from the Grub screen, I get the error:

"error: sparse file not allowed
452: out of range pointer: 0x54b42620
Aborted. Press any key to exit".

Searching online it seems that this problem is linked to btrfs file systems, but I only have Ext4 file systems.

Some online guides suggest editing the /etc/default/grub file by placing entries
GRUB_SAVEDEFAULT=false
GRUB_DEFAULT=0

and then run "update-grub", but this solution didn't work.

When the error appears, pressing a key will boot the system normally.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.16
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Sat May 11 11:42:18 2024
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2015-03-14T11:03:48.280895
mtime.conffile..etc.update-manager.release-upgrades: 2024-05-08T16:33:52.778333

Revision history for this message
vimo (vimot2) wrote :
description: updated
vimo (vimot2)
summary: During boot, after grub selection screen, it appears "error: sparse file
- not allowed"
+ not allowed - Aborted. Press any key to exit."
vimo (vimot2)
affects: ubuntu-release-upgrader (Ubuntu) → ubuntu
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.