Sponsored Content
Operating Systems Solaris Sunfire V440 could not correctly recognize HD Post 302634521 by hicksd8 on Thursday 3rd of May 2012 12:33:33 PM
Old 05-03-2012
How long have you waited for a response? SCSI devices should "time out" perhaps giving an error indication.

From what you've posted it seems like your other drives are the same type. Have you compared the jumpers with a good drive? There are jumpers for terminator power, drive spin-up, etc. It seems like the controller is having some problem talking to the drive, perhaps waiting for it to become "ready". Is the drive spinning? (Perhaps pull it out quickly from the system and put it to your ear to hear it spin down.)

The drive is a highly programmable animal. If you do get into the SCSI menu try "setting all mode pages to default". That might well clear any communication difficulties.
 

10 More Discussions You Might Find Interesting

1. Solaris

Sunfire 280R Can't Recognize Floppy Drive

Greetings all, I'm in a bit of a situation. I have this Sunfire 280R system that did not have a floppy drive in it, yet we needed one. We grabbed one from another Sun box we had laying around unused, and installed it. The system couldnt recognize it. Tried another floppy drive (non-sun) and... (4 Replies)
Discussion started by: snackiesmores
4 Replies

2. Solaris

Can't get ok prompt on V440

Hello all, This is probably a commonly asked question, but it has me stumped. I have a V440 which upon bootup gives me the option of getting into ALOM with #. I don't have the ALOM password so I want to re-install Solaris 10. When connected to the Management serial interface (on the PCI... (3 Replies)
Discussion started by: juanj
3 Replies

3. Solaris

SunFire V440 Quad gigabit ce1 won't run Gig

Hi there. My first time posting so apologies for any indescretions in advance. :o I've got two SunFire V440 servers running Solaris 5v10. Both have a quad Gigabit ethernet card fitted, both have the same symptom; that is, I can't get the first port ce1 to run Gigabit. Motherboard ports are ce0 and... (10 Replies)
Discussion started by: fixit9660
10 Replies

4. Solaris

video card for a V440

I am looking into getting some cards for the SunFire V440. Not sure how most folks go about this but I am assuming we can find compatible cards for this server platform without going through SUN. Do you guys recommend getting this video card from SUN? Yeah we got these servers without the video... (5 Replies)
Discussion started by: bluridge
5 Replies

5. Solaris

SUN V440 Question

I have a SUN V440 and it is running Solaris 9 with two NICs in the box ce0 ce1. Is there any way to get full duplex 1000? I do I check to see what ce0 and ce1 is set at and if it is not set to full duplex 1000, how do I set it and do I have to reboot the system afterward? I am new to the SUN unix... (5 Replies)
Discussion started by: pmwayne01
5 Replies

6. Solaris

V210 to V440

I recently acquired a server for home use. Currently, I'm running a V210. I was wondering of a way to basically swap hard drives into the V440. I would like to avoid reinstall on the V440 for many reasons. Currently on the V440, when I try to boot up it forces itself into System Maintenance... (1 Reply)
Discussion started by: adelsin
1 Replies

7. Solaris

Need ideas what is wrong with v440

Hello everyone, I'm here today looking for help... I have a SunFire v440 running Solaris 9 at work that manages the SCSI tape drives(LTO3) in our L700 tape library (runs SAMFS). I went into work today and found the machine was ping-able but I could not connect to it via SSH and could not... (7 Replies)
Discussion started by: mainegeek
7 Replies

8. Solaris

V210 to V440

I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it... (21 Replies)
Discussion started by: adelsin
21 Replies

9. Solaris

available PCI slots on v440

How do I find any available PCI slots on a v440? When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used. ================================= IO Devices ================================= Bus Freq Brd Type MHz Slot ... (1 Reply)
Discussion started by: jtamminen
1 Replies

10. Solaris

Solaris V440 keeps crashing

Hi, I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file. ... (1 Reply)
Discussion started by: samnyc
1 Replies
SD(4)							     Linux Programmer's Manual							     SD(4)

NAME
sd - driver for SCSI disk drives SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */ CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti- tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive. SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num- ber is the number of the physical drive in order of detection, and partition_number is as follows: +3 partition 0 is the whole drive partitions 1-4 are the DOS "primary" partitions partitions 5-8 are the DOS "extended" (or "logical") partitions For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system. At this time, only block devices are provided. Raw devices have not yet been implemented. DESCRIPTION
The following ioctls are provided: HDIO_GETGEO Returns the BIOS disk parameters in the following structure: struct hd_geometry { unsigned char heads; unsigned char sectors; unsigned short cylinders; unsigned long start; }; A pointer to this structure is passed as the ioctl(2) parameter. The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters. BLKGETSIZE Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long. BLKRRPART Forces a reread of the SCSI disk partition tables. No parameter is needed. The SCSI ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) fails with the error EINVAL. FILES
/dev/sd[a-h] the whole device /dev/sd[a-h][0-8] individual block partitions COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 SD(4)
All times are GMT -4. The time now is 05:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy