Sponsored Content
Operating Systems SCO Warning HD: no root disk controller was found Post 302356370 by mselvaprakash on Friday 25th of September 2009 09:37:47 AM
Old 09-25-2009
Question

now "no root disk controller was found" is rectified.
tis error coz of hardware raid not configured properly.


now only error is

"system error 5: while getting fs type
flushing controller: DAC960PRL cache done."
 

10 More Discussions You Might Find Interesting

1. Solaris

Controller target disk?

Hi, I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below: /pci@8,600000/SUNW,qlc@2 LiD HA LUN --- Port WWN --- ----- Disk description ----- 0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies

2. SCO

warning:hd:no root disk controler was found

hi all i use sco open server reliseas 5 on my system i get an image from system hard disk to another hard disk with acronis software and start system with new(backup)hard disk, but during the boot process some errors generate as follow warning:hd:noroot disk controler was found hd:a boot-time... (2 Replies)
Discussion started by: mehran_malek
2 Replies

3. HP-UX

[Joy Share] - Replace an unknown status controller on HP FC60 disk array

Replace an unknown status controller on HP FC60 disk array Author:JoyOnline JoyChangLu@gmail.com Trouble description: The users detected that the status of controller at A is unknown. Analysis and diagnostic: Physical observed all leds on enclosure of disk array is normal. The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies

4. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

5. Solaris

Help needed to find out the disk controller for veritas disks

hi all i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies

6. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

7. Solaris

Changed disk controller -> drops into GRUB?!

I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all. How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies

8. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

9. Solaris

Disk controller reassignment

Hi The scenario in the oracle t4-1 hardware with solaris 10 is as follows: 1. The initial install on the server was performed with an incorrect disk layout. 2. New disks were ordered and slot into the server. 3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies

10. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
BIO(4)							   BSD Kernel Interfaces Manual 						    BIO(4)

NAME
bio -- Block IO ioctl tunnel pseudo-device SYNOPSIS
pseudo-device bio DESCRIPTION
The bio driver provides userland applications ioctl(2) access to devices otherwise not found as /dev nodes. The /dev/bio device node oper- ates by delegating ioctl calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this interface. The following device drivers register with bio for volume management: arcmsr(4) Areca Technology Corporation SATA RAID controller cac(4) Compaq RAID array controller ciss(4) Compaq Smart ARRAY 5/6 SAS/SATA/SCSI RAID controller mfi(4) LSI Logic & Dell MegaRAID SAS RAID controller The following ioctl calls apply to the bio device: BIOCLOCATE Locate a named device and give back a cookie to the application for subsequent ioctl calls. The cookie is used to tunnel further ioctls to the right device. BIOCINQ Retrieve number of volumes and physical disks for a specific device. BIOCDISK Retrieve detailed information for the specified physical disk. Information returned can include status, size, channel, target, lun, vendor name, serial number, and processor device (ses). BIOCDISK_NOVOL Is just the same as BIOCDISK but doesn't require the disks to be in volume sets, so this applies to any physical disk con- nected to the controller. Note: this ioctl might not be supported on all hardware. BIOCVOL Retrieve detailed information for the specified volume. Information returned can include status, size, RAID level, number of disks, device name association (sd?) and vendor name. BIOCALARM Control the alarm beeper on the device. Supported states are: disable alarm, enable alarm, silence alarm, status and test alarm. Note: These options might not be supported on all hardware. BIOCBLINK Blink an LED of the specified physical disk. Supported blink states are: blink LED, unblink LED and blink alarm LED. Note: This option is only supported if the disk is governed by ses(4) and the hardware supports hardware blinking. BIOCSETSTATE Alter the state of specified physical disk. Supported states are: create/remove hot-spare, create/remove pass through disk, start/stop consistency check in a volume, online disk and offline disk. Note: These options might not be supported on all hardware. BIOCVOLOPS For operations in volume sets. It's able to create and remove a volume set in a supported RAID controller. Note: this ioctl might not be supported on all hardware. FILES
/dev/bio ioctl tunnel device SEE ALSO
ioctl(2), bioctl(8) HISTORY
The bio driver first appeared in OpenBSD 3.2 and NetBSD 4.0. AUTHORS
The bio driver was written by Niklas Hallqvist <niklas@openbsd.org>. The API was written by Marco Peereboom <marco@openbsd.org> and was extended even more for NetBSD by Juan Romero Pardines <xtraeme@netbsd.org>. BSD
May 25, 2008 BSD
All times are GMT -4. The time now is 08:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy