PCIE SATA controller ASM1062 problems or software
#31
The black have better heatsink.

As for o-rings, if they deattached on both sides it means the trace which was connected to o-ring is broken. You may look around the missed o-rings and find disconnected trace. In such cases I'm scratching the coating of the trace and trying to make the trace copper clean from coating closer to the pin but keep the coating at surrounding ground and another traces. When broken trace is scratched and is clear, I'm soldering a thinnest wire from a strand right over the trace and the pin. This way the trace become connected to it's pin even if o-ring is absent.



About the RAID. Here in the last log are these records:

Code:
[    2.809456] ahci 0000:01:00.0: version 3.0
[    2.809468] ahci 0000:01:00.0: enabling device (0000 -> 0002)
[    2.809650] md: multipath personality registered for level -4
[    2.813999] md: raid0 personality registered for level 0
[    2.832249] md: raid1 personality registered for level 1
[    2.851691] md: raid6 personality registered for level 6
[    2.862482] md: raid5 personality registered for level 5
[    2.873154] md: raid4 personality registered for level 4
[    2.897874] md: raid10 personality registered for level 10
[    3.550509] EXT4-fs (mmcblk0p7): 2 orphan inodes deleted
[    3.558010] EXT4-fs (mmcblk0p7): recovery complete
[    3.577286] EXT4-fs (mmcblk0p7): mounted filesystem with writeback data mode. Opts: (null)

Rigth after AHCI device enable the messages from "md", Multiply Devices, aka Linux Software RAID are present.
May be your drives formerly were a part of software RAID? The file system look mounted earlier than when you booted with one drive active.

It will be better to debug in future test to increase debug level. To do that, you need to add a kernel parameter loglevel=6 into the boot configuration file.
The file is in /linux-root/boot/extlinux directory, "extlinux.conf". You need to add loglevel=6 into the line with kerner parameters on the flash drive:

original (example)
Code:
append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4

modified (example, look at the end of line)

Code:
append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 loglevel=6


If I'm not mistaken, the debug log you will get will contain much more information (level 6 is INFO level) about what is happening during a boot.


Messages In This Thread
RE: PCIE SATA controller ASM1062 problems or software - by Nikolay_Po - 06-02-2019, 01:39 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Which SATA card should I use my NAS server RAID5 Louysa 3 914 09-24-2023, 04:40 AM
Last Post: JPT223
  SATA keeps crashing JPT223 1 567 09-21-2023, 10:52 PM
Last Post: tllim
  SATA hotplug not working? JPT223 0 445 09-15-2023, 04:20 AM
Last Post: JPT223
  Compatible PCIe Sata Controller spacebricker 1 1,578 02-06-2023, 10:03 AM
Last Post: diizzy
  ROCKPro64 with 16 ports SATA controller ZeblodS 19 25,922 12-18-2022, 06:25 PM
Last Post: heyghoge
  PCIe bifurcation support (on RK3399) Arn 1 1,346 11-28-2022, 05:12 PM
Last Post: tllim
  Existings disks and using a StarTech SATA Controller jkugler 1 2,090 12-09-2021, 06:41 AM
Last Post: SVDSHRDJD
  RockPro64 doesn't boot when PCIe to M.2 adapter is installed Cerberus 3 3,522 11-27-2021, 11:38 PM
Last Post: Cerberus
  Rockpro64 Sata Card kills itself jerry110 33 44,467 10-20-2021, 04:36 AM
Last Post: fieni
  Right direction SATA card corax 2 2,992 09-15-2021, 12:46 PM
Last Post: corax

Forum Jump:


Users browsing this thread: 1 Guest(s)