I tried yesterday to install 3.19 (also tried 3.18) onto an SSD in my X5040 as a new install and had massive problems getting the installer to recognise the SSD. If I attached other SSDs (also tried an old spinning drive), it saw them just fine but they were disks I didn't want to overwrite. The disk in question is a Kingspec 1TB SATA. Way bigger than needed, but it was spare.

Eventually I managed to get it installed by attaching the disk using a SATA USB adapter. At the end of the install (I think!) it did hang however and on reboot there was a message from SFS stating there was an outstanding transaction (could have been more than one, I forget) and after I clicked OK for it to apply those transaction(s) everything appears to work.

The partitioning tool HDConfig also had big problems doing anything meaningful to this disk. Even crashing a few times. The disk is actually fairly new. Bought some time last year I think.

Of course, I can't rely on this disk so I will find or buy another.

At a guess (and it is a wild guess) there is something about the controller or firmware in the disk that MorphOS code is not happy about. Should I report this to anyone for some sort of debugging? Is anyone from the MOS team interested? Or do I just move on when I've found another drive? I guess it's not unreasonable to assume that it could also be the X5040 or its firmware that isn't happy with the drive. Only thought of that as I was typing this. I'll see how AOS is with it when I have my RX GPU back in.

.