Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Lable=foo is no good on mutliple drives' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Lable=foo is no good on mutliple drives
Authored by: Hes Nikke on Dec 10, '02 01:28:18AM

after much trial and error, i figured out that Lable=foo doesn't work when you have multiple Hard Drives that you want to mount around your filesystem. instaid you have to give the BSD disk name, so in my case Users wound up on /dev/disk2s9

my fstab looks like this:
/dev/disk2s9 /Users hfs rw 1 2

FYI in theory (i havn't tried it yet) you can use fdisk from the cli and repartition the drive to have swap partitions, then you'd put a line that looks like this in:

/dev/disk2s10 swap swap defaults 0 0



[ Reply to This | # ]
Lable=foo is no good on mutliple drives
Authored by: Hes Nikke on Dec 18, '02 03:04:00PM
hmmm... my fstab still isn't quite right, i'm going to have to peek in my rc file and see what needs to be tweeked... when i gave my computer a fresh boot, automountd mounted my Users partition in /Volumes/Users i had to do a
sudo umount -f /Volumes/Users; sudo mount -a
to get my users partition were it needed to go! (the -f switch is a forced, it was complaining that the device was busy - it couldn't be, it just booted! and the -a swtich on mount makes it mount everything in fstab, the way fstab says (useful when changing your fstab)) (did i just do an embeded parensathy? i'm pathetic) i'll let you know if/when i figure out what's up...

[ Reply to This | # ]
Lable=foo is no good on mutliple drives
Authored by: Hes Nikke on Dec 30, '02 01:55:42AM

ok, i have it craked...

the OS reorders my disks each time it boots! sometimes my Users is on /dev/disk2 (and it works) some times it's on /dev/disk1 (and it doesn't work)

i've teeked my netinfo entries, and when they are both in, it doesn't work, when one of them is in, and it's the right one (flip a coin) it's right, otherwise, it still doesn't work!

anyone know the rime and reason to how it designates what disk is what?



[ Reply to This | # ]
Drive detection goo
Authored by: Lanir on Jan 12, '03 06:00:43AM

I don't think I can answer this cleanly but I can tell you a little more about it and hopefully that'll lead you in the right direction. The problem you're running into is the mach kernel is detecting your devices in different orders when it starts up. I don't know jack about your configuration but some things you might want to try if you're on a desktop machine are to move the drives to different controllers if they're on the same one or put them on the same controller (same cable) if they're not already. If they're scsi drives they should be recognized in order of scsi ID. If they're ide they should be recognized in order of primary master, primary slave, secondary master, secondary slave. If that's not true in your case, experiment until you find what works.
If you're on a laptop... Good luck. I can't imagine too many reasons why a laptop would recognize a firewire or usb drive faster than a local disk.



[ Reply to This | # ]
Drive detection goo
Authored by: Hes Nikke on Mar 05, '03 01:52:58AM
the drive has always been master on the 4th controller. however the 2nd and 3rd controller maskerade as a SCSI controler so i _think_ it is pretending to be SCSI ID 2

the good news is that uppong applying the UUID to the partition, and FSTAB, it now works perfectly! woohoo!

---
vacuums do not suck. they merely provide an absence that allows other objects to take the place of what becomes absent.


[ Reply to This | # ]