stf Posted February 7, 2020 Posted February 7, 2020 i have a RK3399 and a samsung-860-pro-512gb when i boot with this ssd connected using this official cable (which was recommended for this model by the orange pi manufacturer), i get this in dmesg: sd 0:0:0:0: [sda] Attached SCSI removable disk sd 0:0:0:0: Attached scsi generic sg0 type 0 but when i do `fdisk /dev/sda` i get `fdisk: cannot open /dev/sda: No medium found` when i put this ssd in my laptop, it is working correctly. i also soldered an alternive sata cable where the 12V power was connected instead of the 5V, don't remember exactly how, but that didn't work either.
TRS-80 Posted February 7, 2020 Posted February 7, 2020 @stf, Where you originally posted this was in a discussion whether or not to even bring the board in question up, which is not a support threat. Since your board is still Unsupported for now, I have moved your post to it's own topic in the P2P sub-forum.
stf Posted February 8, 2020 Author Posted February 8, 2020 thanks, the reason why i posted in that thread, was that there was pictures of someone using an ssd on the sata port and apparently it was working. but yeah, otherwise it was off-topic there.
stf Posted February 9, 2020 Author Posted February 9, 2020 @Igor highlighting you since you had a picture of a working setup in and you mention: Quote SATA port is operating normally (when detected): Expand could it be that it is not detected in my case correctly? is it possible that maybe the kernel doesn't load a kernel module for the drive? since the drive works in my laptop, would it make sense to try another ssd with opi rk3399, i'm not sure. also in case anyone wonders, this opi is not underpowered, i'm feeding it with a 10A chieftec powersupply. thanks a lot for any insights.
Igor Posted February 9, 2020 Posted February 9, 2020 Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed.
stf Posted February 10, 2020 Author Posted February 10, 2020 thanks, didn't know about this tool. here is its output: https://www.ctrlc.hu/~stef/armbian-hardware-monitor.log (i guess it attempted to upload it to ix.io, but somehow it failed, so i uploaded it to my server instead)
Igor Posted February 11, 2020 Posted February 11, 2020 You are using one of the first builds which could be the problem. But SATA bridge is up: Bus 004 Device 002: ID 174c:1153 ASMedia Technology Inc. ASM2115 SATA 6Gb/s bridge which means that probably you have troubles with powering the drive, cable is bad, or: On 2/7/2020 at 7:16 PM, stf said: i also soldered an alternive sata cable where the 12V power was connected instead of the 5V Expand Perhaps you burn your drive. Try another one and/or try images with kernel 5.4.y
stf Posted February 11, 2020 Author Posted February 11, 2020 On 2/11/2020 at 7:04 AM, Igor said: You are using one of the first builds which could be the problem. But SATA bridge is up: Expand i guess this explains why i have a /dev/sda but no medium behind it? 3 hours ago, Igor said: Bus 004 Device 002: ID 174c:1153 ASMedia Technology Inc. ASM2115 SATA 6Gb/s bridge Expand how can i upgrade a build? i was updating using apt update/upgrade. Quote which means that probably you have troubles with powering the drive, cable is bad, or: Perhaps you burn your drive. Try another one and/or try images with kernel 5.4.y Expand nah, i actually built a sata cable where the 12V was fed to the correct pins on the sata power connector. that drive never was in danger and is still working in other devices.
Igor Posted February 11, 2020 Posted February 11, 2020 On 2/11/2020 at 10:48 AM, stf said: how can i upgrade a build? i was updating using apt update/upgrade. Expand Upgrade from preview images might work well ... Once you have updated boot loader on eMMC, you can boot Linux from SD card without a problem.
stf Posted February 11, 2020 Author Posted February 11, 2020 strange, when doing armbian-config, i'm offered the 3 kernels below: linux-image-rk3399=5.98 4.4.192-rk3399 linux-image-rk3399=5.95 4.4.190-rk3399 linux-image-rk3399=5.90 4.4.179-rk3399 according to 'uname -a' i am already on on 4.4.192-rk339, but i choose that anyway since it has the highest version number. after reboot /dev/sda is there but "no medium found" when doing fdisk on it. i did another armbianmonitor log: http://ix.io/2boO
stf Posted February 11, 2020 Author Posted February 11, 2020 i'm a dork, i actually upgraded and i do have 19.11.3 installed now, the kernel is the same though. but as said the disk still shows the same problems: Quote /dev/sda is there but "no medium found" when doing fdisk on it. Expand
stf Posted April 3, 2020 Author Posted April 3, 2020 bumping this question, since i still have no solution. does anyone have success with connecting an ssd over the sata port and is willing to compare our setups, maybe figuring out the difference explains my problems. thanks
Igor Posted April 3, 2020 Posted April 3, 2020 On 4/3/2020 at 2:29 PM, stf said: bumping this question Expand I have issued two private warnings today and block two people for a day that did the same as you did. Try to find another way to keep this alive https://forum.armbian.com/terms On 4/3/2020 at 2:29 PM, stf said: since i still have no solution. Expand and remember to check support terms: https://github.com/armbian/build#support
stf Posted April 5, 2020 Author Posted April 5, 2020 oops. sorry, i wasn't aware. will not happen again.
Recommended Posts