Sponsored Content
Operating Systems Solaris Solaris 8 booting from wrong device Post 302206458 by sparcguy on Tuesday 17th of June 2008 10:36:26 PM
Old 06-17-2008
go to your ok prompt do a devalias
and compares if any boot device alias has /pci@1f,0/pci@1/scsi@8/sd@0,0 in it.

If there isnt. Do a nvalias and map a new alias boot3(whatever) to /pci@1f,0/pci@1/scsi@8/sd@0,0

do a man on devalias
do a man on nvalias
 

4 More Discussions You Might Find Interesting

1. Solaris

What's wrong with my system? Solaris not booting.

Booting the 32-bit OS ... SunOS Release 5.7 Version Generic_106541-31 Copyright (c) 1983-2002, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: wz-ultra1 metainit: wz-ultra1: there are no existing databases The system is coming up. Please wait. checking ufs... (2 Replies)
Discussion started by: CollenM
2 Replies

2. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

3. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

4. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
MPII(4) 						   BSD Kernel Interfaces Manual 						   MPII(4)

NAME
mpii -- LSI Logic Fusion-MPT Message Passing Interface II SYNOPSIS
mpii* at pci? dev ? function ? DESCRIPTION
The mpii driver provides support for storage controllers using the LSI Logic Fusion-MPT Message Passing Interface II family of chipsets: - LSISAS2004, LSISAS2008 These chipsets can be found on the following controllers: - Dell PERC H200 - LSI SAS 9200-8e, SAS 9211-4i, SAS 9211-8i Some models of these controllers have varying degrees of support for RAID 0 and RAID 1. mpii supports monitoring of the logical disks in the controller through the bioctl(8) and envstat(8) commands. EVENTS
The mpii driver is able to send events to powerd(8) if a logical drive in the controller is not online. The state-changed event will be sent to the /etc/powerd/scripts/sensor_drive script when such condition happens. SEE ALSO
intro(4), pci(4), scsi(4), sd(4), bioctl(8), envstat(8), powerd(8) HISTORY
The mpii driver first appeared in OpenBSD 4.7. AUTHORS
The mpii driver was written by James Giannoules and Mike Belopuhov. BUGS
The chips supported by mpii do not use a SCSI-like identifier. Instead they use an opaque ID and leave discovery order up to the operating system. The code to handle this is currently not implemented and therefore it is not a good idea to run this driver on a multi-boot machine or with more than 1 drive. BSD
April 19, 2012 BSD
All times are GMT -4. The time now is 07:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy