Code: Select all
You mean that you will only apply power to the SATA to USB adaptor during boot and then remove it once the RPi has booted?
the previous one I had was working without any external PSU. this one too works without too, but not to boot the ssdThe powered adaptor cable's internal circuitry needs to get powered from the adaptor's PSU (5v? 12v?). It seems not to get its power from the bus side (RPi side).
That might be enough for a Pi3B by itself, but it's not enough with power hungry USB devices, and it may be the reason you are having trouble with USB boot (and the reason you need to power the SATA adapter).
Yes, that is correct. If you don't mind the extra plugs and wires.
Has anything about the configuration changed since then?
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).still no luck. This morning I've booted the raspi with the sd and then mounted the boot partition of the ssd and changed the config.txt by adding boot_delay=5, but after reboot (and removing the sd card) nothing happens. Black screen.
/dev/sda7 ?I changed to
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/sda7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
but still no luck
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.
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.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).
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 scratchIs 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).
yup this that is the "culprit"!
How was that image installed (and was it the latest image)?
It's a combination of the USB adapter, the SSD (or HDD), and the firmware on both. Typically the USB adapter is the fail point, but that may not always be the case, and the small, simple boot-loader on the Pi computers may not handle all combinations correctly. I have one adapter that doesn't like my Samsung SSD, but works fine with other brand SSD, while the Samsung SSD works with a different adapter. ¯\_(ツ)_/¯After reading many forums and discussions I had the idea that usually the biggest problem is not the SSD but that SATA controller.