image
image
Ticket Options
Question Details
TICKET ARCHIVE -> Network Trouble After Hard Drive Replaced
aussiehoudini - Jun 22, 2005 - 10:21 am
image
image
hi,
I recently got a new 80GB hard drive fitted by an apple centre and all seemed to be going smoothly but today I clicked on network and a terminal window and text edit opeded. Weird. Now the apple centre is nearly 2 hours drive away and it'd be a bugger to have to drive all the way back. Can anyone here help?
The network icon when you cick on home no longer looks like it did (i.e. the grey world) but now looks like a text document.

I booted from the startup CD and fixed permissions and it seemed to find a permission that was to do with network:

It said the ./Network permission was wrong - should be drwxr-xr-x but was -rwxr-xr-x

Is this possibly the problem. How do I change it? It said it fixed it but i ran it again and it found the same problem. I fixed it again, rebooted and it had the same problem.

I can see my Mac (an iBook) from the other Mac in the house when i use itunes or iphoto, but I can't use the network thng at all on my Mac.
thanks
D
Vile - Jun 23, 2005 - 3:20 am
image
image
Hi Aussie. Thanks for choosing MacOSX.com for your support questions.

It looks like there is a serious issue here. It says it should be drwxr-xr-x, instead of -rwxr-xr-x. The first character "d" indicates a directory. Since it's no longer a directory, there is a big problem. Could you run the command "df -h" (w/o the quotes) in a terminal, and paste the output so that I can see what is going on with that directory?
aussiehoudini - Jun 24, 2005 - 2:57 am
image
image
Hi, thanks for the response. i ran it:
last login: fri jun 24 15:46:54 on console
welcome to darwin!
damian-heffernans-computer:~ damianheffernan$ df -h
filesystem size used avail capacity mounted on
/dev/disk0s3 74g 37g 38g 49% /
devfs 88k 88k 0b 100% /dev
fdesc 1.0k 1.0k 0b 100% /dev
512k 512k 0b 100% /.vol
damian-heffernans-computer:~ damianheffernan$

that's it. thanks,
damian
Vile - Jun 24, 2005 - 10:23 pm
image
image
Ok. That does pose to be a problem. There is suppose to be a /Volumes/Network mounted device in there, which is linked to your networking utilities. I will try to find the best, and easiest solution for this problem so that you can get your tools back.
aussiehoudini - Jun 25, 2005 - 2:43 am
image
image
Thanks, appreciate it. If I have to reinstall the os that might be aproblem if I can't do it and keep my appliucations as I have heaps of apps that i use. If there was a way to do it and not have to reinstall the 50+ applications I have on my machine that would be great. Otherwise would something like Disk warrior or another program be able to fix it? Just thoughts. Thanks for looking, wait with held breath for your response.
cheers
Damian
Vile - Jun 26, 2005 - 2:10 am
image
image
What you should see from that command is this:

> df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s3 56G 37G 19G 66% /
devfs 89K 89K 0B 100% /dev
fdesc 1.0K 1.0K 0B 100% /dev
512K 512K 0B 100% /.vol
automount -nsl [347] 0B 0B 0B 100% /Network
automount -fstab [350] 0B 0B 0B 100% /automount/Servers
automount -static [350] 0B 0B 0B 100% /automount/static

As you can see, the automount volumes are not getting mounted. Let's look at one more thing. Run this command in a terminal:

cat /var/log/system.log | grep automount

This will show us if automount is working at bootup, or if it erroring out because of something.

