USB not mounting anymore

Hi all,
A USB drive I connected today was not being mounted as usual. Normally it will automatically appear in PCManFM and I've never previously had any issues of this kind. I am however able to see the drive in gparted.
It's been a few weeks since I last connected an external drive, so I can't say for sure whether it was a recent update or not. I note that PCManFM was last updated 13/8, I can't recall using a USB driver between then and now, so may it have occured on that update?
I confirmed my user was in the storage group, as mentioned on the wiki and tried having my xinitrc without the "dbus-launch" before "openbox-session".
I was hoping someone could suggest a fix before I try installing gvfs instead (I'd rather avoid the gnome dependencies).
Thanks.
(EDIT: Have there been any issues with this for the latest kernel? I'm fully up to date with 3.5.3-1)
Last edited by Chowchilla (2012-09-13 04:45:49)

[ 135.585917] usb 1-1.2: new high-speed USB device number 5 using ehci_hcd
[ 135.773343] usbcore: registered new interface driver uas
[ 135.784920] Initializing USB Mass Storage driver...
[ 135.785126] scsi6 : usb-storage 1-1.2:1.0
[ 135.785321] usbcore: registered new interface driver usb-storage
[ 135.785323] USB Mass Storage support registered.
[ 136.788599] scsi 6:0:0:0: Direct-Access OCZ RALLY2 0.00 PQ: 0 ANSI: 2
[ 136.790271] sd 6:0:0:0: [sdb] 7892040 512-byte logical blocks: (4.04 GB/3.76 GiB)
[ 136.791095] sd 6:0:0:0: [sdb] Write Protect is off
[ 136.791105] sd 6:0:0:0: [sdb] Mode Sense: 00 00 00 00
[ 136.792088] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 136.792099] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 136.798320] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 136.798330] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 136.937701] sdb:
[ 136.942544] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 136.942554] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 136.942560] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Hope that helps.
I should I add that I also just tried using pmount. But running
pmount /dev/sdb
only created a folder /media/sdb which I could not access ("Permission denied" when trying to access via PCManFM).
Oh, and I'm using SLiM in case that's relevant.
Last edited by Chowchilla (2012-09-13 05:05:51)

Similar Messages

Update 10.5.6: external HD used for Time Machine does not MOUNT anymore

I've used this LaCie external Little Big Disk since November 2007 with Time Machine, without problems. Recently, after updating to OS 10.5.6, the disk does not mount anymore when connected by FireWire800. Same result when using FW400 and USB.
The disk shows up in the System Profiler under FireWire. When I run analysis with a program 'Data Rescue II', it also sees the disk.
Main issue: disk does not mount anymore. So no more TM backups possible.
Although the disk also shows up in Disk Utilities, I can't partition or reformat it. I ran the LaCie Update Tool 2.0.1 and it says firmware is up-to-date.
I also reinstalled the Combo Update 10.5.6 without result. Also did all the forum recommendations such as resetting PRAM and using Terminal to 'mount /dev/xxx'. Does not help.
I feel this is an Apple issue.

Yes, did it three times. Also already hooked up in daisy chain, and yes, also connected to another Mac (also 10.5.6). Same result. I think it's an OS 10.5.6 issue, because it happened after the update and I had never problems in the last year using this disk with TM (it's not full either). I hope it's not, however, but I am afraid it is. Also I've posted the issue at LaCie support and see what they answer.
Thank you for your reply.

Our XServe-RAID volume does not mount anymore...

Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
XServe Mac OS X (10.3.9)

I've seen an article about volumes not mounting and was wondering if this relates to your problem;
http://discussions.apple.com/thread.jspa?messageID=1239224&#1239224
The thread doesn't refer to journalling but may be of use?
HTH

USB not mounting - Used on a windows, then a Mac, then not working anymore

Hello!
Yesterday a faculty member gave me a USB so I could transfer a few files to it for her. She uses Windows computers but I use a MacBook Pro. It worked fine on my MacBook and I transfered the files, then ejected. However, I noticed even after I ejected and pulled the USB drive out it said I did not eject properly (or something like that).
Today, she tells me that she cannot get it to open on her computer (Windows) that it wanted her to format it - which she did not do. I tried opening it up back on my computer and it does not mount.
An alert did pop up saying "The disk you inserted was not readable by this computer." OPTIONS: "Initialize, ignore, or Eject."
I click "Initialize..." and it shows this...
As you can see, the "8.03 GB JetFlash Transc.." is not giving me the option to Verify or Repair.
I have ran into a problem before where once I put the drive in my Mac, it wasn't usable for Windows again - but I could still use it on my Mac. But this is different, it does not seem to work on either platforms.
I would be MOST appreciative for any help you may provide.
Thanks!
James

