Hi to all,
after the 16GB of the eMMC is slowly reaching my limits, I installed a 128GB M.2 SSD and wanted to use the kobol tutorial to transfer the system data on it...
https://wiki.kobol.io/helios64/install/transfer/#transfer-rootfs-from-emmc-to-sata-or-usb

... unfortunately I see at position 4 only /dev/md0 instead of the M.2 Sata on /dev/sda

 

 

root@helios64:/dev# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda            8:0    0 119.2G  0 disk
sdb            8:16   0   3.7T  0 disk
└─md0          9:0    0   7.3T  0 raid5 /srv/dev-disk-by-label-nas
sdc            8:32   0   3.7T  0 disk
└─md0          9:0    0   7.3T  0 raid5 /srv/dev-disk-by-label-nas
sdd            8:48   0   3.7T  0 disk
└─md0          9:0    0   7.3T  0 raid5 /srv/dev-disk-by-label-nas
mmcblk2      179:0    0  14.6G  0 disk
└─mmcblk2p1  179:1    0  14.4G  0 part  /
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
root@helios64:/dev#

 

does anyone know what my error is here?
I use OMV and have 3 hard disk running in RAID 5.
Previously the hard drives were connected to SATA 1, SATA 3 and SATA 5.
I had to change the hard drive on SATA 1 to 2, because the M.2 needs the SATA 1.
Is it perhaps because of this?

Long shot. In the wiki on the corresponding screenshot you have the choice between /dev/sda1, /dev/sdb1 and /dev/sdc1, which are all partitions. Your sda isn't partitioned. Nor is your md0, but maybe the algorithm simply skips all device nodes which does not end in a number.

So put a partition on your disk.

@RockBian I had already added a partition to the SSD, nevertheless I see only the OMV RAID5 partition...

 

root@helios64:~# parted -l
Model: ATA NT-128 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
 1      0.00B  128GB  128GB  ext4

 

A partition that start on byte 0? That's fishy. I think you don't have a partition on sda, only a filesystem.

@RockBian you are right, the problem was the missing partition.
I forgot to let fdsik create the configured partition at the end with "w".
Now it worked and I could transfer the installation from the eMMC to the SSD.