Solaris 10 x86 1/06 CD1 boot fail

Hello all.
I download last version from sun.com, unzip iso's and burn their to cd's.
When i try to load (on different machines) from first cd i receive this errors:
<div class="pre"><pre>
/kernel/fs/specfs: undefined symbol ''
/kernel/fs/specfs: undefined symbol ''
... several screens same message ...
/kernel/fs/specfs: undefined symbol '' WARNING: mod_load: cannot load module 'specfs'
Press any key to reboot...
</pre></div>
2 and 3 variants of installation stoping without messanges.
First cd data reading is fine.
Where is my problem?

I'd compute MD5 checksums for the files you've downloaded and
verify if they match known good checksums for the downloadable files:
http://whacked.net/2005/12/22/solaris-10-update-1-s10u1-md5- sums/
Maybe there has been some sort of data corruption with the files you've
downloaded / unzipped on your machine....

Similar Messages

Install NetConnect in Global Zone of Solaris 10 x86 with 5 local zone fail

Problem:
Install NetConnect in Global Zone of Solaris 10 x86 with 5 local zone failed
But I didn't have any issue with the same pkg in Solaris 9
Steps taken:
# groupadd netcon
# useradd -d /export/home/netcon -g netcon -m netcon
# vi /etc/shadow
change LK to NP
# ./UninstallNetConnect.003.002.001.sh
# ./InstallNetConnect.003.002.001.sh
Enter the user account to use: netcon
Enter group: netcon
Installing Sun(SM) Net Connect Proxy Core as <SUNWsrspx>
## Installing part 1 of 1.
/etc/opt/SUNWsrspx/CustomerCert.pem
/etc/opt/SUNWsrspx/SRSCACert.pem
/etc/opt/SUNWsrspx/binaries
/etc/opt/SUNWsrspx/srsproxyconfig.cfg
/opt/SUNWsrspx/bin/srsexec
/opt/SUNWsrspx/bin/srsinstall
/opt/SUNWsrspx/bin/srsinstallmode
/opt/SUNWsrspx/bin/srsproxy
/opt/SUNWsrspx/bin/srspxrun
/opt/SUNWsrspx/bin/srspxstat
/opt/SUNWsrspx/bin/srspxtrace
/opt/SUNWsrspx/bin/srsuser
/opt/SUNWsrspx/bin/srsxfer
/opt/SUNWsrspx/lib/srsimapi.jar
/usr/lib/libsrsimapi.so.1
[ verifying class <none> ]
## Executing postinstall script.
copying initial install customer cert into place
copying initial install srs cert into place
copying initial install proxy config file into place
removing any existing uninstallscript before copying the correct one
copying uninstall script into place
/var/sadm/pkg/SUNWsrspx/install/postinstall: /opt/SUNWsrspx/bin/srspxrun: cannot execute
proxy queue initialization failed
pkgadd: ERROR: postinstall script did not complete successfully
Installation of <SUNWsrspx> failed.
ERROR: pkgadd failed for: SUNWsrspx
Please correct this situation and rerun the installation.
Exiting installation.
# cat /var/adm/messages
Oct 7 00:00:01 planet root: [ID 702911 daemon.error] ERROR: proxy queue initialization failed
Any clue, or it will only possible in Global zone that didn't have any local zone
thanks in advance

Problem:
Install NetConnect in Global Zone of Solaris 10 x86
with 5 local zone failed
But I didn't have any issue with the same pkg in
Solaris 9
Steps taken:
# groupadd netcon
# useradd -d /export/home/netcon -g netcon -m netcon
# vi /etc/shadow
change LK to NP
# ./UninstallNetConnect.003.002.001.sh
# ./InstallNetConnect.003.002.001.sh
Enter the user account to use: netcon
Enter group: netcon
Installing Sun(SM) Net Connect Proxy Core as
<SUNWsrspx>
## Installing part 1 of 1.
/etc/opt/SUNWsrspx/CustomerCert.pem
/etc/opt/SUNWsrspx/SRSCACert.pem
/etc/opt/SUNWsrspx/binaries
/etc/opt/SUNWsrspx/srsproxyconfig.cfg
/opt/SUNWsrspx/bin/srsexec
/opt/SUNWsrspx/bin/srsinstall
/opt/SUNWsrspx/bin/srsinstallmode
/opt/SUNWsrspx/bin/srsproxy
/opt/SUNWsrspx/bin/srspxrun
/opt/SUNWsrspx/bin/srspxstat
/opt/SUNWsrspx/bin/srspxtrace
/opt/SUNWsrspx/bin/srsuser
/opt/SUNWsrspx/bin/srsxfer
/opt/SUNWsrspx/lib/srsimapi.jar
/usr/lib/libsrsimapi.so.1
[ verifying class <none> ]
## Executing postinstall script.
copying initial install customer cert into place
copying initial install srs cert into place
copying initial install proxy config file into place
removing any existing uninstallscript before copying
the correct one
copying uninstall script into place
/var/sadm/pkg/SUNWsrspx/install/postinstall:
/opt/SUNWsrspx/bin/srspxrun: cannot execute
proxy queue initialization failed
pkgadd: ERROR: postinstall script did not complete
successfully
Installation of <SUNWsrspx> failed.
ERROR: pkgadd failed for: SUNWsrspx
Please correct this situation and rerun the
installation.
Exiting installation.
# cat /var/adm/messages
Oct 7 00:00:01 planet root: [ID 702911 daemon.error]
ERROR: proxy queue initialization failed
Any clue, or it will only possible in Global zone
that didn't have any local zone
thanks in advance
[I believe that it does not work in x86, watches with pkginfo - l SUNWsrspx, in the platform.
Willy Suarez
Sopport UNIX
Colombia/code]

Solaris 10 x86 b72 "Cannot find boot.bin" booting from SCSI.

Hello,
After several gyrations of installation attempts and dealing with early BIOS PnP issues, I've finally managed to get Solaris 10 x86 installed on an old dual P2 333Mhz system. So far the system is running flawlessly, but I'm still not able to boot directly off the SCSI disk. The primary boot handler is erroring out that it cannot find boot.bin.
I can boot fine off of the IDE CD drive and the floppy (currently pointed to autoboot into the SCSI disk as a workaround). But when I try to boot directly off the SCSI drive, I get the error from the Solaris boot manager that it "Cannot find boot.bin".
I have booted off the CD & Floppy and compared the /boot files from both the CD & floppy, but I cannot find any difference that would prevent the primary boot loader from finding boot.bin. I've even compared files to make sure they were not corrupt, and even force re-installed the boot handlers, and manually partioning, always with the same results. I've also tried both enabling and disabling the DOS >1G translation of the Adaptec SCSI BIOS with no change. I can't find any reason that the boot loader is not seeing boot.bin, or that the file is corrupt in any way (even after several wipe and install attempts).
My System is:
Supermicro P6DLS dual Pentium II 333MHz & 512MB RAM, w/ Adaptec 7880 SCSI-UW and IDE (whopping UltraDMA 33) interfaces.
CD/DVD reader is configured as the secondary master (moved from primary master in an attempt to fix boot problem)
HD is a 16GB UW SCSI disk.
(Other particulars ommited unless someone feels they are relevant to the boot process).
The system came to me with Windows 2000 installed and functioning. I also had Fedora Core 3 installed, both with no boot problems of the SCSI disk. (Although FC3 would not see the second processor even with the canned SMP kernel).
This system is intended to replace a Fedora Core 3 system to be a multi-purpose firewall gateway & proxy server and I'm really liking the performance I'm seeing with Solaris 10 on this system but would like it to be able to go through a normal boot process and not have to depend on a floppy as a boot device to get started.
Anyone have any ideas why the Solaris x86 boot loaders think that they cannot find boot.bin when the full /boot partion is intact?
TIA,
-Troy

I'm getting the same problem trying to install
Solaris 10 in VMware from DVD.
It brings up the Solaris Primary Boot Subsystem, so
it appears to be reading fine, but the only thing
that happens is I get the Cannot find boot.bin
error.Hmm, the "Cannot find boot.bin." message comes from the
CD/DVD's boot code, which is contained in the first 16 sectors
of the media.
The boot.bin file is supposed to be read from the Solaris UFS
slice, which starts at 512 byte block #5151360 (or 2048 byte
dvd sector #1287840). This a byte offset of ~2.6 GBytes.
Maybe an issue with your system's bios not being able to read
DVD media > 2GB, during DVD boot?
Or a problem with burning the DVD media? Maybe some
"smart" PC DVD burning software has decided only to record
the 2.6 GB ISO filesystem, and the 100 MB Solaris UFS
filesystem that follows the ISO filesystem is missing on the DVD?
Or a 2GB filesize issue while burning the DVD?
Do you have a pc / windows utility that can print some information
about the S10 DVD media, especially the size of that DVD?
Maybe your CD/DVD recording software?
The original S10 GA x86 DVD image has a size of 2732195840
bytes, or 1334080 2K DVD blocks.

Solaris 11 x86 installer hangs on boot

I've downloaded both sol-11-1111-live-x86.iso and sol-11-1111-text-x86.iso, they both launch grub successfully, but thereafter they hang almost instantly.
This is a photo of my monitor when the installer has died:
[http://dl.dropbox.com/u/5487392/IMAG0073.jpg]
I've installed ubunut and windows successfully on the machine, so the hardware should be ok.
Is there some way I can launch the installer in verbose mode or something to more accurately pinpoint what fails during the boot?
Any other suggestions that can get me closer to installing solaris are welcome as well.

I am getting this on a Dell SC440.
I thought it might be my lowly E2160 CPU, but I've just put in an Intel Q6600 (Core 2 Quad 2.4 GHz) and it still happens.
The server previously had Red Hat Linux 6 on it (actually I reinstalled it today to test it), but I booted from a DOS USB stick and used fdisk to remove all partitions, so that the 3x 80 GB SATA disks I have in there are all blank.
When I boot it goes through the initial screen with dots printing across and then displays a text line "Solaris Release 5.11 Version snv_151a 64-bit" then a copyright line and then it hangs.
I've tried both the live and text install media, with the same result.
I have used the same Solaris media to install onto another machine (an AMD powered Dell C521), and it is fine.
Any ideas/pointers?

Solaris 10 x86 daylight savings time patch failes

Hello! I'm having trouble getting my solaris box to recognize the new timezone change. I've installed patches 122033-04 and 121208-03 as you can see here:
$ showrev -p | fgrep 122033
Patch: 122033-04 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu
$ showrev -p | fgrep 121208
Patch: 121208-02 Obsoletes: 118345-13, 118849-01, 120018-02 Requires: 118844-22 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcsl, SUNWtoo, SUNWcslr, SUNWhea, SUNWbtool
Patch: 121208-03 Obsoletes: 118345-13, 118849-01, 120018-02, 118565-03 Requires: 118844-14, 118844-22 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcsl, SUNWtoo, SUNWcslr, SUNWhea, SUNWbtool
$ uname -a
SunOS icarus 5.10 Generic_118844-26 i86pc i386 i86pAfter the reboot, the time from the date command jumped forward one hour, but the timezone still shows "CDT", not "CST" for central time.
This problem also seems to affect time calculations in my java version "1.5.0_06" environment.
Does anyone have an idea what could be happening? Thanks for any help.
Joe Gonzalez

Hi Celerius,
I thought that Central Daylight Time would be the correct timezone since DST began last Sunday? CST is the winter timezone.
What might be impacting your java time calculations is a problem which we noticed with java 1.5.0_06, where there is an issue with time zones being incorrectly mapped. We found that the use of 1.5.0_04 was more stable. Maybe you can try that on your test platform to see if it helps.
Cheers.

Solaris 10 10/08 x86 DVD will not boot, workaround inc.

hi,
Downloaded the Solaris 10 10/08 x86 DVD. It will not boot up at all with the 2 Gigabyte boards I have tryed it with. GA-G33-DS3R and GA-N650SLI-DS4L I downloaded the ISO twice and checked the checksum. Burnt the DVD 4 times! The DVD works fine with my Eee PC 900 over usb. Booting the 2 gigabyte board over usb works a bit better, they get to GRUB but they still dont work correctly.
I am using IDE DVD drives with the 2 gigabyte boards. I have never had a problem like his before with my hardware. Been experimenting with lots of diffrent Linux distro's recently and they all booted fine from DVD's I have burnt from downloaded ISO's.
I have tryed the CD install disks, CD1 boots up and start the install OK, but would not finish corrctly for me. Some other problem am not going into.....
The DVD workaround I am using.
Boot up the system with am old Solaris DVD.
At the very first menu, press an arrow key to stop the 6 second timer.
Remove the old Solaris DVD and replace it with the new Solaris 10 10/08 DVD.
Wait a few seconds and select Solaris from the menu.
The install program will now continue with the new DVD. If you dont have am old solaris DVD, you could try downloading CD1 and booting that then swapping it out fot the new DVD. Not tryed this myself.
Brian,

hi,
Downloaded the Solaris 10 10/08 x86 DVD. It will not boot up at all with the 2 Gigabyte boards I have tryed it with. GA-G33-DS3R and GA-N650SLI-DS4L I downloaded the ISO twice and checked the checksum. Burnt the DVD 4 times! The DVD works fine with my Eee PC 900 over usb. Booting the 2 gigabyte board over usb works a bit better, they get to GRUB but they still dont work correctly.
I am using IDE DVD drives with the 2 gigabyte boards. I have never had a problem like his before with my hardware. Been experimenting with lots of diffrent Linux distro's recently and they all booted fine from DVD's I have burnt from downloaded ISO's.
I have tryed the CD install disks, CD1 boots up and start the install OK, but would not finish corrctly for me. Some other problem am not going into.....
The DVD workaround I am using.
Boot up the system with am old Solaris DVD.
At the very first menu, press an arrow key to stop the 6 second timer.
Remove the old Solaris DVD and replace it with the new Solaris 10 10/08 DVD.
Wait a few seconds and select Solaris from the menu.
The install program will now continue with the new DVD. If you dont have am old solaris DVD, you could try downloading CD1 and booting that then swapping it out fot the new DVD. Not tryed this myself.
Brian,

Going back to mirrored after booting unmirrored - Solaris 10 x86

Folks,
On one of my Solaris 10 x86 servers at the last reboot it failed to come up. I put back the versions of /etc/vfstab and /etc/system from before the boot drive was mirrored. "metastat" still reports the md versions of the slices are still in sync but I'm not convinced that's accurate since the failed reboot.
How do I go back to mirrored again at the next boot?
I've been reading doc 819-2789 "x86: How to Create a RAID-1 Volume From the root ..." and it looks like I need to go through most of the steps.
My best guess goes something like this -
Loop for each mounted slice - Use metadetach to remove the one not mounted. Use metaattach to add it back. Use metasync to confirm the mirror synced up again.
Once that loop has completed assume that any MBR stuff is broken. A bit like I've done with "mkboot" on SPARC but following the steps in the doc. Look at menu.lst, fdisk, installgrub, metaroot, have with and without mirror copies of /etc/vfstab and /etc/system ready just in case, reboot.
Basically all of the steps from the doc only instead of using metainit use metadetach, metaattach, metasync.
Does this make sense? It parallels stuff I've done on SPARC but I have a lot more experience on SPARC than on X86.
Thanks in advance, Doug Freyburger

freyburgerd wrote:
Folks,
On one of my Solaris 10 x86 servers at the last reboot it failed to come up. I put back the versions of /etc/vfstab and /etc/system from before the boot drive was mirrored. Exactly how you did that may matter.
"metastat" still reports the md versions of the slices are still in sync but I'm not convinced that's accurate since the failed reboot.You're absolutely correct. As soon as you write (or mount read/write) to one of the raw slices or to one of the sides of the mirror, the mirror will be out of sync, and SVM will not realize it.
How do I go back to mirrored again at the next boot?Detach the side you're not booted from. Redo the metaroot and come up on the (now one-way) mirror. Once booted from the mirror, reattach the other side.
My best guess goes something like this -
Loop for each mounted slice - Use metadetach to remove the one not mounted. Use metaattach to add it back. Use metasync to confirm the mirror synced up again.You'll want to detach before using the mirror again, but you can't attach until you stop using the raw slice. So you can't just detach/attach in one step. You'll need to reboot between them.
Once that loop has completed assume that any MBR stuff is broken. A bit like I've done with "mkboot" on SPARC but following the steps in the doc. Look at menu.lst, fdisk, installgrub, metaroot, have with and without mirror copies of /etc/vfstab and /etc/system ready just in case, reboot.
Not sure why any MBR stuff would have been affected unless you did so explicitly.
Basically all of the steps from the doc only instead of using metainit use metadetach, metaattach, metasync.
Does this make sense? It parallels stuff I've done on SPARC but I have a lot more experience on SPARC than on X86.Should be the same on both. If you're adding a new disk, you need to make sure boot support is added. But in this case I doubt any of the boot support was damaged (depending on the details of what led up to your changes).
Darren

Solaris 10 x86 - software RAID boot

What I can write in eeprom : - for boot form 1-st, and if it absent - from 2-nd disk ? (2 disks in soft raid). two bootpath ?
In Solaris 9/sparc for boot with one working HDD in mirror (2 disks in mirrir) I wrote in /etc/system : set md:mirrored_root_flag=1
What I can wrote for this in solaris 10/ x86 ?

Just for the record: The problem is solved.
I went on looking for more info on this message:
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice] Sense Key: ICRC error during UDMAAnd then found an interesting post from 2004 by Juergen Keil:
The "bad block detected" message appears to be an old/obsolete error
message text, somewhere in the Solaris "ata" driver.
The ATA-1 standard (1997?) defined the 0x80 bit in the IDE
controller's error register as "bad block detected". (See page 32 on
<URL:http://www.t13.org/project/d0791r4c-ATA-1.pdf>)
The 0x80 bit seems to be "reserved" (undefined, not used any more)
with ATA-2 and ATA-3.
ATA-4 and newer now defines this bit 0x80 as ICRC "interface CRC error
has occurred during an Ultra DMA data transfer" when using ultra dma
transfers. (see the description of the "READ DMA" or "WRITE DMA"
command in <URL:http://www.t13.org/project/d1153r18-ATA-ATAPI-4.pdf>).
The Solaris ata driver seems to interpret the 0x80 bit according to
the old / obsolete 1997 ATA-1 standard.
So the "bad block detected" message seems to be a hint that some sort
of data corruption is happening on the IDE interface during UDMA data
transfers with the HDD. With UDMA capable disks it apparently does
not mean "the disk drive is dying".
I went to search what could cause a hardware datacorruption on my system and found that my internal removeable disktray was making bad contact.
After replacement everything worked as expected.

Problem booting a Solaris 10 x86 after Jumpstart Installation

Hi,
I have a strange problem. I have a working x86 machine with Solaris 10 installed. I have made a flash image of it's hard disk, and I have store thar flar on another machine. I have another Solaris 10 with Jumpstart.
I boot other x86 machine through PXE. The Jumpstart machine gives it a valid IP, and the process of sending the flash image begins. The process finish, and the client machine reboots. And here is the strange problem:
When starting, the Grub men� appears, and shows the two options configured: first, start Solaris in normal mode, and second, failsafe.
If I choose normal start, the screen goes black and the machine restart as if you rebooted it. I can only start in failsafe mode.
Here are the config files in Jumpstart for that machine:
Profile:
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
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s3 4251:400 swap
filesys c0t0d0s4 4651:1000 /opt/app
filesys c0t0d0s5 5651:3143 /repositoryCC
filesys c0t0d0s6 8794:100 /tmp
filesys c0t0d0s7 8894:26
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
filesys c0t2d0s7 8894:26
After Script:
touch /a/etc/notrouter
touch /a/noautoshutdown
sync
echo "Changing and syncing bootenv.rc"
# clear the boot-args property
echo "setprop boot-args ''" >> /a/boot/solaris/bootenv.rc
# set the bootpath property to boot from the hard disk
STRING=`df | grep '^/a '� | sed 's/).*//' | sed 's/^.* (//'`
STRING=`ls -l ${STRING}`
MYROOT=`echo $STRING | sed 's/.*..\/..\/devices//'`
echo "setprop bootpath ${MYROOT}" >> /a/boot/solaris/bootenv.rc
# disable kdmconfig from running after the first reboot
sysidconfig -b /a -r /usr/openwin/bin/kdmconfig
sync
And here is the menu.lst for Grub:
title Solaris 10
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
title Solaris Failsafe
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Please, any idea about what may be hapening?

Thanks for your answers.
Yes, both machines have the same hardware exactly. Finally, I could find where the problem was.
The file bootenv.rc, for some reason that I don't know, was corrupted: In it there was a correct line with bootpath variable correctly defined, but, at the end of the file, there was another line setting the bootpath variable to a long and incoherent string of chars. Booting in failsafe, mounting the system in /a, and removing that stupid line from the bootenv.rc, solved the problem.

Boot from second hard drive with ZFS in Solaris 10 x86

Hi,
The usual menu.lst to boot Solaris10 x86 with a boot environment that contains a ZFS boot loader is this one
title Solaris 10 5/08 s10x_nbu6wos_nightly X86
findroot (pool_rpool,0,a)
kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS
module /platform/i86pc/boot_archive
title Solaris failsafe
findroot (pool_rpool,0,a)
kernel /boot/multiboot kernel/unix -s    -B console=ttyb
module /boot/x86.miniroot-safeI understand that to add an alternate boot disk, I have to play with installgrub and then attach it in the pool.
But my question is : Is there a way to boot from my alternate hard disk by adding a new entry in menu.lst or is the only
way is to modify the BIOS parameter?
Thanks for your help,
Groucho_fr

Groucho_fr wrote:
Thanks for your answer Alan,
But ok, I imagineI can add a grub entry. But what I want to know is what is the exact way to boot from an alternate hard disk on Solaris 10u6
x86.AFAIK there are only two ways to do this. Select the disks via BIOS which becomes a royal PITA in a short amount of time or play with a boot manager such as GRUB until you get the syntax right.
Personally I put all OS's on the primary disks if possible to avoid these situations and if I have others to play with then you can easily mount them in or set them up as D: drive etc...
The only exception would be in an enterprise setting where you need to do things such as mirroring but then again in those situations it's only one OS per machine anyways so it's much easier.
So at the end, I am not sure what I have to configure and what is the procedure to boot from my alternate boot diskTry the grub homepage for the grub manual and hopefully for a mailing list or try a search engine.
http://docs.sun.com/app/docs/doc/819-5461/zfsboot-1?a=view
has an example to follow of using -B.
And moreover, the installgrub does not working for me :
root@mac1 # zpool status
pool: rpool
state: ONLINE
scrub: resilver completed after 0h2m with 0 errors on Thu Mar 26 10:56:24 2009
config:
NAME          STATE     READ WRITE CKSUM
rpool         ONLINE       0     0     0
mirror      ONLINE       0     0     0
c5t0d0s0 ONLINE       0     0     0
c5t4d0s0 ONLINE       0     0     0
errors: No known data errors
root@mac1 # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c5t4d0s0
cannot open/stat device /dev/rdsk/c5t4d0s2
You shouldn't need to do an installgrub if you installed Solaris. Try c5t4d0s0 not s2.
alan

Boot failed: solaris server does not boot

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

Boot image for Solaris 8 x86?

Does anyone know where I can download the image for the boot floppy for Solaris 8 x86?
Mine got corrupted, and since System Commander 2000 doesn't recognize the partition, that and the CD are the only ways I can boot the system.
Thanks in advance,
-Phil
pbflores@"REMOVETHIS"usa.net

Are you considering any particular cards ?
I have had good luck with DEC21040 (10baseT) and DEC21140 (100baseT) cards
in Solaris 7 through Solaris 10 on x86.
The same can be said for 3Com 3C905C-TX cards.
Solaris 8x86 will recognize many chipsets natively,
and a number of third party developers have created working driver packages.
Most of their driver packages are free, but a few are not free.
Solaris 9 works with a few more, and Solaris 10 works with yet more adapters.
The Solaris 8x86 HCL list has the native cards.
This other Sun web page can direct you toward 3rd party sites.

Solaris 10 x86 won't boot.

Hello,
I just installed Solaris 10 x86 on a brandnew disk, but the system will not boot. After generating lots of errors, it flips back to Grub. I managed to catch some error messages:
Tue Oct 14 00:13:57 WEST 2008
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice]      Requested Block 4637010, Error Block: 4637025
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice]      Sense Key: ICRC error during UDMA
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice]      Vendor 'Gen-ATA ' error code: 0x16
Oct 14 00:07:09 schille gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@f,1/ide@0/cmdk@0,0 (Disk0):
Oct 14 00:07:09 schille      Error for command 'read sector'     Error Level: Retryable
These errors are repeated many times, for many different disk blocks.
Funny thing is, my old disk had the same problem, therefore I just bought this brandnew disk. It is a WD Model : WDC WD1600AAJB-00PVA0, Revision : 00.07H00.
I 'm not using this disk within a serial ATA configuration.
Since the Award Phoenix BIOS version is quite old (2003), I am beginning to suspect the problem might be there.
Does this look familiar to anyone?
I 'll look forward to your comments.
Thanks, Bram

