G-raid Unmounts Itself

We are using G-raid drives for our projects. When it comes to the end of the day we shut down the systems using normal finder menu.
When we boot up next the g-raid can't be found - should we unmount before closing down?
Also we are using a Sony J30 connected through firewire and when we unplug this, the g-raid unmounts itself and we can't get it to reappear with out rebooting etc..
The J30 is connected through FW400 and the G-raid connected through FW400 - would it be better to connect the deck through the back of the G-raid drive, at the moment they are both connected direct to the PC. Also is there away of unmounting the J30 without just yanking the lead..
Thanks in advance
Cheers
Rob

Well I am no nearer.. it doesn't make sense..
When I turn I unmount the G-raid properly be ejecting it stops the drive. If I then turn the drive off and on it doesn't remount itself and won't do until I reboot.. And it is doing this on two seperate drives... perhaps these are faulty drives but this is weird

Similar Messages

Xserve Raid Unmounts During Playback

We are using our RAID with Final Cut Pro 5. We are trying to layback a 1080i 10bit 23.98 show with 4 audio channels but during playback the Raid often unmounts itself, causing Final Cut to freak out. Normally at this point we have to restart the G5 in order to get the RAID to mount normally again. Sometimes this happens after 20 minutes of playback, sometimes after 40, and last night it was happening after a mere minute or two of playback. Some RAID info: We have about 2.5 TB available which is split between 14 drives (7 on each controller). We are using RAID 5 and there is currently 500 GB of free space. Any suggestions would be greatly appreciated. If you need more info, let me know what/where to get it and I will post it here. Thanks in advance!
G5 Mac OS X (10.4.6)

Ok, here is the system log from one of the crashes:
Aug 14 15:43:30 apples-power-mac-g5 kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "FCP2 RAID" (B52BC88D-65F5-42D7-B208-18F3F91D9ACB), member 82A77A15-2AE5-49EF-AA43-88F8CA0B5734, set byte offset = 2892383387648.
Aug 14 15:43:30 apples-power-mac-g5 kernel[0]: disk3: I/O error.
Aug 14 15:43:30 apples-power-mac-g5 kernel[0]: disk3: device is offline.
Aug 14 15:46:45 localhost kernel[0]: standard timeslicing quantum is 10000 us
Aug 14 15:46:45 localhost mDNSResponder-107.4 (Nov 15 2005 21: 34:38)[41]: starting
Aug 14 15:46:45 localhost kernel[0]: vmpagebootstrap: 1136977 free pages
Aug 14 15:46:45 localhost kernel[0]: migtable_maxdispl = 70
Aug 14 15:46:45 localhost kernel[0]: 110 prelinked modules
Aug 14 15:46:45 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Aug 14 15:46:45 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Aug 14 15:46:45 localhost kernel[0]: using 8192 buffer headers and 4096 cluster IO buffer headers
Aug 14 15:46:45 localhost kernel[0]: DART enabled
Aug 14 15:46:45 localhost kernel[0]: FireWire (OHCI) Apple ID 42 built-in now active, GUID 000d93ff fe6ed1a0; max speed s800.
Aug 14 15:46:45 localhost kernel[0]: Security auditing service present
Aug 14 15:46:45 localhost kernel[0]: BSM auditing present
Aug 14 15:46:45 localhost kernel[0]: disabled
Aug 14 15:46:45 localhost kernel[0]: rooting via boot-uuid from /chosen: 4446EF8E-1DCA-3D82-BCD2-31BD942F1321
Aug 14 15:46:45 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Aug 14 15:46:45 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@7/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/ST3160023AS Media/IOApplePartitionScheme/Untitled@3
Aug 14 15:46:45 localhost kernel[0]: BSD root: disk1s3, major 14, minor 5
Aug 14 15:46:45 localhost kernel[0]: jnl: replay_journal: from: 10632192 to: 11316224 (joffset 0x4aa000)
Aug 14 15:46:45 localhost kernel[0]: HFS: Removed 2 orphaned unlinked files
Aug 14 15:46:45 localhost kernel[0]: Jettisoning kernel linker.
Aug 14 15:46:45 localhost kernel[0]: Resetting IOCatalogue.
Aug 14 15:46:45 localhost kernel[0]: Matching service count = 0
Aug 14 15:46:45 localhost kernel[0]: Matching service count = 6
Aug 14 15:46:45 localhost kernel[0]: Matching service count = 6
Aug 14 15:46:45 localhost kernel[0]: Matching service count = 6
Aug 14 15:46:45 localhost kernel[0]: Matching service count = 6
Aug 14 15:46:45 localhost kernel[0]: KONADriver::init
Aug 14 15:46:45 localhost kernel[0]: KONADriver::probe() score = 0
Aug 14 15:46:45 localhost kernel[0]: KONADriver::start
Aug 14 15:46:45 localhost kernel[0]: BoardID=10174700
Aug 14 15:46:45 localhost kernel[0]: KONADriver::ProgramXilinxDefault()
Aug 14 15:46:45 localhost kernel[0]: IOPlatformControl::registerDriver Control Driver AppleSlewClock did not supply target-value, using default
Aug 14 15:46:45 localhost kernel[0]: KONADriver::start return: OK
G5 Mac OS X (10.4.7)

