Solaris 10 X86 bug at boot

hi,
I've got a serious trouble after installing the OS. the first time i boot on it (i've also got windows XP on my system, a packard bell laptop h5530), it writes me, at screen, something that looks like an html table, and for each tag say : class not found. I don't know if this is the same bug, but the first three times I've installed solaris i had a unable to find kernel/unix

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.

Similar Messages

  • Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

    I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
    It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
    If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
    the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
    no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
    I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
    :0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
    in /usr/dt/config/Xservers file, to start the X server.
    Here is the $HOME_DIR/.dt/startlog file:
    --- ??? 23 ??? 2003 12:10:51
    --- /usr/dt/bin/Xsession starting...
    --- starting /usr/openwin/bin/speckeysd
    --- Xsession started by dtlogin
    --- starting /usr/dt/bin/dtsession_res -load -system
    --- sourcing /root/.dtprofile...
    --- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
    --- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
    --- sourcing /usr/dt/config/Xsession.d/0020.dtims...
    --- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
    --- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
    --- sourcing /usr/dt/config/Xsession.d/1000.solregis...
    --- could not read /root/.profile
    --- starting /usr/dt/bin/dthello &
    --- starting /usr/dt/bin/dtsearchpath
    --- starting /usr/dt/bin/dtappgather &
    --- starting /usr/dt/bin/dsdm &
    --- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
    --- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
    --- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
    --- starting desktop on /dev/pts/3
    Sun Microsystems Inc.     SunOS 5.9     Generic_112234-03     November 2002
    /usr/dt/bin/ttsession[337]: starting
    X connection to :0.0 broken (explicit kill or server shutdown).
    X connection to :0.0 broken (explicit kill or server shutdown).
    I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
    Anyway, I hope this will help developers solve a problem -if it really exists-.
    Angelos Vasilopoulos
    Site Security Officer
    [email protected]

    I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
    It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
    If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
    the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
    no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
    I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
    :0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
    in /usr/dt/config/Xservers file, to start the X server.
    Here is the $HOME_DIR/.dt/startlog file:
    --- ??? 23 ??? 2003 12:10:51
    --- /usr/dt/bin/Xsession starting...
    --- starting /usr/openwin/bin/speckeysd
    --- Xsession started by dtlogin
    --- starting /usr/dt/bin/dtsession_res -load -system
    --- sourcing /root/.dtprofile...
    --- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
    --- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
    --- sourcing /usr/dt/config/Xsession.d/0020.dtims...
    --- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
    --- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
    --- sourcing /usr/dt/config/Xsession.d/1000.solregis...
    --- could not read /root/.profile
    --- starting /usr/dt/bin/dthello &
    --- starting /usr/dt/bin/dtsearchpath
    --- starting /usr/dt/bin/dtappgather &
    --- starting /usr/dt/bin/dsdm &
    --- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
    --- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
    --- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
    --- starting desktop on /dev/pts/3
    Sun Microsystems Inc.     SunOS 5.9     Generic_112234-03     November 2002
    /usr/dt/bin/ttsession[337]: starting
    X connection to :0.0 broken (explicit kill or server shutdown).
    X connection to :0.0 broken (explicit kill or server shutdown).
    I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
    Anyway, I hope this will help developers solve a problem -if it really exists-.
    Angelos Vasilopoulos
    Site Security Officer
    [email protected]

  • 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.

  • 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 5/08 : Boot from DVD gives 'grub ' and no menu

    Hi All,
    I just spent a good deal of time downloading the Solaris 10 5/08 x86 DVD images. When I try to boot from disc 'A', I merely get a 'grub>' prompt.
    From all I can tell due to searching, this is not right.
    Any advice? :(

    @cjblaine4
    Solaris Operating System, Download and Burning Instructions
    [http://www.sun.com/software/solaris/download_instruction.xml]
    That link was prominently listed on the pages you used to get to the download page.
    Perhaps you overlooked it.
    I've saved it as a browser bookmark, and often review it as a reference.
    Consider saving it as a bookmark, as well.

  • 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 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 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 x86: How to boot from Veritas mirror disk?

    Hello team,
    We are using trailware Veritas Storage Foundation (VxVM) on Solaris 10 x86 system and need help in booting from alternative boot disk(Mirror disk).
    Steps did :
    1. Mirrored the root disk group using veritas volume manager command *"vxrootmir"*
    2. Updated the bootpath with mirror disk path in /boot/solaris/bootenv.rc
    Updated the EEPROM information:
    # bootadm update-archive -R /a
    3. Edited the grub configuration file, /boot/grub/menu.lst
    Created the following entry similar to primary disk entry to allow the root disk mirror to be booted
    title Oracle Solaris 10 8/11 s10x_u10wos_17b X86 <VxVM: Alternate Boot Disk>
    findroot (rootfs0,0,a)
    kernel /platform/i86pc/multiboot
    module /platform/i86pc/boot_archive
    4. reboot -- -r
    At the time of boot, selected the newly added entry from the grub list and got the following error,
    *"Reboot and select proper boot device or insert boot media in selected device and press a key".*
    I am unable to move further from here, is this because of the veritas trial version we are using ?
    Please help in resolving this issue and also explain the step by step process of booting from alternative boot disk on a x86 machine.
    Let me know if you find anything inappropriate. Looking forward for your replies.
    Thanks in advance.

    Hi--
    I have not seen this message before but a quick google search says that is pretty common and is related to the system
    trying to boot from a different device (not the one you intended). Can you check your BIOS settings and possibly remove
    devices from the boot order setting... Otherwise, I would suggest running installgrub on the disk that you are trying to boot
    from.
    I'm curious why you are trying Veritas. Is there a Veritas feature that you need? You might consider trying ZFS if you haven't
    already. Its very simple to set up and use.
    Thanks, Cindy

  • Solaris 10 06/06 x86 HP DL585 boot hang aftrer reboot HELP!!!

    Solaris 10 06/06 x86 HP DL585 boot hang aftrer reboot
    when I shutdown server and power on,
    solaris usually start.
    but after "reboot" (or "init 6"), boot hang on
    "SunOS Release 5.10 Version....
    Copyright ...
    Use is subject to license terms"
    HELP!!!

    try getting the Solaris x86 drivers frm HP....
    http://search.hp.com/redirect.html?type=REG&qt=Solaris+x86&url=http%3A//h18007.www1.hp.com/support/files/server/us/download/22412.html%3Fjumpid%3Dreg_R1002_USEN&pos=1
    hope it helps.

  • 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

  • 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.

  • Solaris 10 x86 intallation problems

    I have an athlon based machine which was happily running XP this morning. I had previously divided the disk to use a Linux distribution on one half and XP on the other. I wanst using the Linux bit much due to graphics driver problems so I decided to replace it with a Solaris 10.
    I duly went through the installation and was told that the solaris boot loader was incomaptible with the Linux one, grub I think, so I overwrote it and proceeded with the install. During the disk layout procedure I asked it to preserve my XP partition and use the rest for solaris. I had to shrink the solaris bit beyond teh full size by 100k or so and eventually it was happy, or so I thought.
    Solaris is now duly installed and runs fine. I just need to sort out a network card driver. However my problem is that the sun boot loader sees the old XP partition as an extended dos partition (partition 3) and wont boot from it....
    WHat have I done wrong?
    Please dont tell me my XP partition is lost! Is there some tool I can use to make it bootable again? I have seen the grub bits on the GNU site. Are these any use?
    All Help gratefully recieved.

    FYI: I tried yet another version of solaris as i found out that theres a bug in the 64-bit kernel on update 4 for alot of new processors. Solaris 10 x86 update 7 did the trick! :). Installed right away on a standard 'Solaris 10 (64 bit)' VM. I still find it strange that the most recent version of solaris 10 fails to even start the installation.

  • Installation problem sun solaris 9 x86 on intel

    I am trying to install sun solaris 9 x86 intel platform edition on my home pc hp e-vectra, configuration is PIII 800 Mhz, 10 GB HDD, 128 MB Ram, 17" color monitor, but it giving me following error :-
    BooT Panic: trap type e, error 0 at 117499
    Cr0: 800000011, cr1: 4, cr3: 17e000
    Eax: 0, ebx: 7e2c, ecx: 0 edx: 16e350
    Es: fffffffe, edi: 17dfe0, ebp: 7e40, esp: 7e20
    Entering boot debugger:
    Please help me, how can I install sun solaris 9 x86 on my HP E-Vectra PC.
    Kalpesh Mehta

    I had similar problems several months ago. I suspect this happens when host pc does not have floppy drive(or bios somehow misreports it) as it was in my case. Solaris 8 seems to work fine in the same environment, so I keep using it for now. Possible workaround might be to use DCA from Solaris 8: Installation of Sol9 started just fine after I entered Sol8 DCA and asked it to boot from Sol9 CD.
    Hope this problem will be fixed in subsequent Sol9 releases.
    Victor

  • Several mysterious problems with Solaris 11 x86 install

    Hi folks,
    I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
    I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
    http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
    Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
    There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
    After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
    Many thanks,
    Chris Tidy
    Edited by: Chris Tidy on 23-Mar-2012 03:36

    Hi folks,
    I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
    I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
    http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
    Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
    There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
    After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
    Many thanks,
    Chris Tidy
    Edited by: Chris Tidy on 23-Mar-2012 03:36

Maybe you are looking for

  • Authentication issue with Xcelsius/Portal integration

    I am facing an issue with the way we have integrated our Xcelsius dashboard with our corporate portal. I know this probably is more of a SDK question than Administration, but I figured I will ask it here anyway since Tim and some others are diverse e

  • How to handle userIntraction error in PC

    While running Indesign CS4 script I am getting userIntraction error in PC, how to rectify that error

  • Does iPhoto refresh a folder of images?

    First of all: what a stunning bit of kit! While I have had iPhoto in one form or another I have not really had time to give it a work through and it is certainly impressive. I suppose I need guidance on two matters: 1 - is it possible to have two lib

  • Both Shift Key Not Working

    Hello Friends, I have HP-Pavilion dv6 Laptop, I have recover OS in last week from then Both Sift keys is not working. Kindly Help with solution for the same. Thanks in Advance Nikhil

  • BizTalk and Azure

    hi, For one of our client we are designing an integration solution with BizTalk Server 2013 R2 and need help to design (with best practices) corresponding into Azure. Need help on what we need to consider while moving an existing application/infrastr