05-20-2021, 08:58 PM
This is great t4_4t-- thanks for that tip about checking dmesg to see if the kernel params "took". Turns out I had been using the wrong syntax.
In arbian-config, after going to System --> Boot envs, I added the line
(no quotes or anything-- just exactly like that), which apparently edits the /boot/armbianEnv.txt file (found these details at https://forum.armbian.com/topic/13457-ke...arameters/). After saving and restarting, dmesg shows
"$ cat /proc/cmdline" now also shows that the libata.force param was applied at boot.
This is amazing! I am writing big files to my data drive and it is not failing for the first time in months! Thanks again so much.
In arbian-config, after going to System --> Boot envs, I added the line
Code:
extraargs=libata.force=1.5G
(no quotes or anything-- just exactly like that), which apparently edits the /boot/armbianEnv.txt file (found these details at https://forum.armbian.com/topic/13457-ke...arameters/). After saving and restarting, dmesg shows
Code:
daffy@rockpro64:~$ dmesg | grep limit
[ 3.163820] ata1: FORCE: PHY spd limit set to 1.5Gbps
[ 3.163836] ata2: FORCE: PHY spd limit set to 1.5Gbps
"$ cat /proc/cmdline" now also shows that the libata.force param was applied at boot.
This is amazing! I am writing big files to my data drive and it is not failing for the first time in months! Thanks again so much.