Date: Sat, 22 May 2004 01:14:26 +0930 From: Malcolm Kay <malcolm.kay@internode.on.net> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>, jason-dusek@uiowa.edu Cc: "Questions@BSD" <freebsd-questions@freebsd.org> Subject: Re: Broken Disk Message-ID: <200405220114.26231.malcolm.kay@internode.on.net> In-Reply-To: <20040521125607.GH31695@happy-idiot-talk.infracaninophile.co.uk> References: <40ADF7BB.8050403@cs.uiowa.edu> <20040521125607.GH31695@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 21 May 2004 22:26, Matthew Seaman wrote: > On Fri, May 21, 2004 at 07:36:11AM -0500, Jason Dusek wrote: > > I am trying to put a new disk on my system. I read the description of > > the process in FreeBSD Unleashed and apparently I misunderstood it, > > because I ended up installing a boot manager on the new disk. Now I can > > not mount it - I get error messages like: > > Presence of absence of a boot manager on the drive should make any > difference at all once the system is up and running. > > > # mount /dev/ad1e /mnt/backup > > operation not permitted > > /dev/ad1e is a very odd device name to be using. As far as I remember > that's a backwards compatability thing from changes that were made > somewhere around the FreeBSD-3.x timeframe. You probably want > /dev/ad1s1e > Yes, but at least upto FreeBSD-4.9 /dev/ad1e is understood and likely to be present. I believe it is the e-partition on the first BSD slice on the disk whatever slice that might be. The error message is not the one usually reported for a non-existant device; but when the operator has insufficient privilege. For the OP you (normally) need to be root to mount disks. Malcolm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405220114.26231.malcolm.kay>