BAD PBR sig

After finishing installing Solaris 10 cd 1, i reboot the machine, and it shows a message: BAD PBR sig, what does that mean? Anything i did wrong? How do i fix it? Any help is GREATLY appreciated!
Thank you!

Hello,
have you re-read the documenation on docs.sun.com and searched the net ?
Maybe this thread can help you (Maruisz is the author of the Multiboot FAQ http://multiboot.solaris-x86.org/)
http://www.riddleware.com/solx86/solarisonintel/msg25159.htm l
Michael

Similar Messages

Bad PBR sig and dual booting with Windows

This site's menu config is too difficult for me...
fyi.
=>
Below is the cases that happened in my environment
when installing Solaris 8 Operating Environment, Intel Platform Edition
Some will help you, and some may be just for your thinking.
Bad PBR sig
You know what it means?
I don't know.
If you know, let me know please...
@ Case 1
My Seagate ST39236LW 9.2GB HARD DISK fdisk info
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 Solaris 7183 14341 7159 50
(I use cylinder number to partition hard disk. Why?
When I use % and insert 1% to partition 2 then
fdisk makes start cylinder 7155.
It overlays with partition 1's end cylinder number.
So fdisk save(menu no 4) fails...
because the partition 1's start cylinder number is 0 ?)
After rebooting, bizarre Bad PBR sig, and my system dies...
So I boots my PC with Windows(or Dos) booting diskette.
A> fdisk
First Hard Disk partition info
1 NTFS 4377 50%
2 NON-DOS 10 0%
3 A NON-DOS 10 0% <= Solaris created x86 boot
4 NON-DOS 4363 0%
Solaris created extra X86 boot partition 3 and made it active.
But partition 3 could not boot...
I made partition 2 active from dos fdisk menu,
and pc boots well.
After rebooting, my disk partition info is like this
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 x86 boot 7183 7199 17 0
4 Solaris 7200 14341 7142 50
Then after installation?
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7165 7181 17 0
3 Solaris 7200 14341 7142 50
Partition 2 and 3 changed...
Where did partition 3 go???
Just deleted?
Then why partition 2 Start cylinder changed?
@ Case 2.
Another queer thing....
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active Solaris 7166 14341 7176 50
In Solaris x86 format fdisk menu,
if I've allocated remaining disk space all to Solaris(without x86 boot),
then Solaris also makes x86 boot partition(size 10MB), reboots well.
But install fails due to not enough free disk space
when install begins slicing Solaris partition.
error log says
Installing 32 Bit Solaris Packages
- Configuring boot device
- Using disk(c0t0d0) for "rootdisk"
- Deleting x86 boot fdisk partition (c0t0d0)
- Creating x86 boot fdisk partition (c0t0d0)
ERROR:Not enough free space to create x86 Boot fdisk partition(c0t0d0)
Why does Solaris delete and create x86 boot partition?
Why did it exist?
Case 3.
If I've fdisked like this, what will happen???
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1

BAD PBR SIG message comes from your BIOS - no partition boot record.
Sorry but it's not clear what else is going on - might be worth running a ODS based fdisk to clear the disk before installing Solaris?

Bad PBR Sig - Solaris 10 x86 06/06

Hello all,
I have seen this error over and over... "Bad PBR Sig" and I have yet to find a way to fix it.
I am installing Solaris 10 on a brand new disk. When the installation asks me, I tell it to use the whole disk for Solaris. Call me crazy, but I would expect this to also configure the disk to be bootable. The installation proceeds without problem and then when it reboots, I get the error.
I have searched Sunsolve, Google and everywhere else I could think to look, but I cannot find an answer on how to fix it. I see lots of guesses as to why the problem shows up, but no step-by-step's on how to fix it.
My system is a basic Dell, P4 2Ghz, 512MB RAM, single 40GB HDD and a DVD-ROM drive. Nothing special here. No multi-booting, only one drive... just a simple, basic PC.
Windows installs fine, so I know it isnt the disk.
I understand that for some reason Solaris cant make a disk bootable during installation... which baffles me. Sometimes it seems to be able to and other times it cant. It just doesnt make sense to me how Windows can boot from any disk you give it, but Solaris has a fit.
Anyway, is there anyone out there who can help me make a disk bootable for Solaris 10 after its been installed? I am relatively new to this and it is most frustrating when something as simple as booting the OS that was just installed is do difficult.
Thanks in advance to anyone who can help or point me to where I can find help.

I had the same problem in Solaris 10 X86 Update 8 (10/09). After reading this thread, it made me wonder "Why would the GUI install work, and a Custom JumpStart not?" Well, I looked at the way I was specifying the partition table in the jumpstart client profile, and found that when you use "partitioning explicit" I run into this problem. BUT! When I use "partitioning default" all works just fine.
So, rather than doing something like this:
partitioning explicit
filesys rootdisk.s0 32768 /
filesys rootdisk.s1 8192 swap
filesys rootdisk.s2 all overlap
filesys rootdisk.s3 free /var
I changed to doing this:
partitioning default
filesys any 32768 /
filesys any 8192 swap
filesys any free /var
So, whatever the suninstaller does differently using the second specification avoids the bug.
Also, I did verify, the "Bad PBR sig" error only comes up if installing onto a freshly installed disk, or in my case, a fresly created RAID set. (We have the X4150s with the StorageTek RAID controller.) Just for fun I re-jumpstarted a second time using the "partitioning explicit" method above, and the system booted just fine. So whatever the suninstaller does the first time around (when using "partitioning default") sticks. That's probably why this bug hasn't been caught in testing. Most (or many??) systems from Sun come pre-installed, and unless you re-configure your RAID volumes, you won't run into this problem.

Slice space limits? "BAD PBR SIG"

Hi there,
Is there a slice space limit I should know about? I'm installing Solaris 8 on a Compaq proliant DL380, and I'm stumping them with my problem: I can install and boot Solaris with 3 18-GB drives in a RAID 5 array. But if I use 4 18-GB drives, although I can create my slices the way I want (one big fdisk partition, and a very customized slice layout with one big slice for data), solaris won't boot after the install. All I see is an error message in the lower-left corner of the screen, highlighted in red: "BAD PBR SIG". Help much appreciated.
Thanks,
-Neil

Hi Neil,
your query is a bug. Bug Report for BugID 4304977
workaround for this query:
limit the size of non-Solaris partitions, or move beyond
the Solaris boot partition and Solaris partition.
Thanks.
revert back.
regards,
senthilkumar.
SUN - DTS

Bad PBR Sig nal?

It took me a while to install Solaris8 until I set jumpers on my cdrom to be master on ide2 and the harddrive master on ide1. now when i boot up, I get a "BAD PBR SIGNAL", after that, pushing enter would invoke cdrom bootup. What is this?

The error message <tt>Bad PBR Sig</tt> expands to "Bad partition boot record signature". That is, the solaris master boot record has tried to load the partition
boot record from the active partition, but this sector does not
contain a "valid boot sector signature" at offset 0x1fe (this
word should contain the value 0xaa55), and for that reason the
"boot code" in the invalid partition boot sector is <b>not</b>
executed.
Is the hard disc set to LBA mode in the BIOS setup or is it forced to some other
mode? If you boot from the solaris hard disc and
press both left&right shift key while it starts booting, does it
print "LBA" or "CHS"?

Bad PBR Signal on OVS 3.2.6

Hello,
I have recently installed a couple of OVS 3.2.6 machines and an OVM manager 3.2.6. everything is working fine except when I try to install a Solaris 10 update 11 VMs. The OS installation on the VM goes fine up until the 1st reboot where i get the Bad PBR signal and the VM panics.
I have tried installing redhat VM and it working fine with no problems, so i am guessing that this problem has something to do with Solaris. any ideas?
Solaris 10 update 11 VM config:
Memory:4GB
CPU:1
Disk:40GB
Tried HVM and HVM with PV

Moderator Action:
With apologies to the original author of this thread, it has been hijacked.
To user spbsust,
You have your own thread:
https://forums.oracle.com/thread/2614145
Stay there instead of trying to steal ownership from others.

Bad PBR Signal

When doing a reboot after install on Compaq Deskpro.
Solaris only boots off teh CD
I tried to format-disk but it is telling me that the disk has mounted partitions and also to see the manufacturer's guied for format the drive. I was attempting to reformat the drive and trying the installation again.

Moderator Action:
With apologies to the original author of this thread, it has been hijacked.
To user spbsust,
You have your own thread:
https://forums.oracle.com/thread/2614145
Stay there instead of trying to steal ownership from others.

Making the mirrored disk bootable

I have two drives that have Solaris 10 on them, mirrored.
How do I boot off the 2nd drive to make sure that the mirroring works, in case the primary fails.
It doesn't look like it's bootable now. I tried and it didn't work. Said "Bad PBR Sig"
# eeprom | grep -i bootpath
bootpath=/pci@0,0/pci10de,376@a/pci1000,3150@0/sd@0,0:a
# cat /platform/i86pc/boot/solaris/bootenv.rc | grep -i bootpath
setprop bootpath /pci@0,0/pci10de,376@a/pci1000,3150@0/sd@0,0:a
Ultra 40 M2

Assign an alias name to that secondary disk from OBP, and try to boot using that alias....

Solaris 10 11/06 installation problem?

hi,
i am new to solaris and just started to install the solaris 10 11/06, the partition for solaris installation is the first primary partition, auto slices was 4,4 GB for /, 1,4 GB for ovarlape,10 GB for /export/home and 500 MB for swap but i customized just for 2 slices one / 14 GB and other swap 660 MB, the installation process completed 100% but then hanged with this error messages:
Installing boot information:
-Updating boot enviroment configuration
-Installing boot blocks (c0d1)
-Installing boot blocks (/dev/rdsk/c0d1s0)
connot open/stat device /dev/rdsk/c0d1s2
ERROR: installboot (1M) failed
ERROR: could not install boot blocks
i pressed the reboot button and got the black screen with this message:
Bad PBR Sig
I wiped the installation again and want to install but waiting for help please:
First what all that error means?
Second where is my installation mistake to solve that?
Third is / and swap enough for installaion or use the auto layout of solairs as i mentioned above?

1-Make the Solaris partion "the only" active partition
2-Boot up the system in single user mode, mount "a"
3-Install solaris grub on mbr (/a/sbin/installgrub -m /a/boot/grub/stage1 /a/boot/grub/stage2 /dev/rdsk/<slice>) (i like solaris bundled version of grub :) )
before 3, make sure you got the entries for any other operating system/sytems in your active grub's /boot/grub/menu.lst file to be added to solaris's menu.lst file later.
Reboot, edit menu.lst as necessary.
Good luck.

Solaris 8 installs but wont boot

I am trying to install Solaris 8 on a Compaq Proliant DL360 i am using software cd 1 to do the install, downloaded the raid array drivers for Solaris and the install seems to go fine with no errors. The problem is when it reboots it goes the the screen where you choose which partition to boot from. the choices are:
1 diagnostics(compaq utilities)
2 x86boot active
3 Solaris
when you choose "2" it just boots to the setup screen like i was booting from the CD. If you choose "3" it switches to a screen that says 'booting selected partition' and it says at the bottom of the screen, "BAD PBR SIG" What am i doing wrong?

Hmm, you're using the raid array driver diskettes from compaq.
At the end of the installation (copying stuff from the
software 1 of 2 cdrom), did it copy the compaq
array drivers from the diskette to the fresh solaris
installation; before it rebooted?
Otherwise, your system seems to crash with a kernel
panic. The strange thing is that the install kernel booted
from the software 1 of 2 cd together with the raid drivers
from the compaq itu diskette had no problems installing
the OS to the scsi raid array.
Can you post more details about the crash / kernel panic?
If the system automatically reboots before you can take
some notes about the kernel panic, try to give the
command "b kadb -v" at the "(b) boot or (i) interpreter ..."
prompt.
What's the size of the raid array?
What happens it you boot from the DCA floppy, add the scsi
raid drivers from the compaq itu floppy and boot from the
software 1 of 2 cdrom. After the GUI starts, try to
open a shelltool/commandtool window (right click on the
desktop background). From the commandtool window you
can try to fsck / mount the scsi raid array. Does that
work?

Problem with Jumpstart install

Hi,
I'm having a serious problem installing an x86 Solaris 10 with Jumpstart. I have a server with the profiles and rules, everything is ok I think. The server has a DCHP service running, and I start the target machine from the net. When switched on, it connects to server, get IP address and paramenters, and the Grub menu appears with the correct option to select. I select it and the process begin. First, the language selection page asks for the language, then, the process make the partitions, and start the copy of files (graphic mode). After some hours (the files are the Solaris 10 operative system itself and a flash image from other machine), the file copy process finishes, and, after some other tasks, the machine reboots. And here is where the problem appears.
At booting, I select to boot from the first hard disk drive (where the files have been copied, where the OS resides), and the following message appears: Bad PBR sig. Searching in forums, I have read that message means there is no active partition or it's impossible to find the master boot record.
Booting with a CD, I see there is an active partition, and it is the correct partition. So the problem is that there is no master boot record. Again, searching the net, I read that there are two ways of write a MBR: the command Installboot and the command Installgrub.
I boot from solaris 10 CD and enter the command Installboot, and it says that it's obsolete, so I try with Install grub this way: (note: when booting with Solaris CD, it detects a Solaris installed in /dev/rdsk/c0t0d0s0, and ask me if I want to mount it in /a, I answer yes because I think that I need to use the information of grub at /boot/grub of the hard disk)
installgrub -m /a/boot/grub/stage1 /a/boot/grub/stage2 /dev/rdsk/c0t0d0s0
After that, I rebooted the machine and when it starts (from hard disk), the only thing that occurs is that the word GRUB appears.. and nothing else. A flashing cursor at the end of the word GRUB. Nothing to do. The only way to get out of there, is switching off and then on again.
The first time I tried to install, I did the same but without mounting the disk, and with the command installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c0t0d0s0
Here is the profile at Jumpstart:
install_type flash_install
archive_location nfs 10.95.8.7:/export/backup/platform/alba-ucm/ALBA-UCM-HostID_
2b72c461_4x80GbMirror-Prepared_09042008.flar
partitioning explicit
#DISK-0 MIRROR PREPARED
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s2 4251:400 swap
filesys c0t0d0s3 4651:100 /tmp
filesys c0t0d0s4 4751:1000 /opt/app
filesys c0t0d0s5 5751:3143 /repositoryCC
#SVM+Boot
filesys c0t0d0s7 8894:26
#DISK-1 MIRROR PREPARED
filesys c0t1d0s0 1:2650
filesys c0t1d0s1 2651:1600
filesys c0t1d0s2 4251:400
filesys c0t1d0s3 4651:100
filesys c0t1d0s4 4751:1000
filesys c0t1d0s5 5751:3143
#SVM+Boot
filesys c0t1d0s7 8894:26
#DISK-2 MIRROR PREPARED
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
#SVM+Boot
filesys c0t2d0s7 8894:26
Please, need some urgent help to solve this problem. What am I doing wrong?
Thanks.

Paco,
Quizas deberias de tratar de instalar tus file systems, y sincronizarlos durante el jumpstart. In other words, you should try to mirror your drives during jumpstart. I see you are using cylinders instead of MB sizes, and unless there is a particular reason why you're doing it that way, I suggest you mirror like this:
filesys mirror:d10 c0t0d0s0 c0t1d0s0 /
filesys mirror:d20 c0t0d0s1 c0t1d0s1 /swap
de este modo, una vez el sistema operativo instale, los cambios necesarios al bootenv.rc seran implementados por el sistema operativo.
You should also make sure if you have a live system, that the secondary drive (DRIVE-1) you are trying to boot has been setup with the master boot record:
fdisk -B /dev/rdsk/c0t1d0p0
And make sure your /boot/solaris/bootenv.rc file shows an "alternateboot" property.
Saludos,
--xancatal

Fdisk, jumpstart, and x86boot

When I do an Interactive install of Solaris 8 from CD, I end up with a working system, but when I do my jumpstart install with no fdisk commands in the install profile, I end up with a system that says "bad PBR sig" upon rebooting.
I added fdisk commands to the profile to create the x86boot and Solaris partitions, and the install did in fact create the partitions, however it still came up with the "bad PBR sig" error after the install. So my question is: What am I doing wrong in the profile?
Does anybody have a working profile that will take a system on which you do not want to preserve any existing data, install an x86boot partition and a Solaris partition, and end up with a system that boots to Solaris successfully?
(The documentation about the fdisk keywords in the profile that I found on docs.sun.com don't seem to be helping me on this issue.)
Hopefully,
Lusty

wooke01 wrote:
Hello
I have been told to install solaris via jumpstart and use zfs.
I guess the solaris installer will ask me and then i can choose zfs, so this shouldnt be an issue. However
Do i still need to set up mirroring using metadb, metaattch etc? as I tought i saw somewhere that there are different commands for mirroring zfs?Las metas commands are not applicable with ZFS as you do not have to use Solaris Volume Management. ZFS integrates its own volume management and you can easily construct stripe, mirrored, raidz (raid5), raidz2 (=raid 6) zpool.
For exemple to add a disk mirror to your rpool pool, you just have to do a "zpool add rpool c0t0d0s0 c0t1d0s0"
A "man zpool" should give you more information.
>
Also, if this is a new install of solaris, can i use jumpstart at all yet? Since i would need to be able to get to the OK> prompt to be able to run jumpstart? (and there is no os installed yet, after i exit ilom it goes into a solaris installer).
Can anybody quickly tell me what i need to do to get jumpostart working quickly on this new box? we have a jumpstart server which i have inherited but not sure how i set the clients up. Is it just a case of adding config to the ethers file and thats it?
Thanks
ThanksFrom your client, you have to boot from the network "boot - net" but before you will have to create a new profile in your jumpstart server, but I could not say you in details how to do this. Surely you might be able to find lot of information in docs.sun.com about this or perhaps somebody else could give more information.
Groucho_fr

SOLARIS HANG ON INSTALL

I recently received a Sun Micosystems Solaris 10 DVD. I followed the installation instructions that are online. There was no problems until the installation process. Halfway through the installation window diseapeared. i waited for 20 minutes and then restarted my computer. If i boot from the Hard Drive i get a "bad PBR sig" and if i boot from the disc i get to the loading secound stage. then the highlight what you want to boot. Then it just says all rights reserved SunMicrosystems 1987-2006.
Can someone please help me.
you can call me at 316-708-6139
or Email me at [email protected]

Need more info here.
What sort of Hardware are you using ?
Is it SUN Machines or PC based Intel ?
Check the site below for Hardware Compatibility List
http://www.sun.com/bigadmin/hcl/

Problems installing Solaris 8 w/ Win2k

Hi all,
I tried to install Solaris 8 IA today on a hard drive that previously had Win2000. I ran into many problems and am incredibly frustrated, so please forgive me. I hope somebody can help.
In essence, I installed Solaris 8, and it looks like it changed my MBR for the worse. I managed to fix part of this, but I later found out it completely re-arranged my Win32 drive letters, rendering my Win2k partition practically unusable.
Here is how my two hard disks were laid out before the install:
HDD-0 (IBM DeskStar 60G) -- Primary IDE Master
25G allocated to a bootable Win2k partition w/ NTFS, mapped as drive "F:\"
35G unallocated, unformated space
HDD-1 (WD Caviar 4G) -- Primary IDE Slave
2G bootable Win95 w/ FAT-16, mapped as drive "C:\"
1G Win95 extended w/ FAT-32, mapped as drive "D:\"
71M Linux swap w/ ext2fs
700M Linux native w/ ext2fs
Points:
I am completely uninterested with the MBR of HDD-1. This is just a hard drive I moved over from my old computer that I still use because it has all of my data on it. I no longer boot any OSes from this drive. (BIOS boots to HDD-0.)
When I installed Win2k a month or two ago, it detected my HDD-1 partitions and labelled them as "C:\" and "D:\" (their previous labels when installed on my old computer), and I was forced to make my new Win2k partition on HDD-0 "F:\". I thought this would be a good idea anyway, since I didn't feel like changing all of my old shortcuts, preferences, etc. for my apps on HDD-1.
When I installed Solaris 8 (4/01) today, I gave it about 12G on HDD-0. It seems like I got the whole partitions thing to work well, and after the install, using the Software 1 of 2 CD, it rebooted the computer (as it said it would). I took the CD out, and as it went to boot HDD-0, I got the dreaded "Bad PBR sig". I immediately knew my MBR was messed up.
Now I couldn't boot to Win2k because Solaris was my active partition. I was able to use the Win2k install CD to deactivate the Solaris partition, but I was floored to learn that my drive assignments were completely changed. My F became C, C became D, and D became E. The natural consequence of this was that I couldn't boot Win2k, because my video drivers, etc. are configured to be on "F:\...", which of course doesn't exist. My solution to this was to install another Win2k setup on the same partition (dirty, but works).
Questions:
1) How the heck do I get my original drive assignments back in Win2k? I don't want to have to change all of my setup files to point to C instead of F, D instead of C, etc. (I don't even think this is feasible.) Nor do I want to re-install all of my software. The Win2k install CD and Adminstrative Tools don't seem to provide any way to do this. Is there some (free) partition software I can download to correct this? Can the Solaris fdisk do this?
2) What's up with Solaris? How do I get this to work? I can boot the HD installation from the CD, but I can't do much because my video card apparently isn't supported and so everything comes up yucky. But how can I boot it without the CD and with a dual boot option? Is this one of those "you can't put boot code outside the first 1024 cylinders, yada, yada, yada" deals? If so, just shoot me now. <g>
Any help would be greatly appreciated. I blew the whole day on this. It pains me to say this, but... I know we all crack on Microshaft's business practices, but, FWIW, I installed Win2k in about 30 minutes, with not a single problem, with all devices being configured properly and having drivers, and haven't encountered a glitch since. I think that has a lot to do with their "popularity". There needs to be serious competition.
Thanks,
John
PS: I don't have access to e-mail until this is cleared up, so please post here.

