GNU GRUB - Bugs: bug #54739, "alloc magic is broken"...
You are not allowed to post comments on this tracker with your current authentication level.
bug #54739: "alloc magic is broken" on NVME SSD
Submitter: | Magnus Lucchese <maglu> | ||
Submitted: | Thu 27 Sep 2018 12:50:31 AM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Attached Files
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-09-27 | maglu | Attached File | - | ![]() |
Added grub_error_report.txt, #45104 |
I have a server with multiple NVME SSDs, I noticed that after some tests on these SSDs I got the error below when rebooting (the address change on each run)
alloc magic is broken at 0x34e79f00: ffffffffffffffff
(see full log attached)
The SSD that cause the fail is not the one were GRUB/Linux are installed, when I remove it the system boots correctly.
Some things that I found during debug
My Suspicions
I think that when GRUB calculate the maximum size it can read it is not considering metadata interleaved. The reads that extrapolate the maximum size overflow by the amount of metadata, besides that, it seems that it is not handling the error received from the SSD.
Versions Tested
2.02~beta2-36ubuntu3.18
2.02~beta3-4ubuntu7