Sponsored Content
Full Discussion: Mounting
Operating Systems BSD Mounting Post 302210654 by sniper007 on Tuesday 1st of July 2008 02:15:05 PM
Old 07-01-2008
Mounting

Hi

I mounted disk which have two partition C: , D: ( i am not sure if both partition have same file system) with this commad:

Code:
mount -t msdosfs /dev/ad2s1 /mnt/windows


but this is mounted only first partition with fat file system. ( in windows XP C: )

How can i mount another partition D: ?

this is fdisk for /dev/ad2


Code:
 [root@fbsd1 /mnt/windows 19:58:37] #  fdisk /dev/ad2
******* Working on device /dev/ad2 *******
parameters extracted from in-core disklabel are:
cylinders=77504 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=77504 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
    start 63, size 20487537 (10003 Meg), flag 80 (active)
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 1023/ head 239/ sector 63
The data for partition 2 is:
sysid 15 (0x0f),(Extended DOS (LBA))
    start 20487600, size 57607200 (28128 Meg), flag 0
        beg: cyl 1023/ head 239/ sector 63;
        end: cyl 1023/ head 239/ sector 63
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
 [root@fbsd1 /mnt/windows 20:04:41] #

using freebsd 6.3


tnx for help
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Mounting...?

Hi everyone, this is the first time I have ever properly used Linux - I run Red Hat Linux 8. I have two hardrives, my main 80gig, and my "extra" 15gig, I would like to be able to gain access to my 15gig and view the files. I know to view files on a floppy disk or a cd you need to mount the... (1 Reply)
Discussion started by: mo0ness
1 Replies

2. Solaris

Mounting root

Hello, How do I mount root on networked machines in Solaris 2.5 and 7? I did it before but I lost the clue. Was it something in vfstab? root=? I want to give some machines or users rootaccess on other machines on the lan. Do I specify users or machines at the root is option? Thanks in... (1 Reply)
Discussion started by: Albert
1 Replies

3. UNIX for Dummies Questions & Answers

Mounting cdrom on DG/UX

Hi, I'm looking to mount a cd on an old AViiON system we have. No one here really has any expertise with this platform so any help will be appreciated. I * think* the device is sd(apsc(pci(1),B,0,7),5,0), however I'm not sure at all. Thanks! (0 Replies)
Discussion started by: madesjardins
0 Replies

4. UNIX for Dummies Questions & Answers

Mounting help.

Hello, I am trying to mount a second scsi hard drive on a SCO box. (5.0.5.) And I can't figure out what the device file for it is so I can mount it. Can anyone help me? thanks. (1 Reply)
Discussion started by: iconn
1 Replies

5. UNIX for Dummies Questions & Answers

Mounting fs ext3

I'm trying to find a correct command that will mount a filesystem ext3 the device /dev/sda1 to mount point /mnt/usb but not allow any programs to run from it. I want to be honest as I've read the forum rules... This is a homework question BUT, i'm generally interested in the correct process and... (3 Replies)
Discussion started by: CasperQuiet
3 Replies

6. UNIX for Dummies Questions & Answers

Need help with mounting my USB

My previous post seems to be erased and I didn't get any help. I'm logged as root now but no mounting command seems to work, I've tried: Mount -t vfat /dev/sdc1 /mnt/USB Changing "sdc1" for hda1-7, and sdc1-7, and still nothing. Sometimes i get: "special device not found" and others "device... (4 Replies)
Discussion started by: Dax01
4 Replies

7. Filesystems, Disks and Memory

mounting

I generally use mount many times to mount an iso image or as a bind between directories or mounting a squash file system. Y does one require root permission to do a mount --bind between two of his own directories or just mount an iso/squash image in directory he owns? Also I wish mount had an... (0 Replies)
Discussion started by: bbala
0 Replies

8. Shell Programming and Scripting

Mounting

I have a big confusion in mounting........so please tell me whats the exact meaning of it nd do other os have this concept or not? (8 Replies)
Discussion started by: Mac91
8 Replies

9. HP-UX

Mounting LUN on HP 11.31

