<![CDATA[PINE64 - RockPro64 Hardware and Accessories]]> https://forum.pine64.org/ Thu, 21 May 2026 18:53:43 +0000 MyBB <![CDATA[Powering two disks from RockPro64]]> https://forum.pine64.org/showthread.php?tid=20195 Thu, 19 Feb 2026 21:20:33 +0000 some_pinephone_user]]> https://forum.pine64.org/showthread.php?tid=20195
connect one 2.5" HDD to a USB3.0 port and second HDD to a USB-C port. Can be both powered on simultaneoulsy only from USB?
If I transfer data from one disk to another will the data transfer be too slow because both disk are on the same USB3 controller?

What if I connect the second disk to a USB2 port?

Only one disk will be working 24/7. The other one will only be turned on for weekly backups.]]>
connect one 2.5" HDD to a USB3.0 port and second HDD to a USB-C port. Can be both powered on simultaneoulsy only from USB?
If I transfer data from one disk to another will the data transfer be too slow because both disk are on the same USB3 controller?

What if I connect the second disk to a USB2 port?

Only one disk will be working 24/7. The other one will only be turned on for weekly backups.]]> <![CDATA[What part is L2000 precisely?]]> https://forum.pine64.org/showthread.php?tid=20168 Wed, 14 Jan 2026 12:29:36 +0000 jssfr]]> https://forum.pine64.org/showthread.php?tid=20168
Looks like L2000 gave out on my ROCKPro64:


.jpg   coil.jpg (Size: 188.29 KB / Downloads: 119)

The labeling says 3R3, which leads me to believe this is a 3.3uH inductor. There are three more inductors on the board with a label of 3R3, one in the same size and quite close (can be seen in the photo) and two more closer to the CPU, between the CPU and the PCIe port, which are smaller (3x3mm if I'd have to guess).

The schematics for the 2.1 board revision (mine has Rckpro64 V2.1 2018-07-02 printed on it) only show two 3.3uH inductors and if I'm reading the label correctly ("IND_3x3"), those would be the inductors between the CPU and the PCIe port.

By cross-referencing the V2.0 silk screen with the V2.1 schematic (risky, I know), I identified the damaged part as being L2000, behind the VCC5V0_SYS regulator. That seems plausible and fits my symptoms of random kernel panics (as far as I can tell, the CPUs power is derived from VCC5V0_SYS at some point).

However, the V2.1 schematic lists L2000 (and L2001) as 4.7uH inductors, while my board seems to have 3.3uH inductors in that place.

Is that a manufacturing error or is that a mistake in the schematics or did I do a mistake when identifying the problematic part?

I'm also looking for a replacement, and assuming that 3.3uH is correct, I'd think that MPL-SE4030-3R3 would be a good fit. If it should in fact be a 4.7uH, the MPL-SE4030-4R7 should fit the bill. At least those parts fulfill the current rating (3.3A) and the resistance (0.04Ohm) from the schematics.

Thanks for any insights,
jssfr

P.S.: I do not know what damaged that inductor in that way. I cannot imagine physical force alone, I suspect it got overloaded at some point, but I don't know with what. AFAICT, *that* 5V rail does not power the USB, so it can't be any USB peripherials. I do have some connected to the Pi header, but none of which should draw more than a few dozen milliamperes.]]>
Looks like L2000 gave out on my ROCKPro64:


.jpg   coil.jpg (Size: 188.29 KB / Downloads: 119)

The labeling says 3R3, which leads me to believe this is a 3.3uH inductor. There are three more inductors on the board with a label of 3R3, one in the same size and quite close (can be seen in the photo) and two more closer to the CPU, between the CPU and the PCIe port, which are smaller (3x3mm if I'd have to guess).

The schematics for the 2.1 board revision (mine has Rckpro64 V2.1 2018-07-02 printed on it) only show two 3.3uH inductors and if I'm reading the label correctly ("IND_3x3"), those would be the inductors between the CPU and the PCIe port.

By cross-referencing the V2.0 silk screen with the V2.1 schematic (risky, I know), I identified the damaged part as being L2000, behind the VCC5V0_SYS regulator. That seems plausible and fits my symptoms of random kernel panics (as far as I can tell, the CPUs power is derived from VCC5V0_SYS at some point).

However, the V2.1 schematic lists L2000 (and L2001) as 4.7uH inductors, while my board seems to have 3.3uH inductors in that place.

Is that a manufacturing error or is that a mistake in the schematics or did I do a mistake when identifying the problematic part?

I'm also looking for a replacement, and assuming that 3.3uH is correct, I'd think that MPL-SE4030-3R3 would be a good fit. If it should in fact be a 4.7uH, the MPL-SE4030-4R7 should fit the bill. At least those parts fulfill the current rating (3.3A) and the resistance (0.04Ohm) from the schematics.

Thanks for any insights,
jssfr

P.S.: I do not know what damaged that inductor in that way. I cannot imagine physical force alone, I suspect it got overloaded at some point, but I don't know with what. AFAICT, *that* 5V rail does not power the USB, so it can't be any USB peripherials. I do have some connected to the Pi header, but none of which should draw more than a few dozen milliamperes.]]> <![CDATA[Trying to attach a serial console to my RockChip RK3399]]> https://forum.pine64.org/showthread.php?tid=19935 Sun, 03 Aug 2025 14:50:20 +0000 marietto]]> https://forum.pine64.org/showthread.php?tid=19935
I tried to enable the serial console on my RockChip RK3399 to inspect what happens as soon as FreeBSD boots. This is the tutorial that I'm following :

https://forum.pine64.org/showthread.php?tid=6387

This is the adapter that I'm using :

Code:
Product: CP2102 USB to UART Bridge Controller
usb 1-9: Manufacturer: Silicon Lab
usb 1-9: cp210x converter now attached to ttyUSB0


I followed carefully the instructions but I'm not able to see any message inside the console.

I tried setting port 115200,1500000 and even without setting a speed

On Terminal 1 :

Code:
# screen /dev/ttyUSB0 1500000 (but also 115200 or without a value)

On Terminal 2 :

Code:
# minicom -D /dev/ttyUSB0 -b 1500000 (but also with 115200 or without -b and a value)

The result is the same. No messages inside the console as soon as I power on the board.

Please can you give a look at the pictures that I have attached and help me to understand where could be the mistake :

https://ibb.co/Yn8rhq9
https://ibb.co/99VBxnZS
https://ibb.co/KjFNk28v
https://ibb.co/QvV7rXmr


I followed carefully the tutorial,trying to record what works. It's not easy for me to understand which colors are tied to which pins. It seems that colors change. Unfortunately I'm not using the same adapter of the dude who wrote the tutorial.

The tutorial said to connect black to pin 6 and brown to pin 8. Since my board is exactly the same as the board used by the dude who wrote the tutorial,it should work. But it does not. 


Thank you.]]>
I tried to enable the serial console on my RockChip RK3399 to inspect what happens as soon as FreeBSD boots. This is the tutorial that I'm following :

https://forum.pine64.org/showthread.php?tid=6387

This is the adapter that I'm using :

Code:
Product: CP2102 USB to UART Bridge Controller
usb 1-9: Manufacturer: Silicon Lab
usb 1-9: cp210x converter now attached to ttyUSB0


I followed carefully the instructions but I'm not able to see any message inside the console.

I tried setting port 115200,1500000 and even without setting a speed

On Terminal 1 :

Code:
# screen /dev/ttyUSB0 1500000 (but also 115200 or without a value)

On Terminal 2 :

Code:
# minicom -D /dev/ttyUSB0 -b 1500000 (but also with 115200 or without -b and a value)

The result is the same. No messages inside the console as soon as I power on the board.

Please can you give a look at the pictures that I have attached and help me to understand where could be the mistake :

https://ibb.co/Yn8rhq9
https://ibb.co/99VBxnZS
https://ibb.co/KjFNk28v
https://ibb.co/QvV7rXmr


I followed carefully the tutorial,trying to record what works. It's not easy for me to understand which colors are tied to which pins. It seems that colors change. Unfortunately I'm not using the same adapter of the dude who wrote the tutorial.

The tutorial said to connect black to pin 6 and brown to pin 8. Since my board is exactly the same as the board used by the dude who wrote the tutorial,it should work. But it does not. 


Thank you.]]> <![CDATA[TPM module for rockpro64]]> https://forum.pine64.org/showthread.php?tid=19542 Wed, 04 Dec 2024 00:19:36 +0000 misha64]]> https://forum.pine64.org/showthread.php?tid=19542
Is there any compatible tpm module with rockpro64?

found these for raspberry pi:

https://www.voelkner.de/products/1304508...-1St..html
https://www.berrybase.ch/letstrust-tpm-k...spberry-pi
https://buyzero.de/collections/andere-pl...orm-module

based on Infineon Optiga™ SLB 9672 or 9670 TPM 2.0

GPIO pinout between raspberry and rockpro64 is similar but not identical.

So no idea if they are compatible.

Any suggestion would be appreciated!]]>
Is there any compatible tpm module with rockpro64?

found these for raspberry pi:

https://www.voelkner.de/products/1304508...-1St..html
https://www.berrybase.ch/letstrust-tpm-k...spberry-pi
https://buyzero.de/collections/andere-pl...orm-module

based on Infineon Optiga™ SLB 9672 or 9670 TPM 2.0

GPIO pinout between raspberry and rockpro64 is similar but not identical.

So no idea if they are compatible.

Any suggestion would be appreciated!]]> <![CDATA[using spi and gpio]]> https://forum.pine64.org/showthread.php?tid=19337 Wed, 10 Jul 2024 01:16:13 +0000 nano2]]> https://forum.pine64.org/showthread.php?tid=19337
I am using a MAx31865 RTD temperature sensor module which connects by SPI. I have used this on my orange pi PC (allwinner H3 - 32 bit) as a spidev device which works well. But migrating to the rockpro 64 was a big problem.

On the Rockpro 64 I used the Armbian_24.2.1_Rockpro64_jammy_current_6.6.16_xfce system. This only has Spidev1.x, but it is easy to change from using spidev0.x. However I was unable to get the spidev driver working. Oscilloscope observation showed that the CS pin (header pin) h24 is not toggled at all by the spidev driver. This can be overcome by embedding GPIO write commands around the spidev access to toggle the CS line. I could then transmit and recieve data but the data was corrupt. After many attempts I concluded that the spidev driver is faulty, but i did not want to mess with the device tree. I tried a more recent Armbian bookworm system, but it also failed. I checked other systems including free-bsd, twister, manjaro, ubunto-noble and bionic but none of them have a spidev driver. I installed the bitbang driver using armbian-config, but it does not provide a device in /dev and is not useful. (I presume you need to add a param... line in /boot/Armbianenv.txt but have seen no documentation of the required param) Eventually i resorted to writing my own bitbang subroutine. This was able to correctly access the RTD temperature device. I have given up on using spidev on the rockpro 64.

I had major issues with GPIO access from my C++ code. Wiring-pi does not work on rockpro and i found armbianio. This allows gpio control, but does not have pin-mapping for the rockpro64, however I was able to add the required pin tables easily. But note that several pages describing the pin numbering have typographical errors, in particular pin h19 is actually pad 40 (wrongly shown as pad 48 in several souces). This overcomes the "doesn't work" comments on some sources. This pin is important as it is usually MOSI of the spi bus. Although armbianio has SPI routines, these do not work - because of the suspected problem in spidev.

I cannot attatch a file  - so here is the t change information for the rockpro 64 pin mappings in armbianio.  You need to add this in armbianio.c and re-make. This must be added as the first pin table as the existing pin table indexing is corrupt. You also need to add the *iPinLists and *szBoardNames items.

// Pine RockPro 64  now added as #1 to avoid original indexing mess
  static int iRockPro64Pins[] = {-1, -1, -1, 52, -1, 53, -1, 152, 148, -1, 147,
                                    54, 120, 50, -1, 33, 36, -1, 149, 40, -1,
                                    39, 153, 41, 42, -1, 45, 43, 44, 155, -1,
                                    156, 124, 125, -1, 122, 126, 121, 123, -1, 127};
=====  fix these indexing lines also
static int *iPinLists[] = {iRockPro64Pins,  ipotatoPins, iBPIZPins, iRPIPins, iOPIZPPins, iOPIZP2ins, iOPIZPins, iOPI1Pins, iOPI1Pins,
                          iNPDPins, iNP2Pins, iNPK2Pins, iNPNPins, iNPNPins, iNPNPins, iNPM4Pins, iNPM4Pins,
                          iTinkerPins, iRadxaZeroPins, iMangoPiPins};      //total 20
static const char *szBoardNames[] = {"RockPro 64\n", "Le potato\n","Banana Pi M2 Zero\n","Raspberry Pi\n","Orange Pi Zero Plus\n",
                                    "Orange Pi Zero Plus 2\n","Orange Pi Zero\n","Orange Pi Lite\n","Orange Pi One\n",
                                    "NanoPi Duo\n", "NanoPi 2\n", "Nanopi K2\n", "NanoPi Neo\n", "NanoPi Air\n",
                                    "NanoPi Neo 2\n", "NanoPi M4\n", "NanoPi M4V2\n", "Tinkerboard\n", "Radxa Zero\n",
                                    "Mango Pi Mcore\n", NULL};  //total 20
static int iBoardType;
static int iPinCount[] = {40,40,40,40,29,29,29,43,43,32,40,40,40,40,40,40,41,41,40,41}; // number of pins in the header  rockpro64-40  total 20
// GPIO number of on-board IR receiver
static int iIR_GPIO[] = {0, 7, 0, 0, 363, 363, 363, 363, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0};  //kgb  zero for pine at start, total now  21  !

===== my comment regarding tables in armbianio.c
//  this is a mess with only 17 pin-tables, but a key-list (below) of 20 boards!  Only the first few seem correct. RockPro 64 is correct if put as first]]>
I am using a MAx31865 RTD temperature sensor module which connects by SPI. I have used this on my orange pi PC (allwinner H3 - 32 bit) as a spidev device which works well. But migrating to the rockpro 64 was a big problem.

On the Rockpro 64 I used the Armbian_24.2.1_Rockpro64_jammy_current_6.6.16_xfce system. This only has Spidev1.x, but it is easy to change from using spidev0.x. However I was unable to get the spidev driver working. Oscilloscope observation showed that the CS pin (header pin) h24 is not toggled at all by the spidev driver. This can be overcome by embedding GPIO write commands around the spidev access to toggle the CS line. I could then transmit and recieve data but the data was corrupt. After many attempts I concluded that the spidev driver is faulty, but i did not want to mess with the device tree. I tried a more recent Armbian bookworm system, but it also failed. I checked other systems including free-bsd, twister, manjaro, ubunto-noble and bionic but none of them have a spidev driver. I installed the bitbang driver using armbian-config, but it does not provide a device in /dev and is not useful. (I presume you need to add a param... line in /boot/Armbianenv.txt but have seen no documentation of the required param) Eventually i resorted to writing my own bitbang subroutine. This was able to correctly access the RTD temperature device. I have given up on using spidev on the rockpro 64.

