Rockpro64 hard drives are not seen by omv until reboot

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Rockpro64 hard drives are not seen by omv until reboot

      Hello,

      I have played with omv vm and decided to go with rockpro64, nas case, pcie sata controller and 2x 3.5 wd red drives.
      Main problem is that when i connect power plug to rockpro64 it boots but not recognizes any drives, i get below errors.
      [ 80.509588] ata1: SATA link down (SStatus 1 SControl 310)
      [ 80.534423] ata1: irq_stat 0x00000040, connection status changed
      [ 80.540057] ata1: SError: { CommWake DevExch }
      [ 80.545230] ata1: limiting SATA link speed to 1.5 Gbps
      [ 80.550431] ata1: hard resetting link

      [ 212.084097] ata2: EH complete
      [ 212.097400] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
      [ 212.106333] ata2: irq_stat 0x00000040, connection status changed
      [ 212.110266] ata2: SError: { CommWake DevExch }
      [ 212.114038] ata2: limiting SATA link speed to 1.5 Gbps

      After reboot dmesg below shows that everything is good.
      [ 2.807119] ata1: SATA max UDMA/133 abar m512@0xfa010000 port 0xfa010100 irq 239
      [ 3.269313] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
      [ 3.275468] ata1.00: ATA-10: WDC WD40EFRX-68N32N0, 82.00A82, max UDMA/133
      [ 3.286399] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
      [ 3.299618] ata1.00: configured for UDMA/133
      [ 10.768358] ata1.00: configured for UDMA/133
      [ 10.781388] ata1: EH complete

      [ 2.809115] ata2: SATA max UDMA/133 abar m512@0xfa010000 port 0xfa010180 irq 239
      [ 3.784369] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
      [ 3.790628] ata2.00: ATA-10: WDC WD40EFRX-68N32N0, 82.00A82, max UDMA/133
      [ 3.796111] ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
      [ 3.802514] ata2.00: configured for UDMA/133
      [ 10.986541] ata2.00: configured for UDMA/133
      [ 10.993483] ata2: EH complete


      Reboot resolves them most of the time but sometimes needs second reboot. I thought adding delay to boot will give sufficient amount of time for drives to spinup and be recognized but it didn't. I modified /boot/extlinux/extlinux.conf and /boot/efi/extlinux/extlinux.conf timeout value to 100 (10 secconds) but it didn't help. I know that it did increase startup time when disks are recognized and when not as well.

      Sata controller card i have is ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01).

      I tried changing sata cables, powering hard drives with atx power supply but i just can't find a consistent pattern as to where the problem is.
      I will try to boot armbian tomorrow after being of all night and not connected to electricity.

      Can anyone advise what logs to look at and how to troubleshoot this problem?

      Thanks in advance
    • vecnar wrote:

      I tried changing sata cables, powering hard drives with atx power supply
      Have you also replaced/checked the SATA power cables? Your symptoms sound like a voltage drop on the 5V rail (SATA power cable). Some drives are fine here with as low as 4.4V, some start to have problems already at 4.75V (see this example/list but please keep in mind that there it's about 2.5" drives not comparable to your WD RED -- I don't know how sensitive they are to voltage drops since we don't use WD)
    • tkaiser wrote:

      vecnar wrote:

      I tried changing sata cables, powering hard drives with atx power supply
      Have you also replaced/checked the SATA power cables? Your symptoms sound like a voltage drop on the 5V rail (SATA power cable). Some drives are fine here with as low as 4.4V, some start to have problems already at 4.75V (see this example/list but please keep in mind that there it's about 2.5" drives not comparable to your WD RED -- I don't know how sensitive they are to voltage drops since we don't use WD)
      Hello tkaiser,
      I used atx power supply sata power cables and not the ones that are attached to sbc. The only downside is that i can't power both power supplies at the same time and the issue most likely to happen when power supplies first get power from ac.
      I had it off since last night and had armbian sd card inserted. I plugged in power today and armbian recognized both drives please see screenshot attached. After that i powered it off, replaced sd card with omv powered it on, both hard drives were not recognized. See screenshot of dmesg and full dmesg output from omv. I issued reboot from cli but it didn't recognize hard drives, only after second reboot command from cli they came back.
      Could you advise the best troubleshooting plan in this situation? Every time i take hard drive cage out i move all the cables so there are too many variables in play.
      Thank you for your time
      Images
      • ArmbianAfterNightOff.jpg

        165.11 kB, 841×614, viewed 7 times
      • OMVAfterSuccesfullArmbian_StartOfFailures.jpg

        402.06 kB, 1,280×1,024, viewed 7 times
      Files

      The post was edited 1 time, last by vecnar ().

    • tkaiser wrote:

      vecnar wrote:

      I tried changing sata cables, powering hard drives with atx power supply
      Have you also replaced/checked the SATA power cables? Your symptoms sound like a voltage drop on the 5V rail (SATA power cable). Some drives are fine here with as low as 4.4V, some start to have problems already at 4.75V (see this example/list but please keep in mind that there it's about 2.5" drives not comparable to your WD RED -- I don't know how sensitive they are to voltage drops since we don't use WD)
      Hello tkaiser,

      I tried posting below with a few screenshots and a log file but it was waited to be approved by moderator so i will try to put screenshots in plain text and upload full log if you need it.

      I used atx power supply sata power cables and not the ones that are attached to sbc. The only downside is that i can't power both power supplies at the same time and the issue most likely to happen when power supplies first get power from ac.
      I had it off since last night and had armbian sd card inserted. I plugged in power today and armbian recognized both drives please see dmesg output below.

      Source Code

      1. ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
      2. ata1.00: ATA-10 WDC "serial number", 82.00A82, max UDMA/133
      3. ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
      4. ata1.00: configured for udma/133
      5. ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
      6. ata2.00: ATA-10 WDC "serial number", 82.00A82, max UDMA/133
      7. ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
      8. ata2.00: configured for udma/133
      After that i powered it off, replaced sd card with omv powered it on, both hard drives were not recognized. See below dmesg errors. I issued reboot from cli but it didn't recognize hard drives, only after second "reboot" command from cli they came back.


      Source Code

      1. [ 7.461809] ata2: SATA link down (SStatus 1 SControl 300)
      2. [ 7.476399] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
      3. [ 7.483279] ata2: irq_stat 0x00000040, connection status changed
      4. [ 7.489419] ata2: SError: { CommWake DevExch }
      5. [ 7.495414] ata2: hard resetting link
      6. [ 7.501306] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
      7. [ 7.507682] ata1: irq_stat 0x00000040, connection status changed
      8. [ 7.513909] ata1: SError: { CommWake DevExch }
      9. [ 7.520018] ata1: limiting SATA link speed to 1.5 Gbps
      10. [ 7.525319] ata1: hard resetting link
      Let me know if you would like to see full dmesg output from omv.

      Could you advise the best troubleshooting plan in this situation? Every time i take hard drive cage out i move all the cables so there are too many variables in play.


      Thank you for your time
    • tkaiser wrote:

      vecnar wrote:

      The only downside is that i can't power both power supplies at the same time and the issue most likely to happen when power supplies first get power from ac
      No idea what this means but your issue is clearly hardware related (see the dmesg messages, the drive's controller is physically not available).
      Sorry if i was not clear about atx power supply testing. The issue arises when i plugin dc adapter in the socket with 240 volts and rockpro64 starts itself automatically, i do not need to press anything. I was using atx power supply to power hard drives only, but i wanted to simulate the same behavior as the other dc adapter. I am sure i am not troubleshooting it correctly that is why i am looking for some guidance steps to follow in order to findout where the actual problem is and how to resolve it.

      So does it mean sata controller is an issue that resolves itself after a few restarts under omv? It is strange that armbian doesn't have this problem and detects it. I am not familiar with arm and linux so not sure if they use the same bios like before boot process or armbian and omv use different approaches or versions.

      Do you know if anyone is using rockpro64 wih 2 x 3.5 inch drives and psu 12v 5A successfully and if yes what sata controller card?