jv_5 Posted June 17, 2023 Share Posted June 17, 2023 I was able to flash armbian bookworm cli to the ssd using balena etcher but when I boot the OPI5 from the sdcard and run lsbk it can only see the sdcard any ideas ... 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted June 18, 2023 Share Posted June 18, 2023 How did you flash then? 0 Quote Link to comment Share on other sites More sharing options...
ArmBoy1988 Posted June 18, 2023 Share Posted June 18, 2023 I've seen cases where some ssd just don't work or aren't recognized. With my nanopc-t4, there was a thread just to identify which worked and which didn't. I'm not sure why some work and some don't. FYI, I have a Samsung 980 1 tb and it's working fine on my opi5. Just thought I'd put it out there. If anyone else had the same ssd as you and it worked, that would give some more info. If you can try another ssd from a different manufacturer that could provide more info. Even if it's smaller, just to see if others will work with your board. Also, do any messages for the ssd show up in dmesg? Maybe boot from an SD card with the ssd plugged in. See if it shows up or there are any messages in dmesg related to it. 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 19, 2023 Author Share Posted June 19, 2023 @Werner I flashed it using a different computer running windows 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 19, 2023 Author Share Posted June 19, 2023 @ArmBoy1988 great suggestions, thanks here is the failed item I found in dmesg, I also see at boot time a line complaining about nvmf-autoconnect but I cannot find it in dmesg @orangepi5:~$ dmesg |grep -i failed [ 4.357458] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@00000000': base 0x0000000000000000, size 0 MiB [ 4.357476] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@00000000': base 0x0000000000000000, size 0 MiB [ 6.168853] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up vdpu-supply property in node /power-management@fd8d8000/power-controller failed [ 6.169119] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up rga30-supply property in node /power-management@fd8d8000/power-controller failed [ 6.169302] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up rga31-supply property in node /power-management@fd8d8000/power-controller failed [ 6.170526] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up venc0-supply property in node /power-management@fd8d8000/power-controller failed [ 6.170682] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up vcodec-supply property in node /power-management@fd8d8000/power-controller failed [ 6.170792] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up venc1-supply property in node /power-management@fd8d8000/power-controller failed [ 6.171067] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up rkvdec0-supply property in node /power-management@fd8d8000/power-controller failed [ 6.171352] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up rkvdec1-supply property in node /power-management@fd8d8000/power-controller failed [ 6.171581] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up vi-supply property in node /power-management@fd8d8000/power-controller failed [ 6.171814] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up isp1-supply property in node /power-management@fd8d8000/power-controller failed [ 6.969557] phy phy-fd5d0000.syscon:usb2-phy@0.0: Looking up phy-supply property in node /syscon@fd5d0000/usb2-phy@0/otg-port failed [ 6.969608] phy phy-fd5d0000.syscon:usb2-phy@0.0: Looking up vbus-supply property in node /syscon@fd5d0000/usb2-phy@0/otg-port failed [ 6.970867] phy phy-fd5d8000.syscon:usb2-phy@8000.1: Looking up phy-supply property in node /syscon@fd5d8000/usb2-phy@8000/host-port failed [ 6.971976] phy phy-fd5dc000.syscon:usb2-phy@c000.2: Looking up phy-supply property in node /syscon@fd5dc000/usb2-phy@c000/host-port failed [ 6.973774] phy phy-fee00000.phy.3: Looking up phy-supply property in node /phy@fee00000 failed [ 6.973906] phy phy-fee20000.phy.4: Looking up phy-supply property in node /phy@fee20000 failed [ 6.974373] phy phy-feda0000.phy.5: Looking up phy-supply property in node /phy@feda0000 failed [ 6.974496] phy phy-fedb0000.phy.6: Looking up phy-supply property in node /phy@fedb0000 failed [ 6.974844] phy phy-fed60000.hdmiphy.7: Looking up phy-supply property in node /hdmiphy@fed60000 failed [ 6.976475] phy phy-fed80000.phy.8: Looking up phy-supply property in node /phy@fed80000/dp-port failed [ 6.976511] phy phy-fed80000.phy.9: Looking up phy-supply property in node /phy@fed80000/u3-port failed [ 6.978145] pwm-backlight backlight: Looking up power-supply property in node /backlight failed [ 6.978398] pwm-backlight backlight_1: Looking up power-supply property in node /backlight_1 failed [ 6.983990] mpp-iep2 fdbb0000.iep: allocate roi buffer failed [ 6.985624] mpp_rkvdec2 fdc38100.rkvdec-core: Looking up vdec-supply property in node /rkvdec-core@fdc38000 failed [ 6.986351] mpp_rkvdec2 fdc48100.rkvdec-core: Looking up vdec-supply property in node /rkvdec-core@fdc48000 failed [ 6.987251] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbd0000 failed [ 6.987270] rkvenc_init:1814: failed to add venc devfreq [ 6.987809] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbe0000 failed [ 6.987823] rkvenc_init:1814: failed to add venc devfreq [ 6.988263] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up av1-supply property in node /power-management@fd8d8000/power-controller failed [ 7.014277] [drm] failed to init overlay plane Cluster0-win1 [ 7.014308] [drm] failed to init overlay plane Cluster1-win1 [ 7.014339] [drm] failed to init overlay plane Cluster2-win1 [ 7.014369] [drm] failed to init overlay plane Cluster3-win1 [ 7.026804] rockchip-drm display-subsystem: failed to parse loader memory [ 7.548678] rk_gmac-dwmac fe1c0000.ethernet: Looking up phy-supply property in node /ethernet@fe1c0000 failed [ 7.882793] Goodix-TS 2-0014: Looking up AVDD28-supply property in node /i2c@feaa0000/touchscreen@14 failed [ 7.883010] Goodix-TS 2-0014: Looking up VDDIO-supply property in node /i2c@feaa0000/touchscreen@14 failed [ 7.976326] Goodix-TS 2-0014: i2c test failed attempt 1: -6 [ 8.002973] Goodix-TS 2-0014: i2c test failed attempt 2: -6 [ 8.078433] Goodix-TS 7-0014: Looking up AVDD28-supply property in node /i2c@fec90000/touchscreen@14 failed [ 8.078504] Goodix-TS 7-0014: Looking up VDDIO-supply property in node /i2c@fec90000/touchscreen@14 failed [ 8.169680] Goodix-TS 7-0014: i2c test failed attempt 1: -6 [ 8.196323] Goodix-TS 7-0014: i2c test failed attempt 2: -6 [ 8.304832] sdhci-dwcmshc fe2e0000.mmc: Looking up vmmc-supply property in node /mmc@fe2e0000 failed [ 8.304886] sdhci-dwcmshc fe2e0000.mmc: Looking up vqmmc-supply property in node /mmc@fe2e0000 failed [ 8.305808] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active. [ 8.325431] optee: probe of firmware:optee failed with error -22 [ 8.334543] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up audio-supply property in node /power-management@fd8d8000/power-controller failed [ 8.408866] [BT_RFKILL]: Failed to get bt_default_wake_host gpio. [ 8.408924] rfkill_bt: probe of wireless-bluetooth failed with error -1 [ 8.465739] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up gpu-supply property in node /power-management@fd8d8000/power-controller failed [ 8.466282] vdd_gpu_s0: Failed to create debugfs directory [ 8.466302] vdd_gpu_s0: Failed to create debugfs directory [ 8.466423] vdd_gpu_s0: Failed to create debugfs directory [ 8.469680] vdd_ddr_s0: Failed to create debugfs directory [ 8.470284] vdd_log_s0: Failed to create debugfs directory [ 8.471885] rockchip-dmc dmc: failed to get vop bandwidth to dmc rate [ 8.471892] rockchip-dmc dmc: failed to get vop pn to msch rl [ 8.498276] rfkill_bt: probe of wireless-bluetooth failed with error -12 [ 8.499822] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up sdmmc-supply property in node /power-management@fd8d8000/power-controller failed [ 8.499931] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up sdio-supply property in node /power-management@fd8d8000/power-controller failed [ 8.500029] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed [ 8.500126] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu-supply property in node /power-management@fd8d8000/power-controller failed [ 8.505771] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up nputop-supply property in node /power-management@fd8d8000/power-controller failed [ 8.505942] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu1-supply property in node /power-management@fd8d8000/power-controller failed [ 8.506084] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu2-supply property in node /power-management@fd8d8000/power-controller failed [ 8.506395] vdd_npu_s0: Failed to create debugfs directory [ 8.507039] vdd_npu_s0: Failed to create debugfs directory [ 8.507846] vdd_npu_s0: Failed to create debugfs directory [ 8.535748] RKNPU fdab0000.npu: failed to find power_model node [ 8.535759] RKNPU fdab0000.npu: RKNPU: failed to initialize power model [ 8.535767] RKNPU fdab0000.npu: RKNPU: failed to get dynamic-coefficient [ 9.859532] rk-pcie fe190000.pcie: failed to initialize host [ 10.426379] (sd-execut[352]: /usr/lib/systemd/system-generators/netplan failed with exit status 1. 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 19, 2023 Author Share Posted June 19, 2023 I found something, I am looking into it, maybe if I can get this service to start it will fix the invisible nvme orangepi5:~$ sudo systemctl status nvmf-autoconnect.service × nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot Loaded: loaded (/lib/systemd/system/nvmf-autoconnect.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sun 2023-06-18 20:43:25 CST; 6min ago Process: 5890 ExecStartPre=/sbin/modprobe nvme-fabrics (code=exited, status=1/FAILURE) CPU: 7ms Jun 18 20:43:25 orangepi5 systemd[1]: Starting nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot... Jun 18 20:43:25 orangepi5 modprobe[5890]: modprobe: FATAL: Module nvme-fabrics not found in directory /lib/modules/5.10.160-rockchip-rk3588 Jun 18 20:43:25 orangepi5 systemd[1]: nvmf-autoconnect.service: Control process exited, code=exited, status=1/FAILURE Jun 18 20:43:25 orangepi5 systemd[1]: nvmf-autoconnect.service: Failed with result 'exit-code'. Jun 18 20:43:25 orangepi5 systemd[1]: Failed to start nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot. 0 Quote Link to comment Share on other sites More sharing options...
Turbine Posted June 19, 2023 Share Posted June 19, 2023 (edited) There's always USB3 if all else fails. I attached an externally powered hub and use a SATA ssd. I get very good throughput of around 300+ MB/s. I gave up on nvme M.2. drives as it was never stable under Armbian opi4 LTS (using pcie adaptor). It failed to boot 95% of the time. Moved to the 5 and tried and it didn't work well either. Edited June 19, 2023 by Turbine 0 Quote Link to comment Share on other sites More sharing options...
ArmBoy1988 Posted June 20, 2023 Share Posted June 20, 2023 @jv_5 There are a lot of power related messages in what you posted. Perhaps it's a power supply issue. What kind of power supply are you using? I'm using a 5V4A dumb power supply. I've read about issues using smart/PD type of power supplies with the OPi5. Can't remember the details. Also, I believe the 4A is crucial, especially as you add/use more features, such as a NVME drive that wasn't there before. This is the one I purchased: https://www.amazon.ca/GeeekPi-Supply-Raspberry-Orange-Adapter/dp/B0BMGJNSVS 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 21, 2023 Author Share Posted June 21, 2023 @Turbine Thanks for your suggestion , that would be plan B 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted June 21, 2023 Share Posted June 21, 2023 The PSU that comes with the OPi5 bundle outputs around 5.3 volts when idle. This seems needed in order to compensate for voltage drop under load. From my own measurements I noticed that the drop is quite severe and goes down to 5 volts under full load. Measured across the board at one of the USB ports. If you have a common PSU that outputs "only" 5 volts then you can do the math for yourself and RKs in general are used to slight overvoltage. 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 21, 2023 Author Share Posted June 21, 2023 @ArmBoy1988 yeah , you were right I was using the power supply that the manufacturer bundles with the OPI 5 luckily I had another power supply laying around from an old RPI, using it fixed the issue Now I am happily wasting a perfect nvme with the OPI Its faster with the m.2 but system load jumped from 2% to 8% idle also temp jumped from 36 celsius to 46 celsius So maybe using a self powered usb hub and a sata ssd is not bad idea after all 0 Quote Link to comment Share on other sites More sharing options...
jv_5 Posted June 21, 2023 Author Share Posted June 21, 2023 Thanks for the info @Werner should I mark this as solved or anything ? Its my first time in this forum 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted June 22, 2023 Share Posted June 22, 2023 No need to do anything 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.