Hi,
I am new to unix world. I am facing problem in mounting one of my partition of hard disk.

I have 2 hard disks in my system one each in primary and in secondary IDE. In primary's master hard disk, I have 2 operating system, Windows 2000 and Red Hat linux 9. In same hard disk i have one partition, windows refer to that as D: and Linux as hda5. its of FAT32 FS type. Its working fine from both operating system.

Now in another hard disk, I have solaris 10. This operating system also works fine, but i dont know what should be the name of my previous harddisk's that partition, linux referring as hda5? Solaris mounted c0d0s0 as "/" and c0d0s7 as /export/home. I dont know what the name should be for that partition. Can u guide me ?


regards,

Shaan

Hmm.. I don't know about solaris, but you could check what you see when you see your /proc/partitions (eg. "cat /proc/partitions"), or you can see what fdisk sees in your secondary ide master. That is, "fdisk -l /dev/hdc".

Let me see, It works for me or not ? By the way, does Solaris support vfat ????


Shaan

Solaris supports vfat since a while, but do things pretty differently than linux, so the device file naming, the /proc features and the "fdisk -l" do not apply here.

Solaris can access IDE primary partitions under an name like /dev/dsk/cXdYpZ where X is the controller number (0 or 1 usually), Y is the disk number (0 or 1) and Z is the partition number (1,2,3 or 4). Partition 0 is accessing the whole disk.
This is different from the slice naming scheme (like /dev/dsk/c0d0s0), which describes ufs (or BSD) sub partitioning.

As your VFAT file-system is on an extended partition, it should be mountable under something like c0d0p4:d

where the first two zeros should be adjusted to your configuration, the 4 should be set to the primary partition that was used to create the extended partitions (try 1,2,3 and 4) and "d" should be replaced by the name the partition (try c, d, e ... in doubt).
c means the primary partition, d the first extended etc...

The command to mount is sth like:

# mount -f pcfs /dev/dsk/c0d0p2:d /mnt

Hi jlliagre,
Thanks for ur reply. I have checked all the way but my problem still same.

1) There is /proc folder..... but there is no any partition folder in that. All there is 20-30 numeric folders.... like 1 2 3 .......

2) I am still not able to figure out what my partition name will be? I am try to explain u again, may be u can help me.

I have 2 IDE controller. Primary and Secondary. Each have master and slave.

Primary
Master: "Windows 2000" + "Required Partition" + "Linux Red hat 9"
Slave: Nothing......

Secondary
Master: Solaris 10
Slave: DVD ROM

I am enabling Solaris hard disk as first bootable, so I am reaching to Solaris where c0d0s0 is mounting to "/" and c0d0s7 to "export/home".

Now tell me what will be the name of that Primary-Master partition which is reffered by hda5 by linux.

3) I am trying
mount -F vfat /dev/dsk/cXdYpZ:N /export/hd5

Is it ok? "X, Y, Z, N", I am trying with different combinations.

Thanks for ur time.

regards,
Shaan

That's what I said, this partition folder is linux specific, and no such directory exists under Solaris.

From the rest of your posting, it looks like your primary master disk is c0d0

As linux says hda5, it means it is the first logical partition but doesn't tell from what extended partition was created the logical partition.

To find it, under linux, run:
# fdisk /dev/hda
then enter the "p" command (print partition table) and quit fdisk (q), dont mess your partition table !

It will tell you what is the extended partition name, if it is for example hda3:
/dev/hda3 218 789 4594590 5 Extended
then under solaris, it must be
c0d0p3:1 or c0d0p3:d (equivalent names)

hi,
I feel there is mistake in ur example, instead of 1 there shoud be 5.

well here is my linux's output. tell me what should be now my command.

====================================================
fdisk -l /dev/hda


Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3824 30716248+ 7 HPFS/NTFS
/dev/hda2 3825 9728 47423880 f Win95 Ext'd (LBA)
/dev/hda3 1 1 0 0 Empty
/dev/hda5 3825 7011 25599546 c Win95 FAT32 (LBA)
/dev/hda6 7012 7024 104391 83 Linux
/dev/hda7 7025 9474 19679593+ 83 Linux
/dev/hda8 9475 9728 2040223+ 82 Linux swap


=========================================================
fdisk -l /dev/hda5

Disk /dev/hda5: 26.2 GB, 26213935104 bytes
255 heads, 63 sectors/track, 3186 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda5p1 ? 116388 126889 84344761 69 Unknown
Partition 1 does not end on cylinder boundary.
/dev/hda5p2 ? 105915 222310 934940732+ 73 Unknown
Partition 2 does not end on cylinder boundary.
/dev/hda5p3 ? 1 1 0 74 Unknown
Partition 3 does not end on cylinder boundary.
/dev/hda5p4 179626 179629 26207+ 0 Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

=====================================================

Can u tell me the command now ?

Thanks,

regards,
Shaan

From your "fdisk -l" result, your extended partition is number 2.
Certainly not number 5 as you can only have 4 non logical partitions.

So it must be for your configuration:
/dev/dsk/c0d0p2:1

If it doesn't works, try:
/dev/dsk/c0d0p0:1

If it still fails, can you tell the error message displayed by the mount command ?

Hi,
I tried all the ways I could. Here is the result.