Disk Randomly Unmounts Itself

Dual 2.66GHz dual core Xeon
10.5.6 server
Once of the internal SATA HDs randomly unmounts itself, every one or two days. It's a bit of a pain as its the disc with all the user NHDs, so it's very disruptive.
It's only one partition on a disk that unmounts, the disk has another partition that doesn't unmount, so I think that makes it very unlikely to be a hardware issue.
I have absolutely no idea - would be very grateful for any clues!
thanks

Disks do fail.
My first suspicion here would be a disk error, and particularly a disk error located in an area of the disk "underneath" the partition that is dismounting. I'd expect that when the disk error is hit, the disk gets kicked out. (Disks are far better and more reliable than the giant disk drives I started out working with, but all disks can and do eventually fail.)
This might be a case that a block rewrite would fix. Disks can contend with isolated bad blocks; a rewrite can trigger the use of a spare block. This can involve rewriting the file with the block, or performing a disk erase, or a complete disk (or partition) reload from archive.
This assuming that this case is an isolated bad block.
Empirical studies show a roughly 6% failure rate per year; not the commonly-assumed bell curve of disk failures. Related studies have found measured MTBF figures appear to typically be somewhere around 3.4x and can be as much as 15x higher than the MTBF ratings, too. Older disk drives can fail at rates 30x higher than MTBF, too.
And measured latent hard errors (past what disk-level error correction could handle) were between 3 and 6 per terabyte, IIRC.
Put another way, how good is your RAID set (and -- same studies -- double disk failures in RAID sets are surprisingly common) and/or how current is your disk archive? RAID allows a way to retrieve data from a good block or from checksums when a bad block is encountered, of course. It doesn't and can't allow data to be read from a bad block, of course.
Regardless, I'd get an archive of the contents of the disk or the disk partition (using Disk Utility or otherwise), then would check the console logs for any interesting error messages around the time of the dismount, and would look to move to RAID and/or to a replacement disk.
I don't mean any of this to scare you. I do mean to scare you into having backups. And into taking steps to preserve and to recover this disk. And yes, even RAID fails.
Figures quoted here from my memory from reading Google and CMU studies. (And I could have a bit error in my own memory here, too.)

Raid unmounts on G5 maybe 10.4.3 update problem

So here is the background :
my g5 runs off a striped raid which has run flawlessly for 2 Months
A week after installing 10.4.3 I had a lock up on the computer
Restart, no joy
Start using OSx disk: raid offline, disks are irrepairable in disk utitlity
Rebuild raid, erase and zero drive, clone my OS back from a copy
System freezes after reboot
Reboot from firewire disk
Rebuild raid
Try to copy across but raid unmounts and goes offline
start from scratch
zap the pram 10 times (to be sure)
set up raid
install 10.4
copy across docs, tunes etc
restart locks up knackered!
So my question is, how do I re set the damage and install a lovely new copy of osx 10.4?
is it 10.4.3 firmware problems even though I have tried to roll back to 10.4?
Any help would be great, I will never upgrade like this again, very bad apple!