A reinstall might be the only answer, but we do not know yet. If it is, you might want to go to the store you had the drive replaced, and work out something getting your applications preserved, and reimbursement for drive time since they are liable for their mistake. I should be able to give you a better answer after we see what automount is doing.
aussiehoudini - Jun 26, 2005 - 9:14 am
image
image
HI,
OK ran it and got a huge load of??:
Welcome to Darwin!
Damian-Heffernans-Computer:~ damianheffernan$ cat /var/log/system.log | grep automount
Jun 23 12:10:58 localhost automount[342]: automount version 57
Jun 23 12:10:58 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 23 12:10:59 localhost automount[345]: automount version 57
Jun 23 12:11:00 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 23 12:11:00 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
Jun 23 15:04:40 localhost automount[341]: automount version 57
Jun 23 15:04:40 localhost automount[341]: Can't mount map -nsl on /Network: Not a directory
Jun 23 15:04:41 localhost automount[344]: automount version 57
Jun 23 15:04:41 localhost automount[344]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 23 15:04:41 localhost automount[344]: Can't mount map -static on /automount/static: Not a directory
Jun 23 20:29:49 localhost automount[341]: automount version 57
Jun 23 20:29:49 localhost automount[341]: Can't mount map -nsl on /Network: Not a directory
Jun 23 20:29:51 localhost automount[344]: automount version 57
Jun 23 20:29:51 localhost automount[344]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 23 20:29:51 localhost automount[344]: Can't mount map -static on /automount/static: Not a directory
Jun 24 15:47:02 localhost automount[341]: automount version 57
Jun 24 15:47:02 localhost automount[341]: Can't mount map -nsl on /Network: Not a directory
Jun 24 15:47:03 localhost automount[344]: automount version 57
Jun 24 15:47:03 localhost automount[344]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 24 15:47:03 localhost automount[344]: Can't mount map -static on /automount/static: Not a directory
Jun 24 17:53:46 localhost automount[342]: automount version 57
Jun 24 17:53:46 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 24 17:53:47 localhost automount[345]: automount version 57
Jun 24 17:53:48 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 24 17:53:48 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
Jun 24 22:56:53 localhost automount[342]: automount version 57
Jun 24 22:56:53 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 24 22:56:54 localhost automount[345]: automount version 57
Jun 24 22:56:54 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 24 22:56:54 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
Jun 25 12:33:34 localhost automount[341]: automount version 57
Jun 25 12:33:35 localhost automount[341]: Can't mount map -nsl on /Network: Not a directory
Jun 25 12:33:36 localhost automount[344]: automount version 57
Jun 25 12:33:36 localhost automount[344]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 25 12:33:36 localhost automount[344]: Can't mount map -static on /automount/static: Not a directory
Jun 25 16:17:20 localhost automount[342]: automount version 57
Jun 25 16:17:20 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 25 16:17:21 localhost automount[345]: automount version 57
Jun 25 16:17:21 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 25 16:17:21 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
Jun 25 21:00:40 localhost automount[342]: automount version 57
Jun 25 21:00:40 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 25 21:00:41 localhost automount[345]: automount version 57
Jun 25 21:00:41 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 25 21:00:41 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
Jun 26 12:17:08 localhost automount[342]: automount version 57
Jun 26 12:17:08 localhost automount[342]: Can't mount map -nsl on /Network: Not a directory
Jun 26 12:17:09 localhost automount[345]: automount version 57
Jun 26 12:17:09 localhost automount[345]: Can't mount map -fstab on /automount/Servers: Not a directory
Jun 26 12:17:09 localhost automount[345]: Can't mount map -static on /automount/static: Not a directory
aussiehoudini - Jun 26, 2005 - 9:16 am
image
image
Sorry, also ran that earlier command:
damian-heffernans-computer:~ damianheffernan$ df -h
filesystem size used avail capacity mounted on
/dev/disk0s3 74g 37g 37g 50% /
devfs 88k 88k 0b 100% /dev
fdesc 1.0k 1.0k 0b 100% /dev
512k 512k 0b 100% /.vol
/dev/disk1 500m 478m 21m 96% /volumes/damiandrive
damian-heffernans-computer:~ damianheffernan$
Vile - Jun 27, 2005 - 11:41 pm
image
image
Ok. Let's start by going to the root of the filesystem, and make a few changes:

$ cd /
$ mv Network Network.old
$ mkdir Network
$ chmod 755 Network

After doing that, restart your system, and check the syslog file again to see if automount will mount the Network volume.

If everything seems to be going all right with that volume, run the disk utility again to check permissions, and see if it still complains about /Network. If it doesn't, then we would need to do the same with the /automount/Servers, and /automount/static. Let's make sure everything is ok with Network first though.
aussiehoudini - Jun 28, 2005 - 3:10 am
image
image
hi,
just started to run the commands you said. Got ths error on the first one:
Damian-Heffernans-Computer:/ damianheffernan$ mv Network Network.old
mv: rename Network to Network.old: Operation not permitted
I ran disk utility and repaired permissions and still got the same error. Weird.

Vile - Jun 28, 2005 - 3:34 pm
image
image
ok. Sorry about that. Do you have the root user enabled?

If not, go to Applications > utilties > NetInfo Manager. Inside that, go to the Security menu, and choose Authenticate. After that, go back to the Security tab, and choose "Enable Root User". Go back to your terminal, and type:

$ su

This, puts you in "Super User" mode. Then run the commands again:

$ cd /
$ mv Network Network.old
$ mkdir Network
$ chmod 755 Network
aussiehoudini - Jun 29, 2005 - 3:13 am
image
image
Hi,
man you are working the mojo now! That seemed to work. I now get:
Damian-Heffernans-Computer:~ damianheffernan$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s3 74G 37G 37G 50% /
devfs 88K 88K 0B 100% /dev
fdesc 1.0K 1.0K 0B 100% /dev
512K 512K 0B 100% /.vol
automount -nsl [341] 0B 0B 0B 100% /Network

and the Network icon is back. But when I click on it the server icon os showing as a text doc and when i click on it it says no application is associated. So I assume we have to continue with doing that for servers etc as you said before. I also assume there are some different commands for that.
Thanks for your help so far, I feel hopeful for the first time ina while.
cheers
Damian
Vile - Jun 29, 2005 - 5:06 pm
image
image
Ok, now that the Network dir is out of the way, let's finish the rest.

$ su
$ cd /automount
$ mv Servers Servers.old
$ mkdir Servers
$ chmod 755 Servers
$ mv static static.old
$ mkdir static
$ chmod 755 static

That will setup your other two shares. After you reboot, check the system.log again for any automount error.
aussiehoudini - Jun 29, 2005 - 11:13 pm
image
image
Hi,
you'll probably think i am an idiot but I have the same problem as before:
Damian-Heffernans-Computer:/automount root# mv Servers Servers.old
mv: rename Servers to Servers.old: Operation not permitted
Damian-Heffernans-Computer:/automount root#

I followed the steps as before and authenticated and made sure root user was enabled but it is the same error.

Thanks
Damian
Vile - Jun 30, 2005 - 2:51 am
image
image
Did you make sure to run 'su' first to get superuser access?
aussiehoudini - Jun 30, 2005 - 5:29 am
image
image
Yep, here's the cut n paste:
Welcome to Darwin!
Damian-Heffernans-Computer:~ damianheffernan$ su
Password:
Damian-Heffernans-Computer:/Users/damianheffernan root# cd /automount
Damian-Heffernans-Computer:/automount root# mv Servers Servers.old
mv: rename Servers to Servers.old: Operation not permitted
Damian-Heffernans-Computer:/automount root# su
Damian-Heffernans-Computer:/automount root# mv Servers Severs.old
mv: rename Servers to Severs.old: Operation not permitted
Damian-Heffernans-Computer:/automount root# mv static static.old
mv: rename static to static.old: Operation not permitted
Damian-Heffernans-Computer:/automount root#
Vile - Jun 30, 2005 - 1:54 pm
image
image
Could you please show me the output of this command:

$ ls -l /automount/

Try this (after su):

$ cd /automount
$ chmod 755 Servers
$ chmod 755 static
$ mv Servers Servers.bak
$ mv static static.bak

If that works, then just move on to the last commands:

$ mkdir Servers
$ mkdir static
$ chmod 755 Servers
$ chmod 755 static
aussiehoudini - Jun 30, 2005 - 7:02 pm
image
image
hi,
didnt work unfortunately:
Last login: Fri Jul 1 08:43:51 on console
Welcome to Darwin!
Damian-Heffernans-Computer:~ damianheffernan$ su
Password:
Damian-Heffernans-Computer:/Users/damianheffernan root# cd /automount
Damian-Heffernans-Computer:/automount root# chmod 755 Servers
chmod: Servers: Operation not permitted
Damian-Heffernans-Computer:/automount root# ls -l /automount/
total 0
---------- 1 root wheel 0 1 Jan 1970 Servers
---------- 1 root wheel 0 1 Jan 1970 static
Vile - Jul 2, 2005 - 1:25 am
image
image
Ok. Now that is a problem. Not only are the dates just completely wrong, they don't have any permissions at all. If root can't change them, then something is holding them. We will have to try a different approach.

Reboot your system, and then while it's booting, hold 'Command s'. This will boot you into single user mode, a very minimal boot procedure. You will start out with a terminal, and try those commands again. Since those two files won't be used by anything, changing the permissions and such shouldn't be an issue. Just to recap, here are the commands to run:

$ cd /automount
$ mv Servers Servers.old
$ mkdir Servers
$ chmod 755 Servers
$ mv static static.old
$ mkdir static
$ chmod 755 static

If all goes well, type:

$ reboot
aussiehoudini - Jul 2, 2005 - 3:49 am
image
image
hi, tried that boot and it still wouldn't let me change them. It said operation not permitted. Do I have to do anything else on that boot. I tried the su command but it didn't ask for a password like before so I just assumed it didn't work. It simply wouldn't give me access to those files (said they were read only).
Damian
aussiehoudini - Jul 2, 2005 - 4:07 am
image
image
Hey,
I did a search and found the automount folder and went in and saw the servers and static things there. I noticed they had little locks on the icons. I got info and changed the owner to me (it said system) and then i was able to unlock them and change them from no access to read and write. After that I went to terminal and was able to run the commands. I hope I did they right thing. Running that command you asked for before now gives this:
Damian-Heffernans-Computer:~ damianheffernan$ ls -l /automount/
total 0
drwxr-xr-x 2 root admin 68 2 Jul 18:02 Servers
-rw------- 1 damianhe wheel 0 1 Jan 1970 Servers.old
drwxr-xr-x 2 root admin 68 2 Jul 18:03 static
-rw------- 1 damianhe wheel 0 1 Jan 1970 static.old
Damian-Heffernans-Computer:~ damianheffernan$

Cheers
Damian
Vile - Jul 2, 2005 - 11:12 am
image
image
Awesome! Looks like you are good to go. Is everything working? Does automount still complain in the system.log? You might want to check and repair permissions again as well.
aussiehoudini - Jul 4, 2005 - 7:25 am
image
image
I now have normal looking network and servers icons and after i repaired the permissions it's all honky dory. Thanks very much for all your help. I went deeper into the code parts of a Mac than I have ever been and after looking deep in there I don't think I'm in a hurry to go back. I'm just glad there's guys like you out there.
Cheers, and thanks again,
regards
Damian

IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.


Search Engine Optimization by vBSEO 3.3.0 RC1