Hello!
I have an interesting problem. While I'm using user-ppp in about 2-3
minutes after start all system suddenly hangs up, but after 10-15
seconds it start running normally, and this hangup not repeat in
this ppp session. What is can be?
Bye.
P.S. I'm using FreeBSD 5.2.1 on i386. Kernels are
Hello!
I have an interesting problem. While I'm using user-ppp in about 2-3
minutes after start all system suddenly hangs up, but after 10-15
seconds it start running normally, and this hangup not repeat in
this ppp session. What is can be?
Bye.
P.S. I'm using FreeBSD 5.2.1 on i386. Kernels are
On Fri, 8 Oct 2004, Sergey Babkin wrote:
Try to use the Verify menu from the Adaptec BIOS. It finds and tries
to re-map the bad sectors (it tries to preserve data during this too,
unless the sector is completely unreadable).
The verify commands issued by the BIOS are virtually useless
On Fri, Oct 08, 2004 at 12:25:45PM -0500, Sam wrote:
Sick!
Are there actually systems out there that don't have all-zero NULL pointers?
You have officially shattered my previously held beliefs about the
sacredness of memset :(
If there are, I'd be interested to know of them.
See
Mikhail P. [EMAIL PROTECTED] writes:
I reloaded OS on the new drives, then restored all data from the old drives.
All seemed to be fine for 2 months now... but today I woke up, and noticed
these messages again.
A lot of them, or just one or two? Some ATA drives will spin down at
regular
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
I reloaded OS on the new drives, then restored all data from the old
drives. All seemed to be fine for 2 months now... but today I woke up,
and noticed these messages again.
A lot of them,
On Sat, 9 Oct 2004, Mikhail P. wrote:
MP I reloaded OS on the new drives, then restored all data from the old
MP drives. All seemed to be fine for 2 months now... but today I woke up,
MP and noticed these messages again.
MP
MP A lot of them, or just one or two? Some ATA drives will spin
Mikhail P. [EMAIL PROTECTED] writes:
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
A lot of them, or just one or two? Some ATA drives will spin down at
regular intervals to recalibrate, and you'll get a harmless timeout if
you try to write to the disk while it's doing that.
Hi folks,
While traversing our code, I found that many of our code can survive
WARNS=6 if they get some trivial changes.
I think it would be beneficial if we have our code WARNS=6 clean
because this will give better portability, and a more in-depth review
of the code would be positive for better
On Saturday 09 October 2004 16:23, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
A lot of them, or just one or two? Some ATA drives will spin down at
regular intervals to recalibrate, and you'll get a
Mikhail P. wrote:
Hi,
This question probably has been discussed numerous times, but I'm somewhat
unsure what really causes ATA failures..
I have pretty basic server here which has two IDE drives - each is 200GB.
System is FreeBSD-5.2.1-p9
That server has been setup about 9 months ago, and just
I was able to use the badtrk utility in SCO to identify bad blocks and
put them in the bad block table.
The SCSI card is an old Adaptec, AIC-7880 and I believe it does not
support automatic bad block detection/redirection.
This disk came from a spares kits, so even though it is new and never
On Saturday 09 October 2004 18:26, Søren Schmidt wrote:
Hmm, that means that the drive couldn't find the sector you asked for.
Now, what has me wondering is that it is the exact sector where we
switch to 48bit adressing mode. Anyhow, I've just checked on the old
Maxtor preproduktion 48bit
On Sat, 9 Oct 2004, John Von Essen wrote:
The SCSI card is an old Adaptec, AIC-7880 and I believe it does not
support automatic bad block detection/redirection.
If it has a BIOS it should have the verify tool in there...
All the verify tool does, though, is issue a verify command to each
Gotta love when you reply to your own posts... :)
On Sat, 9 Oct 2004, Doug Russell wrote:
If it has a BIOS it should have the verify tool in there...
All the verify tool does, though, is issue a verify command to each
sector. You can do this yourself, even on a running system, also.
I
Mikhail P. [EMAIL PROTECTED] writes:
Well, there is no pattern. [...]
Could be bad cables, could be bad drives. Environmental factors are a
more likely cause, though. Are all the failing disks in the same
machine? If they're in separate machines, are those rack-mount, or
are they standing on
On Saturday 09 October 2004 20:53, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
Well, there is no pattern. [...]
Could be bad cables, could be bad drives. Environmental factors are a
more likely cause, though. Are all the failing disks in the same
machine? If they're
17 matches
Mail list logo