Actually, I didn't find the FMLE forum until after I posted here. I realized that all the Flash pieces were under "Flash." Doh!!
Thanks.

My external HD Lacie D2 Quadra will not mount anymore

Hi,
Since a few weeks my two year old Lacie external HD (D2 Quadra) won't mount anymore through FW 400 or 800 on my MacPro both in front and rear connection (Usb is working fine though). I also found out that the same external HD still does mount with FW on my Macbook laptop although both machines are using the same OSX.6.8. Also on MacPro in the system profiler I can't see my FW external device. Restarting and refreshinging PRam didn't bring any solution yet. I've also updated the firmware of the HD to the latest version.
Does anyone recognize this problem?
Greetz
Rob

Well I now believe that my whole FW conection is corrupt. I tried different cables and connection through different FW ports (also some in my monitor) and no device corresponds or mounts. In the system profiler I get the message that FW devices can't be displayed. I have other devices that also connects with FW but none of these mount either on my MacPro. I tried several things now such as unplugging all the cables and then slowly building it up and begin to suspect that my FW is done on this machine. It's a pity that you can't test the functioning somehow other than it's not working.

LION-ext.HDD-usb-not mounting!!!!

I upgraded to LION on my MacMini intel core 2 duo as well as on my MacBook Pro.
I work with External HDDs formated in NTFS and have never had problems doing so, (I use an NTFS reader).
But all of a sudden the HDDs will not mount on my MacBook Pro but seem to have no worries mounting on my MacMini...
Have tried everything I know with various programs but nothing...
OS formats and FAT 32 formats mount fine on both. It seems to be the NTFS on the MB Pro
Any ideas?

well you guys i found that im not the only one with this problem... and that it has been a pain for many...
http://blog.fosketts.net/2008/07/04/low-power-usb-ports-haunt-my-macbook-pro/
i have always tried this ext. hard drive on the left side, since i have my time machine backup always connected on the right side (its a powered ext. hard drive)... i will try plugging it on the right side when i get home and let u know.
thanks for all the help!!

Verbatim Expresscard 34 16GB SSD not mounting anymore

Hi,
after sucessfully working 5 days with Verbatim Expresscard 34 (16 GB SSD) in the MacBook Pro slot (also with the USB Adapter on a Powerbook PPC) suddenly the Expresscard ist not recognized anymore...I can "initialize/ignore/eject"...but then I destroy the data on the card.
Any hints, what I can do ?
(In the system-profiler there is an entry in the USB hardware with recognizing as a SATA Flas SSD but only wit a capacity of 1,92 GB)
sepp

Here's some references from other threads on the net:
"Photoshop CS4 Extended seems to load in 3 or 3.5 seconds"
http://forums.macnn.com/69/mac-notebooks/394126/best-config-48gb-expresscard-ssd -320gb/
http://www.xlr8yourmac.com/feedback/express34cardreports.html#storytop
So it seems that it is possible to boot from some types of SSD and performance rocks. I'll head over to those forums for more info.

External Drive not mounting anymore. HELP!

I was messing with permissions. I was trying to restrict others from using my external drive. I do know that I never removed myself. Now I see that my external LaCie 250GB drive will not mount. Both 'Disk Utility' and 'Disc Warrior' see and 'repair' the hard drive, but it still does NOT mount on the desktop. What can I do? Please help!
Robert
Dual 2.5 GHz G5 Mac OS X (10.4.3) 60GB Video iPod

