A20 with buster : hd not recognise

Started by dmalik, January 20, 2021, 10:37:12 am

Previous topic - Next topic

dmalik

I change Debian jessie to buster (A20-OLinuXino-buster-base-20201217-194545.img)
I can not see my hard diskThnk's for reply
Daniel

LubOlimex

Try rebooting. What does fdisk -l returns?

What is your hard disk exactly? How is it powered?
Technical support and documentation manager at Olimex

dmalik

fdisk -l with debian buster
sudo fdisk -l
[sudo] password for olimex:
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.5 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: 0x58ca766b

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1      20480 30375935 30355456 14.5G 83 Linux

with Debian Jessie fdisk -l
sudo fdisk -l

Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 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: 0x000999ee

Device     Boot Start       End   Sectors  Size Id Type
/dev/sda1        2048 117229567 117227520 55.9G 83 Linux

Disk /dev/mmcblk0: 14.4 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: 0x6f20736b

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1       2048    34814    32767   16M 83 Linux
/dev/mmcblk0p2      34816 30228479 30193664 14.4G 83 Linux


The HD is one SSD
I boot the A20 with sd card
Thank you for the help
Daniel

dmalik

I change and install a new Debian Buster version :
Quote from: undefinedA20-OLinuXino-buster-base-20201217-194545.img
fdisk -l command not found my ssd disk !
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.5 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: 0x58ca766b

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1      20480 30375935 30355456 14.5G 83 Linux


LubOlimex

Thanks for the report, it seems there is a problem indeed. Will be fixed in next release.
Technical support and documentation manager at Olimex

dmalik

Thank you for the answer.
How long before the next version is planned?
Daniel

LubOlimex

Probably later this week or next week. The testing image is done but we have to perform some basic testing before moving the image to release. We don't want to introduce bigger and more severe bugs, hence we have to test empirically most peripherals.
Technical support and documentation manager at Olimex