Which is why most don't raid, and if they do, it is mirror and they also keep regular backups. Two months and going belly up is rather common. maybe a bad block isn't being mapped out "on the fly" or occurred in the RAID tables.
Have you zeroed the drive or done a 7-way erase? I would start there.
A RAID can help, but so too can having a fast boot drive for OS/Apps and a separate drive for media. A mirror offers stripped reads but writes to both drives - doesn't protect from file corruption, but does protect from a single drive failure.
I would use SoftRAID 3.3 instead, costs $149. Break the RAID and do a 7-way erase. Check the SMART status (10.4.3 now seems to check status on restarts).
Most desktop drives, including SATA, don't get the testing and burn-in needed. You have to do that yourself - or the attention that SCSI gets. I've had few problems in years with SCSI, but regular problems with desktop drives that have half the MTBF.

USB drive started unmounting itself after OS X update

Has anyone a work around to get a USB hard drive to stop unmounting itself? The drive used to work flawlessly and only started behaving as though the cable were disconnected following an OS X update.

Don't know about the update as a possible cause, but WD externals have a reputation for being very flakey with Macs, or flakey period. You could try a PRAM reset: hold CMD-Option-P-R keys down together at the startup chime, keep holding down until you hear two more chimes, total three, then let go and it will finish booting.
Also, you might try re-applying the 10.5.8 Combo Update.
http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate

External USB hard drive unmounts itself.

Hi all,
I have a 2.5" hard drive connected via USB to my MacBook that keeps unmounting itself. This happens under some (what seems to be) undetermined amount of time, the drive will all of a sudden unmount itself and disappear from the Finder, Disk Utility, et al.
Is there some fix, setting or work around for this? Very annoying. If not, is there a way to re-mount the hard drive without turning it off then on or reconnecting the USB cable?
Any help would be greatly appreciated.
Cheers,
Diego

I have had the same problem trying to use an USB disk as my Time Machine destination. The disk unmounts when the computer is left alone.
Inspecting the logs I discovered that the system requests the disk to unmount and that the backupd allows it. Since it only happens when I am not actively using the computer my guess is that it has to do with the computer trying to fall asleep or at least preserving it.
With time machine, this is a problem before you have made that first backup; subsequent backups are shorter and do not "time out". My solution was to keep the computer awake and, when I forgot that and the computer fell asleep, requesting a new (continuation of the) backup. Unattended about 7GB would be backed up. (There might be a solution if changing the power settings, but I didn't bother.)
Apple might consider not having the backupd allowing unmounts during a backup, or at least before one full backup has been completed.

External Hard Drive unmount itself

Help!
After a I think it was a sucessfull migration to OS X Mountain Lion, My two external hard drives and my card reader unmount itself after 30 second of be connected, every device has the same behavior, any clues to solve this issue?
Thanks in advance

I see. Then, assuming the devices don't try to pull more than 5W of power after they are mounted, I don't think you are experiencing the same issue as me.
Do you have a flash drive (better if USB 2.0)? In general these drives have less complex drivers and if they show the same behavior than it is very likely that you have a problem with your USB ports rather than your OS.
For the OS part, the following comes to mind:
1- Turn off your computer. Plug the charger off. Wait for 10 seconds. Turn it on again and try again.
2- Create another user account, log in with that account and try.
3- Restart the computer. Open Console.app. Try to mount your USB device. After it gets unmounted automatically, copy and paste the last 10 entries in Console.app
4- Reinstall the OS. It might be the case that one of your OS/kernel filels are corrupted. In any case, make sure that you back up your computer before trying this. Normally it should not overwrite any of your files, however just in case.
5- Reinstall the OS after a format. This is clean swipe and the latest choice.
On the hardware side (less likely since you mention that this started happening after the OS update), if you are still under warranty, I would suggest you to take your computer to apple and show them the same problem. They should be able to debug it better than probably anyone. If there is a hardware defect not caused by user, they almost always change your hardware. Again, before taking your laptop to apple make sure that you backed your computer and you have a genius appointment.
Let me know if you are stuck at any point.

Hard Drive Unmounting Itself

Hi,
I have a WD MyBook USB external hard drive that used to work fine. Now, it will not mount unless I unplug its power for at least 15 minutes, plug the power back in, and then plug it into my MacBook Pro. Once it mounts, it will then unmount itself after about an hour. The power light on the hard drive never turns off, though. I've searched the discussion and can't find any similar problems. Any help with this would be greatly appreciated. Thanks.

I am having the same issue.... the USB drive unmounts at unexpected moments.
For me, it happens always with iTunes open, or when trying to transfer files to or from the external drive.
Mine is a new issue since the latest iTunes update. Apple refuses to give phone support and does not answer email event reports.

Having trouble with USB2.0 external hard drive "unmounting" itself

ibook g4 (early 2005)
I have bought an external 120 gig hd and am trying to use it to store files on. when i transfer files to and from it, the hard drive magically unmounts itself and gives an error device removal. I don't know if the HD needs too much power or what. I have tried to update my system... and no help. what can i do... besides taking the freaking hd out of the external case and installing it in my laptop.
I have never had a problem with usb devices before on this laptop. what gives?

I'm not sure of what is the cause for this is, but because it stays alive while it's in use makes me think there is some sort of hardware sleep mode or something. I don't know enough about USB to be sure though. Maybe a temporary fix would be some sort of script we could launch at startup that reads a very small amount of data from the afflicted drive every 10 seconds or so. I have a little programming knowledge. Maybe I can figure the script out. It's definitely not a true fix, but it might get us by for the meantime.

X-Serve RAID unmounts on large file copy

Hi
We are running an X-Serve RAID in a video production environment. The RAID is striped RAID 5 with 1 hot spare on either side and concatenated with Apple Disk Utility as RAID 0 on our G5, to appear as one logical volume.
I have noticed, lately, that large file copies from the RAID will cause it to unmount and the copy to fail.
In the console, we see:
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: FusionFC: Link is down for SCSI Domain = 1.
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 1.
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: FusionFC: Link is active for SCSI Domain = 1.
May 4 00:23:37 Orobourus kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 1
May 4 00:23:37 Orobourus kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "tao.av.complexity.org" (868584D1-E485-4B37-AFCE-E7AFC3AD5BB7), member CBDFD75C-5DC8-4089-A7AE-1EFBE0B1A6EB, set byte offset = 1674060574720.
May 4 00:23:37 Orobourus kernel[0]: disk5: I/O error.
May 4 00:23:37 Orobourus kernel[0]: disk5: device is offline.
May 4 00:23:37 Orobourus kernel[0]: AppleRAID::recover() member CBDFD75C-5DC8-4089-A7AE-1EFBE0B1A6EB from set "tao.av.complexity.org" (868584D1-E485-4B37-AFCE-E7AFC3AD5BB7) has been marked offline.
May 4 00:23:37 Orobourus kernel[0]: AppleRAID::restartSet - restarting set "tao.av.complexity.org" (868584D1-E485-4B37-AFCE-E7AFC3AD5BB7).
May 4 00:23:37 Orobourus kernel[0]: disk5: media is not present.
May 4 00:23:37 Orobourus kernel[0]: disk5: media is not present.
May 4 00:23:37 Orobourus kernel[0]: jnl: dojnlio: strategy err 0x6
May 4 00:23:37 Orobourus kernel[0]: jnl: end_transaction: only wrote 0 of 12288 bytes to the journal!
May 4 00:23:37 Orobourus kernel[0]: disk5: media is not present.
May 4 00:23:37 Orobourus kernel[0]: disk5: media is not present.
May 4 00:23:37 Orobourus kernel[0]: disk5: media is not present.
May 4 00:23:37 Orobourus kernel[0]: jnl: close: journal 0x7b319ec, is invalid. aborting outstanding transactions
Following such an ungainly dismount, the only way to get the RAID back online is to reboot the G5 - attempting to mount the volume via Disk Utility doesn't work.
This looks similar to another 'RAID volume unmounts' thread I found elsewhere in the forum - it appeared to have no solution apart from contacting Apple.
Is this the only recourse?
G5 2.7 6.5Gb + X-RAID 3.5Tb Mac OS X (10.4.9) Decklink Extreme / HD

There should be no need to restart the controllers to get additional reporting -- updating the firmware restarts them.
If blocks are found to be bad during reconditioning, then the data in the blocks should be relocated, and the "bad" blocks mapped out as bad. The Xserve RAID has no idea whatsoever what constitutes a "file," given it doesn't know anything about the OS (you can format the volumes as HFS+, Xsan, ZFS, ext3, ReiserFS, whatever... this is done from the host and the Xserve RAID is completely unaware of this). So if the blocks can be successfully relocated (shouldn't be too hard, given the data can be generated from parity), then you're good to go. If somehow you have bad blocks in multiple locations on multiple spindles that overlap, then that would of course be bad. I'd expect that to be fairly rare though.
One thing I should note is that drives don't last forever. As the RAID ages, the chances of drive failure increase. Typically drive lifespan follows a "bathtub curve," if you imagined looking a a cross-section of a crow's foot tub. Failures will be very high early (due to manufacturing defects -- something testing as "burn in" should catch -- and I believe Apple does this for you), then very low for a while, and then will rise markedly as drives get "old." Where this is would be a subject for debate, but typical data center folks start proactively replacing entire storage systems at some point to avoid the chance of multiple drive failure. The Xserve RAIDs have only been out for 4 years, so I wouldn't anticipate this yet -- but if it were me I'd probably start thinking about doing this after 4 or 5 years. Few experienced IT data center folks would feel comfortable letting spindles run 24x7x365 for 6 years... even if 95% of the time it would be okay.

WD Passport 1TB unmounts itself all the time

I get this once so often: "The disk was not ejected properly. If possible, always eject a disk before unplugging it or turning it off."
I have done the following (to debug/fix) and it stills ejects itself.
- Upgraded OSX to latest version
- Upgraded WD Passport to the latest firmware
- Installed WD Drive Utilities and set the physically sleeper to never
- Unchecked "Put hard disks to sleep when possible"
- Computer sleep set to "Never"
- Checked health status OK when drive is connected (not really an issue since I know the disk works fine with PC/Windows)
About my drive
- External WD Passport 1TB USB 2.0/3.0 - uses USB as power supply
- Worked like a charm for several months on my prior setup (PC/Windows)
- NTFS drive
About my system
- Running iMac (late 2012) w/ latest OSX
- Tuxera NTFS for read/write to my NTFS drive
- Parallels (uses bootcamp partition) running on the side - usually writes data to the disk.
My disk could be up and running for 30 minutes to a couple of hours.
I cant just unplug and replug the disk whenever unmounted - I have to wait for at least 15 minutes or so.
This is really terrible - I'm a new Mac user and this is a deal breaker for me. I'm considering using my expensive iMac for Windows only - just to make my hardware work...

I've seen that post earlier but it didnt help me. I wish I had installed the WD APP. Unfortunely, I haven't. Don't know how to install it even.
The tools I've installed and tested for my WD drive got installed after the unmounting error began, so it can't be that causing the trouble.
Now my drive just got unmounted by itself again, so I'll have to wait half an hour to hook it up again - then I will look for a WD app on the drive itself - but I doubt I find any. (To install it, then maybe uninstall it...?).
Open for any suggestions... - except formatting my two day old iMac.

Time Machine Disc Unmounts Itself

