MacMusic.org  |  PcMusic.org  |  440Software  |  440Forums.com  |  440Tv  |  Zicos.com  |  AudioLexic.org
Loading... visitors connected
> External Firewire Troubles, External Firewire Drive Won't Unmount/Er
banevt
post Wed 22 Jun 2005, 23:36
Post #1


Junior Member
***

Group: Members
Posts: 115
Joined: 06-Nov 03
From: Los Angeles - US
Member No.: 28,332




Hello all
I have an ibook G3 running OSX 10.3.9. My issue is with an external firewire 400 drive I have. The other day I tried to trash something on the drive and it wouldn't go to the trash. I tried restarting but still it wouldn't let me trash anything. I tried to run Disk Utility and repair the disk but it said it couldn't do it because the drive wouldn't unmount and is still in use. I checked to see if any applications were running but nothing else was running. I have to force eject it from the Terminal just to unmount it from my desktop. I backed up all my data and as I was backing it up I found that a lot of the recent files I'd been working with wouldn't copy becuase they could not be read or written. So I tried to erase the drive but I get the same error message about not being able to unmount the drive. I have tried Disk Warrior and it gives me the same message. I've tried logging out and back in. Booting from a startup CD, and booting up in safe mode. I can't figure out what the problem could be. The fact that I can't even erase the firewire drive from the CD boot makes me fear the drive may be dead. Any help would be greatly appreciated. Thanks

Valente
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
banevt
post Fri 24 Jun 2005, 10:29
Post #2


Junior Member
***

Group: Members
Posts: 115
Joined: 06-Nov 03
From: Los Angeles - US
Member No.: 28,332




I've tried several firewire cables in this situation and even tried mounting the drive on a different comptuer like lepetitmartien suggested. I do think you are on to something with it being the enclosure more than the drive. I ran fsck from Terminal on the volume and it said the volume needed repairs but I also ran fsck on the disk and it said it was ok. This makes me wonder if it's the enclosure and not the drive. What do you think?


[Valente-Torrezs-Computer:~] valentet% mount
/dev/disk0s10 on / (local, journaled)
devfs on /dev (local)
fdesc on /dev (union)
<volfs> on /.vol
automount -nsl [389] on /Network (automounted)
automount -fstab [392] on /automount/Servers (automounted)
automount -static [392] on /automount/static (automounted)
/dev/disk2s10 on /Volumes/Bubo 1 (local, nodev, nosuid, journaled)
[Valente-Torrezs-Computer:~] valentet% sudo fsck_hfs -f /Volumes/Bubo\ 1
Password:
/Volumes/Bubo 1 is not a character device
CONTINUE? [yn] y

** /Volumes/Bubo 1 (NO WRITE)
ioctl(DKIOCGETBLOCKCOUNT) for fd 4: Inappropriate ioctl for device
** The volume needs to be repaired.
** Volume check failed.
[Valente-Torrezs-Computer:~] valentet% sudo fsck_hfs -f /dev/disk2s10
** /dev/rdisk2s10
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking Catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
** The volume Bubo appears to be OK.

Thanks for any suggestions on this persistent problem.

Valente

This post has been edited by banevt: Fri 24 Jun 2005, 10:32
Go to the top of the page
 
+Quote Post



Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version - Thu 31 Oct 2024, 10:22
- © 440 Forums 2011