soerenderfor

Prefixes as we knew them a few days ago are gone. The extension which provided those might got abandoned by the author.
Anyway I'll try to do the best of the situation and refactor this stuff.
Forums which only had a "solved" prefix before will now get the option for moderators and topic author to mark a specific post as solution which also will mark the entire topic as solved. You can check this topic to get an example how this works: https://forum.armbian.com/topic/15333-what-should-be-in-my-gnupg-directory/
 
For other forums there will be a few additional clicks needed to get a tag being used as prefix:

 
I just started to rework the forums so stay tuned if it does not work out for your specific forum you are currently enjoying yet
 
Edit: Done so far.

You know, at one point I thought "maybe I should just try" (exactly as you say). 
 
I dunno, I prefer to actually try to read/research and know what I am doing beforehand as much as possible.  But I know, some times you have to just go for it.
 
EDIT:  I figured it out, simple instructions now here: ZFS "just works" now on Armbian (2 step instructions if you are thick like me)!

Following the @lanefu School of Systems Administration ("here, hold my beer!"), I decided to just give it a go.  And IT VEERRRRRKS!   
 
Here are step by step instructions for my fellow nervous, trepidatious sorts out there:
 
1. Install kernel headers.  I did this through armbian-config (Software -> Headers_install), rather than dicker around trying to figure out which exact package I needed for my board and architecture.
 
2. Issue the following command:
 
$ sudo apt -t buster-backports install zfs-dkms zfsutils-linux  
Note: I did not have to enable backports, as apparently they already are "out of the box" in Armbian; however, follow instructions at link if this is not the case for you.
 
Result:
 
 
It took "a little while" to build the module(s).  Just be patient, go grab $BEVERAGE or whatever, take a break...
 
I don't know how to express how happy I am about this.  I have wanted to do ZFS on some ARM based device for literally years now.  RK3399 was very exciting when it came out, but took years to finally get stable.
 
A special thanks to all RK3399 devs, here and elsewhere, for making this a reality.  Beers are on me if/when we ever get around to having ArmbianCon!     
 

I can say this is an excuse but being nice and professional requires much more energy we don't have. Everytime there is a pressure on Armbian, and this happens daily, that has to fix or do something, an unhealthy and unsustainable relationship is formed. Putting a pressure on contributors is a very bad move and another source of troubles. But "you" don't care about that. Hard to be nice to someone that acts like jerk (noob or not), requires pro grade services worth tens or hundreds thousands of dollars ... on and on. I can understand that noobs have no clue, but when telling people that their problem will not be fixed today, nor this week or year ... is not nice to hear. Frustration mounts up, people are angry. Givers receive close to nothing, not even thank you, for their hard work of helping, solving problems and continuous maintaining and some R&D from takers ... certainly some source of anger perhaps?
 

There is a search button - you can do your own research how many times those words were used and by who / how many different people. You can't say this is a community of hate, but we can be sometimes tensed and not supportive. We ran 30-40 h per day service virtually without any budget and most of our "clients" are frustrated since they are totally out of reality. They expect full blown Linux out of nothing on a brand new hardware. Which normally takes years to develop vs. virtualized Linux that works of much better just because of that.
 
It's a big pressure and people do snap sometimes. It's human nature / bug.
 
 
Broadcom / Raspberry Pi foundation has a very nice and professional attitude, but closed product, which sadly fully rely on community support, are bad for that community. It's not just Armbian attitude, but also from people that understand Linux or those close to Debian, which are perhaps more orthodox when its about FOSS.
 
Whenever you are purchasing some commercial product you have to believe into something. We are just trying to shape that. For fun and FYI.
 
If we tell you, that they sold you BS, while you are happy like a child, ofc your feelings will be hurt. So please tell me, how to do that without making more damage? Keep quiet and nod to corporations that milks us? Some do, we don't. I don't say someone is idiot because he is using Rpi, but one should at least question why hardware engineers community, those who actually waste their time to provide support is pissed on vendors, because they are hiding internals and keep full control over the chip. Do you have any estimation how much time (and our money) was lost because of that fact? I don't want to think about ... Closed hardware is like a cancer, a slap toward Linux community. IMO, there lies another big part for this conflict. And the reason why bad words has been used.
 

