Git master installer disk-image has GPT PMBR size mismatch

  • Done
  • quality assurance status badge
Details
3 participants
  • Brice Waegeneire
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
pelzflorian (Florian Pelz)
Severity
serious
Merged with
P
P
pelzflorian (Florian Pelz) wrote on 4 Apr 2019 07:33
(address . bug-guix@gnu.org)
20190404053317.25rr6jxauazyuztw@pelzflorian.localdomain
Since commit 45c0d1d790f01ebc020fc4b2787a6abcdaa3f383 all install ISOs
created with

guix system disk-image --file-system-type=iso9660 gnu/system/install.scm

cannot boot for me, see



fdisk reports this:

florian@florianmacbook ~ [env]$ fdisk g1.iso # commit 391e0d65d7129d53c025963d2758724e75626eb4

Welcome to fdisk (util-linux 2.32.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): q

florian@florianmacbook ~ [env]$ fdisk g2.iso # commit 45c0d1d790f01ebc020fc4b2787a6abcdaa3f383

Welcome to fdisk (util-linux 2.32.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

GPT PMBR size mismatch (3230583 != 3200895) will be corrected by write.

Command (m for help): q
P
P
pelzflorian (Florian Pelz) wrote on 4 Apr 2019 10:51
(address . 35136@debbugs.gnu.org)
20190404085135.5yvowbpy7ilx4sea@pelzflorian.localdomain
On Thu, Apr 04, 2019 at 07:33:17AM +0200, pelzflorian (Florian Pelz) wrote:
Toggle quote (3 lines)
> guix system disk-image --file-system-type=iso9660 gnu/system/install.scm
>

This only happens when specifying --file-system-type=iso9660.
L
L
Ludovic Courtès wrote on 4 Apr 2019 13:25
control message for bug #35136
(address . control@debbugs.gnu.org)
87wokarozq.fsf@gnu.org
severity 35136 important
P
P
pelzflorian (Florian Pelz) wrote on 5 Apr 2019 07:57
Re: bug#35136: Git master installer disk-image has GPT PMBR size mismatch
(address . 35136@debbugs.gnu.org)
20190405055706.jpk6vxc6ad32pqxn@pelzflorian.localdomain
I would like to log the commandline with which parted is executed in
initialize-partition-table in gnu/build/vm.scm, but I do not know
where all the output is going. Apparently it is nowhere in the logs.
P
P
pelzflorian (Florian Pelz) wrote on 6 Apr 2019 19:29
(address . 35136@debbugs.gnu.org)
20190406172942.m3bcdhr226cow7ep@pelzflorian.localdomain
On Fri, Apr 05, 2019 at 07:57:06AM +0200, pelzflorian (Florian Pelz) wrote:
Toggle quote (7 lines)
> I would like to log the commandline with which parted is executed in
> initialize-partition-table in gnu/build/vm.scm, but I do not know
> where all the output is going. Apparently it is nowhere in the logs.
>
>
>

I was wrong; grub-mkrescue in gnu/build/vm.scm creates the ISO9660
partition table, not parted. It appears I can get at its commandline
by reconfiguring with a modified grub package that raises an error
containing the commandline. I will try later.
P
P
L
L
Ludovic Courtès wrote on 14 Apr 2019 17:02
control message for bug #35136
(address . control@debbugs.gnu.org)
875zrgljdy.fsf@gnu.org
severity 35136 serious
L
L
Ludovic Courtès wrote on 14 Apr 2019 17:03
control message for bug #33639
(address . control@debbugs.gnu.org)
874l70ljdn.fsf@gnu.org
merge 33639 35136
B
B
Brice Waegeneire wrote on 11 Dec 2019 18:19
(no subject)
(address . control@debbugs.gnu.org)
f62a2457e39b00adc81ae457baa0a950@waegenei.re
unarchive 33639
?