[Sorry if this is duplicate response. Previous try hasn't shown up on my
server.]
dobey said:
ggull said:
Got a Seagate "FreeAgent Pro" 750GB external drive, tried to connect it
to existing eSATA port (have been using a WD 500GB in PowerSpec enclosure
with no problems).
Couldn't find the Seagate by doing "Rescan Disks" in Computer Management,
so I restart. Here I get a bit fuzzy. I think I had to do this twice,
and cold-booted second time. Both times it went to a blue screen and ran
some diagnostics by me too quickly to really read, much less ponder or
take notes. It ended up with doing a chkdsk complete scan (couple of
hours -- I went and made dinner). It appears to have found some of the
pre-loaded files to be bad, at least they were empty/altered/absent.
The Question: are there log files for those startup diagnostics and/or
chkdsk that I could check out before contacting Seagate customer service.
[Apart from this problem, something is not acting right ... much slower
than the WD, flaky, hangs system.]
Event Viewer usually has the information from blue screens and chkdsk
results, (listed as Winlogon).
Thanks! I never would have found that.
[For future reference, this is under Applications in the Event Viewer.
Double click on an event for details, which can then be copied to the
clipboard with the <printed pages icon> button.]
This is what happened the first logon with the Seagate attached (following
logon it checked but found it no problems, successive logons doesn't do any
check).
Any comments?
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 9/14/2007
Time: 10:15:26 PM
User: N/A
Computer: GATEWAY503GR
Description:
Checking file system on F:
The type of the file system is NTFS.
Volume label is FreeAgent Drive.
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x43 for possibly 0x9e clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x43 for possibly 0x9e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x24 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 36.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xdf for possibly 0xf clusters.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xdf for possibly 0xf clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x30 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 48.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee for possibly 0x6 clusters.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xee for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 49.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf4 for possibly 0x6 clusters.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf4 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x32 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 50.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xfa for possibly 0x8b47 clusters.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xfa for possibly 0x8b47 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x33 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 51.
The object id in file 0x26 does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
The object id in file 0x27 does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x26 is incorrect.
6c 61 6e 67 31 30 35 33 5c 6c 61 6e 67 66 65 31 lang1053\langfe1
30 33 33 5c 6c 61 6e 67 6e 70 31 30 35 33 5c 69 033\langnp1053\i
Correcting error in index $I30 for file 38.
The index bitmap $I30 in file 0x26 is incorrect.
Correcting error in index $I30 for file 38.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff ab 93 d5 d3 d7 62 6d 13 .............bm.
27 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 '...............
Sorting index $I30 in file 38.
The file reference 0x1000000000021 of index entry EULA of index $I30
with parent 0x5 is not the same as 0x2000000000021.
Deleting index entry EULA in index $I30 of file 5.
Index entry Warranty.pdf of index $I30 in file 0x43 points to unused file
0x44.
Deleting index entry Warranty.pdf in index $I30 of file 67.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file NPROTECT (33) into directory file 70.
Recovering orphaned file RP487 (34) into directory file 30.
Recovering orphaned file 200707~1 (38) into directory file 5.
Recovering orphaned file 20070702 Some rainbow pics (38) into directory file
5.
Recovering orphaned file 27MR-S~1.JPG (39) into directory file 38.
Recovering orphaned file 27 MR-Str hH Regenbogen 1.jpg (39) into directory
file 38.
Replacing invalid security id with default security id for file 36.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Inserting data attribute into file 36.
Inserting data attribute into file 48.
Inserting data attribute into file 49.
Inserting data attribute into file 50.
Inserting data attribute into file 51.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
732572000 KB total disk space.
57772 KB in 33 files.
28 KB in 22 indexes.
0 KB in bad sectors.
88388 KB in use by the system.
65536 KB occupied by the log file.
732425812 KB available on disk.
4096 bytes in each allocation unit.
183143000 total allocation units on disk.
183106453 allocation units available on disk.
Internal Info:
50 00 00 00 45 00 00 00 64 00 00 00 00 00 00 00 P...E...d.......
05 00 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 ................
38 9c 1c 00 00 00 00 00 16 d6 36 00 00 00 00 00 8.........6.....
bc 73 34 00 00 00 00 00 00 00 00 00 00 00 00 00 .s4.............
00 00 00 00 00 00 00 00 ec f5 db 0a 00 00 00 00 ................
50 21 d1 b2 00 00 00 00 c0 3b 07 00 21 00 00 00 P!.......;..!...
00 00 00 00 00 b0 86 03 00 00 00 00 16 00 00 00 ................
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
