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
TRM(4)							   BSD Kernel Interfaces Manual 						    TRM(4)

NAME
trm -- Tekram TRM-S1040 ASIC based PCI SCSI host adapter driver SYNOPSIS
trm* at pci? dev ? function ? scsibus* at trm? DESCRIPTION
The trm driver supports PCI SCSI host adapters based on the Tekram TRM-S1040 SCSI ASIC. HARDWARE
Supported SCSI controllers include: Tekram DC-315 PCI Ultra SCSI adapter without flash BIOS and internal SCSI connector Tekram DC-315U PCI Ultra SCSI adapter without flash BIOS Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI connector For Tekram DC-390 PCI SCSI host adapter, use pcscp(4) driver. For Tekram DC-310/U and DC-390U/UW/F PCI SCSI host adapters, use siop(4) driver. SEE ALSO
cd(4), ch(4), intro(4), pci(4), scsi(4), sd(4), ss(4), st(4), uk(4), scsipi(9) http://www.tekram.com/ AUTHORS
The trm driver was originally written for NetBSD 1.4/i386 by Erich Chen of Tekram Technology, and Rui-Xiang Guo rewrote the driver to use bus_space(9) and bus_dma(9) for NetBSD 1.6. BSD
November 6, 2001 BSD
All times are GMT -4. The time now is 03:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy