We've got a Sun Fire V245 that's failing to boot from either boot disk (mirrored using SVM). It simply hangs after loading a few modules:
Code:
Sun Fire V245, No Keyboard
Copyright 2006 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.22, 1024 MB memory installed, Serial #74521658.
Ethernet address 0:14:4f:71:1c:3a, Host ID: 84711c3a.
Rebooting with command: boot -avr /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
Boot device: /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a File and args: -avr /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0
krtld: Unused kernel arguments: `/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@2,0'.
module /platform/sun4u/kernel/sparcv9/unix: text at [0x1000000, 0x10a096d] data at 0x1800000
module /platform/sun4u/kernel/sparcv9/genunix: text at [0x10a0970, 0x12615bf] data at 0x1867cc0
module /platform/SUNW,Sun-Fire-V245/kernel/misc/sparcv9/platmod: text at [0x12615c0, 0x1261e4f] data at 0x18be088
module /platform/sun4u/kernel/cpu/sparcv9/SUNW,UltraSPARC-IIIi: text at [0x1261e80, 0x1272f0f] data at 0x18be900
Once it get's to this stage, we get nothing. This occurs when trying to boot fom either of the mirrored disks. We're getting someone onsite with Solaris media, so we can boot from CD into single user. In the meantime, can anyone shed any light as to what could be the issue here?
After these modules are loaded, am I correct in assuming the kernel tries to mount the root filesystem? I guess if we're having this issue on both boot disks, the root filesystem has become unusable/corrupted in SVM?
Hi,
We have a SunFire V880, hooked up with 2 T3 arrays. When ever we issue a reboot command on the system, it hangs at the same place right where it says
syncing file systems done.
To bring it back we shutdown power and it comes clean.
By the way init 6 command works fine.
Has anyone come... (3 Replies)
Hi all,
I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console .
Both the IP adresses of the server and the console are in a private network (address 10.67.xxx).
For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Greetings Forumers!
I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Solaris 10 (Sun V210) System hangs every couple of months. Have to go into ALOM to reset. I did a consolehistory report and seen this in it.
Failed to exec inetd_start method of instance svc:/network/bootps/udp:default: I/O error
WARNING: /pci@1c,600000/scsi@2 (glm0):
Resetting... (3 Replies)
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Power server up runs through diagnostics.
Goes to the boot section and then the bit where the cursor is spinning and thats it. Hangs completely.
Any ideas? (10 Replies)
Anyone ever see an issue where ufsdump 'hangs' after the IV Pass?
Normally, it will update with an estimate of how long it will take to complete...and update the info every 20 minutes.
I'm running the following command:
root# ufsdump 0f - /fsmount | ( cd /zfs/newfsmount ) ; ufsrestore rf - )... (2 Replies)
dear members,
i am a newbie to solaris 11.3, and deeply impressed. On my test pc (Lenovo M90), however, using the internet hangs the system from time to time;
initializing the connecting (WLAN) during installation (via the live cd)
took two attempts as well.
Maybe someone has a solution... (7 Replies)
Discussion started by: RichardLichten
7 Replies
LEARN ABOUT SUNOS
tavor
tavor(7D)tavor(7D)NAME
tavor - InfiniHost MT23108/MT25208 InfiniBand (IB) Driver
SYNOPSIS
PCI pci15b3,5a44@pci-slot, pci15b3,5a45@pci-slot
PCI-E pci15b3,6278@pci-e-slot, pci15b3,6279@pci-e-slot
The tavor driver is an IB Architecture-compliant implementation of an HCA, which operates on the Mellanox MT23108 InfiniBand ASSP and the
Mellanox MT25208 InfiniBand ASSP. These ASSP's support the link and physical layers of the InfiniBand specification, while the ASSP and
the driver support the transport layer.
The tavor driver interfaces with the InfiniBand Transport Framework (IBTF) and provides an implementation of the Channel Interfaces that
are defined by that framework. It also enables management applications and agents to access the IB fabric.
FILES
/kernel/drv/tavor
32-bit ELF kernel module ( platform only).
/kernel/drv/amd64/tavor
64-bit ELF kernel module ( platform only).
/kernel/drv/sparcv9/tavor
64-bit ELF Kernel Module (SPARC platform only).
/kernel/drv/tavor.conf
Driver configuration file.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |PCI-based systems |
+-----------------------------+-----------------------------+
|Availability |SUNWtavor |
+-----------------------------+-----------------------------+
driver.conf(4), printers.conf(4), attributes(5)
Writing Device Drivers
In addition to being logged, the following messages may appear on the system console.
tavor : driver attached for maintenance mode only.
There was a failure in the boot process of the tavor ASSP and the only function that can be performed is to re-flash firmware on the
ASSP.
driver failed to attach.
The ASSP could not boot into either operational (HCA) mode or into maintenance mode. The device in inoperable.
Unexpected port number in port state change event.
A port state change event occurred, but the port number in the message does not exist on this HCA. This message also indicates the port
number that was in the port state change.
Tavor driver successfully detached.
The driver has been removed from the system, and the HCA is no longer available for transfer operations.
tavor"n": port "m" up.
A port up asynchronous event has occured. "n" represents the instance of the Tavor device number, and "m" represents the port number on
the Tavor device.
tavor"n": port "m" down.
A port down aynchronous event has occurred.
Tavor: <command name> command failed.
A internal firmware command failed to execute.
11 Feb 2005 tavor(7D)