Strange things are afoot at the Circle K...

[leech]

Ok, so I'm sitting in front my computer, watching 24 through DScaler, and adding a few things here and there to my overnet download.... .then for some strange reason my 73gb 10k rpm Ultra160 SCSI harddrive starts making this annoying knocking sound, and windows all but crashes.... Though of course 24 is still running smoothly. So I scream "Oh !@#$" and turn off my PC. So then I load up into linux. Drive acts fine, I run smartctl -a /dev/sda and it reports that it's running at 35 C and the max temp should be 75C. Ok, temperature is good..... Now, I start Overnet under linux... which has as a shared directory, my windows' Overnet.... Well, here comes that knocking sound again.... So off goes the computer. Now if I even select WindowsXP from Lilo, then the screen goes blank and I get the knocking sound. But I KNOW the drive is not dead, 'cause I can read from it under linux (in fact right now I'm running a test on it and moving files off of it at the same time... It's taking quite some time, but most of the time it's pausing, waiting for my UltraSCSI 2 (80mb/s rather than the 160/s) drive that has linux on it... So something isn't quite right here. I tried switching spots on the cabling, and with the power connectors and I had the same thing....

Any ideas? Did I get a virus, or is Overnet's hashing causing the issues? (though I wouldn't think that would affect Windows' boot process....)

Leech

[MultimediaMan]

Hashing problems I'd consider likely.

Some of Filesharing those apps are very poorly written and slam the crap out of the pagefile.

The machine was a decent one, too...Dual P3, 512MB RAM, WD 800JB HDD running WinXP. ~300MB Free memory.

I had a couple of Linux ISOs (Slackware 9.1) I was trying to grab via Bittorrent that would just sit there and hash (Violently) for hours and never synch or reach out for more files on the WAN. I ended up deleting them outright, and trying again from scratch, this time complete success. Never really did figure out what the problem was.

[az]

I've had this problem too, my NTFS was farked (And I thought it was safer than FAT, with which I never had any problems, and could probably have saved a few files off ). Curiously, I was running eDonkey, too. But it wasn't just my eDonkey shares, it was the whole computer. It would be unbearably slow (taking MINUTES to open a window), the HD made munching noises, etc. It also made those noises when trying to access it from Linux (booted from CD). I ended up formatting, lost my earliest digital pictures of my daughter But the HD's been fine ever since.

AZ

[The PIT]

Ah Linux

[leech]

Yeah, PIT, ah, Linux. Linux is working great, windows is Bleh. Windows won't even boot. I did manage, with linux, to remove most of the files in my Overnet Temp directory. Wether or not that fixed it, I haven't tested yet.....

I did run 'smartctl -t long /dev/sda' on it and it came back with;

SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Foreground long Failed in segment --> 1 7105 0x 8715d6f [0x3 0x11 0x0]
# 2 Background long Failed in segment --> 1 7104 0x 8715d6f [0x3 0x11 0x0]


Houston, we have a problem..... I'm thinking if I backed everything up though, and did a fresh format, I'm hoping it'll work. I'm just waiting for that 200 gb baracuda that I ordered.... http://forums.murc.ws/showthread.php?s=&threadid=46761

Leech

[rylan]

Bad sectors on your drive?

[TransformX]

Originally posted by az
I've had this problem too, my NTFS was farked (And I thought it was safer than FAT, with which I never had any problems, and could probably have saved a few files off ). Curiously, I was running eDonkey, too. But it wasn't just my eDonkey shares, it was the whole computer. It would be unbearably slow (taking MINUTES to open a window), the HD made munching noises, etc. It also made those noises when trying to access it from Linux (booted from CD). I ended up formatting, lost my earliest digital pictures of my daughter But the HD's been fine ever since.

AZ

[off topic]<hr>Speaking of your daughter, are we going to see more pictures of her ?<hr>[/off topic]

[Gurm]

Once a drive gets bad sectors, it never gets "better". And long gone are the days when you could have SOME bad sectors and have it stay that way indefinitely.

Back the data up, and get another drive.

- Gurm

[az]

Dogbert, I may post some pictures in the near future. Don't know when though.

AZ

[leech]

Originally posted by Gurm
Once a drive gets bad sectors, it never gets "better". And long gone are the days when you could have SOME bad sectors and have it stay that way indefinitely.

Back the data up, and get another drive.

- Gurm

Actually I was hoping I could just get a voodoo doll, and maybe dance around it like a fool!

Actually this never really specifies that it's a bad sector....

Here's the full report on it.Device: QUANTUM ATLAS10K2-TY734L Version: DDD6
Serial number: {removed}
Device type: disk
Local Time is: Wed Feb 18 16:52:20 2004 MST
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK
Current Drive Temperature: 33 C
Drive Trip Temperature: 75 C

Error counter log:
Errors Corrected Total Total Correction Gigabytes Total
delay: [rereads/ errors algorithm processed uncorrected
minor | major rewrites] corrected invocations [10^9 bytes] errors
read: 105283 1 0 0 0 49.836 0
write: 0 0 0 0 0 4.584 0

Non-medium error count: 23

SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Foreground long Failed in segment --> 1 7105 0x 8715d6f [0x3 0x11 0x0]
# 2 Background long Failed in segment --> 1 7104 0x 8715d6f [0x3 0x11 0x0]
# 3 Background short Completed - 2030 - [- - -]

Long (extended) Self Test duration: 3504 seconds [58.4 minutes]

Leech

[ZokesPro]

Had the same problem with a WD Caviar drive, did a low level format and the drive worked from there on. Can't explain why though.

[az]

No need for low-level formatting IIRC. It sounds exactly like what I had, which was just a really farked filesystem. Just formatting should suffice, if not, LL-formatting it will most likely cure the drive. I don't think it's a hardware problem.

AZ

[Jon P. Inghram]

I think the drives have a servo track recorded on the disk, if it got corrupted a low-level format might fix it and restore functionality.

[leech]

Actually the drive (windows on it still) is working fine now, after I deleted some of the overnet files. Definitely must have been the hashing problems. Though now, if I run dosfsck under linux, it says that the bootsector does not match it's backup... but apparently the bootsector is working....

My next thoughts would be to do a lowlevel format, because that alone will mark the bad sectors, and will make it so the drive won't report them.... ALL harddrives have bad sectors on them and are marked this way from the factory.

Leech