Can you please suggest what that means to Populate the BIOS Partition. I'm not aware of this mechanism.
Regards,
Nasir
---------- Post updated Oct 22nd, 2013 at 01:52 PM ---------- Previous update was Oct 21st, 2013 at 06:37 PM ----------
Quote:
Originally Posted by fpmurphy
Assuming you are using GRUB2, pre-EFI firmware, i.e. a BIOS, and a GPT disk, do you see any sign of a BIOS Boot Partition Table? Partition type should be EF02.
Hi fpmurphy,
I have below given output from the gdisk command for the disk being replaced here.. both replaced and the good disk ( the disk which replicated its data to replaced one )
Code:
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5B747213-253B-4BCD-9022-AC20F6A3EB6C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2925 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02
2 4096 39065599 18.6 GiB FD00
3 39065600 1015627775 465.7 GiB FD00
4 1015627776 5860532223 2.3 TiB FD00
Command (? for help): i
Partition number (1-4): 1
Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition)
Partition unique GUID: 2B25F37D-4DCC-4D62-842A-322176A30AD9
First sector: 2048 (at 1024.0 KiB)
Last sector: 4095 (at 2.0 MiB)
Partition size: 2048 sectors (1024.0 KiB)
Attribute flags: 0000000000000000
Partition name: ' '
and below is the output for the disk ( which is intact till now and I replicated this disk to /dev/sda above )
Code:
Disk /dev/sdb: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 52E97A2C-D5CE-4FBE-8853-9A17F86DC779
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2925 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02
2 4096 39065599 18.6 GiB FD00
3 39065600 1015627775 465.7 GiB FD00
4 1015627776 5860532223 2.3 TiB FD00
Command (? for help): i
Partition number (1-4): 1
Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition)
Partition unique GUID: 95307A72-04D0-48A8-B676-FD04F74E1F62
First sector: 2048 (at 1024.0 KiB)
Last sector: 4095 (at 2.0 MiB)
Partition size: 2048 sectors (1024.0 KiB)
Attribute flags: 0000000000000000
Partition name: ' '
I'm setting-up my new computer, and would like to try out and switch between several OS (mostly different Linux distros). As I prefer to use separate partition for various dirs (/, home, usr, var, opt and perhaps local), I've come to the conclution that I'll run-out of partitions too soon, so I've... (1 Reply)
Hi people,I am trying to install Debian Lenny Betta-2 on a system that has the built in promise chip for "Raid 0" but when I finished the install and then I reboot ,I get "grub loading,pleas wate... Error 2.
also the Debian Lenny Betta-2 is identifying both drives ,instead of a singular drive... (4 Replies)
We have a filesystem which contains 8 hard disks but i am facing disk I/O issue becuase data is not spreading across all the disks.Is there any way i can check how data is spreading and any parameter we need to change to spread ata across all disks.
OS--AIX 5.3 (1 Reply)
All
I am trying to get RHEL 5.4 to load to the XEN enabled kernel but I am not having much luck. My grub.conf looks like it has 2.6.18-194.11.3.el5xen as the 1st one but when I do a uname -a I get the NON xen enabled kernel. I know I am doing something stupid but if anybody has any... (1 Reply)
Hi,
I`m on SunFire480R with Solaris 10. Disk in rootdg group failed, so it was replaced. However, I cannot make Veritas initalise the replaced disk:
# vxdctl enable
# vxdisk list c1t0d0s2
Device: c1t0d0s2
devicetag: c1t0d0
type: auto
flags: online error private autoconfig... (1 Reply)
Hi,
a little while ago, one of the GPT Partitioned hard disk had gone faulty in a Mirror RAID and is now successfully replaced.
here is how I did that.
1) created identical partition table on the new disk.
2) attached the mirrors using md commands.
The whole procedure is given below:... (2 Replies)
Scenario1:
VG00 lvm,not mirrored,2 disk of 36GB vg size
VG00 size is under 30G.
Is possible to remove a disk of 36GB and replace "on fly"
with a disk of 300GB on VG00?
Thanks (6 Replies)
I am having trouble with LVM and one of my physical volumes.
Using Ubuntu Desktop 14.04
I was trying to set up LVM across two disks (not containing the OS or Home).
First I created the initial Physical Volume, the Volume Group, and the Logical volume, and everything seemed fine. The... (2 Replies)
OSLevel: 5300-10-02-0943
System Model: IBM,8203-E4A
Power 6
==
Hi!
I replaced a failed pdisk in the raid enclosure as follows,
- rmdev -l 'pdisk18' '-d'
- Replaced it.
- cfgmgr (detected)
- I can see the new drive, with the correct serial #
lscfg -v -l pdisk18
pdisk18... (2 Replies)
Discussion started by: estrar
2 Replies
LEARN ABOUT OSF1
volrootmir
volrootmir(8) System Manager's Manual volrootmir(8)NAME
volrootmir - Mirror areas necessary for booting to a new disk
SYNOPSIS
/usr/sbin/volrootmir [-a] [nconfig=count] target_disk [swap=target_partition]
OPTIONS
Specifies that all volumes on the system disk be mirrored, not just the root and swap volumes, rootvol and swapvol.
DESCRIPTION
The volrootmir script causes a mirror copy of areas of the root disk involved in booting to be made on the specified target disk.
When used without the -a option, volrootmir adds mirrors of the root and swap volumes and allocates them on the new disk. In addition, all
disk regions required for booting are set up and partitions for the new volume mirrors are created.
When used with the -a option, volrootmir mirrors all in-use partitions on the system disk.
To mirror a swap volume that is on a separate disk from the root volume, the swap attribute must be used to specify a separate target for
the swap mirror.
The target disk(s) must be at least as large as the sum of the sizes of rootvol and swapvol. Also, the physical disk should not have any
disk partition in use.
This script can be called from the voldiskadm menus by choosing the Mirror volumes on a disk operation.
ATTRIBUTES
Specifies the number of log copies and copies of the configuration database, for example, nconfig=2. Specifies that the swap volume,
swapvol, be mirrored on a separate disk, as specified by target_partition.
EXAMPLES
The following command mirrors the rootvol and swapvol volumes onto the target disk, dsk3. This command will fail if swapvol is on a differ-
ent disk from rootvol.
# volrootmir dsk3 The following command mirrors rootvol, swapvol, and any other volumes on the root disk onto the target disk, dsk3.
This command will fail if swapvol is on a different disk from rootvol.
# volrootmir -a dsk3 The following command mirrors rootvol on disk dsk3, swapvol onto partition dsk7d, and any other volumes on the
root disk onto disk dsk3. This command will fail if swapvol is on the same disk as rootvol.
# volrootmir -a dsk3 swap=dsk7d The following command mirrors rootvol onto disk dsk3 and swapvol onto partition dsk7d. This command
will fail if swapvol is on the same disk as rootvol.
# volrootmir dsk3 swap=dsk7d
SEE ALSO volintro(8), voldiskadm(8)volrootmir(8)