Well, this is my solution to my problem:
I was able to install a second Win2k on my first hard drive to at least get back to my Win2k stuff. This leaves a total mess though, because now I have two user accounts, two installations, files pointing to the wrong place, registry settings all messed up, drivers installed twice, etc. So what I'm going to do is go ahead and install Linux, leave my Solaris partition alone (I think it's okay, though I can't boot to it w/o the CD), backup all the Win2k data and files I want to keep (not much -- it's a fresh computer), and then reformat my Win2k partition and reinstall Win2k.
The thing I'm still hazy on is the whole "1024 cylinders" issue. I'm not sure if I have to re-partition my hard drive, etc.
When you install Solaris, be sure to remember that Solaris and Linux swap use the same code (0x82 I think it is) for the partition. Read the Solaris documentation to make sure, but I think after you install Solaris you might have to reinstall Linux, or something like that.
Good luck. This is very confusing. I'm disappointed with the lack of documentation for installing Solaris. What did I pay $45 for? Thirty-five different translations of the same skimpy docs? Terrible. At least M$ takes care of its customers.
John

Solaris 9 made me Crazy

Hi There!
I never thought that inslaling Solaris 9 will be such a big challenge for me! It has been days since I am trying to install it.
1. First it was not picking up my Ethernet Card... now it is loading the Ethernet card but giving me BAD PRB or PBR Sig error What does it means? i read some discussion saying that.... I need to run fdisk in order to over ride on this problem but still I am getting same errors.. I have 40 GIG new maxtor HDD ...and want to run both Windows XP and Solaris on the same HDD but in different partition... Wut you guys suggest me to do? Detail help will be highly appreciated as I am new to Solaris.
God Bless all of you.
.hamid

