Sponsored Content
Full Discussion: Can't unlock encrypted disk
Top Forums UNIX for Beginners Questions & Answers Can't unlock encrypted disk Post 303043057 by zognadal on Thursday 16th of January 2020 10:50:49 PM
Old 01-16-2020
Can't unlock encrypted disk

I use Debian default encryption disk encryption. Only /boot it's not encrypted. When I boot I need to type my password, and then I will be logged in. But now I can't login. It always says that I typed the wrong password, but I typed the correct password.

I tried to boot in live-CD and try unlock volume from there. But It always says wrong password.
Before that I had an achieve that had a 90GB file in it and I tried to underachieve it, but it gave me error not enough space. I get notification that I'm out of space 600mb left, but when type df -h I saw I have same amount of space as before I start to unarchieving file. Looks like file was autodeleted by Debian system.
I have no BADs on disk. Sometimes I have some issues with RAM module and I my PC stucks but I always can unlock the disk. In that case I need to clean RAM module and PC is not stucking anymore. I tried remove RAM modules and boot with only one of them, but still can't unlock disk. I have 2 HDDs with Debian and only one of them is not unlocking. Other one is working fine. I will try to connect that HDD to another PC and try to unlock and then type here if it succeed

Image

When I try to boot like this
Image
I get this
Image
When I boot like this
Image
I get
Image
Image
 

9 More Discussions You Might Find Interesting

1. Solaris

How to unlock my editor?

When I want to use the editor ,whether vi or textedit,it prompts for entering a key. How can I disable this function?many thanks for offering solutions! (1 Reply)
Discussion started by: smartboy1461
1 Replies

2. Solaris

how to unlock user ID in solaris?

I only able to lock user ID with passwd -l username It seems there is no option for me to unlock ID in solaris? Is there any command as below? passwd -u username Appreciate someome can share with me the way to do it. (1 Reply)
Discussion started by: dwarf007
1 Replies

3. UNIX for Dummies Questions & Answers

Unable to unlock users in Tru64

Hi Friends We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error /usr/sbin/usermod -x administrative_lock_applied=0 username account manager has exited unexpectedly - please... (0 Replies)
Discussion started by: madanmb
0 Replies

4. HP-UX

not able to unlock user

Hi, not able to unlock user eventhough executed /usr/lbin/modprpw -k username Thanks in advance (2 Replies)
Discussion started by: bpsunadm
2 Replies

5. AIX

how to unlock a dvd in HMC

When I do HMC upgrade, I download HMC code from IBM web site and burn it to a DVD disk, when I get the first DVD out of HMC's dvd rom and input the second DVD, it shows error: The requested device is already locked by the process: Install Corrective Service. Would you like to try to request a... (2 Replies)
Discussion started by: rainbow_bean
2 Replies

6. Shell Programming and Scripting

perl FileHandle Closure during after unlock

Hi we have one function which is used to append data the file in exclusive lock mode in aperl script. This script is executed by multiple threads at the same time. accessing the same file.this script runs throught the day. sometimes the file2.txt size is getting reduced. for eg from 10 M... (1 Reply)
Discussion started by: Shahul
1 Replies

7. Shell Programming and Scripting

Need help in lock and unlock and after the changes

Requirement:First i need to unlock the directory which i had a script for it.If i select app1 it should unlock the directory and after chnages in the script once need to lock the directory with lock command The below highlighed variables in lock and unlock has to be changed according... (2 Replies)
Discussion started by: bhas85
2 Replies

8. Shell Programming and Scripting

Where are lock and unlock commands?

I'm running cygwin bash on Windows 8.1. I would like to to write a OS neutral bash script that uses the commands like lock, block and unlock. Do I need to write lock, block and unlock myself in C++? I'm hoping someone has already written them. My bash script would look something like this:... (2 Replies)
Discussion started by: siegfried
2 Replies

9. Solaris

Solaris Automatic Account Unlock

Hello, It is to my understanding that when configuring the Solaris operating system to meet compliance standards, you must configure the "LOCK_AFTER_RETRIES" value in the "/etc/security/policy.conf" file to "YES", and then configure the "RETRIES" parameter in the "/etc/default/login" file to the... (4 Replies)
Discussion started by: TrustSovietBear
4 Replies
QEMU-IMG(1)															       QEMU-IMG(1)

