Errors from cfdisk with new exterior USB back-up drive

I've grabbed an HP SimpleSave sd500a back-up drive. This is a 2.5", 500GB drive. It has a strange CD - like partition, yet or else appears to have a WD Scorpio Blue disk. It appears that the CD - like partition is applied in the unit is firmware, yet I've no other way to be particular of this.

I'm repartitioning the drive for the very first time. When trying to open the drive making use of cfdisk /dev/sdb, it leaves with standing 4 after outputting this mistake message:

FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder

sfdisk -l has the ability to result details on the drive without mistakes:

Disk /dev/sdb: 60715 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdb1          0+  60715-  60716- 487699456    7  HPFS/NTFS
/dev/sdb2          0       -       0          0    0  Empty
/dev/sdb3          0       -       0          0    0  Empty
/dev/sdb4          0       -       0          0    0  Empty

Is the mistake from cfdisk any kind of factor to examine the security of the drive or the compatibility of its firmware?

2019-05-18 23:40:24
Source Share
Answers: 2

Supposing there isn't anything of value therein, remove the dividings and also create a new one (either ext3 or ext4), and also run e2fsck -c on it to examine if it has negative blocks. If that passes, and also you take place to be paranoid, run e2fsck -cc to do an extra detailed (and also much looonger) examination.

2019-05-21 09:15:46

cfdisk reviews the partition table of the tool at start-up, it will certainly exit if the geometry of a partition is incorrect. You can compel cfdisk to not read the existing partition table by including -z:

cfdisk -z /dev/sdb

This is a cfdisk details actions, fdisk will certainly show a comparable mistake yet will not exit. The security of the drive is not influenced, it is simply a partition concern.

Conversely make use of a partition device like fdisk, parted or gparted.

I've simply examined my very own partition and also the first one (/boot) additionally reported this mistake. I never ever had any kind of troubles with it.

2019-05-21 09:08:39