I opened a 'Terminal' window and discovered that it appears I changed the owner. My username is bobbysteele. I changed it from 'admin' to my username (it's truncated - bobbyste). The permissions on the external drive are as follows:
d---rwx--- 16 bobbyste bobbyste 646 Jan 7 08:01 Jukebox01
It appears the permissions should be drwxr-xr-x because that is the setting for all other drives and folders. How can I change the permissions? Please help.

Lacie USB not mounting

I have both a 500gb and a 250gb Lacie USB external drives. Recently the 250gb wont mount on my desktop. i've tried unplugging and re plugging, switched the cables between the two but nothing works. it did eventually mount yesterday but again today it refuses to mount. the 500gb harddrive is fine.
the 250 also appears in my system profiler and in my disk utilities. i've repaird disk and permissions, but nothing will make it appear on my desktop.
any help would be greatly appreciated as the drive contains all my music and photos that i dont want to loose.

This is to assure you your photos are fine (I think). My LaCie drive is a DVD, but it has the same problem. LaCie (or someone) claimed it first occurred after MacOSX 10.4.8 was updated, and appears a problem between LaCie's software & Mac's. Various kludges have been suggested, and they all work at times: plugging the cables in carefully (Mac's astute advice), plugging in a different USB (or Firewire) device first (to 'stabilize' the bus), switching between USB & Firewire, & I've found a cold reboot with the drive plugged in occasionally works. I've found that even when an icon doesn't appear on my desktop, some Cocoa applications can access the drive. So if you're really worried about your photos, or frustrated, I might suggest seeing whether Darwin has mounted your drive: just type 'mount' on the 'Terminal' and look for it. If so, why not try a free X11 application until LaCie (or Apple) fixes the problem?

My USB-Stick is marked busy even though not mounted (?)

Also Subject lines are too short.
Hello there, my name is Ayutac, I use Arch for some while now and I probably screwed up.
tl;dr: My USB-Stick is marked busy even though not mounted (?)
Previous History: I was trying to get the newest Arch iso on a stick of my friend, so I got the iso here and moved the stick's content to my extern hard drive. I used the opportunity to experiment how good "mv -t target_dir *" would work and interrupted it because I was stupid. Two folders somehow weren't movable through mv anymore, so I mv'ed everything else – now explicit – and moved the content of the two folders via pcmanfm. After that there were about 16kB on the stick left.
Next I copied the iso using
dd bs=4M if=/path/to/archlinux.iso of=/dev/sdc && sync
as suggested by the wiki. I looked at the stick; to my surprise the two folders I left there where still there, though filled with gibberish data. I thought I might give it a try, shut down, booted from stick. Black screen with a blinking text cursor for minutes. I concluded it didn't work and tried some other way. Following the wiki I was given the task to format the usb stick anew.
Thinking I knew what I was doing I used fdisk several times (including rebooting), getting myself two partitions with FAT32 (or so I think). But that somehow screwed it up.
The problem: After partioning and rebooting it seems I can't mount the partitions to copy the content of the iso. lsblk says
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 21.7G 0 part
├─sda2 8:2 0 350M 0 part
├─sda3 8:3 0 95.4G 0 part
├─sda4 8:4 0 1K 0 part
├─sda5 8:5 0 95.4G 0 part /
├─sda6 8:6 0 7.6G 0 part [SWAP]
└─sda7 8:7 0 711.1G 0 part /home
sdb 8:16 0 465.8G 0 disk
└─sdb1 8:17 0 465.8G 0 part /run/media/nait/nanika
sdc 8:32 1 3.6G 0 disk
├─sdc1 8:33 1 650M 0 part
└─sdc2 8:34 1 3G 0 part
sr0 11:0 1 1024M 0 rom
(sdc is the stick) but I get
> sudo mount /dev/sdc1 /mnt/usb
mount: /dev/sdc1 is already mounted or /mnt/usb busy
> sudo umount /mnt/usb
umount: /mnt/usb: not mounted
Furthermore "lsof | grep sdc" returns nothing, neither does "cat /proc/mounts | grep sdc" or "cat /etc/mtab | grep sdc". The only clue is
> systemctl -a | grep sdc
dev-sdc.device loaded active plugged 1000 ARCH_201409
dev-sdc1.device loaded active plugged 1000 ARCH_201409
dev-sdc2.device loaded active plugged 1000 ARCH_201409
sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d3-3\x2d3:1.0-host9-target9:0:0-9:0:0:0-block-sdc-sdc1.device loaded active plugged 1000 ARCH_201409
sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d3-3\x2d3:1.0-host9-target9:0:0-9:0:0:0-block-sdc-sdc2.device loaded active plugged 1000 ARCH_201409
sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d3-3\x2d3:1.0-host9-target9:0:0-9:0:0:0-block-sdc.device loaded active plugged 1000 ARCH_201409
I tried to shut the devices down, but that didn't seem to work.
Furthermore the pcmanfm shows two mount points of the iso/stick but returns error message when clicking on them:
Error mounting /dev/sdc1 at /run/media/nait/ARCH_201409: Command-line `mount -t "iso9660" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,iocharset=utf8,mode=0400,dmode=0500" "/dev/sdc1" "/run/media/nait/ARCH_201409"' exited with non-zero exit status 32: mount: /dev/sdc1 is write-protected, mounting read-only
mount: /dev/sdc1 is already mounted or /run/media/nait/ARCH_201409 busy
Goal:
1. Make the stick usable again, with 2 partitions.
2. Copy the iso on the first partition.
3. Have a functioning Arch booting stick.

Welcome to Arch Linux.
A few questions and comments. First, are the files you copied from the disk safe? Since the plan was to wipe the disk anyway, I would suggest next time copying rather than moving files. I always get itchy when I move files. I have made some stupid mistakes where I copied hundreds of files to one output file, each one overwriting the previous. Of course, as it was a move, the source file was gone as well. Fortunately, I maintain backups. I would also suggest you look into the rsync facility when doing bulk copies.
That said, another excellent way to destroy data is the dd command (There are those who claim dd means just that) Are you certain that the usb disk had been been placed at the /dev/sda node? In the thread title, you made the assertion that the drive was not mounted. dd will run just fine even if the disk is mounted (I do not recommend this). What were you using to look at those folders that had become full of gibberish? Command line tools? A graphical file manager? (Nautilus, Thunar, Dolphin, SpaceFM) It is possible that the tool you were using was unaware that the contents had changed and was using cached information.
As to your goals. First, copying the iso to /dev/sdc tells the system to use the entire device for the iso, not the first partition. Our iso is not designed to be placed in a partition, I don't think you will meet with success trying to block copy the iso to a partition. If you want to try it, the destination would be /dev/sda1 (for partition 1) Make sure the partition is large enough. I would suggest that you use the entire disk by dd'ing the iso to the /dev/sdc (assuming it is c) node, but make certain that all of the partitions are dismounted. I know you think you did that, but I have my doubts. Please use command line tools. I don't trust GUIs that try to help too much.
If you want multiple partitions, use fdisk and re-partition the device. Then create a file system in each of those partitions.
It has been a while since I have tried to master a USB that will boot. I may have a faulty memory, or I may be using really old, outdated, information, but... I think that a USB has to boot as if it were a CD drive . I am not certain that a hard drive type structure with multiple partitions and a MBR will work on a USB drive (edit)and have it be bootable. In other words, goal 1 and goal 2 might not be achievable if goal 3 means that the disk will boot. I could be wrong.
Last edited by ewaller (2014-09-27 16:18:25)

Iomega MiniMax 2T, not mounting

I owned a Iomega minimax with 2Tb for a year now, and recently while cleaning up my desk and re-conecting all of my peripherals found out that the minimax was not mounting anymore.
I read several discussions, tried all I can find:
re-setting firewire ports
re-setting PRAM
_SMC Reset
replacing the Firewire cable, which I had an extra one and didn't work either
etc.
At the end I decided to open the minimax box, by removing the two rear screws, with the intention to use a different housing for my drive, thinking that the possible cause will be the little board for the usb and firewire connections.
To my surprise! once I open the iomega minimax box I found the 3.5" hard drive completely loose inside the enclosure, and since the connection is a rigid connection to a board, the drice wasn't connected at all. The big question here is, how can Iomega designed this box and never thought about installing 2-3 screwss to the hardrive!? really bad design or really bad quality control.
After plugin the harddrive back again to the mother board, everything worked fine, hope this is a possible solution to your problem if you already tried everything and nothing gets to mount the drive again. Also, there is no warranty stickers, no signs left if you open the iomega box, so don't worry about breaking a piece or a sticker concerning warranty.

You've done everything possible from the MacBook Pro end. Since this is a forum about the MBP, I would suggest contacting Iomega, and seeing if they can help you.

Hard Drive and Disk Image not mounting

Hey everyone,
I'm running a G5 Dual 2Ghz. with OSX 10.5.8 I'm having problems with a back up hard drive. It is an external Western Digital My Book 1.5TB SATA drive. After using it for a few months, it suddenly did not mount anymore.
*1) It also would not appear in Disk Utility.*
a) Disk Warrior couldn't find the drive (I think because it's formatted with FAT32)
*2) I then took the drive out of the enclosure and put it in the spare bay in the G5.*
a) It didn't mount
b) It did show up in Disk Utility
c) In Disk Utility it wouldn't give me the option to Repair Disk Permissions or Repair Disk
d) In Disk Utility is says under Partition Scheme: Unformatted
e) In Disk Utility I don't have the option to mount/eject only gives me the "info" option
f) Tech Tool did find the drive and it passed all tests
g) Disk Warrior still did not find the drive
h) TestDisk finds the drive, but does not find any partitions
*3) I then created a disk image of the drive in Disk Utility onto an external hard drive. The image comes back at 320GB, which seems to be about right I think.*
a) The disk image would not mount with Disk Image Mounter. It would say there is an Unrecognized File System
b) In Disk Utility - I don't have the option to Repair Disk Permissions
c) In Disk Utility - When trying to Repair Disk - I get the error: Repairing Disk failed with error Unrecognized FileSystem
d) In Disk Utility - If I click Open - The Log file says:
+Attach Image+
Initializing...
Verifying...
Finishing...
+Image of "disk0.dmg" attached successfully+
+Mount of "disk0.dmg" succeeded+
-But it is no where to be found
e) Disk Warrior can not find the Disk Image
f) I took the new external drive with the Disk Image to 3 other mac computers but the image would not mount
*4. Other things I've tried when opening the Disk Image for the new external drive.*
a) in Terminal - hdiutil attach -nomount "volumes/untitled/disk0.dmg"
b) in Terminal - sudo hdiutil attach -nomount "volumes/untitled/disk0.dmg"
c) Deleting files System/Library/Extensions.kextcache
System/Library/Caches/com.apple.kernalcaches
ALL UNSUCCESSFUL
I'm running very low on ideas. I know I could just erase the drive and reformat it, but the files on it are very important and must be recovered.
Any help or suggestions would be very helpful. I will not have time until after the weekend to try more things. Thanks in advance if you do not hear back from me until after this weekend.

Yes, it will. But if DU says the disk is unformatted then it is also not accessible. If you have files you don't wish to lose then you will need to try recovery software:
Basics of File Recovery
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery.

External Hard drive will not mount on Macbook Air (mid-2011) OSX 10.9.4

Hello Everyone!
Needs some help resolving this issue. External hard drive (Toshiba v63600-C) will not mount anymore on my mothers-in-law's macbook air. She notice this problem starting on the Aug 6th. You can see it in the Disk Utility but is not mounted. I can get the her ext hard drive to mount on my Macbook Pro with no problem. I also tried my personal ext hard drive (Seagate) on her Macbook Air and it will not mount. Not sure what is going on here. Any help is appreciated in resolving this issue.
Disk Utility
Mount Point : Not mounted Capacity : 1 TB (1,000,096,367,104 Bytes)
Format : Windows NT Filesystem (Tuxera NTFS) Available : -
Owners Enabled : - Used : -
Number of Folders : - Number of Files : -
Actions Taken So Far:
1) Confirmed "external disk" is selected under Finder's Preference
2) Reset PRAM
3) Ran Verify Disk and Repair Disk under Disk Utility with no change.
4) Tried manually mounting disk in Disk Utility but get "Mount Failed" error

You may believe this is Apple's problem but I just like Baltwo have had absolutely no problems with any of my Firewire drives in Lion. So unless you can come up with much stronger evidence to the contrary, I doubt that your feeling are going to carry any weight at all.
Allan

XRAID will not mount (journal corruption)

Hi guys, I have seen in the unanswered archived article below someone with exactly my problems, really looking for a solution to repair the journal within OS X, any ideas or developments on this?
http://discussions.apple.com/thread.jspa?threadID=374802
[QUOTED HERE FOR CONVENIANCE]
Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
[/QUOTE]

I was using RAID mirroring two SCSI drives under 10.3 Server (not an XRAID) and found that one of the two drives was slow to spin up. The System considered the array "degraded" and made the single "good" drive available. Nothing that made any sense to me could get the "slow" drive repaired or re-incorporated into the pair. I could not split the pair for repair, and even after it was spun up and ready, Disk utility refused to repair it or its acceptable partner.
What I eventually did, with some coaching from the forums and re-reading of Mac Help, was to delete the errant drive from the set. Then I could erase it as a single drive, and add it back into the set as a "new" replacement drive. The system accepted it as a replacement, and brought it up-to-date with its partner automatically.
I have got to say that I find this approach completely counter-intuitive. It gives me the creeps to delete the "safety-net" drive, even if I know it is mucked up.
But perhaps a similar approach would work in your situation.

Drive not mounting

G5 = one of my firewire external drives appears in disk utility but only with the vendor name but no volumes and it does not mount anymore on the desktop.
What can be done?
here is part of the console output:
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Nov 27 08:03:01 enrico-tedeschis-Computer mDNSResponder: NOTE: Wide-Area Service Discovery disabled to avoid crashing defective DNS relay 10.0.1.1.
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Looking for devices matching vendor ID=1193 and product ID=8718
thank you

Try fixing the disk using a tool like Disk Utility (which you may not have yet tried -- select the drive and click the Repair Disk button), Disk Warrior (http://www.alsoft.com/DiskWarrior/) or TechTool (http://www.micromat.com/).

USB not mounting anymore

Similar Messages

Maybe you are looking for