Logical volume inactive at boot

Hi,
I'm using 2x 2tb disks in a raid1 configuration with mdadm. On top of that i've got lvm, with basicly one vg and lv, which i mount on /home at boot. Since I updated yesterday my lv won't be active at boot, resulting that /home is not mounted.
When I issue a vgchange -ay and a lvchange -ay /dev/array/data it's active and i can mount it again. But after a reboot it's gone again .
I suspect that my mdadm array got a new name resulting in this unwanted behaviour. Any tips how to resolve this problem?
Edit: The lvm2 hook is active.
Last edited by evert_ (2011-05-16 20:18:12)

The megathread is here: https://bbs.archlinux.org/viewtopic.php?id=158012&p=1
The mdadm_udev hook thing is documented on the mkinitcpio page.
Glad you got it sorted. Please remember to mark your thread as [Solved] by editing your first post and adding it ot the title.

Similar Messages

Corrupt Root Logical Volume

Hey Folks,
I'm having a bit of a problem with the Root Logical Volume / Volume Group on one of our Servers (OEL 4 - Release 7 running on Oracle VM 2.1.2). One of our SAN Administrators pulled the disk from the system by accident, and has since re-presented it to the server but now when it boots I'm getting errors on the Root Logical Volume.
It boots in to maintenance mode and I've tried fsck'ing the root file system but it gives errors about the first SuperBlock...
"Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00
Could this be a zero-length partition? "
I've tried specifying the next SuperBlock and the e2fsck runs through repairing corrupt inodes, but it doesn't make a difference, I still get errors on bootup. Any other LVM commands give an error to say that 'File Descriptor XX not closed'.
I've booted from an OS DVD in to Rescue Mode and it mounts the Volume Groups and I can still see the files are present.
Does anyone know of anything I can do? Are their commands I can run in Rescue Mode to fix corrupted file systems? I'm off to do some googling on the subject but if anyone could offer advice it would be much appreciated.
Thanks
James

Please mind any corruptions inside the filesystem can occur. You should check that in two stages:
-Non-oracle
All operating system tools use normal, buffered IO. (that I am aware of, please correct me if somebody has seen something different)
This means that any file modifications (user-imposed, thus modified configuration files, and system imposed, like installing binaries) are done in memory, and eventually flushed to disk (by a process called 'pdflush'). When a disk is pulled, there is a chance not all modifications are already flushed to disk, thus will be corrupt.
-Oracle
This is the same for the oracle database files, with the exception of databases using DIO, direct IO. Direct IO is enabled if the database parameter 'filesystemio_options' is set to 'direct' or 'setall'. Direct IO bypasses the operating system buffercache and does IO (reading and writing) directly from the blockdevice, instead of asking the operating system for the block in normal mode, which caches the requested block(s) in the operating system/linux buffercache.
That is why normal/cached IO also is said to do 'double buffering', because there are two cache's ('buffers') involved.
-Okay, but it's journalled, isn't it?
Eh, yes.
But it depends on the type of journalling. Journalling might not be what you expect it to be.
Most filesystems, including NTFS and default ext3, only journal metadata transactions. Metadata transactions mean that only changes to the structure of the filesystem are journalled, not data-transactions.
Please mind that it is possible for ext3 to journal all modifications instead of only meta-data with the 'data=journal' mount option.

Logical Volume Group and Logical Partition not matching up in free space

I was dual booting Windows 7 and Mountain Lion. Through Disk Utility, I removed the Windows 7 Partition and expanded the HFS+ partition to encompass the entire hard drive. However, the Logical Volume Group does not think that I have that extra free space. The main problem is that I cannot resize my partition. I am wanting to dual boot Ubuntu with this. Any ideas? Any help is appreciated. I will post some screenshots with the details. Furthermore, here are some terminal commands I ran: /dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 249.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS MAC OS X *248.9 GB disk1 Filesystem 1024-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 243031288 153028624 89746664 64% 38321154 22436666 63% /
devfs 189 189 0 100% 655 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 52A4D825-B134-4C33-AC8B-39A02BA30522
=========================================================
Name: MAC OS X
Size: 249199587328 B (249.2 GB)
Free Space: 16777216 B (16.8 MB)
|
+-< Physical Volume 6D7A0A36-1D86-4A30-8EB5-755D375369D9
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 249199587328 B (249.2 GB)
|
+-> Logical Volume Family FDC4568F-4E25-46AB-885A-CBA6287309B6
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: Converting
Conversion Direction: backward
Has Encrypted Extents: Yes
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume BB2662B7-58F3-401C-B889-F264D79E68B4
Disk: disk1
Status: Online
Size (Total): 248864038912 B (248.9 GB)
Size (Converted): 130367356928 B (130.4 GB)
Revertible: Yes (unlock and decryption required)
LV Name: MAC OS X
Volume Name: MAC OS X
Content Hint: Apple_HFS

Here is another try via the command line:
dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
Started CoreStorage operation
Checking file system
Performing live verification
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Incorrect block count for file 2012.12.11.asl
(It should be 390 instead of 195)
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Invalid volume free block count
(It should be 21713521 instead of 21713716)
The volume MAC OS X was found corrupt and needs to be repaired
Error: -69845: File system verify or repair failed

Logical Volume Manager

I am planning on installing Arch on a laptop soon. I have played with it in VirtualBox on a separate computer, and I am going to hope that it works with my touchpad / wireless mouse.
I might butcher some jargon in this, but this is how I think LVMs work, and I would like to make sure.
I am going to make partitions for boot, swap, /, and /home.
I know boot only needs to be around 100MB, swap is twice the RAM -- and I saw in another thread, / around 10-15GB -- and /home is the rest.
However, I read about installing on an LVM and it is easy to re-size partitions if needed.
I only have 1 HD, and I'm mostly doing this because while I do have room to have too much space on /, if I end up only using around 4GB, I would like to have that 11GB on my /home for music or videos.
So I think that means I would have something like this:
sda1: boot, around 100MB.
sda2: LVM, which contains swap, /, and /home.
pvcreate /dev/sda2 creates the physical volume on the LVM, allowing me to partition it.
After that, this is where I am confused.
The Arch Wiki says:
Create Volume group(s)
Next step is to create a volume group on this physical volumes. First you need to create a volume group on one of the new partitions and then add to it all other physical volumes you want to have in it:
# vgcreate VolGroup00 /dev/sda2
# vgextend VolGroup00 /dev/sdb1
Also you can use any other name you like instead of VolGroup00 for a volume group when creating it. You can track how your volume group grows with:
Can I skip this since I have only 1 HD? I guess that /dev/sdb1 is the LVM from the other harddrive?
I suppose I would have to do vgcreate VolGroup00 /dev/sda2 just to create the volume goup, though. Is this correct?
After this step, I am pretty much lost. Here's what the wiki says, and how I am interpreting it...
# lvcreate -L 10G VolGroup00 -n lvolhome
This will create a logical volume that you can access later with /dev/mapper/Volgroup00-lvolhome or /dev/VolGroup00/lvolhome. Same as with the volume groups you can use any name you want for your logical volume when creating it.
So later, I would turn this into my home partition during the Arch installation? I would create a lvolswap, and a lvolroot?
Then, during the installation process, I would format them to ext3, and mount them as /home, /, and then select lvolswap as my swap partition?
That's about it for now, I guess.
Last edited by COMMUNISTCHINA (2008-08-15 21:53:41)

COMMUNISTCHINA wrote:
Berticus wrote:
COMMUNISTCHINA wrote:I dunno. I tried using LVM on a virtualbox and I keep getting a kernel panic. I followed the Wiki.
If I put GRUB on /boot, it doesn't work, but I got it to work if I installed it on the / LV.
odd, to my knowledge grub can't be on an LVM. why not install grub on MBR?
I actually figured this out maybe an hour ago.
I changed my GRUB configuration file, but since it's in a virtualbox, out of habit I type arch root=/dev/sda3 on startup, but I needed to type root=/dev/VG00/lvolroot. I had grub on /boot (not on the LVM), but when I was trying to boot, I told it to go to the wrong place for root. I could probably unmount the .iso for the vbox, but whatever.
I will read a little more about RAID.
If I end up figuring out how to do it, would I need my external hooked up to it all the time? I have tote the laptop around, and I wouldn't want the external mucking up the portability.
I wasn't aware you were on a laptop. In that case, a file server would do you best. But cheapest solution would be just to stick with an external hard drive and not RAID.

3TB Fusion & logical volume group

I'm in the process of fully reinstalling Mavericks - erasing my internal drive and paring my system way down, to resolve some long lingering issues.
Disk Utility shows the recovery partition as separate (I've booted from it) - but when I went to erase the default Macintosh HD partition I was unable to repartition it as a single partition - it was grayed out - and the TYPE was/is logical volume group - where I was expecting to see GUID. All I could do at that point was ERASE... which I did - so it remains a logical volume group -
I'm unsure if, because of the Fusion drive, this is how they come from Apple - or the previous owner messed with it and trouble could loom wth this setup.
It's a Late 2012 iMac with stock 3TB Fusion Drive.
I'm in the process of reinstalling Mavericks from the Recovery (Internet recovery I'm guessing since it's taking 2 hours). I'm not near an Apple Store unfortunately though do have extended 3 year warranty.
Is it OK to leave the main Macintosh HD as "logical volume group"?????

Yes. That's the technical name for what Apple marketing refers to as a "Fusion Drive." Don't change it.

OSX Yosemite Logical Volume Group - FIX!

Hey guys,
For anyone wondering or concerned about why, when entering Disk Utility, the SSD name has been changed and you now see Macintosh HD and Macintosh HD below. The one above is listed as a Logical Volume Group with an "online" status while the one below that is your physical HDD (so normal as with previous OS's.
I must note that I do not have any recovery partition when holding option when booting (after installing straight onto Mavericks, nor when making my own bootable copy).
However, I did find a way to fix the Hard Drive name issue and revert it back to original format (I did find this fix online, and it has worked for me).
I included pictures below as well.
First one shows original Yosemite SSD name change (from Apple SSD to Macintosh HD with 18.9MB available)
Second shows your normal HHD name unchanged.
Go to Terminal and enter the following:
diskutil cs list
then you will see a bunch of volumes jump up
enter: diskutil cs revert "UUID"
under "UUID", enter the the Logical Volume code number without brackets.
Do not copy and paste it from terminal into your new terminal line. Write it out.
Hit enter and it will ask to reboot your Mac.
Once, rebooted, your old SSD/HDD name with reappear as in Mavericks.
My entire terminal line is shown in the picture attached.
Either way (SSD name changed or reverted) did not changed how the system performed. Everything is running as it should.
Final result shown in last picture!
Hopefully this is just a bug that Apple will fix.
Please ignore the DiskMaker drive (I was making a bootable copy on my external!!)

Thanks for the tip. I see its a common trouble. But i stuck a problem that cannot be solved with this method cause i dont have revertable logic volume.
SO i cannot install system now. There's no visible disk any more.

I need to sudo cs delete an encrypted hard drive but get an error "Not a valid CoreStorage Logical Volume Group UUID"

Ok so I encrypted an internal HDD with DOE compliant encryption, and forgot the password. I am not using a typical mac bootloader so apple C when its booting will not work to delete it before its mounted. I have to do it through the terminal. The drive I want to delete is HDD2. Here is the screen capture of running diskutil cs list in terminal.
Then I disconnected everything to avoid problems, leaving my encrypted HDD only, copied the UUID, it's in this format:
diskutil cs delete XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
But I am unsure which group or physical UUID I need to use, there are three associated with HDD2, logical volume group, physical volume and logical volume family. I thought before pressing enter I better ask first ... as I tried it on the physical volume first and I got the error in the title so dont want to start guessing what do to.
Thanks

Is it not good form for members to advise about using the console? Surely some members are knowledgeable enough to tell me the answer to this .... I know it's easy to bork your system up totally with the console but I'm desparate, my main drive has 1GB free!

RAID on LVM logical volumes

Hey,
i've got a 1T and a 500G hard drive in my workstation. The 500G drive is my media disk. I initialized a software RAID-1 with one missing drive on a 500G logical volume on the 1T disk. After formatting and copying all the data from the media disk over to the new raid partition, I added the old 500G partition to the RAID.
After rebooting my machine, the RAID was in inactive state and hence the filesystem could not be mounted.
I found out, that in /etc/rc.sysinit the search for software RAID arrays is performed before the search for LVM volume groups. I started switching the RAID and LVM sections but after reboot nothing changed. I presume it's caused by the lv devices missing in /proc/partitions, which is used by md to scan for raid members by default.
I decided to add some lines to /etc/rc.local (also my RAID device is /dev/md127 Oo):
mdadm --stop /dev/md127
mdadm --assemble /dev/md127 /dev/vg00/raid-data /dev/sdb1
mount /mnt/raid
It works now, but it is not a clean solution.
How is it supposed to do RAID on top of LVM logical volumes in Arch Linux? Are there any alternative ideas of solutions to this problem (sure there are)?
Thanks in advance.

delcypher wrote:
Hi I've been looking into backing up one of my LVM logical volumes and I came across this (http://www.novell.com/coolsolutions/appnote/19386.html) article.
I'm a little confused by it as it states that "Nice work, your logical volume is now fault tolerant!".
Are you sure that's the article? I can't find anything on that page about "nice work" or "fault tolerant"...?
delcypher wrote:My concern is that because my volumegroup spans across two drives if anyone of them fails I will loose all may data.
Correct.
delcypher wrote:Is there any setup I can do by which I can have a perfect mirror of my volumegroup so that if one of my drives fail I still have a perfectly function volumegroup.
Use 2 disks to create a RAID-1 array, then use that as your PV.
sda1 + sdb1 = md0 => pv
delcypher wrote:I understand linux supports software raid but would I need two drives identically sized (1TB) or can I just have one drive (i.e. 2TB) that is a mirror of my volumegroup?
You can use 2 partitions on the same disk to create a RAID array, but that defeats the whole purpose of RAID.
It sounds like you're merging the meanings of 'redundant' and 'backup' -- they are distinct things, so you need to decide if you want redundancy or backup. Or both ideally.

Extending an LVM Logical Volume to Another Disk

I have read the article in the wiki and also this guide since my drives are encrypted. I have already set up arch on one drive with LVM on top of an encrypted volume (following the linked guide strictly with exceptions on the cipher and the partitioning). So far everything works very well but I'm only halfway where I want to end up. Additional to the one HDD I want to use two more, all of them encrypted (no problem here) and one logical volume spread across all three drives (problem be here).
So, to clarify, on /dev/sda I have two partitions, /boot (unencrypted, 130 MB) and /dev/sda2 (encrypted, ~2TB) on which the LVM volumes are.
/dev/sda2 is added to vgroup and has several logical volumes of which /home is the largest.
On the other hand I have /dev/sdb and /dev/sdc. Both should only contain one encrypted partition and extend /home. That is why I chose LVM in the first place.
I started with /dev/sdc since all the data on it has been backed up already. The entire drive is now one big encrypted partition called /dev/sdc1. I mounted it with sudo cryptsetup luksOpen /dev/sdc1 lvm. And here I am stuck.
1) First of all I'm not entirely clear on the last part "lvm" of that command, I initially thought it would be the name this partition would be mounted under but in the guide I took this from it is not explained and I want to be extra careful here because I have a lot of data on /dev/sda2 that is not backed up and I don't want to accidentally erase the logical volumes I already have.
2) I guess the next part would be creating a physical volume on the mounted partition via lvm pvcreate /dev/mapper/lvm but again I want to be extra clear on this, I really do not want to temper with the volumes I already have unless I know exactly what effects it will have. If I would mount the encrypted partition with sudo cryptsetup luksOpen /dev/sdc1 aaa would I then have to create the physical volume with lvm pvcreate /dev/mapper/aaa? Because I already used lvm when I created all the volumes on the first drive (sda) and I don't know if they are still mounted under the same name (after many reboots and setting up the arch which I am currently using) in which case I might be in danger of overwriting something?
3) From what I have read so far I could extend /home now with lvextend -l +100%FREE vgroup/home, is that correct? After that I would only have to extend the file system (ext4) on /home and it would be done?
I hope it is clear what I am trying to do, if not please do ask. Thanks in advance for reading all of this.

Turns out this is not quite over yet. After successfully dealing with LVM I was about to reboot when something occurred to me: The second HDD (sdc1) will not be decrypted at boot and I have no idea what would happen if LVM tries to mount a volume that is spread across two disks of which one is not available.
So I searched for some time and everything I could find was this thread. Well, he is talking about altering the encrypt hook and generate a new initramfs to be able to enter more than one cryptdevice in grub. I have never dealt with hooks before and never got my hands on bash script like this. Now my options are pretty weak: I could do what he describes although I have no idea how it works or I could revert all the changes to LVM. Naturally I chose option number one, parsed the hook, edited the menu.lst, rebooted and "Waiting 10 seconds for device /dev/sda2".
So yeah it's my fault for trying something I have no clue about.
I tried to access the volumes from the live cd, but even though I decrypted the drives and loaded up lvm with vgchange -a -y I can not access the logical volumes. I naively tried to access the files such as menu.lst but I can't get there. Probably because I just lack the knowledge how to do that. But even if I would be able to access the files, could I build the hooks of my system from within the live cd?
Last edited by venehan_snakes (2011-10-18 16:49:48)

Logical Volumes Not Creating w lvcreate? Install??

After following the arch raid guide i have gotten all tge way down to creating logical volumes and i get this
lvcreate -L 20G VolGroupArray -n lvroot
/dev/VolGroupArray/lvroot: not found: device not cleared
Aborting. Failed to wipe start of new LV.
device-mapper: remove ioctl on failed: Device or resource busy
here is vgdisplay
-- Volume group ---
VG Name VolGroupArray
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 17
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 97.75 GiB
PE Size 4.00 MiB
Total PE 25024
Alloc PE / Size 0 / 0
Free PE / Size 25024 / 97.75 GiB
VG UUID rP0ooH-VdCy-fMZM-sB0g-90zi-Gv2o-gBZWC1
pls help i am now stuck

mattbarszcz wrote:So I went back to the live cd, I ran efibootmgr with no arguments, and sure enough there was only 1 entry for the Windows Boot Manager. It seems that efibootmgr commands don't seem to take effect.
Because of bugs in efibootmgr and/or EFI implementations, efibootmgr doesn't always work. Using bcfg from an EFI shell or bcdedit in Windows can be more effective on some systems. That said, if efibootmgr worked for you before, I'm not sure why it would stop working, or why an existing entry might disappear. (Some EFIs do delete entries that they detect are no longer valid. This shouldn't have happened with a whole-disk dd copy, but if you duplicated the partition table and then used dd to copy partitions, it might well have happened to you. I suppose it's conceivable that the firmware detected the change from one physical disk to another, too, and deleted the original entry because of that change.)
I referenced the rEFInd page here: http://www.rodsbooks.com/refind/installing.html#windows and followed the procedure to install an entry for rEFInd from Windows. I was able to add an entry no problem through windows.
Does anyone have any suggestions as to why this doesn't work? Nothing has changed about the system other than the disk.
It's unclear from your post whether the entry you created in Windows now works. If it does, then don't sweat it; just keep using that entry, and if you need to make changes and efibootmgr doesn't work in the future, plan to use either Windows or the bcfg command from an EFI version 2 shell.

Logical volume activation during bootup shows "Maps lock" errors

this started happening sometime after the creation of two lvm snapshots (including 1 root volume snapshot which, as i have since read, may be an issue) but this has never happened to me before in conjunction with snapshotting. the following outputs before the system successfully finishes booting:
:: Running Hook [lvm2]
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
Scanning logical volumes...
Reading all physical volumes. This may take a while...
Found volume group "a1vg1" using metadata type lvm2
Activating logical volumes...
Internal error: Maps lock 14528512 < unlock 14532608
Internal error: Maps lock 14548992 < unlock 14553088
this is annoying but beyond that seems innocuous enough. the system is stable. can anyone tell me what this error means or refer me to the proper documentation?
TIA

I have also these messages. It had gone away, but few days ago it came back ...

Creating Logical Volume during Oracle VM installation

Hello,
I am trying to install Oracle VM Server on a machine with 2 TB hard-disk. There are 2 disks each with 1 TB capacity.
During Oracle VM Server 2.2.2 installation, if you go with default partitions, layout looks like this
/dev/sda
   sda1          101M ext3        /boot
   sda2       952737M ocfs2       /OVS
   sda3         1027M swap
/dev/sdb
   sdb1         3074M ext3        /
   Free space 950792M Free SpaceIdeally I would like to give everything except what is needed by */ (root), /boot* and swap to */OVS*.
So from the layout above, I also want to give Free Space to */OVS*.
This excerpt talks about Logical Volume Creation during Oracle VM installation.
During the Oracle VM Server installation, press Alt+F2 to use the terminal, and run the lvm command. When you have finished creating the LVM configuration, press Alt+F1 to return to the Oracle VM Server installation.
But I couldn't figure out how to do this? Can anyone give me exact steps to achieve what I am trying to achieve.
regards, Yora

Hi again
It seems I downloaded by mistake the Oracle VM Server 3.0.1 Source for x86_64 (64 bit).
I should have downloaded the Oracle VM Server 3.0.1 for x86_64 (64 bit).
Now I can get started
Rudi

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

Mavericks FileVault 2 Issue - Logical Volume Disappeared

I have a drive out of a damaged, late 2011 MacBook Pro that was FV2 encrypted. I have the password and key and used them to decrypt the drive to recover data. This was done from Disk Utility and appeared to be successful until I rebooted. This was done firewire connected to my 2011 MacBook Pro running Mavericks. The end result is the drive appearing in RED/inaccessible in disk utility and in the running "diskutil cs list" shows the Logical Volume Group "offline" and the Physical Volume "online". Oddly the Logical Volume itself is gone. Below is some output from some diskutil commands:
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         499.2 GB   disk1s2
   3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group FD6BEF04-E4EB-48F1-9E4C-5911245D0273
    =========================================================
    Name:         Macintosh HD
    Status:       Offline
    Size:         499248103424 B (499.2 GB)
    Free Space:   498929328128 B (498.9 GB)
    |
    +-< Physical Volume 2BDA1A0F-4404-43F1-B183-D4DB23FBF669
        Index:    0
        Disk:     disk1s2
        Status:   Online
        Size:     499248103424 B (499.2 GB)
Any ideas or guidance on recovering data from this drive would be greatly appreciated.
Thank you

I'm having a similar problem with FireVault and a USB drive. I formatted and encrypted a USB drive using Disk Utility. I set the password and saved it on my home computer's keychain. Now I'm having problems with FV recognizing the password on other computers.
This morning I mounted the drive and entered the PW with no problem on a computer. I ejected the disk and later remounted it on the same computer. When I was prompted to enter the password, FV paused and grayed out for about 30 sec then rejected the password. If I do the same thing and enter any other password, it is rejected immediately. Not sure what is going on. I've tried it on several computers and it does the same thing with the password.
I can probably reset the password on my home computer, but worried this will be an ongoing issue. Any advice? Has anyone else encountered this?
thanks
Adam

[SOLVED]using dd to make image backup of logical volume?

I recently got my Ocz Revodrive working under Archlinux by creating logical volumes on it which worked out great, i also got openbox configured to my liking but i want to make an image back up of my Revodrives logical volumes into image files to restore for later use. I was reading the disk cloning wiki about the dd command and just wanted to double check that the dd command below would work ok?
Once i boot into the Arch live usb, and run the following commands it should create an image file on the hard drive mounted under /mnt/backupdata ? Sorry for the straight forward question, i just want to make sure i have the right command before i back up data i dont have a copy of.
dd if=/dev/mapper/VolGroupArray-lvroot of=/mnt/backupdata/test.img bs=16m
dd if=/dev/mapper/VolGroupArray-lvhome of=/mnt/backupdata/test.img bs=16m
Also anyone have any feedback on what blocksize to use for backing up to a standard hard drive, is 16m okay?
Last edited by itzmeluigi (2013-08-05 06:01:54)

Oops heh, i would usually rename it to test1.img and test2.img, i was using it as an example. Once i create the images, would the commands below be the proper way to restore them?
dd if=/mnt/backupdata/test1.img of=/dev/mapper/VolGroupArray-lvroot bs=16m
dd if=/mnt/backupdata/test2.img of=/dev/mapper/VolGroupArray-lvhome bs=16m
Thanks
Edit: All the commands ended up working perfectly i had to change the lower case m to bs=16M. Once i did that the image files were created and worked just fine
Last edited by itzmeluigi (2013-08-05 06:01:30)

Logical volume inactive at boot

Similar Messages

Maybe you are looking for