On Tue, Dec 10, 2013 at 1:09 PM, Colin Watson <cjwat...@debian.org> wrote:
> On Tue, Dec 10, 2013 at 12:45:41PM -0600, Michael Lustfield wrote: > > On Tue, Nov 12, 2013 at 8:47 PM, Colin Watson <cjwat...@debian.org> > wrote: > > > Note that systems that were installed with modern versions of the > Debian > > > installer aren't affected by this bug, since that aligns the first > > > partition to a 1MB boundary by default; this is actually a good idea > for > > > performance reasons too so I recommend you look into converting your > > > systems to that if at all possible since this isn't an easy bug to fix > > > in any other way. > > > > How can I convert an installed system to that? This image was created > with > > a recent (at the time) Debian installer. Right now, I have to use a super > > grub2 boot disk to boot the servers. > > You have to use something like gparted from a live CD to move the > partitions around. This is inherently risky and requires taking backups > first, unfortunately. > > > > I agree this is a real problem, though. Could I please see the exact > > > size in bytes of /boot/grub/i386-pc/core.img so that I can make sure > I'm > > > comparing the right thing? I don't get quite the same figures as you > in > > > my local tests, and for this kind of thing every byte matters. > > > > # du /boot/grub/i386-pc/core.img > > 34 /boot/grub/i386-pc/core.img > > That's kilobytes, not bytes. Try this instead: > > ls -l /boot/grub/i386-pc/core.img Sorry, I forgot to reply to the bug too. It's 33106 bytes.
