Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Feb 2000 21:01:35 -0800
From:      Chip <chip@wiegand.org>
To:        Greg Lehey <grog@lemis.com>
Cc:        seafug@dub.net, questions@FreeBSD.ORG
Subject:   Re: Adding another hd and can't mount it
Message-ID:  <00020221433500.01076@chip.homenet>
References:  <20000203124908.B18958@freebie.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 02 Feb 2000, Greg Lehey wrote:
> On Wednesday,  2 February 2000 at 18:02:36 -0800, Chip wrote:
> > On Wed, 02 Feb 2000, Greg Lehey wrote:
> >> On Tuesday,  1 February 2000 at 23:36:20 -0800, Chip wrote:
> >>> Hi,
> >>> I just installed a 2nd hd and ran sysinstall, got it partitioned and
> >>> the file system set up properly. When I try to mount it (as root)I
> >>> get the following message:
> >>> chip# mount /dev/wdc3 /home/2nddrive
> >>> mount: No such file or directory                (** yes there is **)
> >>
> >> No, there isn't.  The disk name is invalid.  I'm sure that 'ls -l
> >> /dev/wdc3' will tell you that it doesn't exist.
> >> <snip>
> >>> So then I try it a little differantly:
> >>> chip# mount /dev/wd3 /home/2nddrive
> >>> mount: /dev/wd3 on /usr/home/2nddrive: incorrect super block
> >>
> >> This message is correct:
> >>
> >>> 8 partitions:
> >>> #        size   offset    fstype   [fsize bsize bps/cpg]
> >>>   a:  3715136   409600    4.2BSD     1024  8192    16   # (Cyl.   25*- 256*)
> >>>   b:   409600        0      swap                        # (Cyl.    0 - 25*)
> >>>   c:  4124736        0    unused        0     0         # (Cyl.    0 - 256*)
> >>
> >> /dev/wd3 is effectively /dev/wd3s0c, which is not a file system.  It
> >> starts at the same place as the swap, so you were effectively trying
> >> to mount your swap partition.  You have your file system on partition
> >> a, so you should be saying
> >>
> >>  # mount /dev/wd3a /data
> >>
> >> (I've deliberately not written /home/2nddrive, because it's not a good
> >> idea to mount disks that far down).
> >
> > Thankyou, Greg, once again.
> > Now it works fine, I even got it in my fstab and an icon for mount/umount on
> > the desktop.
> 
> What do you need that for?
> 

I guess its just for easy access.  I don't remember the commands to do much at
the command line, my memory sucks at such stuff. I keep my books handy just
incase I need 'em. 

 > > Now to figure out the same for my winblows drive. :-)
> 
> Modify this /etc/fstab line to suit your Microsoft drive:
> 
> /dev/wd0s2c             /C:             msdos   ro              0       0
> 

I got that one figured out - its wd0s1, jeez, it took a lot of trial and error
to find the right one. Oh, well. I'm figuring this out little by little, but
its comin' along. The info in the startup screen doesn't seem to help much to
figure out how to designate the drive. Here is the part from running dmesg:

fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <FUJITSU M1636TAU>
wd0: 1225MB (2509920 sectors), 2490 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): <FUJITSU MPC3032AT>
wd1: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 1 (wd3): <ST32122A>
wd3: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
wdc1: unit 0 (atapi): <CD-ROM CDU55E/1.0u>, removable, accel, dma, iordy
acd0: drive speed 344KB/sec, 256KB cache
acd0: supported read types: CD-DA
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
scd0 not found at 0x230                             

> > You mention that it is not a good idea to not mount disks down the
> > directory tree, such as /mnt/whatever, but rather to just mount it
> > to a directory on the top level. Why difference would it make?
> 
> It's marginally faster to access (otherwise every access performs a
> couple of additional I/Os).  But the real reason is that if, for
> whatever reason, your first drive is down, you can't access the second
> one either.
> 
> > Isn't that what the mnt directory is for?
> 
> It's for one drive.  If you want to mount any more, and you can't
> think of a more imaginative name, use /mnt2, /mnt2, etc.  Anyway, even
> if you created subdirectories, they'd still me on the root file
> system.  Yours is on /usr, and it's accessed via a symlink.

I took your suggestion here also, made a directory at the top of the tree,
/2nddrive and /windrive. I probably don't need two separate directorys for
these but it just seemed logical to have one for each drive. Someday I may have
both mounted at the same time, for whatever reason. At least now I can easily
move my data files off the winblows drive to the fbsd drive, and reuse the
winblows drive as a bsd drive.

> 
> Greg
> --
> When replying to this message, please copy the original recipients.
> For more information, see http://www.lemis.com/questions.html
> Finger grog@lemis.com for PGP public key
> See complete headers for address and phone numbers

Chip


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00020221433500.01076>