10-09-2008
Quote:
Originally Posted by
otheus
Ouch!
Have you done ANYTHING to md0 or the underlying devices since then??
No, I haven't done anything to it.
Quote:
I believe that md0 uses an on-disk block for tracking meta information, but that essentially, the underlying partitions are simply kept in sync as normal filesystems are. Translation: you can directly mount the underlying file system. If they're not too out-of-sync, you can just fsck and mount. If the fsck fails at first because the md0 blasted it (unlikely), you can just use a backup superblock and specify that to fsck.
But how exactly do I mount lvm volumes without them being in a group? Does mounting do anything to the underlying devices as you ask?
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey peeps,
Here is somethin u might find interestin....
Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :)
I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies
2. AIX
Hi all,
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
3. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
4. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
5. Filesystems, Disks and Memory
Hi
I am new on your forum, because I need some help.
I have a server with debian and proxmox 2.
The HardDisk is broken.
I am in rescue mode, and I can't mount LVM partition to recover my backups.
What I've already done :
# fdisk -l
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255... (0 Replies)
Discussion started by: pppplu
0 Replies
6. UNIX for Advanced & Expert Users
Hi guys,
I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss.
I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates).
Basic system spec:
AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies
7. Linux
Hi all,
I been trying to recover a volume group of single PV.
vgcfgrestore output
# vgcfgrestore vgoraData
Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
Cannot restore Volume Group vgoraData with 1 PVs marked as missing.
Restore failed.
fdisk output
... (1 Reply)
Discussion started by: h@foorsa.biz
1 Replies
LEARN ABOUT SUSE
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. 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)