03-09-2016
Hi,
In Solaris, it would normally be /dev/dsk/c2t0d0 (Controller 2, Target 0, Disk 0) this is then followed by the Slice id - which can be 0 to 7, with 2 usually being the whole disk and called backup.
Here it would look like you will use /dev/dsk/c2t0d0s0
If you are looking at an other partition on the disk that is NFS exported or you want to mount it directly, there are several things to check.
It may show as being on an other controller.
It may need an other machine available to serve the mount.
Regards
Gull04
Last edited by gull04; 03-09-2016 at 11:40 AM..
Reason: More Info
5 More Discussions You Might Find Interesting
1. Solaris
Hello,
I use Sun Solaris 10 under a x86 computer, and I want to mount a Fat32 partition who are stored in the same disk with the UFS filesystem.
But, before mount this partition, I need to know is location in /dev/dsk
Because there are a lot of file "c0t0d0" etc..., and I didn't find my... (4 Replies)
Discussion started by: willits
4 Replies
2. Linux
We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
3. AIX
I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
4. Solaris
hi all
while formatting hard disk i am getting following error.
Partition 1 ends at 266338338
It must be between 34 and 143374704.
label error: EFI Labels do not support overlapping partitions
Partition 8 overlaps partition 1.
Warning: error writing EFI.
Label failed.
I have formatted the... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
5. Red Hat
Hi,
I need to mount the device from this device
# fdisk -l
.
.
.
Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes
255 heads, 63 sectors/track, 243197 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size... (0 Replies)
Discussion started by: justbow
0 Replies
LEARN ABOUT POSIX
installgrub
installgrub(1M) installgrub(1M)
NAME
installgrub - install GRUB in a disk partition or a floppy
SYNOPSIS
/sbin/installgrub [-fm] stage1 stage2 raw-device
The installgrub command is an -only program. GRUB stands for GRand Unified Bootloader.
installgrub installs GRUB stage 1 and stage 2 files on the boot area of a disk partition. If you specify the -m option, installgrub
installs the stage 1 file on the master boot sector of the disk.
The installgrub command accepts the following options:
-f
Suppresses interaction when overwriting the master boot sector.
-m
Installs GRUB stage1 on the master boot sector interactively.
The installgrub command accepts the following operands:
stage1
The name of the GRUB stage 1 file.
stage2
The name of the GRUB stage 2 file.
raw-device
The name of the device onto which GRUB code is to be installed. It must be a character device that is readable and writable. For disk
devices, specify the slice where the GRUB menu file is located. (For Solaris it is the root slice.) For a floppy disk, it is
/dev/rdiskette.
Example 1: Installing GRUB on a Hard Disk Slice
The following command installs GRUB on a system where the root slice is c0d0s0:
example# /sbin/installgrub /boot/grub/stage1
/boot/grub/stage2 /dev/rdsk/c0d0s0
Example 2: Installing GRUB on a Floppy
The following command installs GRUB on a formatted floppy:
example# mount -F pcfs /dev/diskette /mnt
# mkdir -p /mnt/boot/grub
# cp /boot/grub/* /mnt/boot/grub
# umount /mnt
# cd /boot/grub
# /sbin/installgrub stage1 stage2 /dev/rdiskette
/boot/grub
Directory where GRUB files reside.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
boot(1M), fdisk(1M), fmthard(1M), kernel(1M), attributes(5)
Installing GRUB on the master boot sector (-m option) overrides any boot manager currently installed on the machine. The system will always
boot the GRUB in the Solaris partition regardless of which fdisk partition is active.
24 May 2005 installgrub(1M)