On 01/07/15 05:38 AM, Pascal Hambourg wrote:
Gary Dale a écrit :
On 30/06/15 02:17 PM, Pascal Hambourg wrote:
What I would do is shrink partition 5 by 100M then create a new ef02
partition in the freed space.
Why on earth would you want to do such a dangerous and useless thing ?
As I wrote in
Gary Dale garyd...@torfree.net wrote:
On 01/07/15 10:39 AM, Sven Hartge wrote:
Gary Dale garyd...@torfree.net wrote:
On 30/06/15 07:04 PM, Lisi Reisz wrote:
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter.
Gary Dale a écrit :
On 30/06/15 02:36 PM, Muhammad Yousuf Khan wrote:
should i create partition 2 of a size of 1 GB. and make it as a boot
partition and install grup on that partition. [...]
I've stopped using separate boot partitions since wheezy, which allowed
systems to boot directly
Thanks Gary and Pascal and all for your very informative inputs and
support. now it works and my drive is bootable now.
however one thing i have notice which is also off the topic is that i can
not boot my new GPT hard drive with supergrub CD. when i reaches where
kernel loads it restart
Gary Dale a écrit :
On 30/06/15 02:56 PM, Pascal Hambourg wrote:
You don't need to update the BIOS. All a sensible BIOS has to do is load
the boot code in the MBR, regardless of the partition table style.
That's not true. I have a Dell laptop that needed a BIOS update after I
switched it to
Sven Hartge a écrit :
I had an interesting problem once, where I upgraded a server from
Squeeze to Wheezy. This server had LVM on MD-RAID and so the core.img
has to include the LVM- and MD-RAID drivers in addition to the ext3
code.
With Squeeze this core.img just so fitted into the 31744
Gary Dale a écrit :
On 30/06/15 02:17 PM, Pascal Hambourg wrote:
What I would do is shrink partition 5 by 100M then create a new ef02
partition in the freed space.
Why on earth would you want to do such a dangerous and useless thing ?
As I wrote in a previous message, there is plenty of
Pascal Hambourg pas...@plouf.fr.eu.org wrote:
Sven Hartge a écrit :
I had an interesting problem once, where I upgraded a server from
Squeeze to Wheezy. This server had LVM on MD-RAID and so the core.img
has to include the LVM- and MD-RAID drivers in addition to the ext3
code.
With
Gary Dale garyd...@torfree.net wrote:
On 30/06/15 07:04 PM, Lisi Reisz wrote:
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter. But out of 2T???
Agreed. I remember having a 100M /boot partition which was
On Wed, 01 Jul 2015, Gary Dale wrote:
The size of the RAID array is set by the smallest partition so if you
want to be able to boot from either drive, then putting the ef02
partition in the free space on the new drive means that you will
either not be able to boot from the old drive should the
On 01/07/15 10:39 AM, Sven Hartge wrote:
Gary Dale garyd...@torfree.net wrote:
On 30/06/15 07:04 PM, Lisi Reisz wrote:
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter. But out of 2T???
Agreed. I remember
On 01/07/15 02:43 AM, Muhammad Yousuf Khan wrote:
Partition is created and grub is installed as instructed in the thread.
Also Grub is installed now.
should i make any config changes ( or not )in the /boot/grub/ directory?
Number Start (sector)End (sector) Size Code Name
1
On Wed, 01 Jul 2015, Gary Dale wrote:
You missed the point that this would require different partition
tables on the two drives.
I saw and rejected the point because you do not need different partition
tables, as is illustrated below from my original message.
% diff -u (sudo fdisk -l /dev/sda)
On 01/07/15 07:01 PM, Arno Schuring wrote:
Date: Wed, 1 Jul 2015 18:41:35 -0400
From: garyd...@torfree.net
On 01/07/15 03:24 PM, Don Armstrong wrote:
On Wed, 01 Jul 2015, Gary Dale wrote:
The size of the RAID array is set by the smallest partition so if you
want to be able to boot from
On 01/07/15 10:12 PM, Don Armstrong wrote:
On Wed, 01 Jul 2015, Gary Dale wrote:
You missed the point that this would require different partition
tables on the two drives.
I saw and rejected the point because you do not need different partition
tables, as is illustrated below from my original
On 01/07/15 03:24 PM, Don Armstrong wrote:
On Wed, 01 Jul 2015, Gary Dale wrote:
The size of the RAID array is set by the smallest partition so if you
want to be able to boot from either drive, then putting the ef02
partition in the free space on the new drive means that you will
either not be
Date: Wed, 1 Jul 2015 18:41:35 -0400
From: garyd...@torfree.net
On 01/07/15 03:24 PM, Don Armstrong wrote:
On Wed, 01 Jul 2015, Gary Dale wrote:
The size of the RAID array is set by the smallest partition so if you
want to be able to boot from either drive, then putting the ef02
Partition is created and grub is installed as instructed in the thread.
Also Grub is installed now.
should i make any config changes ( or not )in the /boot/grub/ directory?
Number Start (sector)End (sector) Size Code Name
12048 7813119 3.7 GiB FD00
Hi.
On Tue, Jun 30, 2015 at 11:17:11PM -0400, Gary Dale wrote:
On 30/06/15 07:04 PM, Lisi Reisz wrote:
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter. But out of 2T???
Lisi
Agreed. I remember having
On 30/06/15 07:04 PM, Lisi Reisz wrote:
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter. But out of 2T???
Lisi
Agreed. I remember having a 100M /boot partition which was always
running out of space if I
Thanks Arno, Pascal and Gary with your input i manage to copy the partition
to new drive in GPT format and my all drives (mdadm devices) are synced
now.
I have 4 RAID1 Partitions for all for different purpose.
md1 : active raid1 sdb5[2] sda5[0]
9763768 blocks super 1.2 [2/2] [UU]
md3 :
Am 2015-06-30 15:58, schrieb Muhammad Yousuf Khan:
number 5 is the swap partition as i know it from size. and i also
attached that partition to my mdadm drive md1 which was set to swap
by
me and it is successfully synced. now my question is as i can not see
the extended partition type in the
Muhammad Yousuf Khan a écrit :
Thanks Arno, Pascal and Gary with your input i manage to copy the partition
to new drive in GPT format and my all drives (mdadm devices) are synced
now.
I have 4 RAID1 Partitions for all for different purpose.
md1 : active raid1 sdb5[2] sda5[0]
Christian Seiler a écrit :
So if you want to boot from GPT partitions, you need to have a
small-ish (I typically use 100-200 MB or so) FAT32 partition of
the BIOS Boot Partition type at the beginning of the drive.
That's where the boot loader will be installed. (And you need
EFI to boot
pas...@plouf.fr.eu.org wrote:
Christian Seiler a écrit :
So if you want to boot from GPT partitions, you need to have a
small-ish (I typically use 100-200 MB or so) FAT32 partition of
the BIOS Boot Partition type at the beginning of the drive.
That's where the boot loader will be installed.
On 30/06/15 09:58 AM, Muhammad Yousuf Khan wrote:
Thanks Arno, Pascal and Gary with your input i manage to copy the
partition to new drive in GPT format and my all drives (mdadm devices)
are synced now.
I have 4 RAID1 Partitions for all for different purpose.
md1 : active raid1 sdb5[2]
On Tuesday 30 June 2015 11:55:20 Pascal Hambourg wrote:
Christian Seiler a écrit :
So if you want to boot from GPT partitions, you need to have a
small-ish (I typically use 100-200 MB or so) FAT32 partition of
the BIOS Boot Partition type at the beginning of the drive.
That's where the
Arno Schuring a écrit :
As Pascal has said, the easiest is to create a new partition in the
free space before partition 1 (sectors 34-2047). Make sure it has the
correct type for a Bios Boot Partition (gdisk type ef02, with parted
you need to set the Bootable flag).
Actually no. Parted uses
Gary Dale a écrit :
Number Start (sector)End (sector) Size Code Name
12048 7813119 3.7 GiB FD00 Linux RAID
327344896 1980469247 931.3 GiB FD00 Linux RAID
4 1980469248 2930276351 452.9 GiB FD00 Linux RAID
5
Sorry Arno my last message was mistakenly sent to you only and not the list.
Thanks all for you comments.
Pascal thanks for the tip about extending one of the partition and using
the free space i will do so but for now my primary problem is to create a
boot partition so that i can boot and
Hi again,
Date: Tue, 30 Jun 2015 18:58:36 +0500
From: sir...@gmail.com
but there are few confusions. actually in my old drive. there was a
extended partition for SWAP. however when i copy the partition table
with gdisk x and u option it created the file successfully however.
i
Muhammad Yousuf Khan a écrit :
Pascal thanks for the tip about extending one of the partition and using
the free space i will do so but for now my primary problem is to create a
boot partition so that i can boot and replace the old 1.5 TB with 2TB
drive. as you said boot partition in GPT can
On 30/06/15 02:56 PM, Pascal Hambourg wrote:
Gene Heskett a écrit :
On Tuesday 30 June 2015 11:55:20 Pascal Hambourg wrote:
Actually GPT does not use *all* that space and GRUB could still find
out the available unused space. But the GPT partition table could grow
and overwrite the beginning of
On Tue, 30 Jun 2015, Muhammad Yousuf Khan wrote:
should i create partition 2 of a size of 1 GB. and make it as a boot
partition and install grup on that partition. do you think performing
these steps will do the job. or i have to more in order to boot my New
2TB GPT drive.
Just create a new
On 30/06/15 02:36 PM, Muhammad Yousuf Khan wrote:
Sorry Arno my last message was mistakenly sent to you only and not the
list.
Thanks all for you comments.
Pascal thanks for the tip about extending one of the partition and
using the free space i will do so but for now my primary problem is
On Tue, 30 Jun 2015, Don Armstrong wrote:
Just create a new partition before the 2048 sector to use as a grub
bios_grub partition.
For example:
sudo gdisk /dev/sda
p = print
n = new partition
number = 2
start sector = 34 (or as close to zero as you can get)
end sector = 2047
code =
Ramadan Kareem Yousuf.
What I would do is shrink partition 5 by 100M then create a new ef02
partition in the freed space. This should be completely safe since it is
just a swap partition and contains no permanent data.
Do this on both drives after stopping swap (swapoff) then
Gene Heskett a écrit :
On Tuesday 30 June 2015 11:55:20 Pascal Hambourg wrote:
Actually GPT does not use *all* that space and GRUB could still find
out the available unused space. But the GPT partition table could grow
and overwrite the beginning of the bootloader, so I guess it was
On 30/06/15 02:17 PM, Pascal Hambourg wrote:
Gary Dale a écrit :
Number Start (sector)End (sector) Size Code Name
12048 7813119 3.7 GiB FD00 Linux RAID
327344896 1980469247 931.3 GiB FD00 Linux RAID
4 1980469248
Gary Dale garyd...@torfree.net wrote:
If you are referring to the ef02 partition, you don't install grub on
it. In fact, installing grub on the mbr is preferred.
The first stage is put into the 512 Bytes of the MBR. The rest (the
core.img) is installed into the bios_grub partititon.
With a
On Tuesday 30 June 2015 14:56:46 Pascal Hambourg wrote:
Gene Heskett a écrit :
On Tuesday 30 June 2015 11:55:20 Pascal Hambourg wrote:
Actually GPT does not use *all* that space and GRUB could still
find out the available unused space. But the GPT partition table
could grow and
On 30/06/15 03:05 PM, Muhammad Yousuf Khan wrote:
Ramadan Kareem Yousuf.
What I would do is shrink partition 5 by 100M then create a new
ef02 partition in the freed space. This should be completely safe
since it is just a swap partition and contains no permanent data.
Gary Dale garyd...@torfree.net wrote:
There is, but 2048 sectors is only 1M. Shrinking the swap partition and
creating a 100M ef02 partition in the free space leaves a lot more
headroom. Just because something fits today doesn't mean it will always fit.
Wow. 100MB for a bios_grub partition
On Tuesday 30 June 2015 23:30:46 Sven Hartge wrote:
Wow. 100MB for a bios_grub partition wastes about 99.8MB.
Which used to matter. But out of 2T???
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Arno Schuring a écrit :
Muhammad Yousuf Khan a écrit :
I have been using RAID1 b/w two 1.5 TB drives which worked great with
fdisk. now one of the drive is failed and there is no more 1.5 TB
available in the market. the least available drive is 2TB. Which means
fdisk 2TB issue.
Hi,
Date: Mon, 29 Jun 2015 14:52:32 +0500
From: sir...@gmail.com
I have been using RAID1 b/w two 1.5 TB drives which worked great with
fdisk. now one of the drive is failed and there is no more 1.5 TB
available in the market. the least available drive is 2TB. Which means
fdisk
On 29/06/15 05:52 AM, Muhammad Yousuf Khan wrote:
Dear All,
i have 2 drives installed way back in 2013 /dev/sda and /dev/sdb
I have been using RAID1 b/w two 1.5 TB drives which worked great
with fdisk. now one of the drive is failed and there is no more 1.5 TB
available in the market. the
47 matches
Mail list logo
