Bug#549337: upgrade-from-grub-legacy, had to fsck in order to boot

[Felix Zielcke]

Am Freitag, den 02.10.2009, 17:38 +0200 schrieb 01:
> It asked me to fsck my /dev/sda6 partition.
> 
> 
> I entered my admin password, then fscked it.
> 
> I reboot, then same problem for other partitions.
> I
> did something which I feared could have caused troubles: I started
> fdisk, it detected a problem with some flag set to 000x0 (or something
> like that on /dev/sda5 IIRC), it just asked to rewrite the partition table,
> which I did.
> 
> Then I fscked other partitions (/dev/sda6 and /dev/sda8), then I rebooted, and it fortunately went fine !
> 

Do you remember about what fsck complained?
Was it about the superblock time?

The partition table itself shouldn't ever be modified by grub-setup.

Am Dienstag, den 06.10.2009, 16:44 +0200 schrieb Moritz Möller:
> Same here - it says superblock is in the future - by exactly 2 hours. As we're GMT+2 here, it seems to be a timezone related bug.

I had that a few times too.
Maybe it happens when the journal needs to be recovered on the root
filesystem.

I can't see why our tools can cause this.
The normal system file functions/tools are used to create /boot/grub and
grub-setup only writes directly to MBR or bootsector.
But nothing more.
As long as you don't use XFS which stores it's superblock in the
bootsector, no filesystem metadata should get modified.

Maybe some bug in the umount code.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer