firewire drive will not mount after accidental unplug

i've a firewire adaptor attached to an IDE drive. has been working very well.
the drive was accidently unplugged while mounted.
mac reported that firewire device was missing, to plug it back in immediately
which we did.
message went away.
then an error (-60) was displayed saying the disk had a problem and use a utility.
since then it will not mount, instead showing a "intialize" windoid.
can't get norton to see it as a "missing disk", and can't use Disk Warrior until it is mounted.


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Was the drive being written to when it got unplugged? Can you use Disk Utility?
I would try to manually run fsck (the unix filesystem checker) on the unmounted
volume.  You will have to do this as an Administrator in Terminal.

Look toward the end of /var/log/system.log and locate the messages generated
when the external disk was last mounted BEFORE you unplugged it.  In my log
it looks like this:
Aug 29 17:28:11 neo /sbin/autodiskmount[212]: disk1s2    hfs      yes   yes   G4Backup         [not mounted]    
Aug 29 17:28:11 neo /sbin/autodiskmount[212]: disk1s3    hfs      yes   yes   Part2            [not mounted]    
Aug 29 17:28:11 neo /sbin/autodiskmount[212]: Mounted hfs /dev/disk1s2 on /Volumes/G4Backup
Aug 29 17:28:11 neo /sbin/autodiskmount[212]: disk1s2    hfs      yes   yes   G4Backup         /Volumes/G4Backup

In particular, you are looking for the disk device id of the mounted volume,
in my case  it is disk1s2 which had been mounted as /Volumes/G4Backup.

Now run fsck in non-repair mode - it will check the disk but not attempt to repair it:

% sudo fsck -F hfs -n /dev/disk1s2

Examine the output diagnosis of fsck.   Hopefully it will find tens of things wrong (not thousands).
If the errors seem reasonable (like not trying to move / to lost+found) rerun fsck to fixup the disk.

% sudo fsck -F hfs -p /dev/disk1s2

If fsck exits with a "problem that requires intervention", re-run interactively

% sudo fsck -F hfs /dev/disk1s2

If fsck successfully fixed up the filesystem to the point where it can be mounted,
manually mount the volume so that you can run DiskWarrior or whatever.

% sudo mount -hfs /dev/disk1s2 /Volumes/G4Backup

For additional information, man fsck.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sevasevaAuthor Commented:
thank you! i was able to get it mounted again with your advice, and then diskwarrior did it's wonderful work.
another method i found was to unplug the drive, launch diskwarrior, THEN plug in the drive. DW saw the drive (although not mounted) before the OS tried to put the initialize dialog up, so i could run DW.

thank you again!
Disk Warrior save my life so many time i cannot remember how many

It a must for all hd problem..

Just a comment

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apple OS

From novice to tech pro — start learning today.