Hello, I want monting a LUN on a RX2660 I have created a LUN of 100Go with HP StorageWorks EVA and associated to my server. For the moment I see it with the command below but after i can't used it # ioscan -fnkC disk Class I H/W Path Driver S/W State H/W Type Description ... (10 Replies)
Discussion started by: letters
10 Replies
FDISK(8)						       System Administration							  FDISK(8)

NAME
fdisk - manipulate disk partition table SYNOPSIS
fdisk [-uc] [-b sectorsize] [-C cyls] [-H heads] [-S sects] device fdisk -l [-u] [device...] fdisk -s partition... fdisk -v fdisk -h DESCRIPTION
fdisk (in the first form of invocation) is a menu-driven program for creation and manipulation of partition tables. It understands DOS- type partition tables and BSD- or SUN-type disklabels. fdisk does not understand GUID partition tables (GPTs) and it is not designed for large partitions. In these cases, use the more advanced GNU parted(8). fdisk does not use DOS-compatible mode and cylinders as display units by default. The old deprecated DOS behavior can be enabled with the '-c=dos -u=cylinders' command-line options. Hard disks can be divided into one or more logical disks called partitions. This division is recorded in the partition table, found in sector 0 of the disk. (In the BSD world one talks about `disk slices' and a `disklabel'.) Linux needs at least one partition, namely for its root file system. It can use swap files and/or swap partitions, but the latter are more efficient. So, usually one will want a second Linux partition dedicated as swap partition. On Intel-compatible hardware, the BIOS that boots the system can often only access the first 1024 cylinders of the disk. For this reason people with large disks often create a third partition, just a few MB large, typically mounted on /boot, to store the kernel image and a few auxiliary files needed at boot time, so as to make sure that this stuff is accessible to the BIOS. There may be reasons of security, ease of administration and backup, or testing, to use more than the minimum number of partitions. DEVICES
The device is usually /dev/sda, /dev/sdb or so. A device name refers to the entire disk. Old systems without libata (a library used inside the Linux kernel to support ATA host controllers and devices) make a difference between IDE and SCSI disks. In such cases the device name will be /dev/hd* (IDE) or /dev/sd* (SCSI). The partition is a device name followed by a partition number. For example, /dev/sda1 is the first partition on the first hard disk in the system. See also Linux kernel documentation (the Documentation/devices.txt file). DISK LABELS
A BSD/SUN-type disklabel can describe 8 partitions, the third of which should be a `whole disk' partition. Do not start a partition that actually uses its first sector (like a swap partition) at cylinder 0, since that will destroy the disklabel. An IRIX/SGI-type disklabel can describe 16 partitions, the eleventh of which should be an entire `volume' partition, while the ninth should be labeled `volume header'. The volume header will also cover the partition table, i.e., it starts at block zero and extends by default over five cylinders. The remaining space in the volume header may be used by header directory entries. No partitions may overlap with the volume header. Also do not change its type or make some filesystem on it, since you will lose the partition table. Use this type of label only when working with Linux on IRIX/SGI machines or IRIX/SGI disks under Linux. A DOS-type partition table can describe an unlimited number of partitions. In sector 0 there is room for the description of 4 partitions (called `primary'). One of these may be an extended partition; this is a box holding logical partitions, with descriptors found in a linked list of sectors, each preceding the corresponding logical partitions. The four primary partitions, present or not, get numbers 1-4. Logical partitions start numbering from 5. In a DOS-type partition table the starting offset and the size of each partition is stored in two ways: as an absolute number of sectors (given in 32 bits), and as a Cylinders/Heads/Sectors triple (given in 10+8+6 bits). The former is OK -- with 512-byte sectors this will work up to 2 TB. The latter has two problems. First, these C/H/S fields can be filled only when the number of heads and the number of sectors per track are known. And second, even if we know what these numbers should be, the 24 bits that are available do not suffice. DOS uses C/H/S only, Windows uses both, Linux never uses C/H/S. If possible, fdisk will obtain the disk geometry automatically. This is not necessarily the physical disk geometry (indeed, modern disks do not really have anything like a physical geometry, certainly not something that can be described in simplistic Cylinders/Heads/Sectors form), but it is the disk geometry that MS-DOS uses for the partition table. Usually all goes well by default, and there are no problems if Linux is the only system on the disk. However, if the disk has to be shared with other operating systems, it is often a good idea to let an fdisk from another operating system make at least one partition. When Linux boots it looks at the partition table, and tries to deduce what (fake) geometry is required for good cooperation with other systems. Whenever a partition table is printed out, a consistency check is performed on the partition table entries. This check verifies that the physical and logical start and end points are identical, and that each partition starts and ends on a cylinder boundary (except for the first partition). Some versions of MS-DOS create a first partition which does not begin on a cylinder boundary, but on sector 2 of the first cylinder. Par- titions beginning in cylinder 1 cannot begin on a cylinder boundary, but this is unlikely to cause difficulty unless you have OS/2 on your machine. A sync() and an ioctl(BLKRRPART) (reread partition table from disk) are performed before exiting when the partition table has been updated. Long ago it used to be necessary to reboot after the use of fdisk. I do not think this is the case anymore -- indeed, rebooting too quickly might cause loss of not-yet-written data. Note that both the kernel and the disk hardware may buffer data. DOS 6.x WARNING The DOS 6.x FORMAT command looks for some information in the first sector of the data area of the partition, and treats this information as more reliable than the information in the partition table. DOS FORMAT expects DOS FDISK to clear the first 512 bytes of the data area of a partition whenever a size change occurs. DOS FORMAT will look at this extra information even if the /U flag is given -- we consider this a bug in DOS FORMAT and DOS FDISK. The bottom line is that if you use cfdisk or fdisk to change the size of a DOS partition table entry, then you must also use dd to zero the first 512 bytes of that partition before using DOS FORMAT to format the partition. For example, if you were using cfdisk to make a DOS partition table entry for /dev/sda1, then (after exiting fdisk or cfdisk and rebooting Linux so that the partition table information is valid) you would use the command "dd if=/dev/zero of=/dev/sda1 bs=512 count=1" to zero the first 512 bytes of the partition. BE EXTREMELY CAREFUL if you use the dd command, since a small typo can make all of the data on your disk useless. For best results, you should always use an OS-specific partition table program. For example, you should make DOS partitions with the DOS FDISK program and Linux partitions with the Linux fdisk or Linux cfdisk program. OPTIONS
-b sectorsize Specify the sector size of the disk. Valid values are 512, 1024, 2048 or 4096. (Recent kernels know the sector size. Use this only on old kernels or to override the kernel's ideas.) Since util-linux-2.17, fdisk differentiates between logical and physical sector size. This option changes both sector sizes to sectorsize. -c[=mode] Specify the compatibility mode, 'dos' or 'nondos'. The default is non-DOS mode. For backward compatibility, it is possible to use the option without the <mode> argument -- then the default is used. Note that the optional <mode> argument cannot be separated from the -c option by a space, the correct form is for example '-c=dos'. This option is DEPRECATED. -C cyls Specify the number of cylinders of the disk. I have no idea why anybody would want to do so. This option is DEPRECATED. -H heads Specify the number of heads of the disk. (Not the physical number, of course, but the number used for partition tables.) Reason- able values are 255 and 16. This option is DEPRECATED. -S sects Specify the number of sectors per track of the disk. (Not the physical number, of course, but the number used for partition tables.) A reasonable value is 63. This option is DEPRECATED. -h Print help and then exit. -l List the partition tables for the specified devices and then exit. If no devices are given, those mentioned in /proc/partitions (if that exists) are used. -s partition... Print the size (in blocks) of each given partition. -u[=unit] When listing partition tables, show sizes in 'sectors' or in 'cylinders'. The default is to show sizes in sectors. For backward compatibility, it is possible to use the option without the <units> argument -- then the default is used. Note that the optional <unit> argument cannot be separated from the -u option by a space, the correct form is for example '-u=cylinders'. -v Print version number of fdisk program and exit. ENVIRONMENT
FDISK_DEBUG=0xffff enables debug output SEE ALSO
cfdisk(8), sfdisk(8), mkfs(8), parted(8), partprobe(8), kpartx(8) AVAILABILITY
The fdisk command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux June 2012 FDISK(8)
All times are GMT -4. The time now is 04:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy