10-20-2011
It may be a boot-order problem, with disks appearing in a different order than grub used to see. It finds the boot sector on the right drive, which gets you into grub, but can't find the kernels or config file after that, being on a partition somewhere in a now-different place. Is that adjustable in the bios?
9 More Discussions You Might Find Interesting
1. Solaris
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
hi...
i hav a problem to install sco unix
while installing sco unix 5.0.5 in acer altos with hardware raid
am getting error
"Warning HD: no root disk controller was found
system error 5: while getting fs type
flushing controller: DAC960PRL cache done."
i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies
3. HP-UX
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
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
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
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
Here is my problem:
I have an 1.5TB disk with OpenSolaris (b134, b151a) using non AHCI. I then changed to AHCI in BIOS, which results in severe problems: I can not boot the system.
I suspect the problem is because I changed to AHCI. Now I have changed back to non AHCI, but still I can not... (0 Replies)
Discussion started by: kebabbert
0 Replies
8. Solaris
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
9. Linux
Hi,
a little while ago, one of the GPT Partitioned hard disk had gone faulty in a Mirror RAID and is now successfully replaced.
here is how I did that.
1) created identical partition table on the new disk.
2) attached the mirrors using md commands.
The whole procedure is given below:... (2 Replies)
Discussion started by: busyboy
2 Replies
LEARN ABOUT OSF1
atapi_ide
atapi_ide(7) Miscellaneous Information Manual atapi_ide(7)
NAME
atapi_ide - Interface for ATAPI or IDE (PC) devices
SYNOPSIS
PCI bus CMD/Acer ATAPI/IDE adapter:
bus pci0 at *
bus ata0 at *
controller scsi0 at ata0 slot 0
controller scsi1 at ata0 slot 1
PCI bus Cypress ATAPI/IDE adapter:
bus pci0 at *
bus ata0 at *
bus ata1 at *
controller scsi0 at ata0 slot 0
controller scsi1 at ata1 slot 0
PCMCIA bus ATA/IDE disk card:
bus pcmcia0 at *
bus ata0 at pcmcia?
controller scsi0 at ata0
DESCRIPTION
Devices commonly known for their use on PC devices as ATA or IDE devices are supported using the SCSI CAM device driver. The ATA standard
has also been expanded to include what are known as ATAPI devices. The SCSI CAM device driver is also used for those disks and CD-ROM
devices. These devices may also be known under the names EIDE, ATA-2, Fast-ATA, or Ultra-ATA.
Beacuse the ATA/IDE standard was not developed until after many of the devices that used this standard were produced, there are many
devices which do not strictly comply with the standard. While it is possible some industry standard devices may appear to work, it is also
possible they will cause hang or data corruption cases when used under more stressful situations. For this reason, it is recommended that
only the supported devices be used. These devices have been tested and are certified for correct operation.
ATAPI/IDE controllers allow the connection of two devices. These two devices are known as the master device and the slave device. If only
one device is connected, that device must be the master (slave-only configurations are not supported). When used by the SCSI CAM device
driver, the IDE master device is assigned SCSI id 0 for that controller. The slave device is assigned SCSI id 1 for that controller. No
other SCSI ids are assigned on that controller. Most ATAPI/IDE adapters contain two channels (known as the primary and secondary). Each
of these channels may contain their own master and slave devices. Therefore, a dual channel ATAPI/IDE controller may contain up to 4
devices (a master and slave pair on each channel). These 4 devices are then accessed as SCSI id 0 and 1 on each channel.
Many SCSI operations translate perfectly for use on IDE. For example, read and write operations are the same. However, many SCSI disk
mode pages are emulated by the IDE device driver. For example, you can display the SCSI inquiry mode pages using the following command: %
scu show inq pages pages are created by the device driver to contain the long (full IDE) form of the device name, serial number, revision,
and the operational modes of the device. Only a shortened version of this information is available with the standard SCSI inquiry command.
Note also that the following command: % scu show pages Shows that the SCSI mode pages contain only partial information. Only that informa-
tion (such as geometry) that the drive reports to the system is able to be reformatted into these emulated SCSI mode pages. Much of the
information (such as RPM) is simply not available from the drive, and therefore not accurately reported.
ATAPI devices are much more closely related to SCSI devices, and as such contain their own mode pages. Therefore, for these devices, the
mode page values reported are those from the device, and no emulation is involved.
ATAPI tape devices are not supported at this time.
FILES
/dev/disk/dsk??? /dev/disk/dsk???
RELATED INFORMATION
SCSI(7), rz(7), and disklabel(8) delim off
atapi_ide(7)