PINE64

Full Version: PCIe failure
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Just received my RockPro64, NAS case, and all the goodies.  I installed the Ubuntu Bionic LXDE image, loaded up great, added ATS, etc.  Everything is great except that the 2 WD Reds are not recognized.  Opening the case back up, I see that the PCIe doesn't have its LED lit up.  I'm trying to decide if this is the img or the hardware.  I have gotten the LED to illuminate a couple times by unplugging the SATA cables, but it doesn't stay on.  Also, during boot, the LED will blink on and off, then stay off.  lspci -v shows nothing, df -h / fdisk -l do not show the HDDs.

I do not have the board that requires removing a resistor.

boot log for pci:

[ 0.505675] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[ 0.505723] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 0.505761] vcc3v3_pcie: supplied by dc_12v
[ 0.505828] vcc3v3_pcie: 3300 mV
[ 0.505988] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[ 1.166830] ehci-pci: EHCI PCI platform driver
[ 2.894277] vcc3v3_pcie: disabling
[ 3.257493] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 3.257501] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 3.260566] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 3.260590] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 3.260679] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/[email protected][0]' - status (0)
[ 3.261231] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 3.261553] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 3.261575] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /[email protected] failed
[ 3.261629] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 3.276048] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 3.276086] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /[email protected] failed
[ 3.276142] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 3.290608] rockchip-pcie f8000000.pcie: invalid power supply
[ 3.350984] PCI host bridge /[email protected] ranges:
[ 3.387121] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 3.394721] pci_bus 0000:00: root bus resource [bus 00-1f]
[ 3.401970] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[ 3.409375] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[ 3.417072] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[ 3.417190] pci 0000:00:00.0: supports D1
[ 3.417196] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[ 3.417676] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.425545] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])
[ 3.425588] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
[ 3.425642] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[ 3.432368] pci 0000:01:00.0: reg 0x10: [io size 0x0008]
[ 3.432397] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[ 3.438957] pci 0000:01:00.0: reg 0x14: [io size 0x0004]
[ 3.438971] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[ 3.445415] pci 0000:01:00.0: reg 0x18: [io size 0x0008]
[ 3.445429] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[ 3.451804] pci 0000:01:00.0: reg 0x1c: [io size 0x0004]
[ 3.451818] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[ 3.458122] pci 0000:01:00.0: reg 0x20: [io size 0x0020]
[ 3.458137] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[ 3.458150] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 3.460470] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 3.460537] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
[ 3.470994] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[ 3.497156] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]
[ 3.504734] pci 0000:01:00.0: BAR 4: no space for [io size 0x0020]
[ 3.510579] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0020]
[ 3.516276] pci 0000:01:00.0: BAR 0: no space for [io size 0x0008]
[ 3.521936] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0008]
[ 3.527605] pci 0000:01:00.0: BAR 2: no space for [io size 0x0008]
[ 3.532503] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0008]
[ 3.537180] pci 0000:01:00.0: BAR 1: no space for [io size 0x0004]
[ 3.541789] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0004]
[ 3.546404] pci 0000:01:00.0: BAR 3: no space for [io size 0x0004]
[ 3.550983] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0004]
[ 3.555226] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 3.559035] pci 0000:00:00.0: bridge window [mem 0xfa000000-0xfa0fffff]
[ 3.563143] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 3.567436] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[ 3.571440] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 3.575103] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[ 3.575213] aer 0000:00:00.0:pcie02: service driver aer loaded
My WD Red 3 Tb drive doesn't work either. Initialized 1 time out of 3 and in the end lost all the data. Power supply 5 A and all boards are original. I tried all versions of OMV and 3 power supplies, including 7 A and 400 watt ATX. There are no problems with the WD Blue 1 Tb drive.

odhinnhrafn Just received my RockPro64, NAS case, and all the goodies.  I installed the Ubuntu Bionic LXDE image, loaded up great, added ATS, etc.  Everything is great except that the 2 WD Reds are not recognized.  Opening the case back up, I see that the PCIe doesn't have its LED lit up.  I'm trying to decide if this is the img or the hardware.  I have gotten the LED to illuminate a couple times by unplugging the SATA cables, but it doesn't stay on.  Also, during boot, the LED will blink on and off, then stay off.  lspci -v shows nothing, df -h / fdisk -l do not show the HDDs.

I do not have the board that requires removing a resistor.

boot log for pci:

[    0.505675] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    0.505723] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.505761] vcc3v3_pcie: supplied by dc_12v
[    0.505828] vcc3v3_pcie: 3300 mV
[    0.505988] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[    1.166830] ehci-pci: EHCI PCI platform driver
[    2.894277] vcc3v3_pcie: disabling
[    3.257493] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    3.257501] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    3.260566] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    3.260590] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    3.260679] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/[email protected][0]' - status (0)
[    3.261231] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    3.261553] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    3.261575] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /[email protected] failed
[    3.261629] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    3.276048] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    3.276086] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /[email protected] failed
[    3.276142] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    3.290608] rockchip-pcie f8000000.pcie: invalid power supply
[    3.350984] PCI host bridge /[email protected] ranges:
[    3.387121] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    3.394721] pci_bus 0000:00: root bus resource [bus 00-1f]
[    3.401970] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    3.409375] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    3.417072] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    3.417190] pci 0000:00:00.0: supports D1
[    3.417196] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.417676] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.425545] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])
[    3.425588] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
[    3.425642] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[    3.432368] pci 0000:01:00.0: reg 0x10: [io  size 0x0008]
[    3.432397] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[    3.438957] pci 0000:01:00.0: reg 0x14: [io  size 0x0004]
[    3.438971] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[    3.445415] pci 0000:01:00.0: reg 0x18: [io  size 0x0008]
[    3.445429] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[    3.451804] pci 0000:01:00.0: reg 0x1c: [io  size 0x0004]
[    3.451818] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[    3.458122] pci 0000:01:00.0: reg 0x20: [io  size 0x0020]
[    3.458137] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[    3.458150] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    3.460470] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.460537] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
[    3.470994] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[    3.497156] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]
[    3.504734] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0020]
[    3.510579] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0020]
[    3.516276] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0008]
[    3.521936] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0008]
[    3.527605] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0008]
[    3.532503] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0008]
[    3.537180] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0004]
[    3.541789] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0004]
[    3.546404] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0004]
[    3.550983] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0004]
[    3.555226] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.559035] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    3.563143] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    3.567436] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    3.571440] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    3.575103] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[    3.575213] aer 0000:00:00.0:pcie02: service driver aer loaded
With WD Blue 1 Tb starts good, all working well about 1 hour, then WD switched to read-only mode! What a hell? Sorry for my english. May anibody help?
I can only get the pci to read on armhf images from ayufan, which saddens me as I'd really like to use Ubuntu. The Debian desktop from mrfixit2001 does work. Have to set permissions as root to access the drives, but it does work.

Sent from my SM-G950U using Tapatalk
Thanks for the answer!
Well, try Debian from mrfixit ... I wanted to create a small NAS server using OMV. I'll try the workarounds.
With OMV from auyfan could not achieve stable operation. The power supply, PCI-e card is all original. For a week, the SD card failed twice and 1 time - the HDD, not counting the hangs.
For the server, terrible statistics.
Can I find out which SD card you use when booting? It is believed that many system failures are caused by the slow operation of the SD card. My SD card was a Samsung EVO 32 Gb.
Hello to all!

I noticed that there were a lot of failures due to external interference (in my NAS-server, the body is stock metal NAS, the hard disk is WD Blue 1Tb). Up to the point that any contact with the case, and if it is open, especially to the hard drive cover, leads to a hang. This may explain the rare incidents. It works one hour, one day and voila ...