morgoth
10-16-2006, 08:13 PM
Hopefully someone here will have an answer for me, saves me having to try and find some Windows forum, and I trust you guys know more about Windows than those types anyways.
Getting a bunch of page errors on 1 of the disks:
The device, \Device\Scsi\ultra1, did not respond within the timeout period.
Now, I have a complex drive setup, with a dvd-rom drive, cd-rw drive, and dvd-r drive, as well as a 30gb hdd, 80gb hdd and 300gb hdd. So - I'm using a promise controller (the one that's ata133 compliant, can't remember the model number). The dvd-r and 300gb drive are attached to the promise controller, the rest are attached the motherboards onboard controllers.
Windows' device naming policy is shite, I can't for the life of me confirm what \device\scsi\ultra1 is the 300gb drive, but I suspect it is. I really hate the way that Windows event viewer uses a particular terminology that isn't used anywhere else - consistency problems really annoy me.
Anyways, I've downloaded western digitals diagnostic tools, and ran both short and extended tests on all 3 hdds, they all come up fine. I've rebooted and ran chkdsk during startup for the main 80gb drive (from which Windows boots from). It seems to have come up OK:
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 13 unused index entries from index $SII of file 0x9.
Cleaning up 13 unused index entries from index $SDH of file 0x9.
Cleaning up 13 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.
78140128 KB total disk space.
58114900 KB in 130142 files.
45108 KB in 9578 indexes.
0 KB in bad sectors.
225436 KB in use by the system.
65536 KB occupied by the log file.
19754684 KB available on disk.
4096 bytes in each allocation unit.
19535032 total allocation units on disk.
4938671 allocation units available on disk.
Internal Info:
10 4f 02 00 d3 21 02 00 a5 34 03 00 00 00 00 00 .O...!...4......
0f 09 00 00 01 00 00 00 e2 03 00 00 00 00 00 00 ................
30 a1 b1 04 00 00 00 00 d6 4e 0d 64 00 00 00 00 0........N.d....
e4 46 ac 0a 00 00 00 00 d6 1a 93 bc 05 00 00 00 .F..............
22 23 31 1f 01 00 00 00 6c d2 45 56 07 00 00 00 "#1.....l.EV....
99 9e 36 00 00 00 00 00 b0 3a 07 00 5e fc 01 00 ..6......:..^...
00 00 00 00 00 50 0d db 0d 00 00 00 6a 25 00 00 .....P......j%..
Windows has finished checking your disk.
Please wait while your computer restarts.
The 30gb drive I scanned from within Windows since Windows wasn't using it. Event viewer doesn't show any log for the scan, and it didn't give me any informational results on the scan either. I have no idea if chkdsk keeps logs of scans or where, a quickish google search found *uck all on the subject.
The 300gb drive refuses to scan. Chkdsk won't do it from within windows GUI, or from a dos prompt. It just says it can't scan it after a period of time. I haven't tried doing a check via a reboot yet (that's planned for tonight).
Any suggestion(s) on why chkdsk won't scan it from within windows? Could it be that it doesn't like the drive cos it's attached to a ide controller card? I'm probably going to boot off Knoppix and run a fsck on it as well, although the drive is formatted with ntfs so not much I can really do there...
Furthermore, my system is (OK guys I know you're going to enjoy this), running like a dog of late. spybot shows its clean, Microsoft's own anti spyware software is set to scan at 2am every night, last few times it hasn't scanned, with an error message that something stopped it or it encountered an error. services.exe service is also having issues. Also, event viewer sees entdrv51.sys (a file used by Mcaffee anti virus software enterprise 8i which we use on the network here) as being spyware and as being stopped from accessing the net. This is only a new problem according to event viewer. I've googled a bit, and it seems that this file can be used by some forms of spyware and malware. I'm going to get the network admin to do a scan of my host for viruses from the server end, just in case.
Windows stability has been up the creek for the past month or so, and I suspect it's a direct result of having to create a new profile when the domain controller domain was updated by Warren a few months back. I'm not very happy with Windows stability at all, but sadly, I don't have much choice. I've paid good money for certain pieces of software (Photoshop CS2 and Neat Image) and they run only in Windows. I refuse to fork out money for things like CrossOver office or dual boot a system. If Adobe Photoshop CS2 and Neat Image were ported to Linux I'd be back in Linux land in an instant, I've had a gutful of Windows. It's fucked up more times in 7 months than Linux did in 4 and a half years, with a tonne more applications installed and a shitload more updates. Windows XP is just not robust or reliable enough.
Anyways, any suggestions on the chkdsk issue are appreciated.
Cheers,
Dave
Getting a bunch of page errors on 1 of the disks:
The device, \Device\Scsi\ultra1, did not respond within the timeout period.
Now, I have a complex drive setup, with a dvd-rom drive, cd-rw drive, and dvd-r drive, as well as a 30gb hdd, 80gb hdd and 300gb hdd. So - I'm using a promise controller (the one that's ata133 compliant, can't remember the model number). The dvd-r and 300gb drive are attached to the promise controller, the rest are attached the motherboards onboard controllers.
Windows' device naming policy is shite, I can't for the life of me confirm what \device\scsi\ultra1 is the 300gb drive, but I suspect it is. I really hate the way that Windows event viewer uses a particular terminology that isn't used anywhere else - consistency problems really annoy me.
Anyways, I've downloaded western digitals diagnostic tools, and ran both short and extended tests on all 3 hdds, they all come up fine. I've rebooted and ran chkdsk during startup for the main 80gb drive (from which Windows boots from). It seems to have come up OK:
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 13 unused index entries from index $SII of file 0x9.
Cleaning up 13 unused index entries from index $SDH of file 0x9.
Cleaning up 13 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.
78140128 KB total disk space.
58114900 KB in 130142 files.
45108 KB in 9578 indexes.
0 KB in bad sectors.
225436 KB in use by the system.
65536 KB occupied by the log file.
19754684 KB available on disk.
4096 bytes in each allocation unit.
19535032 total allocation units on disk.
4938671 allocation units available on disk.
Internal Info:
10 4f 02 00 d3 21 02 00 a5 34 03 00 00 00 00 00 .O...!...4......
0f 09 00 00 01 00 00 00 e2 03 00 00 00 00 00 00 ................
30 a1 b1 04 00 00 00 00 d6 4e 0d 64 00 00 00 00 0........N.d....
e4 46 ac 0a 00 00 00 00 d6 1a 93 bc 05 00 00 00 .F..............
22 23 31 1f 01 00 00 00 6c d2 45 56 07 00 00 00 "#1.....l.EV....
99 9e 36 00 00 00 00 00 b0 3a 07 00 5e fc 01 00 ..6......:..^...
00 00 00 00 00 50 0d db 0d 00 00 00 6a 25 00 00 .....P......j%..
Windows has finished checking your disk.
Please wait while your computer restarts.
The 30gb drive I scanned from within Windows since Windows wasn't using it. Event viewer doesn't show any log for the scan, and it didn't give me any informational results on the scan either. I have no idea if chkdsk keeps logs of scans or where, a quickish google search found *uck all on the subject.
The 300gb drive refuses to scan. Chkdsk won't do it from within windows GUI, or from a dos prompt. It just says it can't scan it after a period of time. I haven't tried doing a check via a reboot yet (that's planned for tonight).
Any suggestion(s) on why chkdsk won't scan it from within windows? Could it be that it doesn't like the drive cos it's attached to a ide controller card? I'm probably going to boot off Knoppix and run a fsck on it as well, although the drive is formatted with ntfs so not much I can really do there...
Furthermore, my system is (OK guys I know you're going to enjoy this), running like a dog of late. spybot shows its clean, Microsoft's own anti spyware software is set to scan at 2am every night, last few times it hasn't scanned, with an error message that something stopped it or it encountered an error. services.exe service is also having issues. Also, event viewer sees entdrv51.sys (a file used by Mcaffee anti virus software enterprise 8i which we use on the network here) as being spyware and as being stopped from accessing the net. This is only a new problem according to event viewer. I've googled a bit, and it seems that this file can be used by some forms of spyware and malware. I'm going to get the network admin to do a scan of my host for viruses from the server end, just in case.
Windows stability has been up the creek for the past month or so, and I suspect it's a direct result of having to create a new profile when the domain controller domain was updated by Warren a few months back. I'm not very happy with Windows stability at all, but sadly, I don't have much choice. I've paid good money for certain pieces of software (Photoshop CS2 and Neat Image) and they run only in Windows. I refuse to fork out money for things like CrossOver office or dual boot a system. If Adobe Photoshop CS2 and Neat Image were ported to Linux I'd be back in Linux land in an instant, I've had a gutful of Windows. It's fucked up more times in 7 months than Linux did in 4 and a half years, with a tonne more applications installed and a shitload more updates. Windows XP is just not robust or reliable enough.
Anyways, any suggestions on the chkdsk issue are appreciated.
Cheers,
Dave