11-29-2006
V1280 boot issues
I have a client with a V1280 onsite and it is having boot problems. Below is the message it is returning when trying to boot. Is this something that anybody has run into, or that you might be able to shed some light on?
{0} ok boot
/ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:f
SunOS Release 5.9 Version Generic_112233-01 64-bit
Copyright 1983-2002 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: /ssm@0,0/pci@18,600000/scsi@2 (glm0):
map setup failed
WARNING: /ssm@0,0/pci@18,600000/scsi@2 (glm0):
attach failed
WARNING: /ssm@0,0/pci@18,600000/scsi@2,1 (glm1):
map setup failed
WARNING: /ssm@0,0/pci@18,600000/scsi@2,1 (glm1):
attach failed
WARNING: timeout: reset target chno = 0 targ = 0
WARNING: timeout: reset target chno = 0 targ = 0
Cannot assemble drivers for root /ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:b
Cannot mount root on /ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:b fstype ufs
panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root
0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, 149aa18, 0)
%l0-3: 000000000148e800 000000000148e800 00000000014296c8 00000000014296d0
%l4-7: 0000000001429400 0000000001421f08 000000000148f000 0000000001491c00
0000000001409a20 genunix:main+98 (1409ba0, f000d348, 1409ec0, 33c596, 2000, 500)
%l0-3: 0000000000000001 0000000000000000 0000000001422fa0 0000000078002000
%l4-7: 000000000140a000 000000000033e000 00000000014cd2b0 0000000001061fc0
skipping system dump - no dump device configured
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm having 2 problems.
1. the system will always look to boot from the net. i've changed the prom settings so that it boots from the disk, by entering "setenv boot-device disk0:3", but the system still seems to want to boot from the net.
2. i replaced my creator3d with an elitem6 and i did... (6 Replies)
Discussion started by: xyyz
6 Replies
2. UNIX for Advanced & Expert Users
hardware on my first FreeBSD server has crashed. i was planning on
swapping the HD into another machine, booting the generic kernel and then
custom tailoring it to the new machine specs.
however, i'm having a problem.
the new machine is using a promise ultra100 card. i don't have any... (2 Replies)
Discussion started by: xyyz
2 Replies
3. SCO
Hello those more knowledgeable than I:
I have been trying to get xp and SCO to coexist on the same system. I have tried several different ways to make both work, here's the list:
-install xp, image it, move the partition to the end of drive, verify it boots, image again,
-boot off of SCO... (6 Replies)
Discussion started by: stay0ut
6 Replies
4. UNIX for Advanced & Expert Users
I still haven't got an answer to this question...
Excerpt from My SysAd Blog
A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated.
"cannot... (2 Replies)
Discussion started by: esofthub
2 Replies
5. Solaris
I have a pentium IV with 512 MB ram and 80 GB HDD.
I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies
6. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
7. Solaris
I 'm trying to configure a WAN boot server on Solaris10 x86 for sparc clients ..
when i try to set up the server m getting following error
./setup_install_server -w /var/apache2/htdocs/wanboot10/wpath /var/apache2/htdocs/wanboot10/ipath
ERROR: Cannot make WAN boot Image file on this... (6 Replies)
Discussion started by: fugitive
6 Replies
8. Red Hat
I am installing Red Hat Linux 6.9 as a VM in Hyper-V on an HP laptop running Windows 10. After the install completes and the VM reboots, it gives me the message, "Detected CPU Family 6 model 142; Warning: Intel CPU model - this hardware has not undergone testing by Red Hat and might not be... (1 Reply)
Discussion started by: tigers580307
1 Replies
LEARN ABOUT POSIX
bootctl
BOOTCTL(1) bootctl BOOTCTL(1)
NAME
bootctl - Control the firmware and boot manager settings
SYNOPSIS
bootctl [OPTIONS...] status
bootctl [OPTIONS...] list
bootctl [OPTIONS...] update
bootctl [OPTIONS...] install
bootctl [OPTIONS...] remove
DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system.
bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.
bootctl list displays all configured boot loader entries.
bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
created if there is no current entry. The created entry will be added to the end of the boot order list.
bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.
bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
variables.
If no command is passed, status is implied.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--path=
Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
the ESP to /boot, if possible.
-p, --print-path
This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.
--no-variables
Do not touch the EFI boot variables.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
Boot loader specification[1] systemd boot loader interface[2]
NOTES
1. Boot loader specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
2. systemd boot loader interface
https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface
systemd 237 BOOTCTL(1)