|
Grex > Helpers > #140: Grex System Problems - Spring 2005 | |
|
| Author |
Message |
| 25 new of 457 responses total. |
naftee
|
|
response 271 of 457:
| 
May 5 19:41 UTC 2005 |
thanks for the mulch, tsty !
|
twenex
|
|
response 272 of 457:
|
May 5 19:44 UTC 2005 |
Snicker.
|
drew
|
|
response 273 of 457:
|
May 5 20:54 UTC 2005 |
Re #268:
You have a point about attempting to 'fix' a bad disk. However, a program
that gets the disk electronics to cough up the truth about how much of the
disk is *really* damaged, and how many reserve sectors are left, might be
useful for monitoring purposes.
Re #270:
Humor or not, it may not be far from the truth. cf. HTML content, flash
animations, spam, etc.
|
steve
|
|
response 274 of 457:
|
May 6 05:41 UTC 2005 |
Drew, the problem with that is when things are damaged, how can you trust
the electronics? As an example, IBM has something called smart for their
disks. It's a system where you can run a drive fitness test on a disk to
get a sense of its health. I've found it to be useful in telling me whats
wrong with a dead disk, usually. But it has failed me several times when
testing a disk that the user said had acted weirdly. To be fair, it did
catch a disk that was on the verge of going bad, but I still think the
technology is ripe for improvement.
|
gull
|
|
response 275 of 457:
|
May 6 15:00 UTC 2005 |
Re resp:270: It's definitely true where I work.
I'm not sure how valuable Spinrite-style products really are these days.
You can't directly address sectors on a disk anymore for testing -- the
drive electronics hide all those details and remap bad sectors from a
pool of spares. By the time there are actually visible bad sectors, the
disk has been going south for a long time.
|
tsty
|
|
response 276 of 457:
|
May 6 16:18 UTC 2005 |
re #267 ... oh, right, i forgot. stomp sTomP SToMp st0MP, ds al coda
ummmmmmmmm, about spinrite. every 'objection/dismissal' above demonstrates
that not one of you has read up on *what* it does nor *how*! dammit!!
there is *NO* comparable program in the universe. it FSCKING works!
and all the hidden shit is bypassed, obviated, shunted, circumvented,
counteracted and evaded <insert further descriptions here>.
steve gibson is long overdue for a macarthur grant, imnsho.
and one of it's best built-ins is that it catches stuff and fixes it
BEFORE shit hits the fan. /sheeeeeeeeeeeeeeeeeeeeeeeeeeeSH!
|
russ
|
|
response 277 of 457:
|
May 8 00:13 UTC 2005 |
Configuration of the new disk isn't quite done; /var/log/wrttmp isn't there.
|
richard
|
|
response 278 of 457:
|
May 8 01:33 UTC 2005 |
I have noticed that now when you !finger anybody to see when they logged in
last, it says "never logged in" For any user that I've tried. I guess all
recent login information has been lost?
|
keesan
|
|
response 279 of 457:
|
May 8 01:57 UTC 2005 |
I got garbage again the first time I dialed in but different looking garbage,
and the same wrttmp message.
|
drew
|
|
response 280 of 457:
|
May 8 03:30 UTC 2005 |
Re #274 and 275:
Out of curiosity I checked out a copy of Spinrite. It seems to do the
usual sector checking and attempted 'fixing', with five different levels of
intervention. But in addition, I've found a screen called "SMART settings"
that went something like this:
attribute event cnt margin
---------------------------------
ecc corrected: 0 149
rd chan margin: not reported
relocated sect: 0 60
realloc events: 0
seek errors: 0 49
spin-up retry: 0 49
recal retries: 0 49
cabling errors: 0
uncorrectable: 0
write errors: 0 149
temperature: 40'c /104'f
power-on time: 5,271
Not sure it means anything; a 'margin' of 149 sectors out of 63*255*thousands
seems rather tiny. But I think this is supposed to be the 'bypassing the drive
electronics' part of the program.
Spinrite also works on VMWare virtual machines. However, the SMART screen
does not appear; instead there's a message saying that SMART data is not being
reported.
|
steve
|
|
response 281 of 457:
|
May 8 05:22 UTC 2005 |
/var/log/wrttmp seems OK to me. Is anyone else seeing problems
with anything? The modems are a seperate issue, I think.
|
drew
|
|
response 282 of 457:
|
May 8 05:28 UTC 2005 |
/var/log/wrttmp seems to be restricted-read. is it supposed to be?
|
russ
|
|
response 283 of 457:
|
May 8 12:41 UTC 2005 |
The wrttmp problem is breaking "amin".
|
aruba
|
|
response 284 of 457:
|
May 8 13:27 UTC 2005 |
I get this when I log on:
mesg: Unable to open /var/log/wrttmp to read/write
I guess the mesg program needs access to that directory.
|
eprom
|
|
response 285 of 457:
|
May 8 15:17 UTC 2005 |
looks like /log wasn't permed correctly
last: /var/log/wtmp: Permission denied
mesg: Unable to open /var/log/wrttmp to read/write
|
steve
|
|
response 286 of 457:
|
May 8 21:41 UTC 2005 |
The /log problem is fixed.
|
mary
|
|
response 287 of 457:
|
May 8 23:25 UTC 2005 |
Thanks, STeve, for spending a gorgeous Saturday, working on Grex. And
another thanks to Mark for picking up the new disk and seeing it got to
STeve and that STeve got to Provide.
Is newuser still off?
|
jor
|
|
response 288 of 457:
|
May 9 00:52 UTC 2005 |
|
steve
|
|
response 289 of 457:
|
May 9 01:35 UTC 2005 |
Yes, its still down. I need to finish ressuresting the accounts that
got munged. This next week looks to be better crazy wise, so I should
get it done in the next day or so.
|
keesan
|
|
response 290 of 457:
|
May 9 02:20 UTC 2005 |
I have changed my script to dial the second modem (0513) and no longer get
garbage. Could someone replace the first modem, assuming we have another
working one? Steve et al, thanks.
|
steve
|
|
response 291 of 457:
|
May 9 02:50 UTC 2005 |
I'm sure we have spares. I forgot to reset the modei yesterday. That
might be a good thing to do.
So you've narrowed it down to the first modem. Good and thanks.
|
twenex
|
|
response 292 of 457:
|
May 9 15:45 UTC 2005 |
Thanks, Steve and team.
|
keesan
|
|
response 293 of 457:
|
May 10 01:12 UTC 2005 |
Someone else told me the first modem was bad. At least switch the two.
|
steve
|
|
response 294 of 457:
|
May 10 01:36 UTC 2005 |
Next time I'm there I will. We need to have both of them
working.
|
albaugh
|
|
response 295 of 457:
|
May 10 22:41 UTC 2005 |
It looks like grex went of the 'net for about half an hour just after 6pm.
|