on A20 board bullseye cannot detect ssd

[dmalik]

cfdisk: cannot open /dev/sda: No such file or directory (i boot on sd card with this image http://images.olimex.com/release/a20/ with base or minimal version !)


With boot on sd card with jessie, i can run on the ssd !

Help me
Thank's
excuse my bad english

[LubOlimex]

Are you sure it is sda? Try with fdisk -l to see all listed devices. Did you first mount it before trying to access it?

I tested the base Linux image with a LIME2 board and SSD here and it works fine. The disk I used here was FAT32 formatted and I powered it via the LIME2 board using the sata cable set.

If the issue remains then it is probably something at your side - cabling, powering, disk formatting, etc, etc.

[dmalik]

boot witn bullsey on sd card

sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk0: 14.41 GiB, 15476981760 bytes, 30228480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x50a7dba6

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1      20480 30228479 30208000 14.4G 83 Linux

[LubOlimex]

It is not the problem with the Linux image since with the same software I see my SSD. So it is something else that is different between the two Linux images, maybe newer image requires slightly more power? How do you power the SSD and the LIME2 board?

[dmalik]

I don't think it's a power supply problem. I booted with a debian 11 for arm (I don't know where I found it)
with the bullseye version of olimex I have

Code Select Expand

dmesg | grep -i ata1
 ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 44
 ata1: SATA link down (SStatus 0 SControl 300)
with the other debian 11 version I have

Code Select Expand

dmesg | grep -i ata1
ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 44
ata1: SATA link up 3.0 Gbps (Sstatus 123 Scontrol 300)
ata1.00: ATA8: KINGSTON SV300S37A60G, max UDMA/133
ata1.00: 117231408 sectors, multi 1 : LBA48 NCQ (depth 32)
ata1.00: configured for UDMA/133


I also found this but I don't know what to do with it. It is beyond my knowledge
https://www.olimex.com/forum/index.php?topic=2602.0

thank's

[dmalik]

I bought the power supply with the A20 micro at olimex : 12v 1A

[LubOlimex]

The power supply required can be altered by software means. It is possible that the newer releases are set to require more power (by setting CPU running at higher speeds for example).

We don't have 12V/1A (12W) power supply. We have 12V/0.5A (6W) power supply. And it is insufficient for powering the board and the hard disk.

Your KINGSTON SV300S37A60G hard disk consumes more than 2W when writing (which means 0.4A at 5V). Here are the specs:

https://www.kingston.com/datasheets/sv300s3_us.pdf

Consider another power supply with more amperage.

[dmalik]

In the bottom of a drawer I only found a 12v 1.25A power supply
Unfortunately it doesn't work any better

[dmalik]

I just received my new power supply : 12v 3A
I can't see the ssd disk any better :
"failed to detect SATA device"

[dmalik]

I just changed the sd card with a debian from freedombox. (bullseye 11.0).
here is the fdisk -l[/i]

Code Select Expand

Disk /dev/mmcblk0: 14,48 GiB, 15552479232 bytes, 30375936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb2a4a0c0

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *      8192   270335   262144  128M 83 Linux
/dev/mmcblk0p2      270336 30375935 30105600 14,4G 83 Linux


Disk /dev/sda: 55,9 GiB, 60022480896 bytes, 117231408 sectors
Disk model: KINGSTON SV300S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9718271f

Device     Boot Start       End   Sectors  Size Id Type
/dev/sda1        8192     65535     57344   28M  c W95 FAT32 (LBA)
/dev/sda2  *    65536 117231407 117165872 55,9G 83 Linux


Disk /dev/zram0: 495,39 MiB, 519454720 bytes, 126820 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
I  read and write normally on the hard disk!
The original bullseye version of Olimex still does not detect the hard disk
note: my power supply is now 12v 3A .

[LubOlimex]

Hmm, this is interesting. Can you post a full boot log from the start, I think there is slight chance that your A20-OLinuXino-MICRO doesn't get properly recognized by the Linux. How is it listed at the start of boot - is it the proper board and board revision listed?

It is probably a software issue but it is very hard to debug this issue when it doesn't exist here. Googling the error you get( "ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 44 ata1: SATA link down (SStatus 0 SControl 300)) provides a lot of results. Most of them conclude that it is either insufficient supply or improper clock (but we can rule out insufficient supply)

https://discuss.freedombox.org/t/solved-olimex-bay-ssd-512gb-sata-link-down-both-stable-weekly-images/1808/3

https://forum.armbian.com/topic/1107-sata-down-on-banana-pro-w-452-sunxi/#comment-8412

[dmalik]

command dmesg return with bullsey minimal
file
with a bullseye that allows you to work on the ssd
file_2

[LubOlimex]

Umm, yes! It appears like the board is recognized as A20-OLinuXino-LIME:

"OF: fdt: Machine model: Olimex A20-OLinuXino-LIME"

And you have A20-OLinuXino-MICRO right? This is a problem. You will need to manually set the board to A20-OLinuXino-MICRO and its exact revision.

You need to interrupt the boot process and stay in u-boot. This is done early in the boot process and you might need USB-serial connection to the board. Refer to chapter "7.1 U-boot tools"

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

Let me know if something is not clear.

[dmalik]

yes, but look at the same line in the other file and it is recognised as
OF: fdt: Machine model: Olimex A20-Olinuxino Micro
with the olimex bullseye minimal :

Code Select Expand

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.105-olimex (root@runner-cpbkaozn-project-1-concurrent-0) (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #140134 SMP Wed Sep 28 14:02:52 UTC 2022
[    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model:Olimex A20-OLinuXino-LIME

with bullseye armp

Code Select Expand

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.0-21-armmp (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.162-1 (2023-01-21)
[    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: [Olimex A20-Olinuxino Micro
This is far beyond my competence
At what level is it: code on the card or code on the bullseye?
Thanks again for your interest

[LubOlimex]

Yes, in the image that the SSD is not working - the board is improperly recognized. And in the image the SSD is working - the board is properly recognized.

So you have to interrupt u-boot and define the board manually. Refer to chapter "7.1 U-boot tools" from this document:

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf