fdisk against the existing datagroup DISK

From: Masha Gurenich <gurenich_at_gmail.com>
Date: Mon, 11 Apr 2011 16:56:21 -0400
Message-ID: <BANLkTinQa4r19+gSx98S0rsabfwUR4w94A_at_mail.gmail.com>

Hi all,

Please, help: the fdisk partition was put inside another partition. /dev/sda was already partitioned with a single partition as /dev/sda1 /dev/sda1 was labeled as DISK6 and was part of the DATA diskgroup. But fdisk was run against /dev/sda1 and created another partition table inside /dev/sda1.
We now have a /dev/sda1p1

That's what i did:

[root_at_oscdevdb1 ~]# *fdisk /dev/sda1*
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 51199. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n
Command action
e extended
p primary partition (1-4)
Partition number (1-4): 1
First cylinder (1-51199, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-51199, default 51199): Using default value 51199

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table.
The new table will be used at the next reboot. Syncing disks.
[root_at_oscdevdb1 ~]#
[root_at_oscdevdb1 ~]# /sbin/fdisk -l /dev/sda

Disk /dev/sda: 53.6 GB, 53687091200 bytes 64 heads, 32 sectors/track, 51200 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 51200 52428784 83 Linux
[root_at_oscdevdb1 ~]# /sbin/fdisk -l /dev/sda1

Disk /dev/sda1: 53.6 GB, 53687074816 bytes 64 heads, 32 sectors/track, 51199 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sda1p1 1 51199 52427760 83 Linux
[root_at_oscdevdb1 ~]#

I supposed to do it on *sdai1*

So, /dev/sda1 was a DISK6 in our diskgroup. Now, nothing happened yet. I mean, all 20 database are up and running so far and I got no alerts or anything that would give me clues about catastrophe. I don't know what to do, I am freaking out of course, nut I created critical 1 issue with Oracle Support. It's been 4 hours since I did that and an hour and a half that i opened P1 ticket...

I am looking for any hope you could provide.. It's a 2 node cluster, RedHat4 64 bit..

please, people, tell me I will not need to rebuild RAC...


Received on Mon Apr 11 2011 - 15:56:21 CDT

Original text of this message