NAME
qemu-img - QEMU disk image utility SYNOPSIS
usage: qemu-img command [command options] OPTIONS
The following commands are supported: check [-f fmt] filename create [-s] [-f fmt] [-o options] filename [size] commit [-f fmt] filename convert [-c] [-s] [-f fmt] [-O output_fmt] [-o options] filename [filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a snapshot | -c snapshot | -d snapshot] filename rebase [-u] -b backing_file [-F backing_fmt] filename Command parameters: filename is a disk image filename fmt is the disk image format. It is guessed automatically in most cases. See below for a description of the supported disk formats. size is the disk image size in bytes. Optional suffixes "k" or "K" (kilobyte, 1024) "M" (megabyte, 1024k) and "G" (gigabyte, 1024M) and T (terabyte, 1024G) are supported. "b" is ignored. output_filename is the destination disk image filename output_fmt is the destination format options is a comma separated list of format specific options in a name=value format. Use "-o ?" for an overview of the options supported by the used format or see the format descriptions below for details. -c indicates that target image must be compressed (qcow format only) -h with or without a command shows help and lists the supported formats Parameters to snapshot subcommand: snapshot is the name of the snapshot to create, apply or delete -a applies a snapshot (revert disk to saved state) -c creates a snapshot -d deletes a snapshot -l lists all snapshots in the given image Command description: create [-f fmt] [-o options] filename [size] Create the new disk image filename of size size and format fmt. Depending on the file format, you can add one or more options that enable additional features of this format. If the option backing_file is specified, then the image will record only the differences from backing_file. No size needs to be specified in this case. backing_file will never be modified unless you use the "commit" monitor command (or qemu-img commit). The size can also be specified using the size option with "-o", it doesn't need to be specified separately in this case. commit [-f fmt] filename Commit the changes recorded in filename in its base image. convert [-c] [-f fmt] [-O output_fmt] [-o options] filename [filename2 [...]] output_filename Convert the disk image filename to disk image output_filename using format output_fmt. It can be optionally compressed ("-c" option) or use any format specific options like encryption ("-o" option). Only the formats "qcow" and "qcow2" support compression. The compression is read-only. It means that if a compressed sector is rewritten, then it is rewritten as uncompressed data. Image conversion is also useful to get smaller image when using a growable format such as "qcow" or "cow": the empty sectors are detected and suppressed from the destination image. You can use the backing_file option to force the output image to be created as a copy on write image of the specified base image; the backing_file should have the same content as the input's base image, however the path, image format, etc may differ. info [-f fmt] filename Give information about the disk image filename. Use it in particular to know the size reserved on disk which can be different from the displayed size. If VM snapshots are stored in the disk image, they are displayed too. snapshot [-l | -a snapshot | -c snapshot | -d snapshot ] filename List, apply, create or delete snapshots in image filename. Supported image file formats: raw Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space. Use "qemu-img info" to know the real size used by the image or "ls -ls" on Unix/Linux. host_device Host device format. This format should be used instead of raw when converting to block devices or other devices where "holes" are not supported. qcow2 QEMU image format, the most versatile format. Use it to have smaller images (useful if your filesystem does not supports holes, for example on Windows), optional AES encryption, zlib based compression and support of multiple VM snapshots. Supported options: "backing_file" File name of a base image (see create subcommand) "backing_fmt" Image format of the base image "encryption" If this option is set to "on", the image is encrypted. Encryption uses the AES format which is very secure (128 bit keys). Use a long password (16 characters) to get maximum protection. "cluster_size" Changes the qcow2 cluster size (must be between 512 and 2M). Smaller cluster sizes can improve the image file size whereas larger cluster sizes generally provide better performance. "preallocation" Preallocation mode (allowed values: off, metadata). An image with preallocated metadata is initially larger but can improve performance when the image needs to grow. qcow Old QEMU image format. Left for compatibility. Supported options: "backing_file" File name of a base image (see create subcommand) "encryption" If this option is set to "on", the image is encrypted. cow User Mode Linux Copy On Write image format. Used to be the only growable image format in QEMU. It is supported only for compatibility with previous versions. It does not work on win32. vdi VirtualBox 1.1 compatible image format. vmdk VMware 3 and 4 compatible image format. Supported options: "backing_fmt" Image format of the base image "compat6" Create a VMDK version 6 image (instead of version 4) vpc VirtualPC compatible image format (VHD). cloop Linux Compressed Loop image, useful only to reuse directly compressed CD-ROM images present for example in the Knoppix CD-ROMs. SEE ALSO
The HTML documentation of QEMU for more precise information and Linux user mode emulator invocation. AUTHOR
Fabrice Bellard 2010-07-01 QEMU-IMG(1)
All times are GMT -4. The time now is 02:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy