Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: CtdeBlesse on May 23, 2012, 11:48:21 AM

Title: sme won't make partition bigger than 696gb
Post by: CtdeBlesse on May 23, 2012, 11:48:21 AM: I am making a affa backup server for all my smeservers. My first try was with SME installed on a "older" 120gb IDE disk and than 4x1gb in software raid 5. but one after the other was trown out of the software raid array so i bought a hardware raidcontroller. Here i made the raid array on with 4x1tb disks (arround 2.7tb usable). but now i am trying to make one big partition on it (array is /dev/sda). but with the default value's the sda1 partion won't get any bigger than 696gb. I googled for a couple of houres, but i didn't find something that works.

This is the commands

Code: [Select]
[root@dbiom-bu-ex ~]# fdisk /dev/sda The number of cylinders for this disk is set to 364602. There is nothing wrong with that, but it is larger than 1024, and works with certain setups cause problems with: 1) software that runs at startup (eg, old versions of LILO) 2) boot and partitioning software from other operating systems, such as FDISK DOS and OS / 2 FDISK Command (m for help): p Disk / dev / sda: 2998.9 GB, 2998960914432 bytes 255 heads, 63 sectors / track, 364602 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Command (m for help): n command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-97253, default 1): Using default value 1 Last cylinder or + size or + or + sizeM sizeK (1-97253, default 97253): Using default value 97253 Command (m for help): w The partition table has changed! Calling ioctl () to re-read partition table. Syncing disks.
I am not a sme (linux) expert, so i hope that there is somebody that can help me further, of give me a "kick" in the right direction.

++EDIT++

Translated the command to english
Title: Re: sme won't make partition bigger than 696gb
Post by: Stefano on May 23, 2012, 11:53:25 AM: We don't speak dutch.. so you'd better translate, thank you

anyway, on one server I have:
Code: [Select]
[root@server ~]# fdisk -l Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 fd Linux raid autodetect /dev/sda2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 fd Linux raid autodetect /dev/sdb2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 13 104391 fd Linux raid autodetect /dev/sdc2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdd: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 * 1 13 104391 fd Linux raid autodetect /dev/sdd2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/md1: 106 MB, 106823680 bytes 2 heads, 4 sectors/track, 26080 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 4500.5 GB, 4500576534528 bytes 2 heads, 4 sectors/track, 1098773568 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md2 doesn't contain a valid partition table Disk /dev/dm-0: 4497.9 GB, 4497938055168 bytes 2 heads, 4 sectors/track, 1098129408 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2080 MB, 2080374784 bytes 2 heads, 4 sectors/track, 507904 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-1 doesn't contain a valid partition table
Title: Re: sme won't make partition bigger than 696gb
Post by: CtdeBlesse on May 23, 2012, 12:09:34 PM: Quote from: Stefano on May 23, 2012, 11:53:25 AM
We don't speak dutch.. so you'd better translate, thank you

anyway, on one server I have:
Code: [Select]
[root@server ~]# fdisk -l Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 fd Linux raid autodetect /dev/sda2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 fd Linux raid autodetect /dev/sdb2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 13 104391 fd Linux raid autodetect /dev/sdc2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/sdd: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 * 1 13 104391 fd Linux raid autodetect /dev/sdd2 14 182401 1465031610 fd Linux raid autodetect Disk /dev/md1: 106 MB, 106823680 bytes 2 heads, 4 sectors/track, 26080 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 4500.5 GB, 4500576534528 bytes 2 heads, 4 sectors/track, 1098773568 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md2 doesn't contain a valid partition table Disk /dev/dm-0: 4497.9 GB, 4497938055168 bytes 2 heads, 4 sectors/track, 1098129408 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2080 MB, 2080374784 bytes 2 heads, 4 sectors/track, 507904 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-1 doesn't contain a valid partition table

See the translation.

But you got 3x1500gb in softwareraid x??? don't know if that makes much of a differents.

And if i go over the default last cylinder of 97253 it says the is out of range

Code: [Select]
Last cylinder or + size or + or + sizeM sizeK (1-97253, default 97253): 182401 Value out of range.
Title: Re: sme won't make partition bigger than 696gb
Post by: Stefano on May 23, 2012, 12:52:07 PM: Quote from: CtdeBlesse on May 23, 2012, 12:09:34 PM
But you got 3x1500gb in softwareraid x??? don't know if that makes much of a differents.

4x1.5 TB in sw raid5 no spare

SME was setup on it without any problem

If I understand correctly, you have an existing SME on a 120 GB ide disk (i.e. hdA) and you are trying to add a raid array (sdA, about 3TB).. but you have some problems to create partitions on sdA.. right?
Title: Re: sme won't make partition bigger than 696gb
Post by: CtdeBlesse on May 23, 2012, 01:02:39 PM: Quote from: Stefano on May 23, 2012, 12:52:07 PM
4x1.5 TB in sw raid5 no spare

SME was setup on it without any problem

If I understand correctly, you have an existing SME on a 120 GB ide disk (i.e. hdA) and you are trying to add a raid array (sdA, about 3TB).. but you have some problems to create partitions on sdA.. right?

Yes, that is about right. but i can not create partitions bigger than 696gb....

My first try was with 4x1tb in software raid, but this failed hard... :( so that is why i use a hardware raid controller.

(more information about server ---->its a rack server with room for 8x sata drives, these drives are connected to a LSI MegaRAID 9260-8i. If i got this working i can copy the files from my old backup server tot this one and create another raid 5 array with 4x1tb. that is why i used a "older" IDE drive, so i can use all the 8 sata bays. second raid array is for tempory storage)
Title: Re: sme won't make partition bigger than 696gb
Post by: Stefano on May 23, 2012, 01:15:01 PM: since you will keep SME on the ide disk, you could try to run lvm directly on sda (pvcreate /dev/sda) and then create the f.s. on the lv..

google will tell you more