My Time Machine disc (500 GB FireWire 400) unmounts by itself after 2 to 3 hours. Initially I thought it was the drive. It was always up long enough to get at least one good backup a day so I wasn't too worried about losing much data. Recently, I moved a lot of files (couple hundred GB) and now it can't finish Preparing to Backup before the disc unmounts.
I bought a new disc (2TB FireWire 400) and it is doing the same thing-unmounting after a couple of hours.
However the first disc is now staying mounted (1-1/2 days) with no problems. Obviously it is only the disk defined as the Time Machine disc that unmounts by itself, therefore, it would seem to be a Time Machine problem.
Does anybody know what is going on and, more importantly, how to work around this problem?

Yes, they all drives use Apple Partition Map. I, unfortunately do not have an Intel Mac yet (tears running down my cheek) so GUID is not really an option.
As for #D2, its not slow or hung. In fact, this new drive seems to me MUCH faster the other drives--maybe because it is 7200 RPM instead of 5400 RPM like the others.
Here is a sample of the widget logs. They're all pretty much the same:
Starting standard backup
Backing up to: /Volumes/TimeLapse/Backups.backupdb
Event store UUIDs don't match for volume: Timeless Connections
Event store UUIDs don't match for volume: The Unknown
Event store UUIDs don't match for volume: MasterControl
Event store UUIDs don't match for volume: Music
Event store UUIDs don't match for volume: Entertainer
No pre-backup thinning needed: 493.20 GB requested (including padding), 1.77 TB available
Backup requested by user
Stopping backupd to allow ejection of backup destination disk!
I am not ejecting the disk. It ejects when no one is home. Its working when I leave and ejected when I get home.
Do we need to go to the logs? Here is a sample portion of the system log from yesterday
Jan 20 16:43:18 Master-Control-2 /System/Library/CoreServices/backupd[90769]: Backing up to: /Volumes/TimeLapse/Backups.backupdb
Jan 20 16:43:34 Master-Control-2 /System/Library/CoreServices/backupd[90769]: Event store UUIDs don't match for volume: Timeless Connections
Jan 20 17:57:37: --- last message repeated 3 times ---
Jan 20 17:58:07: --- last message repeated 3 times ---
Jan 20 18:16:33: --- last message repeated 3 times ---
Jan 20 18:17:03: --- last message repeated 3 times ---
Jan 20 18:33:26 Master-Control-2 /System/Library/CoreServices/backupd[90769]: Copied 3032 files (79.1 GB) from volume Timeless Connections.
Jan 20 18:37:38 Master-Control-2 /System/Library/CoreServices/backupd[91797]: Backing up to: /Volumes/TimeLapse/Backups.backupdb
Jan 20 18:37:47 Master-Control-2 /System/Library/CoreServices/backupd[91797]: Event store UUIDs don't match for volume: Timeless Connections
Jan 20 19:39:08 Master-Control-2 /System/Library/CoreServices/backupd[91797]: Copied 30 files (47.4 GB) from volume Timeless Connections.
Jan 20 19:39:24 Master-Control-2 com.klieme.TimeMachineScheduler[92268]: false
Jan 20 20:07:50 Master-Control-2 /System/Library/CoreServices/backupd[92546]: Backing up to: /Volumes/TimeLapse/Backups.backupdb
Jan 20 20:07:57 Master-Control-2 /System/Library/CoreServices/backupd[92546]: Event store UUIDs don't match for volume: Timeless Connections
Jan 20 20:31:42: --- last message repeated 3 times ---
Jan 20 20:32:12: --- last message repeated 3 times ---
Jan 20 22:39:04 Master-Control-2 /System/Library/CoreServices/backupd[92546]: Copied 51 files (118.7 GB) from volume Timeless Connections.
Jan 20 22:39:20 Master-Control-2 com.klieme.TimeMachineScheduler[93729]: false
Do you see anything useful? What's this about the "UUIDs don't match for volume"? I know it is Unique User ID but I'm not sure what it is telling me. What doesn't match?

IPod Classic unmounts itself

