??? 123123123123 .....................................................................................................................................??? 123123123123 .....................................................................................................................................0h   !!!!"<#;T#&# ###$'"$J$S$!g$$$ $$5$2%27%/j%'%7%%$&3&N&Oa&&&&&&H'5b' '$'!'#'C(!T(/v(@(6($)C)@a)*))+)*2* J*k*%*!*:*@ +L+"c+!+"+"++",$(,"M,%p,,&,,,-(#-L- b-7-A-6-(4.&].. ..#.#.-/J/'f/"///)/' 020$P0!u0"000001%(1'N1v111111 2,%2R2,o2524233 =3#^333"3 3 34 +4"L40o47444' 525%L5r5+5)5*526%76]6)v6"63626/*7Z7vz77 8/'8&W80~888 88!9;29+n9 9?949:";:"^:::':0:0;C;$Y;~;;";#;;@ <K<k<<<Q<O = ]=.j=N=%=->%<> b>/>7>>?&?'??g?(???(?L @QW@+@!@%@A O%_OOO&O:OMP4kP5P1P2Qf;QMQ+Q6R#SR*wRR.R2R!S8SWS'gS"SSSS T -TNT#mT!T)T*T$U$-URUBmU,UU!U!V.:ViV}VVVV%VAWUWWkWX 6X&WX~XXNXX YY/YGY!eY'YOYYZ*>Z iZwZ Z ZZZZZ ZZ1 [?[T[ Y[f[[[[([[[ \ \ \1*\\\{\\g^^8__3f`-`1`,`'aBaVa,taaa%aaab+b04b-eb-b(bbAcHcac}ccJcc$cd3d?Ld3d d5d2e46eHkee'eKe3Ff$zff6f0f*&g-Qggg(gg0g0hBOhChh$h+i$@i!eii$i$i$i!j!1j/Sj'j$j8j k.k<NkBk9k*l'3l[l(tll$l$l-m.m)Mm$wmmm*m m n"%n)Hn*rnnnnnn! o#.oRoioooooo*op'4p0\p3pp ppq5qGq^q}qqqqq.q7,r0drr!rr!rs' s%Hs(ns7s*s#s'tFt*ft0t$ttu)uu'u3u/0v$`v vvv)v3v%"wHw-Xw!ww-w-w0$xUx.qx/x*xx#y#8y\ypyyyUyz9zXzkzH~zQz {$&{TK{*{5{!|(#|+L|8x|||'|+}/}/M}}}}$}C}O~,n~2~%~!~ $$(Icr'03N:$׀**'(R<{.4,-WZ*͂B5;1q8+܃*'Rk/~+ڄ, $:D_!Ӆ$ -0?^2ц?$@eu$,*/ +;*g8+ˈG4?(t*$ȉ )EL P8]3؊! .Kҋ4-"P iv/H،1!-S!"YƍM 7n-$Ԏ -9+g*ۏ*%<&[ &&ʐ !'4"\#%"ɑ!H<WĒ!&:Nj?MƓX$m&)E Zgk3r%ŕE Pi-–ޖ % ?/L3|̗З /%9_!f 3!n&7Bl0}J!M1+Qq8\A?VFTf2*h1asmu~/iw4D>jS.c,lIp4Zo^@[}^ 'HZLw?' /`{ 3 vy%=].|RFtG) bn#IW!;jxKr|9C@h$f=JCX[O_ g7rd eU5bDi]e0(%taSY6z<z>vpTM Y\{:QXg5k9" 2B,WmyK8-sxPE~<L6:RPO `A"_U3N;qH-ud)+# c $NEG(&k*Vo "2 ]* is one of: is the device to create under %s is the data device is the device containing verification data hash of the root node on is the device to create under %s is the encrypted device is the LUKS key slot number to modify optional key file for the new key for luksAddKey action Default compiled-in dm-verity parameters: Hash: %s, Data block (bytes): %u, Hash block (bytes): %u, Salt size: %u, Hash format: %u WARNING: real device header has different UUID than backup!# Tests are approximate using memory only (no storage IO). %s header backup of device %s created.%s header on device %s restored.%s: requires %s as arguments, set cipher to [--type ] [] [] []Activating TCRYPT system encryption for partition %s.Activating temporary device using new LUKS header.Activating temporary device using old LUKS header.Activation is not supported for %d sector size.Activation of temporary devices failed.Align payload at sector boundaries - for luksFormatAll key slots full.Allocation of aligned memory failed.Argument missing.Argument required.Attaching loopback device failed (loop device with autoclear flag is required).BITSBackup LUKS device header and keyslotsBlock size on the data deviceBlock size on the hash deviceBoth journal encryption key file and key size options must be specified.Both key file and key size options must be specified.Buffers sizeCan't format LOOPAES without device.Can't format LUKS without device.Can't format VERITY without device.Cannot add key slot, all slots disabled and no volume key provided.Cannot check password quality: %sCannot convert device %s which is still in use.Cannot create LUKS header: header digest failed (using hash %s).Cannot create LUKS header: reading random salt failed.Cannot create header backup file %s.Cannot create header file %s.Cannot determine device type. Incompatible activation of device?Cannot exclusively open %s, device in use.Cannot format device %s in use.Cannot format device %s, permission denied.Cannot format device %s.Cannot get device size.Cannot get info about device %s.Cannot get process priority.Cannot initialize crypto RNG backend.Cannot initialize crypto backend.Cannot initialize device-mapper, running as non-root user.Cannot initialize device-mapper. Is dm_mod kernel module loaded?Cannot open device %s.Cannot open header backup file %s.Cannot open keyfile %s for write.Cannot open reencryption log file.Cannot open temporary LUKS device.Cannot read device %s.Cannot read header backup file %s.Cannot read keyfile from a terminal.Cannot read reencryption log file.Cannot read requested amount of data.Cannot resize loop device.Cannot restore %s header on device %s.Cannot retrieve volume key for plain device.Cannot seek to device offset.Cannot seek to requested keyfile offset.Cannot unlock memory.Cannot use %s as on-disk header.Cannot use a loopback device, running as non-root user.Cannot use device %s which is in use (already mapped or mounted).Cannot use device %s, name is invalid or still in use.Cannot use device %s, permission denied.Cannot use offset with terminal input.Cannot wipe device %s.Cannot wipe header on device %s.Cannot write device %s.Cannot write header backup file %s.Cannot write reencryption log file.Cannot write to device %s, permission denied.Cannot write to keyfile %s.Changed pbkdf parameters in keyslot %i.Command failed with code %i (%s). Command successful. Create a readonly mappingCreate new header on not encrypted deviceCreation of LUKS backup headers failed.Creation of hash area failed.DM-UUID for device %s was truncated.Data area overlaps with FEC area.Data area overlaps with hash area.Data integrity algorithmDevice %s %s%sDevice %s %s%s%s%sDevice %s already exists.Device %s has zero size.Device %s is not a valid LUKS device.Device %s is not a valid VERITY device.Device %s is not active.Device %s is still in use.Device %s is too small.Device is already %s type.Device offset overflow.Display brief usageDo not ask for confirmationDo not change key, no data area reencryptionDo not use verity superblockDo you really want to change UUID of device?Dump operation is not supported for this device type.Ensure you have algif_skcipher kernel module loaded.Enter VeraCrypt PIM: Enter any existing passphrase: Enter any remaining passphrase: Enter new passphrase for key slot: Enter new passphrase: Enter passphrase for %s: Enter passphrase for key slot %u: Enter passphrase to be changed: Enter passphrase to be deleted: Enter passphrase: Error during resuming device %s.Error during suspending device %s.Error during update of LUKS header on device %s.Error re-reading LUKS header after update on device %s.Error reading from RNG.Error reading keyfile %s.Error reading passphrase from terminal.Error reading passphrase.Error reading response from terminal.FEC parity bytesFailed to access temporary keystore device.Failed to acquire read lock on device %s.Failed to acquire write lock on device %s.Failed to assign keyslot %u as the new volume key.Failed to load key in kernel keyring.Failed to open key file.Failed to open temporary keystore device.Failed to read LUKS2 requirements.Failed to read activation flags from backup header.Failed to read passphrase from keyring (error %d).Failed to read requirements from backup header.Failed to set pbkdf parameters.Failed to setup dm-crypt key mapping for device %s. Check that kernel supports %s cipher (check syslog for more info).Failed to stat key file.Failed to swap new key slot.Failed to write activation flags to new header.Fatal error during RNG initialisation.Format type (1 - normal, 0 - original Chrome OS)Generating key (%d%% done). Hash algorithmHash algorithm %s not supported.Hash area overflow.Hash area overlaps with FEC area.Header backup file does not contain compatible LUKS header.Header detected but device %s is too small.Help options:How many sectors of the encrypted data to skip at the beginningHow often the input of the passphrase can be retriedIO error during reencryption.IO error while decrypting keyslot.IO error while encrypting keyslot.Ignore corruption, log it onlyIgnored unknown flag %s.Incompatible loop-AES keyfile detected.Incorrect root hash specified for verity device.Incorrect volume key specified for plain device.Invalid PIM value: 0.Invalid PIM value: outside of range.Invalid PIM value: parse error.Invalid device %s.Invalid device size specification.Invalid journal size specification.Invalid key size.Invalid luks type. Use one of these: 'luks', 'luks1' or 'luks2'.Invalid plain crypt parameters.Invalid salt string specified.Journal commit timeJournal encryption algorithmJournal encryption algorithm must be specified if journal encryption key is used.Journal integrity algorithm must be specified if journal integrity key is used.Journal sizeKernel keyring is not supported by the kernel.Key file can be used only with --key-slot or with exactly one key slot active.Key processing error (using hash %s).Key size in XTS mode must be 256 or 512 bits.Key size must be a multiple of 8 bitsKey slot %d active, purge first.Key slot %d is full, please select another one.Key slot %d is invalid, please select between 0 and %d.Key slot %d is invalid.Key slot is invalid.Keyslot %i: bogus partition signature.Keyslot %i: offset repaired (%u -> %u).Keyslot %i: salt wiped.Keyslot %i: stripes repaired (%u -> %u).LUKS keyslot %u is invalid.Limits the read from keyfileLimits the read from newly added keyfileLocking aborted. The locking path %s/%s is unusable (%s is not a directory).Locking aborted. The locking path %s/%s is unusable (not a directory or missing).Log file %s exists, resuming reencryption. Marking LUKS1 device %s unusable.Maximum device reduce size is 64 MiB.Maximum keyfile size exceeded.MiBN/ANegative number for option not permitted.New LUKS header for device %s created.No decryption in progress, provided UUID can be used only to resume suspended decryption process.No key available with this passphrase.No known problems detected for LUKS header.Non standard key size, manual repair required.Non standard keyslots alignment, manual repair required.Not compatible PBKDF options.Not compatible PBKDF2 options (using hash algorithm %s).Number of bytes to skip in keyfileNumber of bytes to skip in newly added keyfileOnly one --key-file argument is allowed.Only one of --use-[u]random options is allowed.Only values between 1 MiB and 64 MiB allowed for reencryption block size.Operation aborted, keyslots were NOT wiped. Operation aborted. Option --align-payload is allowed only for luksFormat.Option --decrypt is incompatible with specified parameters.Option --keep-key can be used only with --hash, --iter-time or --pbkdf-force-iterations.Option --key-file is required.Option --new cannot be used together with --decrypt.Option --new must be used together with --reduce-device-size or --header.Option --priority, --label or --subsystem is missing.Option --use-[u]random is allowed only for luksFormat.Option --uuid is allowed only for luksFormat and luksUUID.Option --uuid is allowed only together with --decrypt.Out of memory while reading passphrase.PBKDF iteration time for LUKS (in ms)PBKDF memory cost limitPBKDF parallel costPBKDF2 hash algorithm %s not available, skipping.PBKDF2 iteration time for LUKS (in ms)Passphrases do not match.Password quality check failed: %sPassword quality check failed: Bad passphrase (%s)Permanently decrypt device (remove encryption)Please use gpg --decrypt | cryptsetup --keyfile=- ... Print package versionProvided UUID is invalid.Read new volume (master) key from fileRead the key from a fileRead the volume (master) key from file.Really try to repair LUKS device header?Reduce data device size (move data offset). DANGEROUS!Reduce size must be multiple of 512 bytes sector.Reencryption already in-progress.Reencryption block sizeReencryption of device with integrity profile is not supported.Reencryption will change: %s%s%s%s%s%s.Repair failed.Repairing keyslots.Requested LUKS hash %s is not supported.Requested PBKDF type is not supported for LUKS1.Requested data integrity options are not supported.Requested deferred flag is not supported.Requested dm-crypt performance options are not supported.Requested dm-verity FEC options are not supported.Requested dm-verity data corruption handling options are not supported.Requested header backup file %s already exists.Requested maximum PBKDF memory cost is too high (maximum is %d kilobytes).Requested offset is beyond real size of device %s.Requested sector_size option is not supported.Required kernel crypto interface not available.Restore LUKS device header and keyslotsResume is not supported for device %s.Resume suspended LUKS deviceRunning in FIPS mode.SECTORSSaltSector sizeSetting LUKS2 offline reencrypt flag on device %s.Show debug messagesShow this help messageShows more detailed error messagesSlot number for new key (default is first free)Starting offset on the hash deviceSuspend is not supported for device %s.System is out of entropy while generating volume key. Please move mouse or type some text in another window to gather some random events. The UUID used to resume decryptionThe cipher used to encrypt the disk (see /proc/crypto)The hash used to create the encryption key from the passphraseThe number of blocks in the data fileThe size of the deviceThe size of the encryption keyThe start offset in the backend deviceThis function is not supported without TCRYPT header load.This is the last keyslot. Device will become unusable after purging this key.This operation is not supported for %s crypt device.This operation is not supported for this device type.This operation is supported only for LUKS device.This operation is supported only for LUKS2 device.This operation will erase all keyslots on device %s. Device will become unusable after this operation.This version of cryptsetup-reencrypt can't handle new internal token type %s.This will overwrite data on %s irrevocably.Timeout for interactive passphrase prompt (in seconds)Type of LUKS metadata: luks1, luks2UUID is not supported for this crypt type.Unable to move keyslot area.Unable to move keyslot area. Not enough space.Underlying device for crypt device %s disappeared.Unknown PBKDF type %s.Unknown RNG quality requested.Unknown action.Unknown crypt device type %s requested.Unmet LUKS2 requirements detected.Unsupported LUKS version %d.Unsupported VERITY FEC offset.Unsupported VERITY block size.Unsupported VERITY hash offset.Unsupported VERITY hash type %d.Unsupported VERITY version %d.Unsupported encryption sector size.Update log file after every blockUse /dev/random for generating volume keyUse /dev/urandom for generating volume keyUse backup (secondary) TCRYPT headerUse direct-io when accessing devicesUse fsync after each blockUse only specified device size (ignore rest of device). DANGEROUS!Use only this slot (others will be disabled)VERITY header corrupted.Verification of data area failed.Verification of root hash failed.Verifies the passphrase by asking for it twiceVerify passphrase: Volume %s is already suspended.Volume %s is not active.Volume %s is not suspended.Volume key buffer too small.Volume key does not match the volume.Volume key is too small for encryption with integrity extensions.WARNING: The --hash parameter is being ignored in plain mode with keyfile specified. WARNING: The --keyfile-size option is being ignored, the read size is the same as the encryption key size. Writing LUKS header to disk.Wrong LUKS UUID format provided.[OPTION...] [OPTION...] add key to LUKS devicealready contains LUKS header. Replacing header will destroy existing keyslots.benchmark cipherblocksbyteschanges supplied key or key file of LUKS deviceclose device (remove mapping)convert LUKS from/to LUKS2 formatdevice already exists or device is busydoes not contain LUKS header. Replacing header can destroy data on that device.dump LUKS partition informationdump TCRYPT device informationerase all keyslots (remove encryption key)format deviceformats a LUKS devicehex stringkilobytesmsecsno permission or bad passphrasenumberopen device as out of memoryprint UUID of LUKS deviceremoves supplied key or key file from LUKS deviceresize active devicesecsset hash to show active device statusshow device statusshow on-disk informationstringtests for LUKS partition headerthreadstry to repair on-disk metadataunknown errorverify devicevolume keywipes key with number from LUKS devicewrong device or file specifiedwrong or missing parametersProject-Id-Version: cryptsetup 2.0.3.1 Report-Msgid-Bugs-To: dm-crypt@saout.de PO-Revision-Date: 2018-04-27 22:41+0800 Last-Translator: Boyuan Yang <073plan@gmail.com> Language-Team: Chinese (simplified) Language: zh_CN MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bugs: Report translation errors to the Language-Team address. X-Generator: Poedit 2.0.6 Plural-Forms: nplurals=1; plural=0; <动作> 为其中之一： <名称> 是在 %s 下要创建的设备 <数据设备> 就是数据设备 <哈希设备> 是含有验证信息的设备 <根哈希值> 是 <哈希设备> 根节点的哈希值 为要在 %s 创建的设备 为加密设备 为需要更改的 LUKS 密钥槽 提供给 luksAddKey 动作的密钥文件 编译时决定的默认 dm-verify 参数： 哈希: %s, 数据块 (字节): %u, 哈希块 (字节): %u, 盐大小: %u, 哈希格式: %u 警告: 真实设备标头 UUID 和备份不符！# 测试仅使用内存（无存储 IO）。 已创建 %s 标头备份（对应设备 %s）。已恢复 %s 标头（在设备 %s 上）。%s: 需要 %s 作为参数，设定密文为 <数据设备> <哈希设备><数据设备> <哈希设备> <根哈希值><设备><设备> <密钥槽><设备> [--type <类型>] [<名称>]<设备> [<密钥文件>]<设备> [<新密钥文件>]<哈希设备><名称>正在为分区 %s 激活 TCRYPT 系统加密。正使用新 LUKS 标头激活临时设备。正使用旧 LUKS 标头激活临时设备。扇区大小为 %d 时不支持激活。激活临时设备失败。于 个扇区边界处对其载荷数据 - 供 luks 格式用密钥槽全都满了。分配对齐内存失败。缺失参数 <动作>。需要参数。连接回环设备失败（需要有 autoclear 旗标的回环设备）。位备份 LUKS 设备标头和密钥槽数据设备的块大小哈希设备的块大小日志加密密钥文件和密钥大小选项均必须指定。密钥文件和密钥大小选项均必须指定。缓冲大小无法在没有设备的情况下格式化 LOOPAES。无法在没有设备的情况下格式化 LUKS。无法在没有设备的情况下格式化 VERIFY。无法添加密钥槽，所有密钥槽已禁用且未提供卷密钥。无法检查密码质量：%s无法转换正在使用的设备 %s。无法创建 LUKS 标头：标头摘要失败（正在使用哈希 %s）。无法创建 LUKS 标头：读取随机盐失败。无法创建标头备份文件 %s。无法创建标头文件 %s。无法确定设备类型。不兼容的设备激活？无法独占打开 %s，设备正在使用中。无法格式化正在使用的设备 %s。无法格式化设备 %s，权限被拒绝。无法格式化设备 %s。无法获取设备大小。无法获取有关设备 %s 的信息。无法获取进程优先级。无法初始化加密随机数生成器后端。无法初始化加密后端。无法初始化设备映射器，正作为非 root 用户运行。无法初始化设备映射器。dm_mod 内核模块装载了吗？无法打开设备 %s。无法打开备份标头文件 %s。无法打开密钥文件 %s 以供写入。无法打开重加密日志文件。无法打开临时 LUKS 设备。无法读取设备 %s。无法读取标头备份文件 %s。无法从终端读取密钥文件。无法读取重加密日志文件。无法读取请求量的数据。无法改变回环设备大小。无法恢复 %s 标头（在设备 %s 上）。无法获取普通设备的卷密钥。无法寻找到设备偏移位置。无法寻找 (seek) 到请求的密钥文件偏移量。无法解锁内存。无法将 %s 作为磁盘上的标头使用。无法使用回环设备，正作为非 root 用户运行。无法使用正被使用的设备 %s（已被映射或挂载）。无法使用设备 %s，名称无效或它正被使用。无法使用设备 %s，权限被拒绝。不能将偏移量用于终端输入。无法擦除设备 %s。无法将设备 %s 上的标头擦除。无法写入设备 %s。无法写入标头备份文件 %s。无法写入重加密日志文件。无法写入到设备 %s，访问被拒绝。无法写入密钥文件 %s。已在密钥槽 %i 更改 pbkdf 参数。命令失败，代码 %i（%s）。 命令成功。 创建只读映射在未加密的设备上创建新的标头LUKS 备份标头创建失败。创建哈希区失败。设备 %s 的 DM-UUID 被截断。数据区域重叠覆盖了 FEC 区域。数据区域重叠覆盖了哈希区域。数据完整性校验算法设备 %s %s%s设备 %s %s%s%s%s设备 %s 已存在。设备 %s 大小为零。%s 不是有效的 LUKS 设备。%s 不是有效的 VERITY 设备。设备 %s 未激活。设备 %s 仍在使用。设备 %s 太小。设备已为 %s 类型。设备偏移量溢出。显示简短用法不要请求确认不要更改密钥，无数据区重加密不使用真理超级块你真的想改变设备的 UUID 吗？不支持在此类设备上执行导出操作。请确定您已载入内核模块 algif_skcipher。输入 VeraCrypt PIM: 输入任意已存在的口令: 输入任意剩余的口令: 输入密钥槽的新口令: 输入新口令: 输入 %s 的口令：输入密钥槽 %u 的口令: 输入要更改的口令: 输入要移除的口令: 输入口令：恢复设备 %s 时出错。挂起设备 %s 时出错。更新设备 %s 上的 LUKS 标头时出错。在更新设备 %s 后重新读取 LUKS 标头失败。从随机数生成器（RNG）读取时出错。读取密钥文件 %s 出错。从终端读取口令时出错。读取口令出错。从终端读取响应时失败。FEC 校验字节访问临时密钥存储设备失败。无法获取设备 %s 的读取锁。无法获取设备 %s 上的写入锁。将密钥槽 %u 指定为新卷密钥的操作失败。在内核密钥环中加载密钥失败。打开 (open) 密钥文件失败。打开临时密钥存储设备失败。读取 LUKS2 需求时失败。从备份标头读取活动旗标失败。从密钥环读取口令失败（错误 %d）。从备份标头读取需求失败。设置 pbkdf 参数失败。为设备 %s 配置 dm-crypt 键映射失败。 请确认内核支持 %s 加密（查看系统日志 (syslog) 以获取更多信息）。获取 (stat) 密钥文件信息失败。交换新密钥槽失败。向新表头写入活动旗标失败。随机数生成器初始化时发生致命错误。格式类型 (1 - 正常, 0 - 原版 Chrome OS)正生成密钥（%d%% 已完成） 哈希算法不支持哈希算法 %s。哈希区域溢出。哈希区域重叠覆盖了 FEC 区域。标头备份文件不包含兼容的 LUKS 标头。检测到标头但设备 %s 太小。帮助选项：从开头要跳过的加密数据扇区数量输入密码的最大重试频率重加密时发生 IO 错误。解密密钥槽时发生输入输出错误。加密密钥槽时发生输入输出错误。忽略数据损坏，仅对其进行日志记录已忽略未知旗标 %s。探测到不兼容的 loop-AES 密钥文件。为 verity 设备指定的根 hash 不正确。为普通设备指定的卷密钥有误。无效的 PIM 值：0。无效的 PIM 值：超出范围。无效的 PIM 值：解析错误。设备 %s 无效。无效的设备大小指标。无效的日志大小指标。无效的密钥大小。无效的 luks 类型。请使用下列选项之一：'luks'、'luks1' 或 'luks2'。无效的纯加密选项。指定了无效的盐字串。日志提交时间日志加密算法如果使用了日志加密密钥，则必须指定日志加密算法。如果使用了日志加密密钥，则必须指定日志完整性校验算法。日志大小该内核不支持内核密钥环。密钥文件只能在指定 --key-slot 时或有且只有一个槽启用时使用。密钥处理错误（使用散列 %s）。XTS 模式的密钥大小必须是 256 或 512 位。密钥尺寸必须是 8 的倍数密钥槽 %d 已激活，请先清除。密钥槽 %d 满了，请选择另一个。密钥槽 %d 无效，请选择 0 到 %d 间的数字。密钥槽 %d 无效。密钥槽无效。密钥槽 %i：虚假的分区签名。密钥槽 %i: 偏移已修复 (%u -> %u)。密钥槽 %i: 已清除盐。密钥槽 %i：已修复条带（%u -> %u）。LUKS 密钥槽 %u 无效。限制从密钥文件读取限制从新增密钥文件的读取锁定中止。锁定路径 %s/%s 不可用（%s 不是目录）。锁定中止。锁定路径 %s/%s 不可用（不是一个目录或缺失）。日志文件 %s 存在，继续重加密。 正在标记 LUKS1 设备 %s 为不可用状态。最大设备缩减大小为 64 MiB。超出最大密钥文件大小。MiB不可用不允许在选项中填入负数。已创建设备 %s 的新 LUKS 标头。没有正在进行中的解密操作，提供的 UUID 仅能用于继续已挂起的解密操作。此口令无可用的密钥。未在 LUKS 标头发现已知问题。不标准的密钥大小，需要手动修复。不标准的密钥槽对齐，需要手动修复。PBKDF2 选项不兼容。PBKDF2 选项不兼容（正在使用哈希算法 %s）。要从密钥文件跳过的字节数要从新增密钥文件跳过的字节数只允许存在一个 --key-file 选项。--use-[u]random 选项只能用一处。重加密块大小只能是 1 MiB 到 64 MiB 之间的值。操作已中止，密钥槽没有被擦除。 操作中止。 选项 --align-payload 只允许用于 luksFormat。选项 --decrypt 与选定参数不兼容。选项 --keep-key 只能与 --hash、--iter-time 或 --pbkdf-force-iterations 共用。需要选项 --key-file。选项 --new 不可与 --decrypt 共用。选项 --new 必须与 --reduce-device-size 或 --header 共用。选项 --priority、--label 或 --subsystem 缺失。选项 --use-[u]random 只适用于 luksFormat。选项 --uuid 只允许用于 luksFormat 和 luksUUID。选项 --uuid 不可与 --decrypt 共用。读取密码时内存耗尽。LUKS 默认 PBKDF 迭代时间（毫秒）PBKDF 内存开销限制PBKDF 并行开销PBKDF2 哈希算法 %s 不可用，将跳过。LUKS 默认 PBKDF2 迭代时间（毫秒）口令不匹配。密码质量检查失败： %s密码质量检查失败：无效密码 (%s)永久解密设备（移除加密）请使用 gpg --decrypt <密钥文件> | cryptsetup --keyfile=- ... 打印软件包版本提供的 UUID 无效。从文件读取卷（主）密钥从文件读取密钥从文件读取卷（主）密钥。确定要尝试修复 LUKS 设备标头吗？减少数据设备大小（移动数据偏移量）。危险！缩减大小必须为 512 字节扇区的倍数。重加密已在进行中。重加密块大小不支持带有完整性 profile 信息的设备的重加密。重加密会改变：%s%s%s%s%s%s。修复失败。正在修复密钥槽。不支持请求的 LUKS 哈希 %s。请求的 PBKDF 类型不被 LUKS1 支持。不支持请求的数据完整性选项。不支持请求的推迟（deferred）标记。不支持请求的 dm-crypt 性能选项。不支持请求的 dm-verity FEC 选项。不支持请求的 dm-verity 数据损坏处理选项。请求的标头备份文件 %s 已存在。请求的最大 PBKDF 内存开销过大（最大为 %d 千字节）。请求的偏移量超出设备 %s 的真实大小。不支持请求的 sector_size 选项。无法找到所需的内核加密接口。恢复 LUKS 设备标头和密钥槽设备 %s 不支持恢复。恢复已挂起的 LUKS 设备在 FIPS 模式下运行。扇区盐扇区大小正在设备 %s 上设定 LUKS2 离线重加密旗标。显示调试信息显示此帮助显示更详细的错误信息新密钥的槽号（默认为第一个可用的）哈希设备开始位置偏移量设备 %s 不支持挂起。系统在生成卷密钥时熵不足。 请随意移动鼠标或是在别的窗口打字，以便生成随机事件让系统使用。 用于继续解密的 UUID用于加密磁盘的密文（参见 /proc/crypto）用于从密码创建加密密钥的哈希值数据文件的块数量设备大小加密密钥大小后端设备的起始偏移量未载入 TCRYPT 标头时不支持此功能。这是最后一个密钥槽。设备在清空此密钥后将不可用。不支持在 %s 加密设备上执行此操作。不支持在这类设备上执行此操作。此操作只适用 LUKS 设备。此操作只适用 LUKS2 设备。该操作将清空设备 %s 上所有的密钥槽。 设备在此操作后将不可用。该版本的 cryptsetup-reencrypt 无法处理新的内部 token 类型 %s。这将覆盖 %s 上的数据，该动作不可取消。交互式密码提示符超时长度（秒）LUKS 元数据类型：luks1、luks2此加密类型不支持 UUID。无法移动密钥槽区域。无法移动密钥槽区域。空间不足。加密设备 %s 下层的设备消失了。未知的 PBKDF 类型 %s。未知的随机数生成器质量请求。未知动作。请求了未知的加密设备类型 %s。探测到未满足的 LUKS2 需求。不支持的 LUKS 版本 %d。不支持的 VERITY 哈希偏移量。不支持的 VERITY 块大小。不支持的 VERITY 哈希偏移量。不支持的 VERITY 哈希类型 %d。不支持的 VERITY 版本 %d。不支持的加密扇区大小。在每个数据块后更新日志文件使用 /dev/random 生成卷密钥使用 /dev/urandom 生成卷密钥使用备份（次级）TCRYPT 标头在访问设备时使用 direct-io在每个数据块后使用 fsync只使用指定的设备大小（忽略设备其余部分）。危险！仅使用这个密钥槽（其他的密钥槽将被禁用）VERITY 标头损坏。数据区检验失败。根哈希值检验失败。两次询问密码以进行验证确认密码：卷 %s 已挂起。卷 %s 未激活。卷 %s 未挂起。卷密钥缓冲区太小。卷密钥与卷不匹配。卷密钥对于带完整性校验扩展的加密而言过小。警告：在纯文本模式下指定密钥文件时将忽略参数 --hash。 警告：将忽略参数 --keyfile-size，读取大小应与加密密钥大小一致。 正在将 LUKS 标头写入磁盘。提供了错误的 LUKS UUID 格式。[选项…] <动作> <动作特定参数>[选项...] <设备>向 LUKS 设备添加密钥已包含 LUKS 标头。替换标头将损毁已存在的密钥槽。测试密文块字节更改 LUKS 设备中指定的密钥或密钥文件关闭设备（移除映射）在 LUKS 和 LUKS2 格式之间转换设备已存在或设备正忙不包含 LUKS 标头。替换标头可能损毁设备上的数据。调出 LUKS 分区信息调出 TCRYPT 设备信息清空所有密钥槽（移除加密密钥）格式化设备格式化一个 LUKS 设备十六进制字符串千字节毫秒无权限或口令错误数字以 <名称> 打开设备内存耗尽输出 LUKS 设备的 UUID（唯一标识符）移除 LUKS 设备中指定的密钥或密钥文件改变活动设备大小。秒设置哈希值为 显示已激活的设备信息显示设备状态显示磁盘上的信息字符串从 探测 LUKS 分区标头线程尝试修复磁盘上的元数据未知错误验证设备卷密钥从 LUKS 设备清理标号为 的密钥指定了错误的设备或文件错误或缺失的参数PRIu64Device %s is too small. (LUKS1 requires at least % bytes.)设备 %s 过小。（LUKS1 需要至少 % 字节。）