|
Grex > Helpers > #140: Grex System Problems - Spring 2005 | |
|
| Author |
Message |
| 25 new of 457 responses total. |
nharmon
|
|
response 245 of 457:
| 
May 4 12:15 UTC 2005 |
Is the disk bad? Have we plugged it into another computer and verified it has
problems?
|
aruba
|
|
response 246 of 457:
|
May 4 14:31 UTC 2005 |
No, the disk is still attached to Grex.
|
steve
|
|
response 247 of 457:
|
May 4 15:03 UTC 2005 |
I should point out that in puting the sd0 disk in some other machine,
it might work. It might appear OK for an hour, or a week. Moving a
damaged disk jossles things. I had a small ide disk at work which did
exaqctly this. It was flaky in the machine it was running on, but
ran OK for some while on a test machine I had. Finally, after several
days of pounding on it, the exact same error cropped up. This is rare,
but if the problem involves something in the head or arm mechanics,
anything can happen. I do not believe that will happen in this case
but moving a suspect disk around can lead to unexpected results.
|
cross
|
|
response 248 of 457:
|
May 4 15:32 UTC 2005 |
This response has been erased.
|
tod
|
|
response 249 of 457:
|
May 4 16:02 UTC 2005 |
Let us know how the 3.7 disc works out.
|
twenex
|
|
response 250 of 457:
|
May 4 16:59 UTC 2005 |
If Plan9 has "dd", why not "fsck"? After all, "dd" isn't even (originally)
native to Unix.
|
cross
|
|
response 251 of 457:
|
May 4 17:18 UTC 2005 |
This response has been erased.
|
twenex
|
|
response 252 of 457:
|
May 4 17:23 UTC 2005 |
Yeeees, but you could still call it "fsck"....
|
mcnally
|
|
response 253 of 457:
|
May 4 17:52 UTC 2005 |
They could also call it "scandisk". After all, lots more people are used
to scandisk than fsck, right?
What does it matter to you what they called it?
|
twenex
|
|
response 254 of 457:
|
May 4 18:01 UTC 2005 |
Just seems arbitrary to name Plan9 "dd" after Unix "dd" but not do the same
with fdisk, that's all.
|
gull
|
|
response 255 of 457:
|
May 4 18:06 UTC 2005 |
A lot of such decisions are arbitrary. Heck, on Linux, 'fsck' is really
just a front end that calls any of a number of more specific
filesystem-checking tools, depending on the type of filesystem in question.
|
drew
|
|
response 256 of 457:
|
May 4 21:01 UTC 2005 |
FWIW, I've had a disk *image file* (created with 'dd if=/dev/hdc of=filename')
produce read errors when used in the virtual machine it was attached to.
|
keesan
|
|
response 257 of 457:
|
May 4 21:14 UTC 2005 |
Three times now, with two different modems, we have dialed into grex and got
garbage. The second dial logged us in. Another grexer reports that the modem
on 484-0513 works but the first one does not, from his location. Is there
any other reliable modem that could be switched with the 0512?
|
steve
|
|
response 258 of 457:
|
May 4 23:03 UTC 2005 |
I think first we need to verify that the line and connection is OK,
physically. Sindi, do you know when these problems started? That
would be good to know.
|
cross
|
|
response 259 of 457:
|
May 5 00:53 UTC 2005 |
This response has been erased.
|
keesan
|
|
response 260 of 457:
|
May 5 01:02 UTC 2005 |
The garbage on dialin happened this week, probably in the last three days.
Jim mentioned it to me yesterday but I had already noticed. It might just have
started yesterday. It occurred again this afternoon.
Jim tried switching from 38 to 19K which did not help.
|
steve
|
|
response 261 of 457:
|
May 5 01:30 UTC 2005 |
Is it always the same modem that messes up?
|
albaugh
|
|
response 262 of 457:
|
May 5 15:22 UTC 2005 |
Drift: Does anyone else think that the fsck program name was partially chosen
because it looks like a get-past-the-censors-disguise for the f-word? ;-)
|
keesan
|
|
response 263 of 457:
|
May 5 16:11 UTC 2005 |
We always dial 0512 but I don't know which modem we actually reach. SOmeone
said the 0512 modem does not work for him but 0513 does, something about
distance from the phone company.
|
twenex
|
|
response 264 of 457:
|
May 5 16:42 UTC 2005 |
Re: #259 - ah, I see.
Re: #262 - Heh. I bet that is exactly the reason! :-)
|
tsty
|
|
response 265 of 457:
|
May 5 16:52 UTC 2005 |
hullo disk problems! there *IS* the best disk repair/recover
software for everyone - and now spinrite 6 will also do xnix drives
and mac drives.
the procedure for xnix formatted drives is a tad more detailed but
if you put *any* worth on your drives you simply must (sorry if that's
preachy) run spinrite on them about every 6 months.
i feel as if i *should* be preachign to the choir when i state adn
restate the obvious, but the choir is still out of tune, it seems.
spinrite 6 grc.com ............................... please!
|
tsty
|
|
response 266 of 457:
|
May 5 16:53 UTC 2005 |
oh, i also wnat to thankx STeve & company for all the extra efforts
on behalf of grex. thank you very mulch.
|
jor
|
|
response 267 of 457:
|
May 5 17:01 UTC 2005 |
Nonsense. None of that thank you stuff.
All we do is criticise, stamp our little feet,
and declare oursleves to be "paying members".
tsty get with the program dude.
|
steve
|
|
response 268 of 457:
|
May 5 18:12 UTC 2005 |
Heh...
The problem with disk "fixing" software is that is nearly all cases its
a giant kludge. With bit densities being hundreds of millions+ per square
inch, the most minute impurities left inside the disk case can cause disasters,
and the tolerances for everything mechanical has shrunk to amazing porportions.
This means that when something in a disk goes wrong its far harder to fix.
When bad disks come in the disk oem's look at the control electronics and
the disk case (mechanical) for problems. Depending on which they find bad
they throw that away and put another "known good" component in, test it and
then have a refurb disk for replacements. I'm not really happy with that
but thats the way things are.
Trying to alter a disks surface by rewriting something just isn't a good
idea now. Back in the era of 300M disks it worked to some extent.
Lastly, when you think of the sheer amount of data that you can put on
a 100G+ disk, you have a huge investment in that data, be it personal or
professional. It just doesn't make sense to trust kludges. Disks are too
cheap not to replace; data is too expensive to replace.
|
keesan
|
|
response 269 of 457:
|
May 5 18:57 UTC 2005 |
Regarding modems, I got garbage again dialing 0512 and before the garbage
there was briefly something about tty00. A second dialin immediately after
connected me properly - does this imply that I got the second modem this time
because the first was still tied up? If so can someone replace the first
modem, or at least confirm the problem? We got it at two locations.
|