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 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
On Thu, 7 Oct 2004, John Von Essen wrote:
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while
On Mon, 4 Oct 2004, Jim Durham wrote:
The reboots started out happening at 5.15 pm or so. I had them unplug the
server completely from AC and restart it and now it's happening withing a few
minutes of 12:40pm every day.
The 'last' command output is the only thing showing anything log-wise.
On Sat, 2 Oct 2004, Max Laier wrote:
I am not a fan of providing seat belts like this. People concerned about
Neither am I.
One of the best features of UNIX has always been that you can shoot
yourself in the foot if you want to.
If someone really wants seatbelts, they must be optional.
On Sat, 2 Oct 2004, Sean Farley wrote:
I had sudden reboots over a period of two years. Recently, they started
happening more often. It turned out that the capacitors had gone bad.
Capacitors from about two to three years ago used a poor formula. This
site has information about it:
On Sat, 2 Oct 2004, Dimitry Andric wrote:
Of course, your work is commendable, but isn't is much simpler to just
not type commands like that? I mean, rm -rf /etc or rm -rf /bin
are just as bad, but do you really want to be checking for all
possible `bad' deletions? That way, we'll start to
On Sat, 2 Oct 2004, Giorgos Keramidas wrote:
I see a lot of people don't like the change, even though I made it
default to off and controlled by an environment variable. There's
no reason to keep pushing for it, then.
There's significant support for it, too.
As long as it can be disabled,
On Sat, 2 Oct 2004, Thomas David Rivers wrote:
If I'm remembering correctly - the historical way to
do this is to alias the rm command to something that
else that checks the arguments and complains appropriately
(and then executes /bin/rm.) Typically with just a shell
This would be a
On Mon, 27 Sep 2004, John Von Essen wrote:
I have a new replacement 4Gb disk. With a FreeBSD boot CD I did a dd
and was able to get the new disk setup with all of the old disks
partition maps, boot data, etc.,. The new disk actually boots into SCO
but fails because it only has 100Mb or so of
Oh, I love replying to my own posts :)
On Mon, 27 Sep 2004, Doug Russell wrote:
Try addingconv=sync,noerrorto your dd line. If most of the data
after the defect(s) can be read, you'll end up with an almost complete
partition which will likely run. You can then fsck and restore
On Sun, 3 Mar 2002, Volker Sturm wrote:
I want to write a driver for a device on the serial port. The problem is
that I dont get any info on the protocol that is used for data
..
there already? If not, are there ways to analyze the protocol by a
monitor or whatever technique appropriate?
On Sun, 8 Jul 2001, Matthew Emmerton wrote:
Richard Hodges wrote:
I'm not sure how much of a difference the certificate would make, as far
as import duties goes. I live in Canada (Toronto, Ontario), and accoriding
...
duty, 7% GST, 8% provincial tax, plus a $5.00 handling charge by
On Sun, 8 Jul 2001, Wes Peters wrote:
customer service. Who knows, we might even get a few local shops to pre-
install FreeBSD on a machine or two, with their own FreeBSD discs thrown
in. It could happen.
Heh.. We already do. :) I'm getting quite good at convincing small
shops that
On Tue, 8 May 2001, Bill Paul wrote:
I sent a confirmation of receipt and thank you note to the SMC
people today. I'm not sure if I should be posting their e-mail addresses
all over the lists though.
Perhaps in this type of situation, someone needs to simply collate a list
of
On Sat, 5 May 2001, Alfred Perlstein wrote:
i have never killed a keyboard with un / plugging.
at linux it works.
Well, it works, until your keyboard does actually break :)
It can actually fry the entire motherboard. I doubt linux can
prevent that.
FreeBSD 4.3 allows hotswap
On Sat, 5 May 2001, Alfred Perlstein wrote:
Anything is possible, and I have heard of it happening at least
once. One of the other fun things about hot swapping keyboards
is that you can actually damage the connector which can cause a
short on the motherboard if the poor thing detaches
On Wed, 2 May 2001, Andrew Hesford wrote:
However, I'm quite fond of the green_saver module, which shuts down my
monitor after 15 minutes. Other screensavers are really just for
entertainment; I think green_saver is the only one that serves a really
good purpose.
Perhaps we should make it
On Thu, 13 Jan 2000, Michael Lucas wrote:
So, if I was to sit down and start reading /usr/src/sys, where's the
logical place to start? Or should I start elsehwere? Or is there no
Start with the PR database. Grab a PR, see if you can figure out what makes
it go wrong, and then
20 matches
Mail list logo
