Device is mounted or busy

Hello,
I am running Solaris 11 with multiple zones. When I set up one of my zones, I configured it with a device (add device, set match=/dev/*dsk/device_name). Within a non-global zone, I created an ufs file system on this device and mounted i in /etc/vfstab. Now I want to remove this device and mount it in a global zone and export it out as lofi to multiple zones. I am able to remove the device from the zone's config, reboot the zone, confirm that the device is gone. I also made sure that the device entry is no longer in /etc/vfstab in non-global zone. Now I added this entry to /etc/vfstab in global zone. When I attempt to mount it, I get an error message:
mount: /dev/dsk /c0t600601600A212D00D6E38ED56C32E111d0s2 is already mounted or /sandsk/sanvnx-arr1/t3s1 is busy
I am not sure why I am getting it as I can't see anywhere (in both global and non-global zones) the device to be mounted.
If I reboot my Solaris 11 server, the problem will most likely get resolved, but I would like to do in a way that is least destructive to my users and prod env.
Any help would be much appreciated.
Thank you,
Igor

Hello Eze,
You are right that dynamic zone config is now available with 11.2
The issue is that despite dynamic and static attempts to remove the device from non-global zone, the device is still considered mounted within a global zone.
There is no problem with device removal from non-global zone from the non-global zone's perspective, yet the global zone still thinks that the device is mounted within that non-global zone. Reboot resolves the issue as it flushes out the config info for all zones.
Thank you for your reply.
Regards,
Igor

Similar Messages

Getting Error Message - mount.ocfs2: No such device while mounting

I am trying to mount an ocfs2 file system. The file system seems to have been created fine but I get an error message when I try to mount it. Here's what I get :
[root@mdcpsdb1 init.d]# ./o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking cluster ocfs2: Online
Checking heartbeat: Active
[root@mdcpsdb1 init.d]# fsck.ocfs2 /dev/sdc1
Checking OCFS2 filesystem in /dev/sdc1:
label: oracle_hr
uuid: f6 23 5e 3b ad bb 49 87 81 a3 cb f0 b7 2a d0 ad
number of blocks: 24416784
bytes per block: 4096
number of clusters: 6104196
bytes per cluster: 16384
max slots: 4
/dev/sdc1 is clean. It will be checked after 20 additional mounts.
[root@mdcpsdb1 init.d]# mount -t ocfs2 /dev/sdc1 /hr_data
mount.ocfs2: No such device while mounting /dev/sdc1 on /hr_data
The same thing happens going through the ocfs2console.
Thanks,
David

Did you get anwer for this error? I got same error. Thanks in advance.

"underlying task reported failure..." & "root device is mounted read-only"

My ibook is not starting up. It was having problems loading up and getting in interminable spinning ball fits as I tried to use the computer for basic things like surfing internet, word processing, itunes. I ran disk repair several times, and the problems would resume. Finally I left it on, afraid to turn it off, but my boyfriend unplugged it, and it eventually ran out of juice. Now I hear it power up, but it doesn't start up all the way (it's gotten to different points in start-up process after I took each step below, but never all the way).
What I've tried so far:
1. I've run disk repair from the start-up disk, and got the "The underlying task reported failure on exit" message.
2. I did the archive reinstall, did not work either. Tried disk repair again and still getting same message as #1.
3. Also tried starting up in single-user mode and running fsck, but getting message "root device is mounted read-only." Not sure what this means. Ran disk repair again after this, gets me same message as #1.
I'm hesitant to do a complete reinstall, as I have documents and music files that haven't been backed up. I have an external hard drive to move files if I could just start up my computer.
My questions:
1) Any thing else I can try short of complete reinstall to fix the problem?
2) Any way I can save my files if I can't get the computer fully loaded?
3) Would a 3rd-party disk repair program allow me to fix the problem without wiping out my files?
4) Why is fsck not running?
Any advice would be appreciated!

Hi, tgt. DiskWarrior would be a good bet to fix the "keys out of order" errror, if things haven't gotten much worse since you saw that message. You can order it direct from its developer, Alsoft, or you can call around to Mac dealers in your area to see if one carries it. If you already have a bootable external hard drive with OS X 10.3.9 or better installed on it, you can boot to the external drive, buy DW from Alsoft via download, install it on the external drive, and use it to therapize the internal drive. If you don't have an external drive with 10.3.9 or better installed, you'll need the DW CD to start up from.
To shut your computer down while it isn't working properly, just press and hold down the power button for a few seconds.

/dev/shm not mounted /dev busy

Recently I was trying out a boot disk I had made, and basically, I switched it off several times due to it booting the completely wrong kernel.
Now, I'm getting to the stage "Checking File systems" and then comes up [Failed]. I then get a message saying Reboot required, and that it will reboot in 15 seconds, just a few seconds before it reboots I get "/dev/shm not mounted, /dev busy" or something similar.
I've booted up my sysresccd, ran "fsck.ext4 -fcv /dev/sda2" to force a check and scan for any bad blocks, it came up clean, then I rebooted and got the same error, so I copied the kernel and system.map over to /boot to make sure there's no corruption and reinstalled initscripts and util-linux-ng, rebooted, same error.
Tried different kernels, I've checked fstab and menu.lst, no problems there, so I still don't get why I still get the same problem.
Anybody know of any fix other than reinstalling arch?
EDIT: Editing /etc/rc.sysinit and commenting out the fsck part made it work, finding out why fsck failed now.
Last edited by compgenius999 (2010-03-03 19:21:35)

anybody?

Device Media Processor is busy

I just recently purchased a new torch 9850 and have only had it some six days. Overall its been working wonderfully so far whoever after a while the music player portion of the phone becomes unresponsive in playing a song with the notification of Device Media Processor is Busy. Thing is there isn't anything else playing whenever this comes about. Now I've been able to temporarily get rid of the problem by removing the battery while the phone is still on and performing a cold boot. Thing is I've had to do this 3 times now, so its starting to get rather annoying particularly for the fact I shouldn't have to do this or be experiencing this problem at all. Any ideas of what I should do would be greatly appreciated.

AmunRa wrote:
I just recently purchased a new torch 9850 and have only had it some six days. Overall its been working wonderfully so far whoever after a while the music player portion of the phone becomes unresponsive in playing a song with the notification of Device Media Processor is Busy. Thing is there isn't anything else playing whenever this comes about. Now I've been able to temporarily get rid of the problem by removing the battery while the phone is still on and performing a cold boot. Thing is I've had to do this 3 times now, so its starting to get rather annoying particularly for the fact I shouldn't have to do this or be experiencing this problem at all. Any ideas of what I should do would be greatly appreciated.
Hi AmunRa,
Reload your OS. Read this article.
How to perform a clean reload of the BlackBerry Device Software for Windows
Good luck!
Please thank those who help you by clicking the button.
If your issue has been solved, please resolve it by marking "Accept as Solution"

X86_64: Skype2.0 - "RtApiOss: OSS playback device (/dev/dsp) is busy."

I should say that I managed to get Skype to work by installing the 32-bit alsa-oss and passing Skype through it (i.e. "aoss skype").
What's confusing to me is that, according to ArchWiki, versions 2.0 and up have native ALSA support. This means that alsa-oss should no longer be necessary, right?
Running plain Skype in a terminal, I always get the error "RtApiOss: OSS playback device (/dev/dsp) is busy."
dsp_hijacker has no effect in this case, nor does adding
pcm.dmixout {
# Just pass this on to the system dmix
type plug
slave {
pcm "dmix"
to my ~/.asoundrc (as the wiki suggests). The latter does nothing; running Skype by itself with this modification produces the same error, and Skype with aoss32 works without an .asoundrc.
Is there some obvious solution that I'm missing?
Last edited by cautha (2009-04-03 08:22:32)

@themaister: thanks for pointing that out!
I removed those modules from rc.conf and added my soundcard modules (according to wiki):
MODULES=(snd-ice1724 snd-intel8x0 snd-pcm-oss)
I now have "dev/dsp" and "/dev/dsp1", but still no "/dev/sound/dsp" (though I'm not sure if I need this).
Hmmmm... It works! I don't know what did it. I retried several steps of the wiki. The last steps I tried were adding my cards with indices to /etc/modprobe.d/modprobe.conf and having alsaconf set up /dev/modprobe.d/sound.conf. Outputs are stille the same as in my first thread. Maybe I got mixed up along the way with pulseaudio installation/removal and blacklisting modules...
Last edited by JackSchnippes (2010-06-16 22:58:54)

Mount fat32 on x86: already mounted or busy

hi. i suppose mounting fat32 on x86 is well-documented, but i'm having trouble, so i'd appreciate some help.
im dual booting with solaris 10 and xp. my partitions are as follows:
1st physical drive
[boot sector] 55 MB
[c:] label XP (NTFS)
solaris partitions...
2nd physical drive
[d:] label Data (FAT32) (about 17 GB)
i'd like to mount my FAT32 drive. according to man mount and man pcfs, i thought i'd do seomething like:
bash-3.00# mount -F pcfs /dev/dsk/c1t0d0p0:d /mnt/data
which yields:
mount: /dev/dsk/c1t0d0p0:d is already mounted or /mnt/data is busy
theres nothign in the /mnt/data folder. as far as i can tell, the drive isn't mounted. am i naming hte wrong device? im reading this "device-special:logical drive" stuff and i guess it's not making sense. i've included some more info below.
hopefully after this i can mount the drive in the vfstab, but if not i suppose ill be back.
bash-3.00# iostat -nxp
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
3.6 1.0 30.5 4.5 0.0 0.0 2.9 4.9 0 2 c0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 5.7 0 0 c0d1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 fd0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t1d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 unknown:vold(pid507)
bash-3.00# mount
/ on /dev/dsk/c0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/oner ror=panic/dev=1980000 on Sun Feb 19 20:27:38 2006
/devices on /devices read/write/setuid/devices/dev=4380000 on Sun Feb 19 20:27:24 2006
/system/contract on ctfs read/write/setuid/devices/dev=43c0001 on Sun Feb 19 20:27:24 2006
/proc on proc read/write/setuid/devices/dev=4400000 on Sun Feb 19 20:27:24 2006
/etc/mnttab on mnttab read/write/setuid/devices/dev=4440001 on Sun Feb 19 20:27:24 2006
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=4480001 on Sun Feb 19 20:27:24 2006/system/object on objfs read/write/setuid/devices/dev=44c0001 on Sun Feb 19 20:27:24 2006
/lib/libc.so.1 on /usr/lib/libc/libc_hwcap1.so.1 read/write/setuid/devices/dev=1980000 on Sun Feb 19 20:27:37 2006
/dev/fd on fd read/write/setuid/devices/dev=4680001 on Sun Feb 19 20:27:38 2006
/tmp on swap read/write/setuid/devices/xattr/dev=4480002 on Sun Feb 19 20:27:38 2006
/var/run on swap read/write/setuid/devices/xattr/dev=4480003 on Sun Feb 19 20:27:39 2006
/export/home on /dev/dsk/c0d0s7 read/write/setuid/devices/intr/largefiles/logging/xattr/oner ror=panic/dev=1980007 on Sun Feb 19 20:27:44 2006
thanks!!!

thanks martin
i think i was trying to mount a SCSI drive instead of IDE that I have... thanks for clearing that up. i was also frustrated with teh :c part, I think I forgot about the 1st partition part.
im under the impression that c0d0p1:c is my first physical drive, which is NTFS because of:
bash-3.00# mount -F pcfs /dev/dsk/c0d0p1 /mnt/data
mount: /dev/dsk/c0d1p1:c is not a DOS filesystem.
but then why would c0d1p1 also yield:
bash-3.00# mount -F pcfs /dev/dsk/c0d1p1 /mnt/data
mount: /dev/dsk/c0d0p1, c0d0p2 is not a DOS filesystem.
then again c0d0p0, c0d0p2, and c0d1p0 yields the same...
is there a way to list the devices present, or do i have to throw knives at the wind? does anyone understand the naming schema of cN and dN? man pcfs and man mount don't help a whole lot.
i dont see anything helpful in the vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0d0s1 - - swap - no -
/dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no -
/dev/dsk/c0d0s7 /dev/rdsk/c0d0s7 /export/home ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
i also found thsi script that output the devices... but it doesnt see any fat32 partitions =(
bash-3.00# for f in /dev/rdsk/* ; do echo "$f = $(fstyp $f 2>/dev/null )"; done
/dev/rdsk/c0d0p0 =
/dev/rdsk/c0d0p1 =
/dev/rdsk/c0d0p2 =
/dev/rdsk/c0d0p3 =
/dev/rdsk/c0d0p4 =
/dev/rdsk/c0d0s0 = ufs
/dev/rdsk/c0d0s1 =
/dev/rdsk/c0d0s10 =
/dev/rdsk/c0d0s11 =
/dev/rdsk/c0d0s12 =
/dev/rdsk/c0d0s13 =
/dev/rdsk/c0d0s14 =
/dev/rdsk/c0d0s15 =
/dev/rdsk/c0d0s2 =
/dev/rdsk/c0d0s3 =
/dev/rdsk/c0d0s4 =
/dev/rdsk/c0d0s5 =
/dev/rdsk/c0d0s6 =
/dev/rdsk/c0d0s7 = ufs
/dev/rdsk/c0d0s8 =
/dev/rdsk/c0d0s9 =
/dev/rdsk/c0d1p0 =
/dev/rdsk/c0d1p1 =
/dev/rdsk/c0d1p2 =
/dev/rdsk/c0d1p3 =
/dev/rdsk/c0d1p4 =
/dev/rdsk/c0d1s0 =
/dev/rdsk/c0d1s1 =
/dev/rdsk/c0d1s10 =
/dev/rdsk/c0d1s11 =
/dev/rdsk/c0d1s12 =
/dev/rdsk/c0d1s13 =
/dev/rdsk/c0d1s14 =
/dev/rdsk/c0d1s15 =
/dev/rdsk/c0d1s2 =
/dev/rdsk/c0d1s3 =
/dev/rdsk/c0d1s4 =
/dev/rdsk/c0d1s5 =
/dev/rdsk/c0d1s6 =
/dev/rdsk/c0d1s7 =
/dev/rdsk/c0d1s8 =
/dev/rdsk/c0d1s9 =
/dev/rdsk/c1t0d0p0 =
/dev/rdsk/c1t0d0p1 =
/dev/rdsk/c1t0d0p2 =
/dev/rdsk/c1t0d0p3 =
/dev/rdsk/c1t0d0p4 =
/dev/rdsk/c1t0d0s0 =
/dev/rdsk/c1t0d0s1 =
/dev/rdsk/c1t0d0s10 =
/dev/rdsk/c1t0d0s11 =
/dev/rdsk/c1t0d0s12 =
/dev/rdsk/c1t0d0s13 =
/dev/rdsk/c1t0d0s14 =
/dev/rdsk/c1t0d0s15 =
/dev/rdsk/c1t0d0s2 =
/dev/rdsk/c1t0d0s3 =
/dev/rdsk/c1t0d0s4 =
/dev/rdsk/c1t0d0s5 =
/dev/rdsk/c1t0d0s6 =
/dev/rdsk/c1t0d0s7 =
/dev/rdsk/c1t0d0s8 =
/dev/rdsk/c1t0d0s9 =
/dev/rdsk/c1t1d0p0 =
/dev/rdsk/c1t1d0p1 =
/dev/rdsk/c1t1d0p2 =
/dev/rdsk/c1t1d0p3 =
/dev/rdsk/c1t1d0p4 =
/dev/rdsk/c1t1d0s0 =
/dev/rdsk/c1t1d0s1 =
/dev/rdsk/c1t1d0s10 =
/dev/rdsk/c1t1d0s11 =
/dev/rdsk/c1t1d0s12 =
/dev/rdsk/c1t1d0s13 =
/dev/rdsk/c1t1d0s14 =
/dev/rdsk/c1t1d0s15 =
/dev/rdsk/c1t1d0s2 =
/dev/rdsk/c1t1d0s3 =
/dev/rdsk/c1t1d0s4 =
/dev/rdsk/c1t1d0s5 =
/dev/rdsk/c1t1d0s6 =
/dev/rdsk/c1t1d0s7 =
/dev/rdsk/c1t1d0s8 =
/dev/rdsk/c1t1d0s9 =
/dev/rdsk/c2t0d0p0 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p0>
/dev/rdsk/c2t0d0p1 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p1>
/dev/rdsk/c2t0d0p2 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p2>
/dev/rdsk/c2t0d0p3 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p3>
/dev/rdsk/c2t0d0p4 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p4>
/dev/rdsk/c2t0d0s0 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s0>
/dev/rdsk/c2t0d0s1 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s1>
/dev/rdsk/c2t0d0s10 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s10>
/dev/rdsk/c2t0d0s11 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s11>
/dev/rdsk/c2t0d0s12 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s12>
/dev/rdsk/c2t0d0s13 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s13>
/dev/rdsk/c2t0d0s14 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s14>
/dev/rdsk/c2t0d0s15 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s15>
/dev/rdsk/c2t0d0s2 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s2>
/dev/rdsk/c2t0d0s3 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s3>
/dev/rdsk/c2t0d0s4 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s4>
/dev/rdsk/c2t0d0s5 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s5>
/dev/rdsk/c2t0d0s6 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s6>
/dev/rdsk/c2t0d0s7 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s7>
/dev/rdsk/c2t0d0s8 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s8>
/dev/rdsk/c2t0d0s9 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s9>
thanks again for your help

A thousand USB questions .. later why do USB devices not mount/stop working

I know this is loaded post but I'm getting really torqued at the USB sub-system in OS X.
I bought a mini ~2 years to see what the OSX scene was like, so far it's mostly been a great OS but the USB problems past at work, on my home system only cropped up in the past few months is very frustrating. :-P
I've done the googling, apples pathetic troubleshooting pages, run the Profiler and USB Prober trying to determine all with no luck.
Can any of you help me "get it"?
At work, we had a OSX server a few years that failed to stop mounting a USB drive that had been used several time before. It was under support and Apple failed to resolve the problem!!
I had a Transcend usb enclosure that worked in 10.3 and by the time 10.4 rolled around it stopped working (checked on a few different macs)
Now I have a iogear gfr280 memory card reader/writer that worked three months ago and just tried to use it the other day ... borked!!. I then take it to work plug it into my co-workers iMac running 10.5, mounts up and I can copy my photos off the SD card, no issues. WTH!?
Also, just the other day my digital camera powershot A630 batteries ran out right as I was importing... Took me three hours of reboots, plugging in my thumb drive and camera only to have them show up for a split second then disappear from iphoto or the desktop.
I even thought of calling Apple on this one but I'm leary based on prior experience with the server incident.
This is even worse than under Linux(run that too), most times the kernel either supports the device or it doesn't ( I can live with that! ). None of this .. I'm gonna work and then all the sudden stop one day.
Anyone? Would it be worth paying for a one-time support call?

Try things in this USB faq.
DALE

[Device Auto-mounting] HAL,KDE4.4 and default permissions

Hello,
I have a small problem with default permissions of Automounted
Removable Devices. Whenever I mount it via KDE4.4's Auto-mounter. it
sets all files to be owned by root.
> ls -la /media/Backup/
total 28
drwxr-xr-x 4 root root 4096 Feb 11 14:46 .
drwxr-xr-x 6 root root 4096 Feb 11 14:44 ..
drwxr-xr-x 3 root root 4096 Feb 11 14:46 Gaurish_data
drwx------ 2 root root 16384 Feb 10 16:07 lost+found
I know KDE does not mount anything, it asks HAL. nothing is in
/etc/fstab but in /etc/mtab and in /proc/mount I got
$ cat /etc/mtab
/dev/sdb1 /media/Backup ext4 rw,nosuid,nodev,uhelper=hal 0 0
$ cat /proc/mounts
/dev/sdb1 /media/Backup ext4
rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
I like all my files and folders to be owner by me and NOT by root.
any help?

Are you using [testing]? Partially updated system?
The error looks like you have a different version of gcc-libs / glibc than the app was built against.
Last edited by Mr.Elendig (2011-06-20 19:16:33)

Cannot mount cgroup: already mounted or busy

I am unable to mount cgroups on a fresh boot of a recent installation, fully up-to-date.
# mkdir /cgroups
# mount -t cgroup none /cgroups
mount: none already exists of /cgroups busy
According to lxc-config, I have cgroups enabled, and `dmesg | grep -i cgroup` confirms that the relevant subsystems are initialized. I am not finding anything added to dmesg.log, kernel.log, everything.log, etc., by the mount command.
Any ideas?

I am unable to mount cgroups on a fresh boot of a recent installation, fully up-to-date.
# mkdir /cgroups
# mount -t cgroup none /cgroups
mount: none already exists of /cgroups busy
According to lxc-config, I have cgroups enabled, and `dmesg | grep -i cgroup` confirms that the relevant subsystems are initialized. I am not finding anything added to dmesg.log, kernel.log, everything.log, etc., by the mount command.
Any ideas?

USB devices not mounting in one port?

I have two late 2007 MacBooks, neither of which reliably mounts a USB device plugged into the port closest to the firewire port on the left side. These two MacBooks were purchased within a week of each other about four months ago. I have returned one of them for factory repair of this problem. This was actually the second repair, since a few weeks previous the mainboard failed catastrophically.
The repair consisted of replacing the hard drive. The tech ("genius") at my local Apple store said it had been a software problem. I reinstalled each software package while testing for the problem to re-emerge, and it seemed to happen when I installed Skype for Mac 2.7.0.330. This may have been coincidental, since the problem doesn't occur when Skype isn't running, and the other MacBook doesn't have Skype installed on it at all. If I cold restart this Macbook, a USB device in the port in question will mount.
Has anyone experienced anything like this? Any tips will be appreciated!

I found this article whilst researching which external drive to buy to use with my powerbook and a future macbook purchase: All USB ports aren’t created equal
Could this be the cause of the problem - specifically that the problem port is not supplying enough power to your external drive because it's also powering the iSight etc?
Regards, Andrew.

X4100 mount command for second drive shows device already mounted

I have a new x4100 system and I created a new partition and ext3 filesystem on the second drive. When I try to use that partition I get the error:
mount: /dev/sdb1 already mounted
Since this is a new system, that partition has never been used and I can't see anywhere that the device is in use. I tried the same thing on other systems and I get the same error. Has anyone seen this problem and if so how was it resolved?
thanks

Post Unix/Terminal queries to its forum under OS X Technologies.

External firewire devices stopped mounting on my Xserve

I have two external Firewire 800 Lacie hard drives that I connect to my Xserve alternately to act as backup drives (and use an Applescript to copy over important files daily).
But this week, after having worked fine for a couple of years, the drives are refusing to mount on the Xserve desktop.
They both mount fine if connected to my G5 tower and work fine, but just won't show on the Xserve.
Nothing on the Xserve has changed, it hasn't crashed recently or had any upgrades done, they've just stopped working. I've tried different cables but nothing.
Any ideas?
Thanks in advance of any replies.
John

Those LaCie drives can be funky. The external AC power supply bricks tend to fail prematurely. The symptom can be hard to troubleshoot since the drive will attempt to and can pull the juice it needs from the firewire bus. If the drive in question is under warranty LaCie will replace the brick at no charge. Otherwise they sell them for around $20 US. I keep a spare around because I have a lot of LaCie drives.

IOS devices not mounting

Recently my iMac seems not to notice when I connect any of my iOS devices via the USB cable. The devices do recharge when connected, so it's not the cable. But the device won't appear either in the iTunes or Finder sidebars. How do I troubleshoot this?

http://www.apple.com/support/itunes/assistant/ had all my answers. Problem solved!

Usb device no mount

My Garmin GPS will not mount. The usb cable is data rated and worked fine a year ago with system 10.6 . Following the discussion groups I have zapped the PR, reset the SMC, repaired permissions, repaired disk (no defects found), created a second user account, did command R at startup. Disk Utility can see something that is the right size, but it is grayed out.
Garmin has not come up with anything useful.
Any suggestions?

The usb cable is data rated and worked fine a year ago
not sure what being data rated imply for an usb cable but the fact that it worked a year ago dont matter anymore then my car used to work a year ago too but that don't mean it does now
so my first test would be to change the cable then I
would try to connect the gps with another computer to see if it act up in the same way

Device is mounted or busy

Similar Messages

Maybe you are looking for