Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Cannot boot from CDROM nor get to OK prompt SunV210
Operating Systems Solaris Cannot boot from CDROM nor get to OK prompt SunV210 Post 302363824 by incredible on Wednesday 21st of October 2009 11:49:32 AM
Old 10-21-2009
Quote:
Originally Posted by LittleLebowski
Still crashing incessantly and rebooting when I go to console. Tried everything suggested so far, cannot get to OK prompt. I appreciate the help so far.

---------- Post updated at 02:23 PM ---------- Previous update was at 02:16 PM ----------

Here's what happens when I try to send a break from the sc prompt and then attempt to get to the OK prompt. Nothing but endless reboots.

Code:
sc> break
Are you sure you want to send a break to the system [y/n]? y
sc> 
SC Alert: SC Request to send Break to host.
console
Enter #. to return to ALOM.
boot -s cdrom
\0x11Probing system devices
Probing memory
Probing I/O buses
Probing system devices
Probing memory
Probing I/O buses



---------- Post updated at 04:27 PM ---------- Previous update was at 02:23 PM ----------

Just cannot get to an OK prompt no matter what. So I also cannot get the box to boot from CDROM.
You will need to see the console and switch to ALOM before you sendbreak, at least with some estimation. You cant break when the system is doing probe tests..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot cdrom error

I'm running a Ultra 60 and having problems booting from the cdrom. This is the error I get, Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args: The file just loaded does not appear to be executable. Any know what could be the problem here? I've even tried connecting a 2nd cdrom... (3 Replies)
Discussion started by: merlin
3 Replies

2. Red Hat

linux will not boot, boot to grub prompt

my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot. The machine come up to grub prompt. I tried the following from grub prompt root (hd0, then press tab key partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies

3. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

4. Solaris

Can't boot from cdrom at ok prompt

I want to install Solaris 9 on SUN ULTRA 10. The cdrom is attached to an ide controller. The server is currently running Solaris 2.6 I insert Solaris cd 1 of 2 and at the ok prompt I type boot cdrom i get the error below Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:... (11 Replies)
Discussion started by: Msororaji
11 Replies

5. Solaris

Boot from cdrom

i am having a problem when trying to boot from cdrom. I received the below message system is not bootable, boot command is disabledfound how can i fix this. also what is the key combination on ordinary keyboard for STOP+A. Is it ctrl+break? (2 Replies)
Discussion started by: shabu
2 Replies

6. Solaris

not able to boot from cdrom

Hi all am trying to boot the system from cdrom in single user mode , however when i am giving command boot cdrom -s i am getting below error Boot Device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0: f file and args: Can't read disk label Can't open disk label package can,t open boot device ... (17 Replies)
Discussion started by: kumarmani
17 Replies

7. Solaris

can't boot cdrom

iam traying to install o/s in spark machine it showing error ok >boot cdrom is showing error short disk read failed to read superblock the file just loaded does not appear to excutable how to solve this can u help me (6 Replies)
Discussion started by: tirupathi
6 Replies

8. Solaris

Boot cdrom - install

Hi community, Does anyone can tell me the difference between "boot cdrom" and "boot cdrom - install" ? Thank you very much:D (3 Replies)
Discussion started by: Sunb3
3 Replies

9. Hardware

Cannot boot from scsi cdrom

I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies

10. UNIX for Beginners Questions & Answers

Cannot boot cdrom -s

Good Afternoon, I'm trying to boot from cdrom so I: bash-2.05# init 0 {1} ok boot cdrom -s and I get: Rebooting with command: boot cdrom -s Boot Device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s Can't read disk label. Can't open disk label package Evaluating: Can't open boot... (13 Replies)
Discussion started by: Stellaman1977
13 Replies

LEARN ABOUT XFREE86

grub-install

GRUB-INSTALL(8) 					  System Administration Utilities					   GRUB-INSTALL(8)

NAME

       grub-install - install GRUB to a device

SYNOPSIS

       grub-install [OPTION...] [OPTION] [INSTALL_DEVICE]

DESCRIPTION

       Install GRUB on your drive.

       --compress=no|xz|gz|lzo
	      compress GRUB files [optional]

       -d, --directory=DIR
	      use images and modules under DIR [default=/usr/lib/grub/<platform>]

       --fonts=FONTS
	      install FONTS [default=unicode]

       --install-modules=MODULES
	      install only MODULES and their dependencies [default=all]

       -k, --pubkey=FILE
	      embed FILE as public key for signature checking

       --locale-directory=DIR use translations under DIR
	      [default=/usr/share/locale]

       --locales=LOCALES
	      install only LOCALES [default=all]

       --modules=MODULES
	      pre-load specified modules MODULES

       --themes=THEMES
	      install THEMES [default=starfield]

       -v, --verbose
	      print verbose messages.

       --allow-floppy
	      make the drive also bootable as floppy (default for fdX devices). May break on some BIOSes.

       --auto-nvram
	      only update NVRAM variables if possible. This option is only available on EFI and IEEE1275 targets.

       --boot-directory=DIR
	      install GRUB images under the directory DIR/grub instead of the boot/grub directory

       --bootloader-id=ID
	      the ID of bootloader. This option is only available on EFI and Macs.

       --core-compress=xz|none|auto
	      choose the compression to use for core image

       --disk-module=MODULE
	      disk module to use (biosdisk or native). This option is only available on BIOS target.

       --efi-directory=DIR
	      use DIR as the EFI System Partition root.

       --force
	      install even if problems are detected

       --force-file-id
	      use identifier file even if UUID is available

       --label-bgcolor=COLOR
	      use COLOR for label background

       --label-color=COLOR
	      use COLOR for label

       --label-font=FILE
	      use FILE as font for label

       --macppc-directory=DIR use DIR for PPC MAC install.

       --no-bootsector
	      do not install bootsector

       --no-extra-removable
	      Do not install bootloader code to the removable media path. This option is only available on EFI.

       --no-nvram
	      don't update the `boot-device'/`Boot*' NVRAM variables. This option is only available on EFI and IEEE1275 targets.

       --no-rs-codes
	      Do not apply any reed-solomon codes when embedding core.img. This option is only available on x86 BIOS targets.

       --no-uefi-secure-boot
	      do  not install an image usable with UEFI Secure Boot, even if the system was currently started using it. This option is only avail-
	      able on EFI.

       --product-version=STRING
	      use STRING as product version

       --recheck
	      delete device map if it already exists

       --removable
	      the installation device is removable. This option is only available on EFI.

       -s, --skip-fs-probe
	      do not probe for filesystems in DEVICE

	      Usage: grub-install [OPTION...] [OPTION] [INSTALL_DEVICE]

       Install GRUB on your drive.

       --compress=no|xz|gz|lzo
	      compress GRUB files [optional]

       -d, --directory=DIR
	      use images and modules under DIR [default=/usr/lib/grub/<platform>]

       --fonts=FONTS
	      install FONTS [default=unicode]

       --install-modules=MODULES
	      install only MODULES and their dependencies [default=all]

       -k, --pubkey=FILE
	      embed FILE as public key for signature checking

       --locale-directory=DIR use translations under DIR
	      [default=/usr/share/locale]

       --locales=LOCALES
	      install only LOCALES [default=all]

       --modules=MODULES
	      pre-load specified modules MODULES

       --themes=THEMES
	      install THEMES [default=starfield]

       -v, --verbose
	      print verbose messages.

       --allow-floppy
	      make the drive also bootable as floppy (default for fdX devices). May break on some BIOSes.

       --auto-nvram
	      only update NVRAM variables if possible. This option is only available on EFI and IEEE1275 targets.

       --boot-directory=DIR
	      install GRUB images under the directory DIR/grub instead of the boot/grub directory

       --bootloader-id=ID
	      the ID of bootloader. This option is only available on EFI and Macs.

       --core-compress=xz|none|auto
	      choose the compression to use for core image

       --disk-module=MODULE
	      disk module to use (biosdisk or native). This option is only available on BIOS target.

       --efi-directory=DIR
	      use DIR as the EFI System Partition root.

       --force
	      install even if problems are detected

       --force-file-id
	      use identifier file even if UUID is available

       --label-bgcolor=COLOR
	      use COLOR for label background

       --label-color=COLOR
	      use COLOR for label

       --label-font=FILE
	      use FILE as font for label

       --macppc-directory=DIR use DIR for PPC MAC install.

       --no-bootsector
	      do not install bootsector

       --no-extra-removable
	      Do not install bootloader code to the removable media path. This option is only available on EFI.

       --no-nvram
	      don't update the `boot-device'/`Boot*' NVRAM variables. This option is only available on EFI and IEEE1275 targets.

       --no-rs-codes
	      Do not apply any reed-solomon codes when embedding core.img. This option is only available on x86 BIOS targets.

       --no-uefi-secure-boot
	      do not install an image usable with UEFI Secure Boot, even if the system was currently started using it. This option is only  avail-
	      able on EFI.

       --product-version=STRING
	      use STRING as product version

       --recheck
	      delete device map if it already exists

       --removable
	      the installation device is removable. This option is only available on EFI.

       -s, --skip-fs-probe
	      do not probe for filesystems in DEVICE

       --target=TARGET
	      install  GRUB  for  TARGET  platform  [default=i386-pc];	available targets: arm-efi, arm-uboot, arm64-efi, i386-coreboot, i386-efi,
	      i386-ieee1275, i386-multiboot, i386-pc,  i386-qemu,  i386-xen,  ia64-efi,  mips-arc,  mips-qemu_mips,  mipsel-arc,  mipsel-loongson,
	      mipsel-qemu_mips, powerpc-ieee1275, sparc64-ieee1275, x86_64-efi, x86_64-xen

       --uefi-secure-boot
	      install  an  image  usable  with UEFI Secure Boot.  This option is only available on EFI and if the grub-efi-amd64-signed package is
	      installed.

       -?, --help
	      give this help list

       --usage
	      give a short usage message

       -V, --version
	      print program version

       Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options.

       INSTALL_DEVICE must be system device filename.  grub-install copies GRUB images into boot/grub.	On some platforms,  it	may  also  install
       GRUB into the boot sector.

REPORTING BUGS

       Report bugs to <bug-grub@gnu.org>.

SEE ALSO

       grub-mkconfig(8), grub-mkimage(1), grub-mkrescue(1)

       The full documentation for grub-install is maintained as a Texinfo manual.  If the info and grub-install programs are properly installed at
       your site, the command

	      info grub-install

       should give you access to the complete manual.

grub-install (GRUB) 2.02-2ubuntu8.3				     July 2018							   GRUB-INSTALL(8)
All times are GMT -4. The time now is 05:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy