Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: "Steve M. Fabac, Jr." <smfabac@xxxxxxx>
- Date: Sat, 10 Mar 2007 16:01:33 GMT
Bill Vermillion wrote:
In article <DoLHh.6802$jx3.2341@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
Steve M. Fabac, Jr. <smfabac@xxxxxxx> wrote:
Jean-Pierre Radley wrote:ThreeStar typed (on Wed, Mar 07, 2007 at 05:14:05PM -0800):Even so, the size of syslog was 108M (about 10% of 1G). So not relevant.
| The total size of the file might be more relevant than the number of
| entries. 6.0 has special large file utilities for handling files >
| 1Gb which it sounds like this might be.
| | Prepend /u95/bin to your PATH. I would then just blow away syslog:
| /u95/bin/cp /dev/null /usr/adm/syslog
| Restart syslogd and then read it to see what all the errors are.
Oh? I thought that the binaries for "large" files had to to with files
exceeding 2Gb, not 1GB.
I copied syslog to syslog.old and zeroed out syslog in maintenance mode.
wc -l syslog.old caused immediate reboot.
cat syslog.old | wc -l returned 1.5M+ lines.
examining syslog.old shows no recorded messages about any problems on the
hard disk.
And attempting badtrk returns a message that the command is removed
from OS6 and the kernel is in charge of automatically managing bad
tracks.
If this were a SCSI system, I would use the SCSI controller to perform
a "verify" (ala Adaptec 29160), but since it is IDE, I don't have that
tool to check the disk.
And many IDE manufacturers have utility disks for download with
which you can verify and entire drive, and if needed reformat and
lock out bad sectors, very similar to SCSI utilities.
Check the IDE vendors site. The disks are handy.
Replacing the disk is a shotgun approach to diagnosing the problem.
Anyone have any suggestions as to why a system command would
cause a reboot?
Could there be something strange IN the syslog file?
I'm beginning to suspect that this is a DMA issue.
I see in the syslog that DMA has been disabled due to
too many failures (or words to that effect, not on-site
and I don't have the print out).
Other failures that I have noted include reboot when executing
mkisofs to create an ISO image containing a small subdirectory
with files I wanted to move to the replacement system.
But since the client has purchased a used Dell PowerEdge 2600,
we have abandoned trying to get this system repaired and have
concentrated on loading the OS on the replacement hardware.
There is the rub: The Dell has a PERC4/Di RAID on motherboard
controller and everything (every driver downloaded from Dell
and SCO) has failed to resolve the "No root disk controller"
issue.
Just last night while searching Google for PERC4/Di, I came
across a post to the Dell Forms that recommended that both
channels be set to RAID. That may be my problem as in the BIOS
only the first channel is set to RAID the second is set as SCSI.
This apparently was not a problem for Windows Server 2000
as when we first powered on the the machine, it booted to the
login screen. The machine had a DLT tape drive on the second
channel and I think that it was set to SCSI.
.
- References:
- Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: Steve M. Fabac, Jr.
- Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: ThreeStar
- Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: Jean-Pierre Radley
- Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: Steve M. Fabac, Jr.
- Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- From: Bill Vermillion
- Openserver 6.0 wc -l /usr/adm/syslog reboots system
- Prev by Date: Re: Arp warnings at console, IP moving from/to same MAC address?
- Next by Date: Re: Need help installing OS6 on Dell PowerEdge 2600 with PERC4/Di RAID
- Previous by thread: Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- Next by thread: Re: Openserver 6.0 wc -l /usr/adm/syslog reboots system
- Index(es):
Relevant Pages
|
