View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002594Kali LinuxGeneral Bugpublic2015-08-25 02:352018-01-29 11:54
Reporterded5557 Assigned Tog0tmi1k  
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionsuspended 
Summary0002594: Kali 2.0 swap issues
Description

I am having an issue that might be a possible bug with Kali 2.0 and encrypted swap, for some reason the first time i set it up it worked but after rebooting it has issues calling up the encrypted swap partition.

i have been trying to look for logs to see what the issue is but I am unable to find anything pertaining to the swap drive after the first successful mounting. I will continue to try and find more logs

in the meantime these are the only logs i could find ,

Aug 24 01:34:04 kernel: [ 27.702829] EXT4-fs (sda6): mounting ext2 file system using the ext4 subsystem
Aug 24 01:34:04 kernel: [ 27.715743] EXT4-fs (sda6): mounted filesystem without journal. Opts: (null)
Aug 24 01:34:04 kernel: [ 39.772158] Adding 8495100k swap on /dev/mapper/sda7_crypt. Priority:-1 extents:1 across:8495100k FS

Steps To Reproduce

created unencrypted /boot partition
Created a encrypted / ext2 partition
Created a encrypted swap partition

Installed system to /

System booted fine the first time, after the second reboot the swap partition is no longer being mounted at boot, the password is never asked for on the swap partition at boot, it only asks for the / password now.

Attached Files
logfile.txt (5,720 bytes)    
-- Logs begin at Mi 2015-08-26 11:02:10 CEST, end at Mi 2015-08-26 12:08:33 CEST. --
Aug 26 11:03:38 salix-box systemd[1]: Job dev-mapper-sda5_crypt.device/start timed out.
Aug 26 11:03:38 salix-box systemd[1]: Timed out waiting for device dev-mapper-sda5_crypt.device.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Encrypted Volumes.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for /dev/mapper/sda5_crypt.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Swap.
Aug 26 11:03:38 salix-box systemd[1]: Job dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device/start timed out.
Aug 26 11:03:38 salix-box systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device.
Aug 26 11:03:45 salix-box systemd[1]: greenbone-security-assistant.service: main process exited, code=exited, status=1/FAILURE
Aug 26 11:03:45 salix-box systemd[1]: Unit greenbone-security-assistant.service entered failed state.
Aug 26 11:03:46 salix-box systemd[1]: openvas-scanner.service: control process exited, code=exited status=1
Aug 26 11:03:46 salix-box systemd[1]: Failed to start Open Vulnerability Assessment System Scanner Daemon.
Aug 26 11:03:46 salix-box systemd[1]: Unit openvas-scanner.service entered failed state.
Aug 26 11:03:47 salix-box systemd[1]: openvas-manager.service never wrote its PID file. Failing.
Aug 26 11:03:47 salix-box systemd[1]: Failed to start Open Vulnerability Assessment System Manager Daemon.
Aug 26 11:03:47 salix-box systemd[1]: Unit openvas-manager.service entered failed state.
Aug 26 11:03:53 salix-box systemd[873]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0)
Aug 26 11:03:53 salix-box systemd[873]: Starting Paths.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Paths.
-- Logs begin at Mi 2015-08-26 11:02:10 CEST, end at Mi 2015-08-26 12:08:33 CEST. --
Aug 26 11:03:38 salix-box systemd[1]: Job dev-mapper-sda5_crypt.device/start timed out.
Aug 26 11:03:38 salix-box systemd[1]: Timed out waiting for device dev-mapper-sda5_crypt.device.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Encrypted Volumes.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for /dev/mapper/sda5_crypt.
Aug 26 11:03:38 salix-box systemd[1]: Dependency failed for Swap.
Aug 26 11:03:38 salix-box systemd[1]: Job dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device/start timed out.
Aug 26 11:03:38 salix-box systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device.
Aug 26 11:03:45 salix-box systemd[1]: greenbone-security-assistant.service: main process exited, code=exited, status=1/FAILURE
Aug 26 11:03:45 salix-box systemd[1]: Unit greenbone-security-assistant.service entered failed state.
Aug 26 11:03:46 salix-box systemd[1]: openvas-scanner.service: control process exited, code=exited status=1
Aug 26 11:03:46 salix-box systemd[1]: Failed to start Open Vulnerability Assessment System Scanner Daemon.
Aug 26 11:03:46 salix-box systemd[1]: Unit openvas-scanner.service entered failed state.
Aug 26 11:03:47 salix-box systemd[1]: openvas-manager.service never wrote its PID file. Failing.
Aug 26 11:03:47 salix-box systemd[1]: Failed to start Open Vulnerability Assessment System Manager Daemon.
Aug 26 11:03:47 salix-box systemd[1]: Unit openvas-manager.service entered failed state.
Aug 26 11:03:53 salix-box systemd[873]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0)
Aug 26 11:03:53 salix-box systemd[873]: Starting Paths.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Paths.
Aug 26 11:03:53 salix-box systemd[873]: Starting Timers.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Timers.
Aug 26 11:03:53 salix-box systemd[873]: Starting Sockets.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Sockets.
Aug 26 11:03:53 salix-box systemd[873]: Starting Basic System.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Basic System.
Aug 26 11:03:53 salix-box systemd[873]: Starting Default.
Aug 26 11:03:53 salix-box systemd[873]: Reached target Default.
Aug 26 11:03:53 salix-box systemd[873]: Startup finished in 123ms.
Aug 26 11:05:16 salix-box systemd[1]: Job dev-mapper-sda5_crypt.device/start timed out.
Aug 26 11:05:16 salix-box systemd[1]: Timed out waiting for device dev-mapper-sda5_crypt.device.
Aug 26 11:05:16 salix-box systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt.
Aug 26 11:05:16 salix-box systemd[1]: Dependency failed for /dev/mapper/sda5_crypt.
Aug 26 11:05:16 salix-box systemd[1]: Job dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device/start timed out.
Aug 26 11:05:16 salix-box systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device.
Aug 26 11:07:33 salix-box systemd[1]: Job dev-mapper-sda5_crypt.device/start timed out.
Aug 26 11:07:33 salix-box systemd[1]: Timed out waiting for device dev-mapper-sda5_crypt.device.
Aug 26 11:07:33 salix-box systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt.
Aug 26 11:07:33 salix-box systemd[1]: Dependency failed for /dev/mapper/sda5_crypt.
Aug 26 11:07:33 salix-box systemd[1]: Job dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device/start timed out.
Aug 26 11:07:33 salix-box systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-52c0a4f4\x2d1d38\x2d4766\x2daebf\x2dbea139cb2f04.device.
logfile.txt (5,720 bytes)   

Activities

katzenjaeger

katzenjaeger

2015-08-26 10:26

reporter   ~0003835

Last edited: 2015-08-27 09:48

have the same issue on i386 with fresh kali 2.0.
installed with

/boot (ext2)
encrypted swap as /sda5
encrypted / (ext4) as /sda6
enccrypted /home (ext4) as /sda7.

This issue is reproducible.

I installed Kali 2.0 4x with this configuration and got always the same issue.
After installing, first reboot, all worked correctly. After second reboot swap mounting failed without passphrase request.
g0tmi1k

g0tmi1k

2018-01-29 11:54

administrator   ~0008095

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2015-08-25 02:35 ded5557 New Issue
2015-08-26 10:26 katzenjaeger Note Added: 0003835
2015-08-26 10:27 katzenjaeger File Added: logfile.txt
2015-08-26 10:31 katzenjaeger Note Edited: 0003835
2015-08-26 10:32 katzenjaeger Note Edited: 0003835
2015-08-27 09:44 katzenjaeger Note Edited: 0003835
2015-08-27 09:46 katzenjaeger Note Edited: 0003835
2015-08-27 09:48 katzenjaeger Note Edited: 0003835
2018-01-29 11:54 g0tmi1k Assigned To => g0tmi1k
2018-01-29 11:54 g0tmi1k Status new => closed
2018-01-29 11:54 g0tmi1k Resolution open => suspended
2018-01-29 11:54 g0tmi1k Note Added: 0008095