Dear Sadiqin:
Remember you answered my question at Sun Solaris forum. I appreciate
your time and attention to my problems regarding installation for Solaris 9.
I wanted to share my installation experience with you and looking back
for help.
System Configuration
550 Mhz Compaq DeskPro
512MB RAM
40Gig Hard disk [I installed Windows XP and Solaris 9 on this Hard
drive as
you recommended me to do]
13.5 Gig Maxtor hard drive [I attached this drive later after Solaris
installation, when system�s power was off]
52 x 32 x 52x LG CD writer
DVD ROM
3.5� floppy drive [I attached that after Solaris installation]
Solaris Installation:
Network: Yes
Use DHCP:Yes
Enable IPV6: No
Name Services: None
Then I chose �Standard� for layout I guess
During installation: Solaris showed me that it detected my Ethernet
card and
created interface as exls0 I guess.
Problems:
1.     I can not access the Internet using Solaris Netscape
2.     It says �log host could not be resolved
3.     It says � hostname unknown�
4.     In correct block count
5.     unqualified host name
Seeking help for:
1.     how to get access to internet
2.     how to resolve above problems
3.     how to see my see my CD or hard drive I plugged onto the system
after
Solaris installation.
I am currently reading a Solaris 9 book but it will take ages to
understand
and then resolve above problems. I would appreciate if you please give
me
your expert advice to overcome above problems.
Thanks in advance.
Regards,
.hamid
Hamid Bari
[email protected]

BAD PBR sig

Similar Messages

Maybe you are looking for