Just for the record: The problem is solved.
I went on looking for more info on this message:
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice] Sense Key: ICRC error during UDMAAnd then found an interesting post from 2004 by Juergen Keil:
The "bad block detected" message appears to be an old/obsolete error
message text, somewhere in the Solaris "ata" driver.
The ATA-1 standard (1997?) defined the 0x80 bit in the IDE
controller's error register as "bad block detected". (See page 32 on
<URL:http://www.t13.org/project/d0791r4c-ATA-1.pdf>)
The 0x80 bit seems to be "reserved" (undefined, not used any more)
with ATA-2 and ATA-3.
ATA-4 and newer now defines this bit 0x80 as ICRC "interface CRC error
has occurred during an Ultra DMA data transfer" when using ultra dma
transfers. (see the description of the "READ DMA" or "WRITE DMA"
command in <URL:http://www.t13.org/project/d1153r18-ATA-ATAPI-4.pdf>).
The Solaris ata driver seems to interpret the 0x80 bit according to
the old / obsolete 1997 ATA-1 standard.
So the "bad block detected" message seems to be a hint that some sort
of data corruption is happening on the IDE interface during UDMA data
transfers with the HDD. With UDMA capable disks it apparently does
not mean "the disk drive is dying".
I went to search what could cause a hardware datacorruption on my system and found that my internal removeable disktray was making bad contact.
After replacement everything worked as expected.

Solaris 10 x86 failed to reboot after initial installation due to display error

Hi everyone,
i just finished installing solaris 10 x86 on my computer, and the installation process went smoothly. However, when the system tried to reboot, i got some error related to the display of the monitor, which caused no desktop login can be displayed and no access to the console. I had no way to proceed with the any other operations. The error read as:
" Out of range<br />
Hf 30KHz - 70KHz<br />
Vf 30Hz - 160 Hz<br />
Current frequency<br />
Hf 90.3KHz "
I tried to boot to solaris failsafe mode and run "kdmconfig"
command to reconfigure video and monitor, but it did not work, since kdmconfig is not supported under that mode.
Because i have no way to login, the currently available solution seems not working with my situation. Dose anyone have idea or suggestion to figure it out, without reinstalling the OS from the very beginning?
Very appreciate your time and help.

Solution found:
First tried to login using "console login" when solaris booted up, before the desktop login window appeared. Then, run command "kdmconfig", changed the video device to X86 VESA compatible device, which is from the x86 driver and porting kit for solaris, then test/save and exit. After that, reboot the system. Now it is working, not perfect though (due to my old monitor) :)-

Solaris 10 x86 CD install - stops after cd1

Experienced linux user.
Recent new second hard drive means I can install Solaris.
Downloaded and burnt CDs (5)
CD1 boots. Used text based installer. Installed to 2nd partition on primary IDE slave drive. Grub to MBR on this drive then plan to either boot changing BIOS boot or chain load from Lilo on master hd MBR.
CD1 install set-up fine(I think I answered right)starts to install software - after approx 15-20%. Stops. Tells me CD1 installation complete and reboots.
However -reboots succesfully to GRUB but no menu or unable to boot kernel using GRUB root and kernel commends.
CD2 never requested.
Any help would be appreciated.
HH

OK -no replys
Have now sorted myself by using DVD download and installing on first patition of second hd. Still need to change boot disk in bios to boot so trying to work round this.
Solaris seems very good.
Will now try to get speedtouch 330 usb modem working so I ca connect to net.
HH

Solaris 10 x86 1/06 CD1 boot fail

Similar Messages

Maybe you are looking for