Going SCSI
NSF_BC
It is time to upgrade and we are looking at SCSI drives.
First of all, is NW3.12 compatible with the latest SCSI standards? If
the SCSI stuff available on the market today is overkill for NW3.12,
would it still work? I know we just need a regular dual channel UW
adapter with regular UW hard drives, but I beleive they are not being
sold anymore.
Also, is there a size limit problem with SCSI? We are looking at 18Gb
drives.
Thanks.
* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Felton Green
A major brand SCSI controller and major brand SCSI drives are recommended.
Good Teflon cables from: http://www.scsipro.com would be in order also. I
like to use a product called Stabilant 22 on the connectors:
http://www.stabilant.com to enhance the contact. Solves lots of problems.
Any size SCSI drive will work and pay attention to the termination. You
might get a little overkill with UW2 drives, but that will be dependent on
the PCI bus and controller. Remember to have enough ram to support the
volume space:
The rule of thumb we use around here is 16 MB of ram per gigabyte of volume
space. 12 MB of ram per gigabyte of volume space thereafter rounded up to
the next ram increment:
i.e. 9 gig of volume space.
16 MB + ( 12 x 8 ) = 16+96 = 112 or 128 MB ram required
You would need 256 MB ram to support 18GB of volume space.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
Brainshare is coming!
March 18 - 23, 2001
Barry Schnur
>It is time to upgrade and we are looking at SCSI drives.
>
>First of all, is NW3.12 compatible with the latest SCSI standards? If
>the SCSI stuff available on the market today is overkill for NW3.12,
>would it still work? I know we just need a regular dual channel UW
>adapter with regular UW hard drives, but I beleive they are not being
>sold anymore.
>
>Also, is there a size limit problem with SCSI? We are looking at 18Gb
>drives.
>
if they are going to be used on the boot (and SYS) partition.
Alternatively, see if you can scare up previous generation (UW) type controllers (such as
2940UW or TekRAM DC390F for example).
You can use the current drives with these controllers -- but remember that with ANY of the
LVD type drives, you need to use an active terminator at the end of the chain whether or
not you use a UW or U2W controller.
18G drives are not a problem, provided you have the memory for them.
Barry Schnur
Novell Support Connection Volunteer Sysop
http://support.novell.com/forums/
Please post replies ONLY via the Newsgroup
Barry Schnur
but if you replace references to it with whatever controller driver is specific to your
U2W or U3W controller, it should work:
Installing the AHA-2940U2W as the Primary Host Adapter and NetWare 3.12 for the first
time.
1. Create the DOS partition and/or install DOS from the Setup diskette.
2. If using a SCSI CD-ROM connected to a Adaptec SCSI adapter, insert
EZ-SCSI for DOS/Windows 3.1 in drive A.
Type A:\DOSINST
(note: If you do not have EZSCSI, download the file DOSDRVR.EXE
from www.adaptec.com and follow the readme to install the drivers
for CD ROM access)
3. Install the software. You need a DOS version of MSCDEX.EXE and will
be prompted to install the file if it is not in your DOS directory.
4. If installing from an IDE based CD-ROM, consult your vendor
documentation for driver install.
5. Reboot your system after install.
6. Start the NetWare 3.12 installation from the CD.
(i.e., D:\netware.312\english\install [or whatever letter MSCDEX
assigns to your CD-ROM])
7. After NetWare installs the DOS portion of the software, DOWN and
EXIT to DOS from the server prompt.
8. Copy the AIC78U2.HAM and AIC78U2.DDI from the 7800 Family Manager
Set Lite NetWare directory to the C:\server.312 directory.
9. Obtain the NWPA_UP.EXE patch from the Novell Web site
http://developer.novell.com/devres/sas/certinfo.htm
10. Change directory to c:\server.312, and copy the patch file
NWPA_UP.EXE to the directory.
11. Execute NWPA_UP.EXE (note: this will create another file,
312PTD.EXE. Answer 'Y' to the prompt to overwrite CDROM.NLM.)
12. Execute 312PTD.EXE.
13. Create the directory c:\server.312\CDSAVE
14. Copy CDROM.NLM to c:\server.312\CDSAVE
15. Update the server with the following command
c:\server.312\312PTD\native\loader\lswap<space>c:\server.312\
312PTD\native\loader\loader.exe<space>c:\server.312\server.exe
16. Type Server from the prompt. Type the server name and IPX address
17. From the console prompt
load c:\server.312\312PTD\native\start\npapatch
load mmattrfx
load nbi31x
load c:\server.312\AIC78U2
18. Note the slot number detected for the AIC78U2W adapter. This will
be added to the Startup.ncf load AIC78U2 statement to automate driver
load using the parameter SLOT=x (x is the detected slot number).
19. Load Install. Create the NetWare partition, SYS volume, and mount
the volume. Complete the installation of the System and Public Files.
20. Create the Autoexec.NCF file. Add the following lines and save
load after311
search add 1 c:\server.312\cdsave
load cdrom
21. Create the Startup.NCF file. Edit the AIC78U2 command line to add
the slot=x parameter. Delete the MEM and INT parameters inserted
by Novell.
22. Load, from the command line, the following
load c:\server.312\312PTD\patch312
23. Install the patches from the c:\server.312\312PTD directory when
prompted for a path.
24. DOWN and EXIT the server
25. Run Server.EXE
26. Installation of the AHA-2940U2W for NetWare 3.12 is complete.
Note: If you have problems with memory registration issues and are
unable to mount the system volume, please refer to the document
Above16.txt at ftp://ftp.adaptec.com/pub/BBS/netware/above16.txt.
NSF_BC
Just to re-confirm...I need 256MB RAM to run a 18Gb (mirrored) drive?
Currently, our server has 64MB RAM with a 8.4Gb mirrored drive and
works fine. Would 128MB do?
Do you know the steps for installing the 39160 adapter (or similar)
into an existing Novell 3.12 server?
How do I copy the data, including trustee info, from the existing
primary IDE 8.4Gb drive to the new SCSI 18Gb drive?
Appreciate the help.
Felton Green
I'd go with the 256 if I could get the bean counters to agree.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming
Brainshare is COMING!
18 - 23 March 2001
Felton Green
LOL... yes there is that.
Barry Schnur
For 18G, using 16K block sizes with OS2 Name space, you could use 128M of RAM I suspect
and do fine.
>Do you know the steps for installing the 39160 adapter (or similar)
>into an existing Novell 3.12 server?
These are going to be quite complicated -- not the controller I'd use -- I'll post the
steps though: (these are for the 2940U2W, I believe the 39160 would work the same simply
change the Adaptec specific drivers).
Barry Schnur
John Pence (a frequent contributor) put together this note which may be of
use here:
This process will let you swap the disk containing the sys volume with
another disk in the same server. Very useful for upgrading server hard
drives without using tape. (I've modified this to take into account the
likely need for the replacement drive to be a DOS boot drive with the OS)
This version of the note is modified for 3X use.
1) Install the new drive in the server.
2) Using FDISK, create a DOS partition -- say 100M.
3) Format the DOS partition with /S to include boot DOS files.
4) Copy all files from the 'to be replaced' DOS partition over to
the new drive with something like XCOPY C:\*.* D:\ /S /E /V
5) Restart Netware (from the original C drive).
6) Create a netware partition on the new drive.
7) Create a "newsys" volume on the new drive and mount it.
NOTE, make sure to add long file name support if the original volumes
had it.
8) Log in to the server as Supervisor and run BINDFIX. This will copy
the old bindery files to *.OLD and create new *.SYS files.
9) Run BINDFIX a second time to insure that the *.OLD and *.SYS files are
the same.
10) Copy data from sys to newsys -- note! Ncopy will not retain rights.
You will either need to use something like Arcserve's copy function,
or something like fstrust. (FSTrust can be found at www.dreamlan.com).
If rights are not an issue, then ncopy will work fine.
Also, Novell provides a downloadable utility for handling rights as
well -- TCOPY2.EXE (track it down at:
http://support.novell.com/cgi-bin/search/patlstdownload?file=/pub/updates/nwos/inw411/tcopy2.exe
11) Dismount sys
12) Dismount newsys
13) Load Install from one of the DOS partitions.
14) Rename sys to oldsys
15) Rename newsys to sys
16) Down and restart Server from the NEW drive's DOS partition. At this
Point, default minimalist versions of the bindery files will be in
place with Supervisor and Guess access and no passwords.
17) Log in to the server as supervisor (no passwords required) from a
workstation and run BINDREST. This will restore the original Bindery
files (steps 8 thru 9 above created these files)
18) Verify that all files, users, groups, trustee rights, etc have been
copied properly and users can log in and work as before the change.
Having done this, you can remove move OLDSYS.
19) Down the server, exit to DOS, and power off. You can remove the
original drive, then make sure to change the SCSI ID's to make the
replacement drive the boot drive.
20) It's possible that DOS won't let you boot from the replaced drive,
if this is the case, boot from a DOS floppy, run FDISK and make sure
to set the DOS partition on the new drive to be the primary and boot
partition. Doing this should NOT affect existing files on the DOS
partition.
21) Power off and restart the system and server.
Barry Schnur
True and anyone who has funding for a 39160 can afford the extra $100 for 128M of RAM.
Barry Schnur
If it were me, I'd go with a TekRAM DC390U2W for about $150 and take the extra $200 for
RAM <smile>
NSF_BC
Is it possible to rename a volume? I'm presuming that the volume has to
be un-mounted before renaming. Does that explain why I don't get the
Rename option when I "Load Install" and go into Volume Options?
Bowing to the Gods of Netware,
Ash
Felton Green
Yes
Rename a Volume
You can use INSTALL to rename a volume. To rename volume SYS:, dismount
SYS:, create another volume, and name the new volume "SYS:".
To rename a volume, complete the following steps.
Procedure
1.Use MONITOR to determine if users have files opened on the volume.
Use BROADCAST to tell users to move to another the volume.
2.Load INSTALL.
3.Select "Volume Options."
4.Select the volume you want to rename.
The "Volume Information" form appears:
5.Highlight the "Status" field and press <Enter>.
6.Select "Dismount Volume."
7.Move to the "Volume Name" field.
8.Type the new name of the volume over the old name and press <Enter>.
9.Answer "Yes" at the prompt to change the volume name.
10.To mount the newly named volume, highlight the "Status" field and press
<Enter>.
11.Select "Mount Volume."
> Bowing to the Gods of Netware,
LOL Thanks