Welcome to the MacNN Forums.

Mac Write · Mar 5, 2004, 02:46 AM

I have logged out/in and still can't eject a networked server. Even restarted my network server. I don't want to have to restart my G4, good uptime. Is there anyway to force eject the drive? Use the temrinal?

Thanks

utidjian · Mar 5, 2004, 07:12 AM

Originally posted by Mac Write:
I have logged out/in and still can't eject a networked server. Even restarted my network server. I don't want to have to restart my G4, good uptime. Is there anyway to force eject the drive? Use the temrinal?

It depends on how that network share is mounted. I have sixteen Panther systems mounting shares via NFS. Sometimes a client will "drop" a share and there is no way I have found to force an unmount... either GUI or commandline. Rebooting the server is certainly not an option because then all the other systems also drop the share. The only solution I have found is to reboot the client. I have the same problem with AFP from Apple and Linux servers and Samba from Apple and Linux servers. Network shares via NFS from a Linux server gives me the least problems. Simplest solution that always works is to reboot the client.

Apple needs to work on this.

SMacTech · Mar 5, 2004, 07:26 AM

I don't know why some people are having this problem with unmounting network shares. There has to be something specific to an installation. As a sys admin with ~ 10 OS X computers in use, I see none of this happening. This is with several samba on RedHat 9 and NT, 2000 and 2003 with either native Services for Macintosh or 3rd party AFP/IP service.
I can say that the 10.3.3 seed currently out, does fix some other issues with using the Network icon, and shares appearing on the desktop.
Networking is far from perfect, but it is not the abomination that some are making it out to be. If it were, I would never get my job done.

-Q- · Mar 5, 2004, 08:40 AM

Originally posted by Mac Write:
I don't want to have to restart my G4, good uptime.

The fact that you can't eject the drive says your uptime is no longer 'good.' Restart your machine and I bet your problem is solved.

philzilla · Mar 5, 2004, 10:19 AM

i have this problem right now. it happens a lot. i have to use umount -f servername, which should not have to be done. Apple seriously needs to work on the networking side of things.

utidjian · Mar 5, 2004, 11:11 AM

Originally posted by SMacTech:
I don't know why some people are having this problem with unmounting network shares. There has to be something specific to an installation. As a sys admin with ~ 10 OS X computers in use, I see none of this happening. This is with several samba on RedHat 9 and NT, 2000 and 2003 with either native Services for Macintosh or 3rd party AFP/IP service.
I can say that the 10.3.3 seed currently out, does fix some other issues with using the Network icon, and shares appearing on the desktop.
Networking is far from perfect, but it is not the abomination that some are making it out to be. If it were, I would never get my job done.

I don't know about 10.3.3 seed. But I have almost always had problems with Mac OS X and network shares. It must be said that, for most of the time, the problems are rare (for me). This can be quite variable... from one upgrade of Mac OS X to another. Sometimes it improves and sometimes it gets worse. Sometimes I go for weeks without any problems at all and sometimes several machines seem to be dropping shares and therefore need rebooting each day. I have been running Mac OS X server for over 4 years and Mac OS X client for the past 3 years. In my experience, the Mac OS X client has been far less reliable than the Linux clients over that time as regards network shares. That is not to say they have been unuseable... but I would be lying if I said I "never" had a problem.

For the most part it is a matter of perception. If one almost never has to reboot or fiddle with a machine for any reason... when the time comes when one does have to reboot... it seems, to me, that something is fundamentally broken. Some of this can be masked by the neccessary reboots as one applies updates.

As the sticker in the window says... Your mileage may vary.

frozentundra · Mar 5, 2004, 11:45 PM

Hello

I had a similar problem with my Powerbook when I would change locations and forget to umount my server before moving. I would put my PB to sleep go home open it and the server was still there and I would get the spinning beach ball blues. There was no way to get rid of the server which is nolonger connected. I had to reboot.

That is until I upgraded to 10.3.2

Now if/when I forget to unmount my server. I get an option to unmount a disconnected server. It takes less than a minute for my Mac to realise the server is no longer connected and it askes you if you want to disconnect.

I don't know what level your OS is at but it may be a simple fix to upgrade.

Later,
FT

Mac Write · Mar 6, 2004, 04:23 AM

I am running 10.3.2. and 10.2.8 on my Server (It isn't supported in Panther damm you Apple!)

jmiddel · Mar 6, 2004, 04:04 PM

Mac Write,

In case you have not tried this, there is an app called XPostFacto that claims to allow Panther to run on older Macs.

http://www.versiontracker.com/dyn/moreinfo/macosx/11168

Deicide · Mar 6, 2004, 05:40 PM

This has happened to me and a couple of my users too. A umount -f host or a restart is the only fix I have seen so far. Another problem I have seen with all users running 10.3.x(which is about 20 or so users) is that 10.3 will try to log into every host in the network. It's not fun hitting the cancel or escape key a couple hundred times to dismiss the login dialog. I have not seen either of these problems with 10.2.x.

Mac Write · Mar 6, 2004, 09:00 PM

Originally posted by jmiddel:
Mac Write,

In case you have not tried this, there is an app called XPostFacto that claims to allow Panther to run on older Macs.

http://www.versiontracker.com/dyn/moreinfo/macosx/11168

I know about XFacto but I don't have a Family Licence as 10.3 came with both new computers. and last I heard 3.0 final isn't out and also I don't have OS 9 for that computer. OS X exclusively.