HawaiianPi wrote: ↑Wed Nov 14, 2018 7:47 pm
Has anything about the configuration changed since then?
Different power supply?
Different USB cables?
Any devices or accessories connected or removed?
The only big think I changed is that I cloned the img of another raspberry (with noobs) on this ssd and then it didn't boot anymore. I copied the working sd with Win32DiskImager and then copied back to ssd both with the same tool and with Etcher, but without luck.
Changing config.txt on a non booting device won't fix anything (the config file can't be read if the drive won't boot).
MM interesting point, it was not clear to me. I supposed that being able to access the file on the disk and being able to boot from the disk are 2 different things.
Is this a NOOBS install?
While NOOBS can work with USB boot, it's not recommended (NOOBS doesn't update with Raspbian, so it gets outdated). Try it with a Raspbian image written directly to the USB drive with Etcher (backup important data first).
Also, use UUID or PART-UUID and not /dev/sda_ to identify devices mounted at boot time (/dev/sd identifiers can change from boot to boot).
Yes this is a noobs install, it was the first distro I found on the dev kit and I continued using it. Now probably too many things installed and configured to restart from scratch
setting the PART-UUID was one of the test I had in mind and that I forgot :/
I tried installing a defatul raspbian image to the SSD, but still no luck
Just today I sent back to Amazon my SanDisk SSD and I would change it for a
Crucial MX500 CT250MX500SSD1(Z)
Do you think the latter could work better? could the SSD have an impact on my issue? any experience with SSD working more reliably? Afte reading many forums and discussions I had the idea that usually the biggest problem is not the SSD but that SATA controller.
I've to wait the new SSD before doing other tests, but the only one not yet done is the PART-UUID