Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!vsi1!ubvax!pyramid!leadsv!esl!dml From: dml@esl.com (Denis Lynch) Newsgroups: comp.sys.next Subject: Re: "Can not eject SOME disk" message -HELP!! Message-ID: Date: 26 Feb 91 00:18:29 GMT References: <1991Feb15.174213.58@hulaw1.harvard.edu> Sender: news@esl.ESL.COM Reply-To: dml@esl.com (Denis Lynch) Organization: ESL, Inc. Sunnyvale, CA Lines: 31 In-reply-to: roth2@hulaw1.harvard.edu's message of 15 Feb 91 22:42:13 GMT In article <1991Feb15.174213.58@hulaw1.harvard.edu> roth2@hulaw1.harvard.edu writes: About half the time I log out I get a message panel saying "Can't eject some disk" and I have no Idea why... I am booting of off a 210 MB external Quantum Pro Drive and am Using the 105MB internal that came with the station as a storage device. I'd guess that what's going on here is NeXT automounting. When you boot off the 210, the 105 isn't mounted. (Is it in your /private/etc/fstab on the 210?). Instead, it just sits there as an unmounted SCSI device. Then, when you log in, the automounter kicks in. It sees an unmounted device with media. This is just what you'd expect with an OD or floppy, but may not be just what you'd expect with a hard disk! Anyway, all SCSI devices and OD's work the same way: when you log in the automounter tries to mount them, and when you log out anything you mounted tries to get unmounted. This turns out to be really neat when you buy a new SCSI drive: you just hook it up, and the automounter discovers the uninitialized drive, just like it does for OD's. So, just like for OD's, it asks if you'd like it to be initialized. That's all you need to do to get your new drive up. Then, if you want to avoid roth's situation, add the hard disk to your fstab. But of course, only do this if you are planning on always having the drive there. (A good bet in his case, since it's the internal drive, but maybe not in all cases.) Hope that helps, --Denis Lynch, ESL Inc. Brought to you by Super Global Mega Corp .com