Abdul Badalambadad

@foxx1337 If you are interested somebody on Radxa forum has the same opinion. I am not experienced enough with DTOs so maybe he can help you as well https://forum.radxa.com/t/samsung-990-pro-2tb-ssd/20166/6?u=bamboo

I confirm this. But I still think it is not a kernel problem as all (radaxa, joshua, armbian 6.8) behave exactly the same. On my Pi the mark is about 11 GB. I already raised a complaint at Radaxa so wish me luck. Thank you guys, I won't bug you here any more.

I've got another update: the SSD isn't dead. I was just tired and didn't notice that the USB cable fell from USB-A to USB-C adapter. That was the reason it didn't appear on another PC. Then I decided to use the new SSD in my main machine and use my old SSD in Rock Pi. Didn't help. Now I've got two different SSDs which behave the same. This rules out a hardware fault on SSD side. I've tested different filesystems (ext4 and exfat) to rule out a bug in the filesystem implementation. Both behave the same except ext4 has much more consistent performance. Then I installed memtester. And boom. The fault is not caused by NVMe, but rather faulty memory as @foxx1337 suggested. This happens all the time even in big PC world. So I guess that I just wasn't lucky and my Pi has faulty memory. Does this make sense?

Thank you guys, but the SSD is probably dead. I've tried Arch based on 5.10 kernel and after I've started the copy process it crashed as well but this time the SSD doesn't appear on any other PC. So I am going for a service with it. So this might actually be a HW failure. Good thing is that the Pi survived (crossed fingers) and that I won't have to address refund with China.

Hello, I've problem... Message from syslogd@rock-5b at Feb 23 21:58:00 ... kernel:[ 443.674152] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Message from syslogd@rock-5b at Feb 23 21:58:00 ... kernel:[ 443.674152] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Message from syslogd@rock-5b at Feb 23 21:58:00 ... kernel:[ 443.718480] Code: b40001b3 f1036273 d503201f 54000140 (f9402261) Message from syslogd@rock-5b at Feb 23 21:58:00 ... kernel:[ 443.718480] Code: b40001b3 f1036273 d503201f 54000140 (f9402261) I have exactly zero experience with debugging this. But from my trial-error it will have something to do with NVME as this is the only thing that remains. This error happen after copying data to SSD in M.2 slot. I tried copying USB -> SSD and SFTP -> SSD . Happens everytime after about 5 GB is copied. Configuration: * Rock Pi 5B, 32 GB RAM * SSD: Samsung 990 PRO 2TB * Power Supply: Dummy 12V DC adapter 3A * Up-to-date Armbian with 6.8.0-rc1-edge-rockchip-rk3588 * Latest bootloader in NAND * Boot from NVME The only NOT up-to-date thing is the Samsung firmware. I haven't found a way how to update it inside the Pi. What can I do? Please help.

I understand your reasons, but I haven't good feeling about this board any more and I just don't want it. The dissapointment was too brutal :). The best thing is that most of the image links on their official forum is dead. Plus there is a law in my country, that the merchant must refund me full price if I return it before 3 days since purchase so I will happily use it. I already own the first RPi and because everything was smooth with it, I've tought that it works this way with all vendors since they are all open source, sharing, not greedy, etc... And the next try will not be RPi-zero, but NanoPi M1 1GB. It actually suits me better.

Well, that's it. I am migrating to rpi-zero. I will miss those extra 3 cores, but screw it. Thank you for your support.

I must be doing something wrong. I am not able to get any output on screen with self-compiled armbian. Prebuilt image based of ubuntu worked (not great). What am I doing wrong? With the prebuilt image the red LED turned of after a while and then it started to work. But with self-complied armbian it glows red forever, CPU generates heat, but nothing on display. Any tips? For a complete noob? I've tried Stretch and Jessie, both mainline kernel.

I've compiled something. Stretch, mainline, no-gui. I'm waiting for postman's arrival. At least there is no firmware flashing, so no chance to destroy the device....

Thank you for your quick reaction. I will try to give it a shot, but I will probably try to return the device to the merchant, because I've found the thread, where tkaiser is explaining the situation. I feel like a total dumbass now... Do you know how long does Armbian take to compile?

Hello, I've not found an Armbian version which states compatibility with Banana Pi M2 Zero. Is there a compatible version? My first guess would be the Banana PI M2. Is that so? I've tryied to search the forum but all I've found is something about compilation. Please help.