[DRBD-user] Problem with disk geometry

Theophanis Kontogiannis theophanis_kontogiannis at yahoo.gr
Fri Sep 5 14:34:09 CEST 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hello All,



Though I have posted this to centos hardware forum, I also post it here
since it affects my cluster and drbd setup (the drbd complains that "drbd0:
The peer's disk size is too small!", so the LV cannot become available, so
the cluster services on node-1 do not start).


I have 2.6.18-92.1.10.el5.centos.plus and fdisk (util-linux 2.13-pre7)

My old 80GB disk failed and I had replaced.
However the vendor replaced it with a different model.
My old disk was WD800JB-00JJC0 but the new one is a WD800JB-22JJC0.
Since I must have the new disk with the same partitions as the old one
(apart from RAID-1 software, I also have installed DRBD mirrored with a
second node), I use fdisk to partition it.

But there start the problems:

1. BIOS reports C38308, H16, S255, Landing Zone 38307, Precomp 0

2. Kernel reports hda: 156301488 sectors (80026 MB) w/8192KiB Cache,
CHS=65535/16/63, UDMA(100)

3. fdisk reports 

Disk /dev/hda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

and the disk turns up like:

Device Boot Start End Blocks Id System
/dev/hda1 * 1 208 104800+ fd Linux raid autodetect
/dev/hda2 209 20554 10254384 fd Linux raid autodetect
/dev/hda3 20555 24500 1988784 83 Linux
/dev/hda4 24501 155061 65802744 83 Linux


The result is that I cannot create the same layout on the disk as the old
disk.
The old disk was like that:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 fd Linux raid autodetect
/dev/hda2 14 1288 10241437+ fd Linux raid autodetect
/dev/hda3 1289 1543 2048287+ 82 Linux swap / Solaris
/dev/hda4 1544 9729 65754045 83 Linux

Any help?

Why the is the new disk known in different ways by BIOS, kernel and fdisk?
And how can I fix this?


Thank you All for your Time,
Theophanis Kontogiannis

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20080905/15868019/attachment.htm>


More information about the drbd-user mailing list