Novell Cool Solutions

Illegal Partition Table Error While Booting



By:

September 10, 2007 10:47 am

Reads:5,810

Comments:0

Score:Unrated

Print/PDF

Problem:

System throwing Illegal Partition Table error while booting.

Solution:

Illegal Partition Table error message during system booting is because the Partition Table got corrupted / deleted.

Example:

After successful completion of OES 2.0, try to create NSS volumes by typing the nssmu command on the Linux console. You will see a blue screen with the Main menu having following options:

Devices			Partitions			Pools
Volumes			RAID Devices			Snapshot

Select Pools and press the Ins key to create a pool. You will see only sda under devices. This is because hdb is not initialised. Go back to main menu and select Devices. You will be able to see both the HDDs. Now you can initialise hdb by selecting it and pressing F3 key from the keyboard. It will throw a warning message to proceed / not. You can accept this. Now go back to Pools and try to create a pool. You will get both the HDDs displayed under devices.

Important: While initialising the HDD from Devices menu, by mistake if you initialise the HDD where OS is installed and restart the system, you will end up with Illegal Partition Table error while booting and you will loose your OS and data. You will have to reinstall the whole thing again.

Tip: Never initialise the HDD where OS and data exists.

Environment:

OES 2.0 with 2 HDDs (sda & hdb)

sda is used for Linux partitions (/, swap and boot).
hdb is free.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS