Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Help for HD boot up! 2
- Thread starter poolgun
- Start date
-
1
- #2
marvhuffaker
MIS
It's not mounting the SYS volume. Mirroring a disk doesn't guarantee that it will work in another server. You have to reconfigure the startup for the correct Disk adapter. Otherwise the system won't know how to find the SYS volume.
Look in your C:\SERVER.312\STARTUP.NCF file and find .DSK or .HAM file references. Make sure they match what is actually in the server.
Marvin Huffaker, MCNE
Look in your C:\SERVER.312\STARTUP.NCF file and find .DSK or .HAM file references. Make sure they match what is actually in the server.
Marvin Huffaker, MCNE
- Thread starter
- #3
marvhuffaker
MIS
No. that's not what I mean. you have to make sure the correct drivers are loading. the drivers load from the STARTUP.NCF file.
Marvin Huffaker, MCNE
Marvin Huffaker, MCNE
-
1
- #5
JockMullin
MIS
Hi, Danny
Look at the contents of your startup.ncf file, looking for a load command for something.DSK or something.HAM.
Boot up the server and when it asks for the server name, give it a name (it doesn't matter what). That should get you a console prompt.
Type in the load command from startup.ncf manually and see what errors it gives. If it says the module is already loaded or if it seems to load OK (unlikely) then enter the command MOUNT SYS and see what errors that gives.
That should tell you why the server is unable to mount sys - either the driver is wrong or there is a problem with the SYS volume. If the server can't mount SYS then it is unable to execute autoexec.ncf, which resides on the sys volume and that contains the commands that give the server its name and start the network etc.
Jock
Look at the contents of your startup.ncf file, looking for a load command for something.DSK or something.HAM.
Boot up the server and when it asks for the server name, give it a name (it doesn't matter what). That should get you a console prompt.
Type in the load command from startup.ncf manually and see what errors it gives. If it says the module is already loaded or if it seems to load OK (unlikely) then enter the command MOUNT SYS and see what errors that gives.
That should tell you why the server is unable to mount sys - either the driver is wrong or there is a problem with the SYS volume. If the server can't mount SYS then it is unable to execute autoexec.ncf, which resides on the sys volume and that contains the commands that give the server its name and start the network etc.
Jock
- Thread starter
- #6
- Thread starter
- #7
Jockmullin,
Like you said there are msgs pop-up by typing 2 command.
err msg for load startup.ncf:
invalid load file format
module STARTUP.NCF NOT loaded
Err msg for MOUNT SYS:
There are no accessible disk drivers with Netware partitions check to see that the needed disk drivers have been loaded, and that your disk drivers are properly connected and powered on.
How should I do ??
Thanks!
Danny
Like you said there are msgs pop-up by typing 2 command.
err msg for load startup.ncf:
invalid load file format
module STARTUP.NCF NOT loaded
Err msg for MOUNT SYS:
There are no accessible disk drivers with Netware partitions check to see that the needed disk drivers have been loaded, and that your disk drivers are properly connected and powered on.
How should I do ??
Thanks!
Danny
JockMullin
MIS
Hi Danny
No, you are not supposed to LOAD STARTUP.NCF.
I want you to look at the contents of startup.ncf (it is a text file, you can :
cd \server.312
type startup.ncf
That will show you the contents of that file.
There should be one or more load commands in there, one of which will be loading a file with a .DSK or .HAM file extension. That is the name of the disk driver.
1. make sure that .ham or .dsk file exists in the startup directory. If it isn't there then that is the problem.
2. when you get a console prompt after giving the server a name, type the exact same load command manually. The disk driver should try to load, but will likely give an error message.
Normally the startup directory is called server.312, but it isn't necessarily so. Look at the autoexec.bat file in the root directory to see where the server is loading from.
Jock
No, you are not supposed to LOAD STARTUP.NCF.
I want you to look at the contents of startup.ncf (it is a text file, you can :
cd \server.312
type startup.ncf
That will show you the contents of that file.
There should be one or more load commands in there, one of which will be loading a file with a .DSK or .HAM file extension. That is the name of the disk driver.
1. make sure that .ham or .dsk file exists in the startup directory. If it isn't there then that is the problem.
2. when you get a console prompt after giving the server a name, type the exact same load command manually. The disk driver should try to load, but will likely give an error message.
Normally the startup directory is called server.312, but it isn't necessarily so. Look at the autoexec.bat file in the root directory to see where the server is loading from.
Jock
- Thread starter
- #9
yes, u right.
There is No .DSK & .HAM file in STARTUP.ncf,
BTW after I check the old server's STARTUP.NCF file also No these file.
Here is my STARTUP.ncf
Load c:\srver.312\patches\312ptc\pm312
PMLOAD c:\server.312\patiches\312ptc\
Load os2
load mac
load c:\server.312\mmattrfx
load c:\server.312\nbi31x
load c:\server.312\aic78u2 slot=10003
Set Reserved Buffers below 16 meg = 2000
the old server file is only different with No last Set.
Thanks!
There is No .DSK & .HAM file in STARTUP.ncf,
BTW after I check the old server's STARTUP.NCF file also No these file.
Here is my STARTUP.ncf
Load c:\srver.312\patches\312ptc\pm312
PMLOAD c:\server.312\patiches\312ptc\
Load os2
load mac
load c:\server.312\mmattrfx
load c:\server.312\nbi31x
load c:\server.312\aic78u2 slot=10003
Set Reserved Buffers below 16 meg = 2000
the old server file is only different with No last Set.
Thanks!
JockMullin
MIS
Hi, again.
OK, it looks like it may be a SCSI hard drive.
Ignore os2 and mac.
Check the startup folder to make sure there is mmattrfx.*, nbi31x.* and aic78u2.* present in the directory. I think the disk driver is the aic78u2 one - if memory serves that is for an Adaptec card, but I don't have any docs here so I'm not positive.
Get to a console prompt and type each of those 3 load commands manually. They should either load or say module not found or already loaded or give errors.
I am assuming you have attached the hard drive to a SCSI controller. If there is a SCSI controller then when you power on the machine you should see the bios scan the bus and it should identify all scsi devices attached. If the scsi drive was previously in a machine with several drives, it may not be properly terminated. The last device typically has a special connector to terminate the scsi bus, though some devices will auto-terminate.
If the drive isn't seen by the scsi controller there is no way you can access it.
Jock
OK, it looks like it may be a SCSI hard drive.
Ignore os2 and mac.
Check the startup folder to make sure there is mmattrfx.*, nbi31x.* and aic78u2.* present in the directory. I think the disk driver is the aic78u2 one - if memory serves that is for an Adaptec card, but I don't have any docs here so I'm not positive.
Get to a console prompt and type each of those 3 load commands manually. They should either load or say module not found or already loaded or give errors.
I am assuming you have attached the hard drive to a SCSI controller. If there is a SCSI controller then when you power on the machine you should see the bios scan the bus and it should identify all scsi devices attached. If the scsi drive was previously in a machine with several drives, it may not be properly terminated. The last device typically has a special connector to terminate the scsi bus, though some devices will auto-terminate.
If the drive isn't seen by the scsi controller there is no way you can access it.
Jock
- Thread starter
- #11
Yes. It is 18GB scsi HD with Intel server board, there are 2 SCSI channel on board.
I try 3 command, aic78u2.ham is pop upmsg:
load the module aic78u2.ham
support slot option: 10002
But in startup.ncf slot = 10003
Is this the problem cause the server wont boot up?
Thanks!
I try 3 command, aic78u2.ham is pop upmsg:
load the module aic78u2.ham
support slot option: 10002
But in startup.ncf slot = 10003
Is this the problem cause the server wont boot up?
Thanks!
marvhuffaker
MIS
Yes, change the slot number in the STARTUP.NCF to 10002.
That should be a good start.
Marvin Huffaker, MCNE
That should be a good start.
Marvin Huffaker, MCNE
- Thread starter
- #13
marvhuffaker
MIS
Go into the install utility. LOAD INSTALL.
Check the partition info and see if you can see a NetWAre partition, and check the Volume settings and see if you can see reference to SYS.
You could also use FDISK from DOS and see if it reports either a Netware partition (or it may show up as unknown). The point being that you should have something listed. If there is only a DOS partition, then your SYS volume is not there at all.
Marvin Huffaker, MCNE
Check the partition info and see if you can see a NetWAre partition, and check the Volume settings and see if you can see reference to SYS.
You could also use FDISK from DOS and see if it reports either a Netware partition (or it may show up as unknown). The point being that you should have something listed. If there is only a DOS partition, then your SYS volume is not there at all.
Marvin Huffaker, MCNE
- Thread starter
- #15
marvhuffaker
MIS
Try doing a this at the server command prompt after you enter the server name..
MOUNT SYS
See what the error message is.
Marvin Huffaker, MCNE
MOUNT SYS
See what the error message is.
Marvin Huffaker, MCNE
marvhuffaker
MIS
I found this troubleshooting information in some Novell docuementation. If you can't get it from here, you will probably need to contact someone that has more experience dealing with this type of issues and have them troubleshoot.
Make sure you go through this step by step. It has some good info.
----------------------------------------------------------
A Hard Disk Cannot Be Accessed. (The Format or Surface Test Options in Install Will Not Run, for Example)
02/20/2002
Possible Causes
l The disk driver has not been loaded.
l A hard disk is not installed or cabled correctly.
l The communication channel between the controller interface board, the host bus adapter, and the hard disk is not functioning.
l The hard disk controller interface board is not terminated or addressed correctly.
l The hard disk has not been partitioned.
02/20/2002
Possible Solutions
l Make sure the disk driver is loaded. Run MODULES to view the loaded disk drivers. Use DISKSET if you have loaded the host-bus-adapter driver more than once.
l Check the cables between the hard disks and the controller interface boards. Be sure Pin 1 of each cable is attached to Pin 1 of each connector.
l Check the power cables and make sure they are seated correctly in the power sockets on the hard disks and on the controller interface boards.
l Check the jumper settings on the host bus adapter, the controller interface board, and the hard disk. See the hardware documentation for correct jumper settings.
l Run DISKSET to make sure the hardware configurations contained on the EEPROM chip on the host bus adapter match the hard disks in your file server.
l Run DOS FDISK for internal hard disks.
l Load INSTALL to check the NetWare partition and volume information on the hard disk.
l Make sure that each controller interface board connected to the same host bus adapter has its own valid address.
02/20/2002
None of the Volumes, Including SYS:, Were Mounted
Volume SYS: is the backout volume for TTS. It also contains the bindery files and NLMs. If this volume does not mount when the file server is booted, the AUTOEXEC.NCF file will not execute, LAN drivers will not load, the bindery cannot be opened, and TTS will not be enabled.
02/20/2002
Possible Causes
l Volume SYS: is corrupted.
l The hard disk containing volume SYS: has failed.
l The cable or power to the external hard disks has malfunctioned.
02/20/2002
Possible Solutions
l Run VREPAIR on volume SYS:.
l Check the cabling and power to the external hard disks. Replace any faulty components.
l Replace the hard disk containing volume SYS:.
l If you install a new hard disk type to replace the hard disk in a disk subsystem, be sure to run DISKSET.
l Load INSTALL to create the partitions and volume SYS:.
l Restore the data from a backup copy.
02/20/2002
The Operating System Reports Disk Errors When a Volume is Being Mounted
02/20/2002
Possible Causes
l The file server does not have enough memory to mount the volume.
l The operating system is experiencing directory sector mismatching. This mismatching can be caused if the media is defective or if the file server is turned off without the DOWN command.
02/20/2002
Possible Solutions
l Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.
l Minor will correct themselves through normal network use. For example, if a FAT entry is wrong, the entry is updated and corrected the next time it is written to. If errors do not correct themselves, run VREPAIR.
l Some problems may be corrected automatically with TTS.
02/20/2002
The Operating System Reports Memory Errors When a Volume is Being Mounted
02/20/2002
Possible Causes
l Volumes take more memory to mount than they require after being mounted because the mounting process performs consistency checks (for example, the duplicate copies of all the tables are checked).
l Volumes and directory entries grow dynamically. Therefore, if your file server is using most of the memory (file cache buffers are close to 20% of the memory) and you dismount a volume, you may not be able to remount the volume unless additional memory is available.
l Each additional name space support that you add to a volume increases the size of the FATs and Directory Tables. Adding name space support can cause the tables to grow so large that the file server does not have enough memory to mount the volume.
02/20/2002
Possible Solutions
l Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.
l Free up memory by unloading resources.
l Streamline the directory structure. Every subdirectory takes at least one directory block (a 4KB block of memory). Therefore, subdirectories with only one file require as much memory as directories with 32 files. If you combine directories so that most directories have about 32 files and purge the deleted subdirectories and files, you can free up memory.
l Remove the recently added name space support. This is a destructive step and destroys all the extended file information. Before taking this step, try to free enough memory so that the volume mounts and you can back up the data.
Have all users log out, and then unload all modules except the volume's disk drivers. Dismount any mounted volumes. Down the file server and reboot it to return memory from the Permanent and Alloc pools to the Cache Buffer pool.
To remove the name space, load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume that will not mount.
l Calculate how much memory you need and add memory to the file server. View current volume size with INSTALL INSTALL. Then use the following chart to estimate the total amount of memory needed per volume.
Calculating memory needed for added name space
02/20/2002
A Volume Cannot Be Mounted Because of Corrupted Directory Entry Tables or FATs
02/20/2002
Possible Causes
The following can cause mismatches in the duplicate copies of the FAT and Directory Entry Table:
l A power failure occurs and the file server is not downed with the DOWN command.
l A hard disk fails.
l A disk channel error occurs.
l A volume is not dismounted with the DISMOUNT command.
l Directory information in cache is not completely written to disk.
02/20/2002
Possible Solutions
Complete one or more of the following:
l Run VREPAIR.
l Add a UPS system so that the file server is automatically downed when a commercial power failure occurs.
l Replace faulty disks or controllers.
l If the volume resides on mirrored hard disks, salvage the data on one of the drives. Use INSTALL to unmirror the hard disks (highlight the hard disk you think is least reliable and delete that disk from the mirroring list). Then run VREPAIR on the volume and mount the volume. If the volume will not mount or the data shows some corruption, read the next suggestion before remirroring the hard disks.
l If the volume resides on mirrored hard disks, salvage the data on both hard disks. Use INSTALL to unmirror the hard disks and to salvage the orphaned ("Out Of Sync") hard disk as a new volume. Run VREPAIR on both the old and the new volumes. Mount both volumes and compare the files. Use INSTALL to delete the volume that has the least useful information; rename the salvaged volume, if necessary. Then use INSTALL to remirror the hard disks.
02/20/2002
A Volume Cannot Be Mounted Because a Name Space Module Was Not Loaded First
02/20/2002
Possible Causes
Once a volume has been configured to support more than the DOS naming convention, the loadable name space module must be loaded before the volume can be mounted. One of the following has probably occurred:
l The command to load the name space module is not in the STARTUP.NCF file.
l The module to load the name space has not been copied to the boot directory of the file server.
02/20/2002
Possible Solutions
l Load the name space module; then mount the volume. Copy the name space module to the file server boot directory (C: or A
, and add the load command to the STARTUP.NCF file. The module then loads automatically whenever the file server is booted.
l Delete the name space configuration from the volume. This is a destructive step and destroys all the extended file information. Back up all non-DOS files. Then load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume.
Marvin Huffaker, MCNE
Make sure you go through this step by step. It has some good info.
----------------------------------------------------------
A Hard Disk Cannot Be Accessed. (The Format or Surface Test Options in Install Will Not Run, for Example)
02/20/2002
Possible Causes
l The disk driver has not been loaded.
l A hard disk is not installed or cabled correctly.
l The communication channel between the controller interface board, the host bus adapter, and the hard disk is not functioning.
l The hard disk controller interface board is not terminated or addressed correctly.
l The hard disk has not been partitioned.
02/20/2002
Possible Solutions
l Make sure the disk driver is loaded. Run MODULES to view the loaded disk drivers. Use DISKSET if you have loaded the host-bus-adapter driver more than once.
l Check the cables between the hard disks and the controller interface boards. Be sure Pin 1 of each cable is attached to Pin 1 of each connector.
l Check the power cables and make sure they are seated correctly in the power sockets on the hard disks and on the controller interface boards.
l Check the jumper settings on the host bus adapter, the controller interface board, and the hard disk. See the hardware documentation for correct jumper settings.
l Run DISKSET to make sure the hardware configurations contained on the EEPROM chip on the host bus adapter match the hard disks in your file server.
l Run DOS FDISK for internal hard disks.
l Load INSTALL to check the NetWare partition and volume information on the hard disk.
l Make sure that each controller interface board connected to the same host bus adapter has its own valid address.
02/20/2002
None of the Volumes, Including SYS:, Were Mounted
Volume SYS: is the backout volume for TTS. It also contains the bindery files and NLMs. If this volume does not mount when the file server is booted, the AUTOEXEC.NCF file will not execute, LAN drivers will not load, the bindery cannot be opened, and TTS will not be enabled.
02/20/2002
Possible Causes
l Volume SYS: is corrupted.
l The hard disk containing volume SYS: has failed.
l The cable or power to the external hard disks has malfunctioned.
02/20/2002
Possible Solutions
l Run VREPAIR on volume SYS:.
l Check the cabling and power to the external hard disks. Replace any faulty components.
l Replace the hard disk containing volume SYS:.
l If you install a new hard disk type to replace the hard disk in a disk subsystem, be sure to run DISKSET.
l Load INSTALL to create the partitions and volume SYS:.
l Restore the data from a backup copy.
02/20/2002
The Operating System Reports Disk Errors When a Volume is Being Mounted
02/20/2002
Possible Causes
l The file server does not have enough memory to mount the volume.
l The operating system is experiencing directory sector mismatching. This mismatching can be caused if the media is defective or if the file server is turned off without the DOWN command.
02/20/2002
Possible Solutions
l Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.
l Minor will correct themselves through normal network use. For example, if a FAT entry is wrong, the entry is updated and corrected the next time it is written to. If errors do not correct themselves, run VREPAIR.
l Some problems may be corrected automatically with TTS.
02/20/2002
The Operating System Reports Memory Errors When a Volume is Being Mounted
02/20/2002
Possible Causes
l Volumes take more memory to mount than they require after being mounted because the mounting process performs consistency checks (for example, the duplicate copies of all the tables are checked).
l Volumes and directory entries grow dynamically. Therefore, if your file server is using most of the memory (file cache buffers are close to 20% of the memory) and you dismount a volume, you may not be able to remount the volume unless additional memory is available.
l Each additional name space support that you add to a volume increases the size of the FATs and Directory Tables. Adding name space support can cause the tables to grow so large that the file server does not have enough memory to mount the volume.
02/20/2002
Possible Solutions
l Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.
l Free up memory by unloading resources.
l Streamline the directory structure. Every subdirectory takes at least one directory block (a 4KB block of memory). Therefore, subdirectories with only one file require as much memory as directories with 32 files. If you combine directories so that most directories have about 32 files and purge the deleted subdirectories and files, you can free up memory.
l Remove the recently added name space support. This is a destructive step and destroys all the extended file information. Before taking this step, try to free enough memory so that the volume mounts and you can back up the data.
Have all users log out, and then unload all modules except the volume's disk drivers. Dismount any mounted volumes. Down the file server and reboot it to return memory from the Permanent and Alloc pools to the Cache Buffer pool.
To remove the name space, load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume that will not mount.
l Calculate how much memory you need and add memory to the file server. View current volume size with INSTALL INSTALL. Then use the following chart to estimate the total amount of memory needed per volume.
Calculating memory needed for added name space
02/20/2002
A Volume Cannot Be Mounted Because of Corrupted Directory Entry Tables or FATs
02/20/2002
Possible Causes
The following can cause mismatches in the duplicate copies of the FAT and Directory Entry Table:
l A power failure occurs and the file server is not downed with the DOWN command.
l A hard disk fails.
l A disk channel error occurs.
l A volume is not dismounted with the DISMOUNT command.
l Directory information in cache is not completely written to disk.
02/20/2002
Possible Solutions
Complete one or more of the following:
l Run VREPAIR.
l Add a UPS system so that the file server is automatically downed when a commercial power failure occurs.
l Replace faulty disks or controllers.
l If the volume resides on mirrored hard disks, salvage the data on one of the drives. Use INSTALL to unmirror the hard disks (highlight the hard disk you think is least reliable and delete that disk from the mirroring list). Then run VREPAIR on the volume and mount the volume. If the volume will not mount or the data shows some corruption, read the next suggestion before remirroring the hard disks.
l If the volume resides on mirrored hard disks, salvage the data on both hard disks. Use INSTALL to unmirror the hard disks and to salvage the orphaned ("Out Of Sync") hard disk as a new volume. Run VREPAIR on both the old and the new volumes. Mount both volumes and compare the files. Use INSTALL to delete the volume that has the least useful information; rename the salvaged volume, if necessary. Then use INSTALL to remirror the hard disks.
02/20/2002
A Volume Cannot Be Mounted Because a Name Space Module Was Not Loaded First
02/20/2002
Possible Causes
Once a volume has been configured to support more than the DOS naming convention, the loadable name space module must be loaded before the volume can be mounted. One of the following has probably occurred:
l The command to load the name space module is not in the STARTUP.NCF file.
l The module to load the name space has not been copied to the boot directory of the file server.
02/20/2002
Possible Solutions
l Load the name space module; then mount the volume. Copy the name space module to the file server boot directory (C: or A
, and add the load command to the STARTUP.NCF file. The module then loads automatically whenever the file server is booted.l Delete the name space configuration from the volume. This is a destructive step and destroys all the extended file information. Back up all non-DOS files. Then load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume.
Marvin Huffaker, MCNE
- Thread starter
- #18
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question