| Summary: | sys-fs/cryptsetup-1.4.3 : error msg during swapon of an encrypted swap file - mkswap: /dev/mapper/crypt-swap: warning: don't erase bootbits sectors on whole disk. Use -f to force. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
FWIW at an unstable Gentoo I don't see this issue :
* Setting up dm-crypt mappings ...
* crypt-swap using: -c aes -h sha1 -d /dev/urandom create crypt-swap /dev/ubdb ...
[ ok ]
* pre_mount: mkswap ${dev} ...
[ ok ]
[ ok ]
* Checking local filesystems ...
*** This bug has been marked as a duplicate of bug 288270 *** |
While starting a user mode linux image with an encrypted swap partition with this command line : earlyprintk ubda=/home/tfoerste/virtual/uml/gentoo_unstable ubdb=/home/tfoerste/virtual/uml/swap_gentoo_unstable eth0=tuntap,tap1,7a:cf:14:11:67:01, mem=256M con=pts con0=fd:0,fd:1 root=98:0 I get during startup this message: * Setting up dm-crypt mappings ... * crypt-swap using: -c aes -h sha1 -d /dev/urandom create crypt-swap /dev/ubdb ... [ ok ] * pre_mount: mkswap ${dev} ... mkswap: /dev/mapper/crypt-swap: warning: don't erase bootbits sectors on whole disk. Use -f to force. I found a lot of links related to the "Use -f to force" but always for different environments and often quiet old. /me wonders whether this is a bug or only a cosmetic issue. Reproducible: Always