03-25-2011
/dev/sdb is the entire disk, you can't mount an entire disk unless the entire disk is just one partition.
What kind of RAID is it? Is it a software raid? You may not be able to mount it until you activate it with mdadm, in which case it'll become a new device, /dev/md*.
Maybe it's activated itself already. That would explain why it thinks it's busy -- it's been "eaten" by the software RAID driver. Try ls -l /dev/md* to see if you have any software RAID devices available. And df -h for good measure to see what devices you already have mounted where.
This User Gave Thanks to Corona688 For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi...
question is this:
How do I mount an LVD hotswap scsi drive in bay #2 on a netra using the mount command? volmgt doesn't seem to mount it and/or I don't know how to view the drives data if it's formatted which it may not be. This drive is not new out of the box so I'm not sure.
... (4 Replies)
Discussion started by: soulshaker
4 Replies
2. Solaris
Hi,
I set up a RAID 5 configuration and for some reason the volumes won't mount when the system boots. I have to manually mount them from the command line and all is fine.
Here's the vfstab entries:
#device device mount FS fsck mount mount
#to mount ... (2 Replies)
Discussion started by: rpollard001
2 Replies
3. UNIX for Advanced & Expert Users
I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access. # mount -t cifs //servername/sharename /mnt/temp -o password=""
mount error 13 = Permission denied Refer to the... (3 Replies)
Discussion started by: humbletech99
3 Replies
4. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
5. Solaris
Dear ALl,
I have a RAID 5 volume which is as below
d120 r 60GB c1t2d0s5 c1t3d0s5 c1t4d0s5 c1t5d0s5
d7 r 99GB c1t2d0s0 c1t3d0s0 c1t4d0s0 c1t5d0s0
d110 r 99GB c1t2d0s4 c1t3d0s4 c1t4d0s4 c1t5d0s4
d8 r 99GB c1t2d0s1 c1t3d0s1... (2 Replies)
Discussion started by: jegaraman
2 Replies
6. Solaris
Hello All,
I have read enough of texts on Raid 01 and Raid 10 on solaris :wall: . But no-where found a way to create them using SVM. Some one pls tell me how to do or Post some link if that helps.
TIA
Curious
solarister (1 Reply)
Discussion started by: Solarister
1 Replies
7. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
8. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
9. Red Hat
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
LEARN ABOUT DEBIAN
mount.crypt
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 for PLAIN (non-LUKS) volumes. pmt-ehd(8) defaults to
creating volumes with "aes-cbc-essiv:sha256" as a cipher.
crypto_name
Select the name for the crypto device (optional). This option is currently only usable with dm-crypt systems.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key. The special keyword "none" can be used to bypass decryption and pass the file con-
tents directly to libcryptsetup.
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.
hash The cryptsetup hash used for the encrypted volume. This defaults to no hashing, because pam_mount assumes EHD volumes with strong
and simple fskey generation.
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 2011-12-15 mount.crypt(8)