I've had at least 3 iPods over the years, but the behavior or this iPod is unusual. It worked normally until I got my iPhone, which I also sync by connecting to my MacPro.
Typically, what happens is that I plug in my iPod and my iPhone for syncing which works correctly. (One device s plugged in via the USP on the back of my 30 inch Cinema Display and the other device is via the USB on the front of my MacPro.) Both devices show up in iTunes and the iPod mounts and appears on my desktop.
After syncing I disconnect the iPhone and leave the iPod connected. When I come back to my Mac later, the iPod has been unmounted and does not appear in iTunes or on my desktop. This has happened NUMEROUS times now.
This has only begun since I got my iPhone. Nothing else has changed. What's up?
Mac OSX 10.6.3
iTunes 9.1
iPod Classic 120GB (2.0.1)
iPhone 3GS 32GB (3.1.3)

You might try enabling disk mode on the Classic, that should keep it connected until you eject it (which would be required every time if you enable this option).

[SOLVED] Mounted USB stick immediately unmounts itself - why?

Hi all,
I thought I was unable to mount a USB stick, however it does actually mount but then it gets immediately unmounted by something:
# mount /dev/sdd1 /mnt
# ls /mnt
<empty folder>
# umount /mnt
umount: /mnt: not mounted
# mount /dev/sdd1 /mnt && ls /mnt
<contents of USB stick>
# ls /mnt
<empty folder>
Somehow the USB stick is getting automatically *unmounted* almost immediately after I mount it!
I don't have any automounts enabled, so I'm not sure why this would happen. If I make a different folder (e.g. /root/test) and mount it there then it sticks, it is only the /mnt folder that gets automatically unmounted.
Any idea what's going on? I've never seen this happen before, and last time I tried this (a week or two ago) it worked fine.
Last edited by Malvineous (2015-03-15 01:15:16)

brebs wrote:Use "mount -v" (i.e. "verbose") to get some feedback - it's most likely not being mounted.
Like I said in my first post, if you run "ls" immediately after the mount then you can see the contents of the USB stick, so it's definitely getting mounted, but waiting only a few hundred milliseconds after the mount reveals it has been unmounted again. What is causing the unmount is unknown.
brebs wrote:
Immediately after running that mount command, run:
echo $?
To see the return code. It should be 0.
Yes it is zero, because the mount command succeeds. "ls" wouldn't be able to list the files on the USB stick if the mount failed. It is something else that is unmounting the folder mere milliseconds after it is successfully mounted, but I don't know where else to look to find out what it could be.
brebs wrote:Also, mounting to /mnt is very weird - you should be mounting a directory *inside* /mnt.
I am mounting inside /mnt, I just used /mnt as an example to keep things simple.
Vain wrote:
I made the same “mistake”. Try running “systemctl status mnt.mount” and see which device the output refers to. For me, it still listed the old device name. Hence, when you mount it, systemd tries to find the (old) device—which it can’t—and thus unmounts your device immediately.
I was too lazy/annoyed to find out how to solve this properly. I rebooted my system.
Interesting idea! Unfortunately I have nothing listed for this particular mount point. The only *.mount services on my system are the ones that are mounted at boot (e.g. srv.mount for /srv). I have the "noauto" option against this mount point in fstab (as USB sticks aren't normally attached to my system when I boot) so sensibly enough I don't seem to have a mount service running for this particular mount point.

External Hard Drive Unmounts itself

I have a WD 500Gb external hard drive which I use solely for Time machine. The other day for no reason I got the error message that the drive had not been properly ejected. Since then the Mac does not recognise that the hard drive is attached. I have tried using the Disk Utility to repair permissions and repair disk but this has had no effect. There is some crucial information in Time Machine that I need to recover. Does anyone know how I can get this drive back please.

Hello Jennsy:
Welcome to Apple discussions.
Try this:
Turn your external disk off. Trash a preference file (com.apple.timemachine.plist) and restart. Turn the external disk on. If the external disk is not recognized as a TM disk, go to system preference>time machine>select disk.
Barry
P.S. I do not have a WD disk, but I have read other posts in these forums about people that have had problems with them (FWIW).

G-raid Unmounts Itself

Similar Messages

Maybe you are looking for