Am 06.01.2016 um 21:08 schrieb Cristian Rodríguez:
I have the same problem with a oldish samsung SSD. it is not that the disk is wiped (at least in my case) but grub2 installation gets corrupted. reinstalling grub2 from a rescue system "fixes" the problem.
That revived also my machine, thanks for the hint. I observed that behavior on both discs I have: ata1.00: ATA-10: Crucial_CT250MX200SSD1, MU03, max UDMA/133 scsi 0:0:0:0: Direct-Access ATA Crucial_CT250MX2 MU03 PQ: 0 ANSI: 5 ata10.00: ATA-9: Samsung SSD 840 EVO 1TB, EXT0DB6Q, max UDMA/133 scsi 9:0:0:0: Direct-Access ATA Samsung SSD 840 DB6Q PQ: 0 ANSI: 5 Not sure if this problem is related to the discs (both seem to have the same problem, maybe they have the same controller inside) or to the software. 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. I will do some experiment when it is installed in the MBR. Let's see what happens then. Br, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org