# mount -F pcfs /dev/dsk/c0d0p0:1 /export/hd5
mount: /dev/dsk/c0d0p0:1 is not a DOS filesystem.

# mount -F vfat /dev/dsk/c0d0p0:1 /export/hd5
mount: Operation not applicable to FSType vfat

# mount -F ufs /dev/dsk/c0d0p0:1 /export/hd5
mount: /dev/dsk/c0d0p0:1 or /export/hd5, no such file or directory

# mount -F autofs /dev/dsk/c0d0p0:1 /export/hd5
# cd /export/hd5
# ls -l
Total 0
# umount /dev/dsk/c0d0p0:1

# mount -F pcfs /dev/dsk/c0d0p2:1 /export/hd5
mount: /dev/dsk/c0d0p2:1 is not a DOS filesystem.

# mount -F vfat /dev/dsk/c0d0p2:1 /export/hd5
mount: Operation not applicable to FSType vfat

# mount -F ufs /dev/dsk/c0d0p2:1 /export/hd5
mount: /dev/dsk/c0d0p2:1 or /export/hd5, no such file or directory

# mount -F vfatfs /dev/dsk/c0d0p2:1 /export/hd5
mount: Operation not applicable to FSType vfatfs

# mount -F fatfs /dev/dsk/c0d0p2:1 /export/hd5
mount: Operation not applicable to FSType fatfs

# mount -F ufs /dev/dsk/c0d0p2:1 /export/hd5
mount: /dev/dsk/c0d0p2:1 or /export/hd5, no such file or directory


// one mount was sucess above, but it was showing no data inside.

guide me where I am going wrong.

Thanks,

Shaan

pcfs is the right and only name for fat filesystems under Solaris, no need to try any other (like vfat, ufs, vfatfs, autofs).

the rest is perplexing, some ideas to keep trying:

try: devfsadm -v just to be sure your h/w hasn't changed since o/s install.

run:

dd if=/dev/dsk/c0d0p2 bs=1024k | strings | more

and look if what is displayed looks like coming from you FAT partition.

try :d vs :1

perhaps one workaround would be to set your partition table in a way the fat one is on the third primary partition vs on a logical partition, this should be doable without actually moving data, but just changing the partition table, but don't forget to save your table if you try things in this area ...

I've just found a configuration similar to yours, the vfat partition was properly mounted with:

mount -F pcfs /dev/c0d0p0:c /mnt

So it looks like the driver find itself the extended and the logical partition to use inside it (first fat partition) when the letter are used to specify them.

I will try this as well. I tried devfsadm -v, but forgot to note down output for you. output was something like 5-6 lines of "removing cX1dY1pZ1.... removing cX2dY2pZ2...." I will get u exact output by evening.

and in ur last post u didnt mention "dsk" in path. "/dev/c0d0p0:c" Is it ok?

I found one GUI tool in solaris (Solaris management console "smc"), which suppose to give all the configuration and hardware details. But when i run it, i see GUI with so many options left side. All options ask for username password. I give my Root username password. Then I see some messages like: XYZ service require to gain access, I have option to grant them access or deny them. I tried in both ways. But in end always I receive "process is not able to connect to server. reason RMIERROR". Any idea, how to tackle this. May be from here I get some way to mount my hard disk.

Thanks.

regards,
Shaan

Never mind, if you saw only "removings", that won't help.
My mistake, "dsk" is needed.
What error message have you with that one "mount -F pcfs /dev/dsk/c0d0p0:c /mnt" ?

Did you try the "dd if=/dev/dsk/c0d0p2 bs=1024k | strings | more " and see if you FAT looks like to be here ?

What gives: "fdisk -RW - /dev/rdsk/c0d0p0" ?

Wooooooooooooooooooow I have done it !! (sorry "we have done it" )

Thanks jlliagre for ur support and guidance. instead c0d0p0, it must be c1d0p0:1 or c1d0p0:c ....... we were doing wrong going with c0. This hard disk was in another controller. I even told you that, but might be u didnt notice that. Well now its done. but still to be master in this, i have to see it closely. if we see logically, it really must be c0 not c1.... as its primary controller.... and while solaris installed on secondary controller. For solaris sliceses it names as c0.....c0d0s0,c0d0s7... its makes confusion.....

jlliagre can u guide me to some document online regarding same..... or any book....

thanks any way.

regards,
Shaan

I'm glad you finally succeeded mounting your partition !

You're right, I could have notice in your third posting that the solaris and the fat partition were in different controllers, but I didn't ...
Concerning the controller numbering, it is true Solaris an Linux are doing the things differently:
Linux scans the controllers at reboot, and name disks according to their physical location.
Solaris name each controller in the order it discover/use it, and stick with this name from that, so the first disk seen is always c0<sth>, the first disk on a different controller is c1<sth>, and so on. I think the goal is to ease the administrator's job, as their Solaris partition is (almost) always on c0 and they don't have to known the internal wiring.
That explains the discrepancy.

btw, now you master Solaris partitions scheme, do you know you can mount std Linux partitions, read-only, on Solaris 10 with this ? :
ftp://sun.drydog.com/pub/solaris/ext...laris10.tar.gz

To install it, you can skip the "make" step described in the README file, as the binary are already there.