Opinions are always perspective matter. From hardware engineering perspective, from things we do around here, is as open source as this:
https://azure.microsoft.com/en-us/services/virtual-machines/

If you have physical connection to your Pi, you can cut the power or attach it. Attach something else. That's you freedom. Of course I am exaggerating, so you will perhaps stop, think and look on things from a different angle.

Hardware engineers can be offended, when we start talking about Pi this way, end customer who only wants to run some application ... usually don't care if they don't have full access to hardware. They don't even know what that means. We do.
 

Neither people around. Which is the reason that topics as such exists. Try looking beyond ...
 
People with lots of knowledge and years of experience is very difficult to convince someone is messing with their know-how and perception. And that someone is not Armbian - we are just delivering something we know and something we are not happy about.
 
I am not native speaker so I apologize if some wording is not well crafted.

I received an email notification same as title of this post 2 days ago.  Just now I changed my password.  But I thought I would make a post to see if anyone else might have been targeted (as I am a Moderator), especially any other Admins or Moderators.
 
I am going to ping everyone I can think of (actually, I simply use the list here) below, but please add anyone else who I miss.
 
@Igor @lanefu @Werner @TonyMac32 @SteeMan @soerenderfor @pfeerick @NicoD @JMCC @balbes150 @_r9

@TRS-80 - I  do use i 5 port card now, works out of the box, and very cheap.. any ways.

If i remember correct, i did something like this:
 
cd /etc/udev/rules.d sudo nano 99-9230.rules in the file add this line
 
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1b4b", ATTR{device}=="0x9230", RUN+="/bin/bash -c 'echo %k > /sys/bus/pci/drivers/ahci/bind'" reboot, and the card should be visible, in OMV

Hi, i have inserted link from a older thread, where we talked about rockpro64 as a NAS
 
 

@jtremblant @Salvador Liébana @Werner @TRS-80 - From my point of view, i did not think @Werner wanted to insult you on purpose. 

@Werner did propose

I think you all in some point misunderstand each other.. Lets all take a deep breath  Again from my point of view, it seems you all are on the "same page"

@Waryle Thanks for update, and the fine description. Yeah, BTRFS is a problem i did also hit the "wall" and did also go through with Ext4, i havent got any downtime yet.

That was very kind of you, thank you!
I have finally found the problem after hours of looking up for documentation and retries. I had the idea to take a PC monitor and plug the RockPro64 on it to see what kind of error it could throw, and work from there :
Uboot seem to boot only on the first SATA drive of the list : I had a SATA card with 4 ports, I plugged my SDD in the port 1 and my two other drives in the 3 and 4. Uboot does not like BTRFS. Once I have plugged the SSD on the port 1, I had a initramfs error, so I went again in armbian-config, used the "Boot from SPI - System on SATA" option, and this time I chosed Ext4 instead of BTRFS. It's working now. I could have found a way to put only the /boot on an Ext4 partition and the system on BTRFS, but I have lost too much time and I'm gettting lazy, so I'll just leave it that way, Ext4 is perfectly fine anyway.
 
Thanks for you help !

This command can be used to figure out how to control the fan.

 
sudo find /sys -name pwm1 | grep hwmon  

ftdoverlay is a convenient way to apply an overlay staticly to a base dtb. You spare the DTC decompile - manually edit - DTC compile dance. Usually you write overlays with label refernces, but to be able to apply such an overlay, the base dtb has to be compiled with the @-option. This has significant impact on the size and distributions usually don't do this. When you write the overlay with full paths, it contains all the information to be applied to a base dtb that was not created with the @-option. The mainline ftdoverlay need the patch to be able to apply it.
 
Edit the pwms property to any value you like as shown in the provided rk3399-rockpro64-tz.dts (50000 default changed to 10000).

Did you buy the sata power cable from pine also? It splits the power into 2 sata cables and on both mount a splitter. Or you can like you say just split one cable to 4 with a sata splitter. I do power my rockpro64 with 4hdd in that way with a 12v 10a psu. It works like charm, no problem (but 8A is enough).

@wolf7250 - Just so you know, if you plan to use that NAS case from pine. In that case there is only room for 2x 3.5" and 2x 2.5". But back to your question, i have found a universal PSU from 7.5volt to 22.5volt and 10amp, so i did just use that one. 

Use 12V always to ROCKPRO64, and around (8A on the safe side) or so to power it all.

Yes, "0" off and "255" full speed. You can change anything inbetween.
 
I have 4 disk in the nas case, the 80mm noctua i did have installed before it was enough to cool it down, CPU temp around 40degress.  The orginal 80mm fan that "belongs" to the case is only around 10mm in thickness, and the noctua is 25mm. So to fit in the small space 90degree sata power cables is a very great idea. But you can fit normal sata power cables with some "violence" ;-)
 
 
No, I like always on, so i did find a number to fit my demands. But many fan scripts is avaible, but you have to fit it the fan controller (FAN name)
 
Just cut the cables and fit the plus and minus wire to the same cables at the fan. Very easy. Hope it was a little help, just ask again if there is something i can help with. Thanks.
The reason i did fit a 92mm noctua in the case was to get it silent, nothing else.

With new kernels the fan spins at "255" always, you can find the fan with this command 
sudo find /sys -name pwm1 | grep hwmon and then change the output to your setup - But on the new kernels the fan point can jump, i am not sure of what reason.

I have tested the Ziti... card for 1 week now, and runs very nice. So go for it, works right out of the box with new kernel also.

One of the cards i have costed around 80euro, and it is almost useless.. The cheap cards is the best here, in my opinion.

@wolf7250 - here you go, here is a couple i got home.

Delock 4 port SATA PCI Express Card - Marvell 88SE9215 - Works out of the box.
 
StarTech.com 4 Port PCI Express SATA III 6Gbps RAID Controller Card with Heatsink (PCIe SATA 3 Controller Adapter (PEXSAT34RH), Styreenhed til lagring (RAID), 4 Kanal, SATA 6Gb/s lavprofil, 600 MBps, RAID 0, 1, 10, JBOD, PCIe 2.0 x2, for P/N: ST521PMINT - Marvell 88SE9230) - Some problems. But i did mange to get it working.

DeLOCK - Lagringskontrol - SATA 6Gb/s - 600 MBps - RAID 0, 1, 10 - PCIe 2.0 x4 (Producent: DeLOCK | Model-nr.: DEL-89395 - Marvell 88SE9215) - Some probs. But did mange to get it working.

Ziyituod PCIe SATA Card, 4 Port (SA3014 - Marvell 9215) Works out of the box.

@wolf7250 - That card from pine64 should be avoided in my opinion, i did only have trubles with it.  I have only cards with Marvell chipset, and i found out buy a simple card not a fancy raid card - less problems. I can later today find my different cards and name them for you.

@wolf7250 - That card from pine64 should be avoided in my opinion, i did only have trubles with it.  I have only cards with Marvell chipset, and i found out buy a simple card not a fancy raid card - less problems. I can later today find my different cards and name them for you.

In my opinion it is a fine board, I run my ROCKPRO64 as a NAS. Runs 24/7 - wirh a sata card and 4 harddrivers in the nas case. OMV works fine, but there can be some probs with sata cards. 

I run krenel 5.7.13 focal, no problems what so ever. And it runs very stable.

Have you tried to use xrandr for the purpose?

sudo nano /etc/hdparm.conf
#Disk1 /dev/disk/by-id/ata-YOURDISK { # mult_sect_io = 16 # write_cache = off # dma = on spindown_time = 240 } #Disk2 /dev/disk/by-id/ata-YOURDISK { # mult_sect_io = 16 # write_cache = off # dma = on spindown_time = 240 } 240 = 20mins - It works at my setup, i did't try lower spindown time.
 
Some drives can bee spun down with hd-idle. change HD_IDLE_OPTS value, then start and activate hd-idle.service. let me know if it works. Thanks.

On all Armbian image, it is like follows:
root
1234

More or less. The blue LED can say a lot, especially if the person cannot connect the console.
This was useful not so long ago in the 5.x kernel where after upgrading from 4.14 simply Odroid HC does not boot and the diode just lights up all the time indicating that the sbc is hanging. For example, if the sd card were damaged and the boot partition is missing, the LED would not light up at all, the same effect as without an sd card.
For novice users it is always best to stick to the standards because later unnecessary problems are created especially with headless sbc and no uart.