I had major issues with GPIO access from my C++ code. Wiring-pi does not work on rockpro and i found armbianio. This allows gpio control, but does not have pin-mapping for the rockpro64, however I was able to add the required pin tables easily. But note that several pages describing the pin numbering have typographical errors, in particular pin h19 is actually pad 40 (wrongly shown as pad 48 in several souces). This overcomes the "doesn't work" comments on some sources. This pin is important as it is usually MOSI of the spi bus. Although armbianio has SPI routines, these do not work - because of the suspected problem in spidev.

I cannot attatch a file  - so here is the t change information for the rockpro 64 pin mappings in armbianio.  You need to add this in armbianio.c and re-make. This must be added as the first pin table as the existing pin table indexing is corrupt. You also need to add the *iPinLists and *szBoardNames items.

// Pine RockPro 64  now added as #1 to avoid original indexing mess
  static int iRockPro64Pins[] = {-1, -1, -1, 52, -1, 53, -1, 152, 148, -1, 147,
                                    54, 120, 50, -1, 33, 36, -1, 149, 40, -1,
                                    39, 153, 41, 42, -1, 45, 43, 44, 155, -1,
                                    156, 124, 125, -1, 122, 126, 121, 123, -1, 127};
=====  fix these indexing lines also
static int *iPinLists[] = {iRockPro64Pins,  ipotatoPins, iBPIZPins, iRPIPins, iOPIZPPins, iOPIZP2ins, iOPIZPins, iOPI1Pins, iOPI1Pins,
                          iNPDPins, iNP2Pins, iNPK2Pins, iNPNPins, iNPNPins, iNPNPins, iNPM4Pins, iNPM4Pins,
                          iTinkerPins, iRadxaZeroPins, iMangoPiPins};      //total 20
static const char *szBoardNames[] = {"RockPro 64\n", "Le potato\n","Banana Pi M2 Zero\n","Raspberry Pi\n","Orange Pi Zero Plus\n",
                                    "Orange Pi Zero Plus 2\n","Orange Pi Zero\n","Orange Pi Lite\n","Orange Pi One\n",
                                    "NanoPi Duo\n", "NanoPi 2\n", "Nanopi K2\n", "NanoPi Neo\n", "NanoPi Air\n",
                                    "NanoPi Neo 2\n", "NanoPi M4\n", "NanoPi M4V2\n", "Tinkerboard\n", "Radxa Zero\n",
                                    "Mango Pi Mcore\n", NULL};  //total 20
static int iBoardType;
static int iPinCount[] = {40,40,40,40,29,29,29,43,43,32,40,40,40,40,40,40,41,41,40,41}; // number of pins in the header  rockpro64-40  total 20
// GPIO number of on-board IR receiver
static int iIR_GPIO[] = {0, 7, 0, 0, 363, 363, 363, 363, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0};  //kgb  zero for pine at start, total now  21  !

===== my comment regarding tables in armbianio.c
//  this is a mess with only 17 pin-tables, but a key-list (below) of 20 boards!  Only the first few seem correct. RockPro 64 is correct if put as first]]> <![CDATA[How many HD's can I utilize?]]> https://forum.pine64.org/showthread.php?tid=18826 Mon, 30 Oct 2023 19:04:57 +0000 dairymilkbatman]]> https://forum.pine64.org/showthread.php?tid=18826
I'm looking for a lot of space!

Simple question; what is the max number of drives I can get the rockpro to use? and how might I best go about that? I assume I can use x2 SSD's in the USB ports, but what else can I plug into?

edit: could not find this question answered, as simply as it is :p]]>
I'm looking for a lot of space!

Simple question; what is the max number of drives I can get the rockpro to use? and how might I best go about that? I assume I can use x2 SSD's in the USB ports, but what else can I plug into?

edit: could not find this question answered, as simply as it is :p]]> <![CDATA[SATA keeps crashing]]> https://forum.pine64.org/showthread.php?tid=18731 Thu, 21 Sep 2023 09:23:16 +0000 JPT223]]> https://forum.pine64.org/showthread.php?tid=18731
I had several problems with my harddrives during burn in test. I believe I made it more stable by using an overpowered beQuiet ATX power supply.
But still after about 10 hours of burn in, one of the drives disappeared from system.

is there anything I could do about it, or should I try a different SATA adapter?
It's a ASM1166 based one.

thanks
JPT

Code:
kernel: [20815.037460] ata31.00: exception Emask 0x11 SAct 0xffffffff SErr 0x0 action 0x6 frozen
kernel: [20815.037488] ata31.00: irq_stat 0x48000008, interface fatal error

kernel: [20815.037498] ata31.00: failed command: WRITE FPDMA QUEUED
kernel: [20815.037504] ata31.00: cmd 61/00:00:00:b4:68/04:00:06:00:00/40 tag 0 ncq dma 524288 out
kernel: [20815.037504]          res 40/00:90:00:78:68/00:00:06:00:00/40 Emask 0x10 (ATA bus error)
kernel: [20815.037728] ata31.00: status: { DRDY }
(repeated  ~30 times)
kernel: [20815.038403] ata31.00: failed command: WRITE FPDMA QUEUED
kernel: [20815.038407] ata31.00: cmd 61/00:f8:00:94:68/04:00:06:00:00/40 tag 31 ncq dma 524288 out
kernel: [20815.038407]          res 40/00:90:00:78:68/00:00:06:00:00/40 Emask 0x10 (ATA bus error)
kernel: [20815.038425] ata31.00: status: { DRDY }

kernel: [20815.038438] ata31: hard resetting link
kernel: [20815.351579] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20815.351797] ata31.00: revalidation failed (errno=-2)
kernel: [20820.373226] ata31: hard resetting link
kernel: [20820.687580] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20820.687821] ata31.00: revalidation failed (errno=-2)
kernel: [20825.749275] ata31: hard resetting link
kernel: [20826.063641] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20826.063877] ata31.00: revalidation failed (errno=-2)
kernel: [20826.063884] ata31.00: disable device
kernel: [20826.064897] ata31: EH complete

kernel: [20826.065122] sd 30:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=11s
kernel: [20826.065137] sd 30:0:0:0: [sdb] tag#16 CDB: opcode=0x2a 2a 00 06 68 b4 00 00 04 00 00
kernel: [20826.065145] I/O error, dev sdb, sector 107525120 op 0x1:(WRITE) flags 0x800 phys_seg 128 prio class 2
kernel: [20826.065414] sd 30:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [20826.065423] sd 30:0:0:0: [sdb] tag#16 CDB: opcode=0x2a 2a 00 02 c4 61 00 00 03 00 00
kernel: [20826.065427] I/O error, dev sdb, sector 46424320 op 0x1:(WRITE) flags 0x0 phys_seg 96 prio class 2
(repeated ~5 times)
kernel: [20826.066623] sd 30:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=11s
kernel: [20826.066634] sd 30:0:0:0: [sdb] tag#20 CDB: opcode=0x2a 2a 00 06 68 c6 80 00 05 40 00
kernel: [20826.066640] I/O error, dev sdb, sector 107529856 op 0x1:(WRITE) flags 0x4800 phys_seg 168 prio class 2
kernel: [20826.069242] md: super_written gets error=-5
kernel: [20826.069252] md/raid:md127: Disk failure on sdb1, disabling device.
kernel: [20826.069258] md/raid:md127: Operation continuing on 2 devices.

udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [21040.731415] scsi_io_completion_action: 38 callbacks suppressed
kernel: [21040.731431] sd 30:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [21040.731443] sd 30:0:0:0: [sdb] tag#20 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31257]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31271]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [21640.672280] sd 30:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [21640.672297] sd 30:0:0:0: [sdb] tag#21 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31286]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
CRON[31287]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31300]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [22240.621574] sd 30:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [22240.621590] sd 30:0:0:0: [sdb] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31319]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [22840.638787] sd 30:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [22840.638804] sd 30:0:0:0: [sdb] tag#22 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31329]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31344]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [23440.723283] sd 30:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [23440.723303] sd 30:0:0:0: [sdb] tag#1 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31360]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31361]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [24040.628704] sd 30:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [24040.628722] sd 30:0:0:0: [sdb] tag#23 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31384]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [24640.892353] sd 30:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [24640.892370] sd 30:0:0:0: [sdb] tag#2 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
CRON[31391]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31406]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [25240.596445] sd 30:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [25240.596479] sd 30:0:0:0: [sdb] tag#24 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
CRON[31422]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31435]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [25840.681021] sd 30:0:0:0: [sdb] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [25840.681037] sd 30:0:0:0: [sdb] tag#25 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31452]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [26440.930199] sd 30:0:0:0: [sdb] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [26440.930220] sd 30:0:0:0: [sdb] tag#26 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31461]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31473]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [27040.733170] sd 30:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [27040.733186] sd 30:0:0:0: [sdb] tag#3 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31491]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31492]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [27640.759305] sd 30:0:0:0: [sdb] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [27640.759322] sd 30:0:0:0: [sdb] tag#27 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31513]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [28240.801000] sd 30:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [28240.801015] sd 30:0:0:0: [sdb] tag#4 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31522]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31537]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
]]>
I had several problems with my harddrives during burn in test. I believe I made it more stable by using an overpowered beQuiet ATX power supply.
But still after about 10 hours of burn in, one of the drives disappeared from system.

is there anything I could do about it, or should I try a different SATA adapter?
It's a ASM1166 based one.

thanks
JPT

Code:
kernel: [20815.037460] ata31.00: exception Emask 0x11 SAct 0xffffffff SErr 0x0 action 0x6 frozen
kernel: [20815.037488] ata31.00: irq_stat 0x48000008, interface fatal error

kernel: [20815.037498] ata31.00: failed command: WRITE FPDMA QUEUED
kernel: [20815.037504] ata31.00: cmd 61/00:00:00:b4:68/04:00:06:00:00/40 tag 0 ncq dma 524288 out
kernel: [20815.037504]          res 40/00:90:00:78:68/00:00:06:00:00/40 Emask 0x10 (ATA bus error)
kernel: [20815.037728] ata31.00: status: { DRDY }
(repeated  ~30 times)
kernel: [20815.038403] ata31.00: failed command: WRITE FPDMA QUEUED
kernel: [20815.038407] ata31.00: cmd 61/00:f8:00:94:68/04:00:06:00:00/40 tag 31 ncq dma 524288 out
kernel: [20815.038407]          res 40/00:90:00:78:68/00:00:06:00:00/40 Emask 0x10 (ATA bus error)
kernel: [20815.038425] ata31.00: status: { DRDY }

kernel: [20815.038438] ata31: hard resetting link
kernel: [20815.351579] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20815.351797] ata31.00: revalidation failed (errno=-2)
kernel: [20820.373226] ata31: hard resetting link
kernel: [20820.687580] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20820.687821] ata31.00: revalidation failed (errno=-2)
kernel: [20825.749275] ata31: hard resetting link
kernel: [20826.063641] ata31: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [20826.063877] ata31.00: revalidation failed (errno=-2)
kernel: [20826.063884] ata31.00: disable device
kernel: [20826.064897] ata31: EH complete

kernel: [20826.065122] sd 30:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=11s
kernel: [20826.065137] sd 30:0:0:0: [sdb] tag#16 CDB: opcode=0x2a 2a 00 06 68 b4 00 00 04 00 00
kernel: [20826.065145] I/O error, dev sdb, sector 107525120 op 0x1:(WRITE) flags 0x800 phys_seg 128 prio class 2
kernel: [20826.065414] sd 30:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [20826.065423] sd 30:0:0:0: [sdb] tag#16 CDB: opcode=0x2a 2a 00 02 c4 61 00 00 03 00 00
kernel: [20826.065427] I/O error, dev sdb, sector 46424320 op 0x1:(WRITE) flags 0x0 phys_seg 96 prio class 2
(repeated ~5 times)
kernel: [20826.066623] sd 30:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=11s
kernel: [20826.066634] sd 30:0:0:0: [sdb] tag#20 CDB: opcode=0x2a 2a 00 06 68 c6 80 00 05 40 00
kernel: [20826.066640] I/O error, dev sdb, sector 107529856 op 0x1:(WRITE) flags 0x4800 phys_seg 168 prio class 2
kernel: [20826.069242] md: super_written gets error=-5
kernel: [20826.069252] md/raid:md127: Disk failure on sdb1, disabling device.
kernel: [20826.069258] md/raid:md127: Operation continuing on 2 devices.

udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [21040.731415] scsi_io_completion_action: 38 callbacks suppressed
kernel: [21040.731431] sd 30:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [21040.731443] sd 30:0:0:0: [sdb] tag#20 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31257]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31271]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [21640.672280] sd 30:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [21640.672297] sd 30:0:0:0: [sdb] tag#21 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31286]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
CRON[31287]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31300]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [22240.621574] sd 30:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [22240.621590] sd 30:0:0:0: [sdb] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31319]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [22840.638787] sd 30:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [22840.638804] sd 30:0:0:0: [sdb] tag#22 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31329]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31344]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [23440.723283] sd 30:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [23440.723303] sd 30:0:0:0: [sdb] tag#1 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31360]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31361]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [24040.628704] sd 30:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [24040.628722] sd 30:0:0:0: [sdb] tag#23 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31384]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [24640.892353] sd 30:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [24640.892370] sd 30:0:0:0: [sdb] tag#2 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
CRON[31391]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31406]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [25240.596445] sd 30:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [25240.596479] sd 30:0:0:0: [sdb] tag#24 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
CRON[31422]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31435]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [25840.681021] sd 30:0:0:0: [sdb] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [25840.681037] sd 30:0:0:0: [sdb] tag#25 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31452]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [26440.930199] sd 30:0:0:0: [sdb] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [26440.930220] sd 30:0:0:0: [sdb] tag#26 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31461]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31473]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
kernel: [27040.733170] sd 30:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [27040.733186] sd 30:0:0:0: [sdb] tag#3 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31491]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
CRON[31492]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [27640.759305] sd 30:0:0:0: [sdb] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [27640.759322] sd 30:0:0:0: [sdb] tag#27 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31513]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
udisksd[1114]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST31500341AS_9VS4VMED: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
kernel: [28240.801000] sd 30:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
kernel: [28240.801015] sd 30:0:0:0: [sdb] tag#4 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
CRON[31522]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
systemd[1]: sysstat-collect.service: Deactivated successfully.
systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
CRON[31537]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
]]> <![CDATA[SATA hotplug not working?]]> https://forum.pine64.org/showthread.php?tid=18703 Fri, 15 Sep 2023 10:20:10 +0000 JPT223]]> https://forum.pine64.org/showthread.php?tid=18703
I set up a NAS but I realized SATA hot plug is not working.
Is it a limitation of my SATA adapter or doesn't it work in general?

Looks like I got a ASM1166 chip, but this is odd because the chip got 6 SATA lines but my card has 8 sockets.

this adapter is not optimal because it uses only 2 PCIe-Lanes.
I probably should by a new one. it was cheap, though Wink



thanks
JPT

Code:
01:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
       Subsystem: ASMedia Technology Inc. ASM1166 Serial ATA Controller
       Flags: bus master, fast devsel, latency 0, IRQ 50
       Memory at fa080000 (32-bit, non-prefetchable) [size=8K]
       Memory at fa082000 (32-bit, non-prefetchable) [size=8K]
       Expansion ROM at fa000000 [virtual] [disabled] [size=512K]
       Capabilities: [40] Power Management version 3
       Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
       Capabilities: [80] Express Endpoint, MSI 00
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [130] Secondary PCI Express
       Capabilities: [170] Latency Tolerance Reporting
       Capabilities: [200] L1 PM Substates
       Kernel driver in use: ahci
]]>
I set up a NAS but I realized SATA hot plug is not working.
Is it a limitation of my SATA adapter or doesn't it work in general?

Looks like I got a ASM1166 chip, but this is odd because the chip got 6 SATA lines but my card has 8 sockets.

this adapter is not optimal because it uses only 2 PCIe-Lanes.
I probably should by a new one. it was cheap, though Wink



thanks
JPT

Code:
01:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
       Subsystem: ASMedia Technology Inc. ASM1166 Serial ATA Controller
       Flags: bus master, fast devsel, latency 0, IRQ 50
       Memory at fa080000 (32-bit, non-prefetchable) [size=8K]
       Memory at fa082000 (32-bit, non-prefetchable) [size=8K]
       Expansion ROM at fa000000 [virtual] [disabled] [size=512K]
       Capabilities: [40] Power Management version 3
       Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
       Capabilities: [80] Express Endpoint, MSI 00
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [130] Secondary PCI Express
       Capabilities: [170] Latency Tolerance Reporting
       Capabilities: [200] L1 PM Substates
       Kernel driver in use: ahci
]]> <![CDATA[Can i use this Emmc for Rockpro 64]]> https://forum.pine64.org/showthread.php?tid=18678 Sat, 02 Sep 2023 12:38:24 +0000 Supratec]]> https://forum.pine64.org/showthread.php?tid=18678 https://www.reichelt.at/at/de/entwickler..._pdn&nbc=1

Is there an reason i cant use this emmc board for the rockpro 64?

Are there a difference between emmc boards at all?

Thank you]]> https://www.reichelt.at/at/de/entwickler..._pdn&nbc=1

Is there an reason i cant use this emmc board for the rockpro 64?

Are there a difference between emmc boards at all?

Thank you]]> <![CDATA[Which SATA card should I use my NAS server RAID5]]> https://forum.pine64.org/showthread.php?tid=18611 Wed, 16 Aug 2023 08:24:51 +0000 Louysa]]> https://forum.pine64.org/showthread.php?tid=18611
These are the card I am considering but right now:
this
this
this

Any recommendations? I just want to make sure it works before I buy it. I am open the alternatives.
Have a nice day.]]>
These are the card I am considering but right now:
this
this
this

Any recommendations? I just want to make sure it works before I buy it. I am open the alternatives.
Have a nice day.]]> <![CDATA[ROCKPro64 Battery Power Supply]]> https://forum.pine64.org/showthread.php?tid=18604 Mon, 14 Aug 2023 00:16:12 +0000 hoarfrosty]]> https://forum.pine64.org/showthread.php?tid=18604
Has anyone found a solution to battery power the RP64? I will run headless, so no additional accessories are needed (except for onboard or usb Wi-Fi adapter).

Power Input: 12V 3A or 5A type M 5.5mm OD/2.1mm ID barrel type DC Jack Power Supply.]]>
Has anyone found a solution to battery power the RP64? I will run headless, so no additional accessories are needed (except for onboard or usb Wi-Fi adapter).

Power Input: 12V 3A or 5A type M 5.5mm OD/2.1mm ID barrel type DC Jack Power Supply.]]> <![CDATA[Powering on the Rockpro64]]> https://forum.pine64.org/showthread.php?tid=18582 Sun, 06 Aug 2023 14:25:44 +0000 JPT223]]> https://forum.pine64.org/showthread.php?tid=18582
I am new here.
I've got a Rockpro64 2.1 running Armbian_23.5.1_Rockpro64_bookworm_current_6.1.30.
I am beginning to like it. Looks robust and got a ton of connectors.
It's going to be my NAS. 

