07.01.2016 00:49, Jan Engelhardt пишет:
On Wednesday 2016-01-06 21:56, Frank Kunz wrote:
When the problem can be fixed by reinstall the bootloader only it looks a bit that the fstrim command is not aware of the bootloader installation location and therefore it is getting trimmed. My setup has the bootloader installed in the root partition.
Of course - that makes total sense. The filesystem basically has no idea what you are doing with unreferenced sectors outside its purview.
btrfs explicitly reserves space for bootloader; if btrfs then "trims" this space, it is a serious bug in btrfs. I actually expect any filesystem to trim only space it has allocated and knows about.
Which is probably why running fstrim on a volume with a hidden volume (akin to what truecrypt did) would also be a bad idea.
I guess the extra /boot partition (for old systems) and /boot/efi saved me from observing it so far, since I hardly see a reason to run trim there :p
I'm still not sure what happened here (and as I understand original state is no more available). "Non-System disc or disk error" is /probably/ output by BIOS; and as far as I understand the only thing BIOS can check is 0xAA55 signature; but this is not changed by reinstalling GRUB (GRUB only rewrites code part in MBR). It may be possible that it is output by INT 18H (some Microsoft MBRs return to it if no bootable partition was found), but then again, installation of GRUB does not change it - unless GRUB location was changed from partition to MBR. So there is unfortunately simply not enough information to make any guess what happened. Before "fixing" it was really needed to collect as much information as possible :( If it is possible to reproduce it I would really love to see - information about GRUB configuration - original MBR and VBR before fstrim - MBR and VBR after fstrim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org