09-19-2016
Question on selling/unloading Sunfire V240
Over 6 years ago I picked up a Sunfire V240 from my employer who was unloading all of their Sun hardware. Two processors, 4GB RAM and half dozen SCSI disk drives. It doesn't have an OS or a CD Rom/DVD drive. I have a collection of SCSI drives that should work with the server. So if I can get Solaris 10 or 11 installed, I can fill up the drive bays with working hard drives. I also have a working DEC VT240 terminal and the right rollover cable for the server.
My question is this, since I haven't yet been able to get Solaris installed, would the server be worth more money if it had an OS installed? What would you do if you had this server? I would really just like to get it out of my basement.
Thanks.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey guys,
I had a Sunfire V240 with Solaris 10 preinstalled but replaced the original 2 -73g harddrives with 2 146g drives now I'm trying to install Solaris 9 which I want to use not 10.
Now I keep getting this error:
Rebooting with command: boot
Boot device: disk0:a File and args:
The... (2 Replies)
Discussion started by: kingdbag
2 Replies
2. UNIX for Advanced & Expert Users
Hi ... apologies for posting in this section ... I figured this would be the best place to pose this question - does anyone know a good forum for selling Unix related hardware - I have a handful of HP C3750's that I would like to sell. I am located in Toronto. Thx. (2 Replies)
Discussion started by: krs1
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I trying to jumpstart SunFire V240 Solaris 10, 2006_01. All the jumpstart files on jumpstart install and boot server are ok (tested on another machine Sun Ultra 10). But this system comes out with: "The file just loaded does not appear to be executable." after "boot net - install" and setting... (0 Replies)
Discussion started by: jump
0 Replies
4. Hardware
I recently acquired a sunfire v240 and I'm trying to get into it so I can install linux on it. Right now I'm still trying to get a monitor connected so I can do this.
I've tried connecting to it with a crossover cable to my laptop (vista and linux equipped). I was able to get a connection... (2 Replies)
Discussion started by: QuadRunner750
2 Replies
5. Solaris
Hi All, I'm new to this site. I have a few question since I'm in the process how to to repair my raid on Sun V240 Server.
1. How can we create RAID in Sun Sparc v240?
2. What utility can help people create RAID in Sun Sparc v240?
3. Do we need any special software to create the... (12 Replies)
Discussion started by: angkor
12 Replies
6. Solaris
Question: Which commands to use to shutdown with safety the server; (2 Replies)
Discussion started by: doudou2012
2 Replies
7. UNIX for Dummies Questions & Answers
please help, I am a Linux newbie and I have a sunfire v240 that I got used with the hard drives removed and I am hoping to install Solaris 10 on it to learn. I bought 2 scsi hard drives which are the exact replacement for the machine. I've installed the hard drives and have downloaded Solaris 10... (9 Replies)
Discussion started by: nodgeman
9 Replies
8. Solaris
I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies
9. Solaris
Hi Guys,
I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one).
May I know what the reason of this error and how can I fix it so I can upgrade ALOM using... (0 Replies)
Discussion started by: myrpthidesis
0 Replies
CD(9) BSD Kernel Developer's Manual CD(9)
NAME
cd -- CDROM driver for the CAM SCSI subsystem
DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags.
QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver.
The following is a list of quirks that the driver recognize.
CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
size it is. This flag is currently unimplemented in the CAM cd driver.
CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems
to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.
CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with
multiple luns that are not a part of a changer.
CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto-
matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial
read capacity command for LUN 0 of the changer through the changer scheduling code.
CD_Q_10_BYTE_ONLY
This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these
types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine
whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam-
ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only
reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
byte commands.
FILES
/sys/cam/scsi/scsi_cd.c is the driver source file.
SEE ALSO
cd(4), scsi(4)
HISTORY
The cd manual page first appeared in FreeBSD 2.2.
AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
September 2, 2003 BSD