| 1 | | I tested this again on my machine (Intel SSDNow) on a partition with only data and it apparenly erased the whole disk, or at least the boot sector and part of the system partition (then I got a KDL before I could capture any logs). |
| | 1 | I tested this again on my machine (Intel SSDSC2CT180A4). Soon after running fstrim on a test partition which resides on the same drive as my boot one, I hit a KDL in get_next_team_info. After a reboot using the reboot command, my SSD wouldn't be visible in the BIOS, nor in DriveSetup after I booted from an USB disk. |
| | 2 | |
| | 3 | I did a cold reboot, and after that the SSD is back and no data was erased, at least. |
| | 4 | |
| | 5 | A possible interpretation is that the commands we sent to the SSD managed to somehow confuse the firmware enough that it didn't reply to anything after that. |
