05-31-2019, 12:16 PM
(This post was last modified: 05-31-2019, 01:13 PM by Nikolay_Po.)
Do not solder the board. It is very tiny, many small components that is too easy to damage.
First of all it need to compare the logs and find the difference to get a clue about problem. I can solder mine boards just because I have a soldering station and enough experience. So I can eliminate possible hardware problem to examine a software problem. But in your case is better to examine (and exclude if not actually present) a software problem first. Solder the wires only after we define the hardware problem is definitely persist. More testing, probably of more users, more boards needed. Don't damage your board right now.
Have attached your logs for history.
There is no difference in logs until file system initialization starts:
Armbian (good):
OMV (bad):
The problem is arising right at the start of file system operation. The start sequences are differ.
Had never investigated SATA problems before. Need to look at exception mask bits of ATA library and SATA Error register of a controller.
First of all it need to compare the logs and find the difference to get a clue about problem. I can solder mine boards just because I have a soldering station and enough experience. So I can eliminate possible hardware problem to examine a software problem. But in your case is better to examine (and exclude if not actually present) a software problem first. Solder the wires only after we define the hardware problem is definitely persist. More testing, probably of more users, more boards needed. Don't damage your board right now.
Have attached your logs for history.
There is no difference in logs until file system initialization starts:
Armbian (good):
Code:
[ 10.306823] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 10.310112] systemd[1]: Starting Load/Save Random Seed...
[ 10.315855] systemd[1]: Starting udev Coldplug all Devices...
[ 10.320900] systemd[1]: Mounting FUSE Control File System...
[ 10.327677] systemd[1]: Mounting Configuration File System...
[ 10.333960] systemd[1]: Starting Apply Kernel Variables...
[ 10.346053] systemd[1]: Mounted Configuration File System.
[ 10.349502] systemd[1]: Mounted FUSE Control File System.
[ 10.354745] systemd[1]: Started Nameserver information manager.
[ 10.359864] systemd[1]: Started Load/Save Random Seed.
[ 10.365358] systemd[1]: Started Create Static Device Nodes in /dev.
[ 10.370737] systemd[1]: Started Apply Kernel Variables.
[ 10.389286] systemd[1]: Starting udev Kernel Device Manager...
[ 10.476560] systemd[1]: Started udev Kernel Device Manager.
[ 10.535139] systemd[1]: Started Set the console keyboard layout.
[ 10.538736] systemd[1]: Reached target Local File Systems (Pre).
[ 10.548600] systemd[1]: Mounting /tmp...
[ 10.560632] systemd[1]: Mounted /tmp.
[ 10.565920] systemd[1]: Started Journal Service.
[ 10.621985] systemd-journald[310]: Received request to flush runtime journal from PID 1OMV (bad):
Code:
[ 4.668895] systemd[1]: Mounting FUSE Control File System...
[ 4.677607] systemd[1]: Mounting Configuration File System...
[ 4.683865] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 4.691704] systemd[1]: Starting Initial Check File System Quotas...
[ 4.700326] systemd[1]: Starting udev Coldplug all Devices...
[ 4.706770] systemd[1]: Starting Load/Save Random Seed...
[ 4.714409] systemd[1]: Starting pNFS block layout mapping daemon...
[ 4.727700] systemd[1]: Mounted FUSE Control File System.
[ 4.737374] systemd[1]: Mounted Configuration File System.
[ 4.741549] systemd[1]: Started Journal Service.
[ 4.786973] systemd-journald[337]: Received request to flush runtime journal from PID 1
[ 4.822384] ata1: SATA link down (SStatus 1 SControl 300)
[ 4.826507] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen t4
[ 4.830837] ata1: irq_stat 0x00000040, connection status changed
[ 4.834850] ata1: SError: { CommWake DevExch }
[ 4.838688] ata1: hard resetting linkThe problem is arising right at the start of file system operation. The start sequences are differ.
Had never investigated SATA problems before. Need to look at exception mask bits of ATA library and SATA Error register of a controller.