Shadow of a Former Volume!!!!!!!

[amnesiac1984]

Hi all.

I have this very strange problem with my DUAL 1ghz G4.

I used to have a volume named amnesiac that was my audio hard disk. Then, I got another new drive and I had, System, Audio, and Video volumes (all separate drives). Now, however i am back to two drive as my original 80gb died. So now I have System and Audio drives.

However, ever since i got rid of "Amnesiac" (I think I just renamed it in the finder) it has not dissappeared. It still appears as a mountpoint in /Volumes and no matter how many times I delete it, it comes back.

This has been the case across a couple of system reinstalls as well. Where is this rogue volume coming from and how can I get rid of it?

Thanks in advance

[amnesiac1984]

***!!Bump!!***

Nobody has any ideas? This problem is just too weird for my liking.

[gekko513]

I'm don't know if mounting works the same way as in Linux in any way, but you could try the command:

sudo umount /Volumes/Amnesiac

This would unmount the volume in Linux, but in Linux it would probably pop back next time you restart if it is included in /etc/fstab

I'm not on my Mac right now, so I can't check if there is a /etc/fstab in Mac OSX, but you could check it out and if you find a line with /Volumes/Amnesiac you could try to remove it.

Do this at your own risk though ;)

[cluthz]

I'm don't know if mounting works the same way as in Linux in any way, but you could try the command:

sudo umount /Volumes/Amnesiac

This would unmount the volume in Linux, but in Linux it would probably pop back next time you restart if it is included in /etc/fstab

I'm not on my Mac right now, so I can't check if there is a /etc/fstab in Mac OSX, but you could check it out and if you find a line with /Volumes/Amnesiac you could try to remove it.

Do this at your own risk though ;)

Yes there is a /etc/fstab in osx, but it does'nt look like the one in linux..
LittleAl:~ tsb$ cat /etc/fstab
# fs_spec fs_file fs_vfstype fs_mntops
#
# UUID=DF000C7E-AE0C-3B15-B730-DFD2EF15CB91 /export ufs ro
# UUID=FAB060E9-79F7-33FF-BE85-E1D3ABD3EDEA none hfs rw,noauto
# LABEL=This\040Is\040The\040Volume\040Name none msdos ro
LittleAl:~ tsb$



In tried the same on my G4 tower (which also runs Panther...)

[G4-400:/Volumes] tsb% cat /etc/fstab.hd
IGNORE THIS FILE.
This file does nothing, contains no useful data, and might go away in
future releases. Do not depend on this file or its contents.
[G4-400:/Volumes] tsb% cat /etc/fstab
cat: /etc/fstab: No such file or directory
[G4-400:/Volumes] tsb%

???

edit: The Powerbook also have the fstab.hd file


In /Volumes i still have all the names on evey volume on my machine, many of them are partitions that was on the disk berfore i have formatted it..

[G4-400:/Volumes] tsb% ls -la
total 40
drwxrwxrwt 13 root admin 442 29 Nov 21:09 .
drwxrwxr-t 57 root admin 1938 29 Nov 12:42 ..
-rwxrwxrwx 1 tsb wheel 6148 26 Oct 2003 .DS_Store
drwxrwxrwx 37 tsb unknown 1258 29 Nov 17:10 Annet
drwxr-xr-x 3 root wheel 102 14 Feb 2003 Games and fun
drwxr-xr-x 8 tsb admin 272 29 Nov 21:05 Mongojerry
drwxrwxrwx 18 per staff 612 29 Nov 17:42 Mp3
drwxr-xr-x 3 root wheel 102 14 Feb 2003 Os 9 Disk
drwxr-xr-x 69 tsb admin 2346 8 Aug 18:08 Os9 Disk
lrwxr-xr-x 1 root admin 1 29 Nov 12:42 OsX Disk -> /
drwxr-xr-x 21 tsb unknown 714 28 Nov 22:27 Spill
drwxr-xr-x 3 root wheel 102 14 Feb 2003 Video Disk
[G4-400:/Volumes] tsb%

[cluthz]

I'm still thinking of the reason of the /etc/fstab file on my powerbook, and the only reason I could find is that i'm also running GNOME on it (in x11), (but that also sounds strange, because this shouldn't be created by the window manager.???)

[gekko513]

Strange ... it is at least apparent that the Mac OS file system / Finder uses different mechanisms than Linux for managing mounting.

Actually running fsck if you haven't tried that already is a very good idea here, as it fixes many issues with corruption of the file system.

How to run FSCK

• Restart your Mac holding down "Command(the Apple key)+S" key to enter 'Single user mode'.
• Type "fsck -f", and hit return.
• Once complete type "reboot" and hit return to reboot you Mac back in to OS X as normal.

[cluthz]

Strange ... it is at least apparent that the Mac OS file system / Finder uses different mechanisms than Linux for managing mounting.

Actually running fsck if you haven't tried that already is a very good idea here, as it fixes many issues with corruption of the file system.

How to run FSCK

• Restart your Mac holding down "Command(the Apple key)+S" key to enter 'Single user mode'.
• Type "fsck -f", and hit return.
• Once complete type "reboot" and hit return to reboot you Mac back in to OS X as normal.


I'm running fsck about every month, and it has been there since i reformatted the drive.. I can't mount them, but they aren't making any troubles at all. (The macine never asks about them..)
I haven't tried to delete the files either...

I have to blank this machine and reinstall OSX, because I'm giving it to my brother as soon as i get my new iMac.