Originally posted by: Jiggz
Not necessarily. Sometimes it's just a corrupted File Allocation Table (FAT) and not necessarily a dying hdd. Run chkdsk/f.
Originally posted by: aphex
Verifying volume ?EXTERNAL?
** /dev/disk1s1
** Phase 1 - Read FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (576) not free
fix? no
59921 files, 3730016 free (5359443 clusters)
Mounting Disk
1 non HFS volume checked
Volume passed verification
Originally posted by: Jiggz
Originally posted by: aphex
Verifying volume ?EXTERNAL?
** /dev/disk1s1
** Phase 1 - Read FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (576) not free
fix? no
59921 files, 3730016 free (5359443 clusters)
Mounting Disk
1 non HFS volume checked
Volume passed verification
Except for the cluster referred to in block 576 it seems that everyting is fine. I was wondering why you did not let if fix that particular cluster? Anyways, I'm not too familiary with OSX so hopefully somebody out here has a better idea. Goodluck.
Originally posted by: biostud
Could it be that you had unplugged the drive before "ejecting", so if the data in the HDD cache didn't get properly written to the HDD? or something similar
