[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

facing problem "Partition 2 does not start on physical sector boundary"



i have baught a new HD with same size and capacity. and trying to copy partition via command "sfdisk -d /dev/sda | sfdisk --force /dev/sdb"

above command work well. however one confusing part it   "fdisk -l /dev/sdb" is giving some information which i am worried about.

i think it souldnt give me this error as the harddrives are same specs and even vendor is same. can anyone kindly share why it is giving me this message. should i worried about the stability of my raid as it is going to be in production soon and i do not wanna loos my data.

here is the detail .

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004623a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1228     9862144   fd  Linux raid autodetect
/dev/sda2            1229        4268    24413185    5  Extended
/dev/sda3            4268       60802   454108160   fd  Linux raid autodetect
/dev/sda5            1229        4268    24413184   fd  Linux raid autodetect

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0004623a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        1228     9862144   fd  Linux raid autodetect
/dev/sdb2            1229        4268    24413185    5  Extended
Partition 2 does not start on physical sector boundary.
/dev/sdb3            4268       60802   454108160   fd  Linux raid autodetect
/dev/sdb5            1229        4268    24413184   fd  Linux raid autodetect



Reply to: