+1 ;) Seriously, there is no reason why, when flushing disk cache through reboot -f, makes grub being corrupted afterwards.
BTW, using the install CD when I do the recovery procedure i'm still using reboot -f. Mount options perhaps? Although, nothing special in here... # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda3 during installation UUID=815b5e09-bc03-402f-8272-24fc2d080dbd / xfs defaults 0 1 # /data was on /dev/sda7 during installation UUID=58616A6210DDE281 /data ntfs defaults,umask=007,gid=46 0 0 # /home was on /dev/sda6 during installation UUID=8361e288-8409-451a-a4a0-f27c44e718cf /home xfs defaults 0 2 # /windows was on /dev/sda2 during installation UUID=BC6A79C76A797EC8 /windows ntfs defaults,umask=007,gid=46 0 0 # swap was on /dev/sda5 during installation UUID=e37a449e-7a70-42a5-b179-91306ccbe1d7 none swap sw 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1051280 Title: reboot into grub prompt after system update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1051280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
