Hello

 

I need to change a drive in the Helios64, and so I bought a new WD 2TB drive.

Using a WD My Book 111D USB enclosure, I have partitioned, formatted and copied the data from the old drive. But when I change the drives to put the new one in the Helios64, the drive appears unformatted. See below.

I can't understand what's happening, when I plug it back through USB everything is back to normal.

Does the partitioning through USB differ somehow???

It appears as if the partition table "stays in the USB enclosure", which doesn't make sense for me.

Is there something to try?

Do I have to start again the process in the NAS enclosure? I don't want to spend 6+ hours copying everything back...

 

I'm using armbian 5.10.35-rockchip64, and OMV 5.

The disk appears in /dev/sda. When connected through SATA:

 

eclapton@helios64:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda            8:0    0   1,8T  0 disk  
sdb            8:16   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sdc            8:32   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sdd            8:48   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sde            8:64   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
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

 

When connected through USB:

 

eclapton@helios64:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda            8:0    0   1,8T  0 disk  
├─sda1         8:1    0   1,2T  0 part  
└─sda2         8:2    0   613G  0 part  
sdb            8:16   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sdc            8:32   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sdd            8:48   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sde            8:64   0 931,5G  0 disk  
└─md0          9:0    0   2,7T  0 raid5 /srv/dev-disk-by-label-Backup
sr0           11:0    1    30M  0 rom   
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 

 

 

Maybe encryption is enabled on mybook and that is why removed from the enclosure it cannot be read?

There’s no option for that, it’s just an enclosure. The drives formatted from the helios64, in ext4.

An encription would cause even the partition table to disappear??

Depends on implementation which can be just guessed on proprietary stuff.

Gonna write down the partition table again.. lets see...

Funny thing is, now fdisk says :

 

Disk /dev/sda: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFAX-68F
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x899593b4

 

But before (I have a txt copy) it said:

 

Disk /dev/sdf: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors

Disk model: My Book 111D    

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: gpt

Disk identifier: A82DBF47-D710-4648-96E9-74B44F5FCA0F

 

Device          Start        End    Sectors   Size Type

/dev/sdf1        2048 2441406250 2441404203   1.1T Linux filesystem

/dev/sdf2  2441406464 3906963422 1465556959 698.9G Linux filesystem

 

Physical sector size is now different???? Does that make sense to you?

 

Thanks

Looking up on Google @Werner was right: the WD My book has a chip to encrypt the drive. 
Wiped it up and started anew. 
Thanks!!