But... How to I power it on?
The POWER button shuts it down, but it doesn't turn it on again.
Do the POWER/RESET headers behave the same as the physical buttons?

What is the current state of WoL?
I only found that it is unclear why it doesn't work.


There are a few cool ATX heads from Tim Tibbets:
https://www.tindie.com/products/tomtibbe...-module-4/

I am not sure if they would work with the Rockpro64.
He told me they backpower the raspberry PI through the GPIO connector, so via 5V I guess.


thanks

Jan]]>
I am new here.
I've got a Rockpro64 2.1 running Armbian_23.5.1_Rockpro64_bookworm_current_6.1.30.
I am beginning to like it. Looks robust and got a ton of connectors.
It's going to be my NAS. 

But... How to I power it on?
The POWER button shuts it down, but it doesn't turn it on again.
Do the POWER/RESET headers behave the same as the physical buttons?

What is the current state of WoL?
I only found that it is unclear why it doesn't work.


There are a few cool ATX heads from Tim Tibbets:
https://www.tindie.com/products/tomtibbe...-module-4/

I am not sure if they would work with the Rockpro64.
He told me they backpower the raspberry PI through the GPIO connector, so via 5V I guess.


thanks

Jan]]> <![CDATA[Any suggestions for USB audio devices?]]> https://forum.pine64.org/showthread.php?tid=18300 Sat, 03 Jun 2023 17:11:34 +0000 unixpoet]]> https://forum.pine64.org/showthread.php?tid=18300 ]]> ]]> <![CDATA[External Touchscreen via DP-Alt Mode]]> https://forum.pine64.org/showthread.php?tid=18190 Mon, 01 May 2023 18:29:57 +0000 soloquintett]]> https://forum.pine64.org/showthread.php?tid=18190 I am trying to connect my thinkvision m14t touchscreen to the rockpro64. For the life of me, I can't get it to work.
Here is what i did:

I connected the screen to an external usb-c power source. Then connected to the rock. The wacom input source is recognized (until the screen goes into standby), but no Display is detected.

I tried

- Armbian
- Debian
- Manjaro generic
- Manjaro rockpro64 (gitlab)
- Manjaro with the old 5.7 Kernel for the pinebook pro (link) (this Kernel specifically has a patch to make DP-Alt mode work, and boots just fine on the rockpro64)
- Manjaro pinebook-pro image does not seem to boot.

I also flipped the usb-c wire multiple times.

What actually worked:
A mysterious wire from club3d (bi-directional usb-c to hdmi) actually gave the me video output from the rocks hdmi port. However, the screen needs an additional power source from its other usb-c port. The rock can't provide enough power from usb. So there was no way to make the wacom input available.

What i am thinking to do:
- Can i inject external power into an usb-c wire to power the rock and connect it to the rock at the same time? I already tried to do this with an usb-c dongle connected to the rock, which has external power. (Power is passed on, but no wacom input recognized by rock)
- Could i use a PCI- thunderbolt like the Gigabyte GC-TITAN Ridge to power and connect everything with a single usb-c wire? (I have a feeling the gpu won't send the video to the card, if the card were even to be supportet)

I also bought a Pinebook Pro. I thought i read about someone having connected the thinkvision m14t to it. But i could not get it to work either (tried many distros)

Thanks for any Info on this.]]> I am trying to connect my thinkvision m14t touchscreen to the rockpro64. For the life of me, I can't get it to work.
Here is what i did:

I connected the screen to an external usb-c power source. Then connected to the rock. The wacom input source is recognized (until the screen goes into standby), but no Display is detected.

I tried

- Armbian
- Debian
- Manjaro generic
- Manjaro rockpro64 (gitlab)
- Manjaro with the old 5.7 Kernel for the pinebook pro (link) (this Kernel specifically has a patch to make DP-Alt mode work, and boots just fine on the rockpro64)
- Manjaro pinebook-pro image does not seem to boot.

I also flipped the usb-c wire multiple times.

What actually worked:
A mysterious wire from club3d (bi-directional usb-c to hdmi) actually gave the me video output from the rocks hdmi port. However, the screen needs an additional power source from its other usb-c port. The rock can't provide enough power from usb. So there was no way to make the wacom input available.

What i am thinking to do:
- Can i inject external power into an usb-c wire to power the rock and connect it to the rock at the same time? I already tried to do this with an usb-c dongle connected to the rock, which has external power. (Power is passed on, but no wacom input recognized by rock)
- Could i use a PCI- thunderbolt like the Gigabyte GC-TITAN Ridge to power and connect everything with a single usb-c wire? (I have a feeling the gpu won't send the video to the card, if the card were even to be supportet)

I also bought a Pinebook Pro. I thought i read about someone having connected the thinkvision m14t to it. But i could not get it to work either (tried many distros)

Thanks for any Info on this.]]> <![CDATA[Issues with several boards]]> https://forum.pine64.org/showthread.php?tid=18109 Wed, 05 Apr 2023 23:58:32 +0000 geekboy01]]> https://forum.pine64.org/showthread.php?tid=18109