06-14-2011
It attempts to mount the device /dev/dsk/c1t0d0s3 onto /mnt. You haven't specified any filesystem type, hopefully it can autodetect.
Only you can tell whether that's the correct disk or not unfortunately. And how to restore from tape depends on how you made the backup.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello!
When I use "sar -d" I get information about disk activities like:
sd0 ...
sd0,a ...
sd0,b ...
.....
sd22 ...
sd22,a ...
.....
How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies
2. Solaris
I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one.
This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies
3. Solaris
I use the following command dk -k and get the following output:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 1587078 56546 1482920 4% /
/dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr
/proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies
4. Solaris
Hi all,
I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below:
bash-3.00# cd /dev/dsk
bash-3.00# ls c3*
c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4
c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies
5. Solaris
Hi,
I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies
6. Solaris
I have a Solaris machine running OpenSolaris v5.11.
It came with a hard drive. It's called /dev/dsk/c4d0s0.
I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk.
How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies
7. Solaris
how to make less capacity on /dev/dsk/c1t0d0s5
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% /
/dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr
/dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies
8. Solaris
Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb.
Where is my space. Where was lost?
Could you please I need your opinions?
{root}/space>du -s -h *
308K alaerrm-jprof
1K argerela
20G baerckup_in
1.8G cererm
28M ecerlipselink
... (8 Replies)
Discussion started by: getrue
8 Replies
9. Solaris
Hello friends,
I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start.
The original mounting this, mirror in Raid 0:
c1t0d0s0 (master)... (10 Replies)
Discussion started by: grymorum
10 Replies
10. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
LEARN ABOUT SUSE
mount.crypto_luks
mount.crypt(8) pam_mount mount.crypt(8)
Name
mount.crypt - mount a dm-crypt encrypted volume
Syntax
mount.crypt [-nrv] [-o options] device directory
Options
-o options
Set further mount options. mount.crypt will take out its own options it recognizes and passes any remaining options on to the under-
lying mount program. See below for possible options.
-n Do not update /etc/mtab. Note that this makes it impossible to unmount the volume by naming the container - you will have to pass
the mountpoint to umount.crypt.
-r Set up the loop device (if necessary) and crypto device in read-only mode. (The mount itself will necessarily also be read-only.)
Note that doing a remount using `mount /mnt -o remount,rw` will not make the mount readwrite. The crypto and loop devices will have
to be disassociated first.
-v Turn on debugging and be a bit more verbose.
Mount options
cipher The cryptsetup cipher used for the encrypted volume. This option is mandatory. pmt-ehd(8) defaults to creating volumes with
"aes-cbc-essiv:sha256" as a cipher.
dm-timeout=seconds
Wait at most this many seconds for udev to create /dev/mapper/name after calling cryptsetup(8). The default value is 0 seconds.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key.
fsk_hash
The OpenSSL hash used for producing key and IV.
fstype The exact type of filesystem in the encrypted container. The default is to let the kernel autodetect.
keyfile
The path to the key file. This option is mandatory for "normal" crypto volumes and should not be used for LUKS volumes.
remount
Causes the filesystem to be remounted with new options. Note that mount.crypt cannot switch the underlying loop device (if applies)
or the crypto device between read-only and read-write once it is created; only the actual filesystem mount can be changed, with lim-
its. If the loop device is read-only, the crypto device will be read-only, and changing the mount to read-write is impossible. Sim-
ilarly, going from rw to ro will only mark the mount read-only, but not the crypto or loop device, thus making it impossible to set
the filesystem the crypto container is located on to read-only.
ro Same as the -r option.
verbose
Same as the -v option.
Obsolete mount options
This section is provided for reference.
loop This option used to set up a loop device, because cryptsetup(8) expects a block device. The option is ignored because mount.crypt
can figure this out on its own.
pam_mount 2008-10-08 mount.crypt(8)