Debian Configuration :: Timeouts And Dependency Failures On Boot - Crypto Related
Mar 27, 2016
I've got this weird problem: when I reboot my Debian 8.3 server, I have to run through the crypto unlocking processes for my encrypted volumes a few times before I actually get to a login screen. The operation times out 85% of the time, leaving me to reboot and try over and over until the system is happy.
Here's my partitioning setup (manually partitioned at install):
/boot: 500 MB, EXT2, nodev, nosuid, noexec
/tmp: 2 GB, EXT2, AES-256/xts-plain64 with RANDOM KEY
swap: 2.5 GB, AES-256/xts-plain 64 with RANDOM KEY
/: 35 GB, EXT4, AES-256/xts-plain 64 with PASSPHRASE
/var: 35 GB, EXT4, AES-256/xts-plain 64 with PASSPHRASE
/home: 45 GB, EXT4, AES-256/xts-plain 64 with PASSPHRASE
Here's the output from journalctl -b -p 3:
Code: Select allDate and time | server name | systemd[1]: Timed out waiting for device dev-sda5.device
Date and time | server name | systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt
Date and time | server name | systemd[1]: Dependency failed for Encrypted Volumes
Date and time | server name | systemd[1]: Dependency failed for dev-mapper-sda5_crypt.device
Date and time | server name | systemd[1]: Dependency failed for /tmp
[Code] ....
I had the same problem in previous builds where I chose Twofish instead of AES, and I was hoping that the timeouts would be fixed by switching to AES as my CPU has the AES instruction set. Obviously that didn't make a damn bit of difference.
What am I doing wrong, or what should I change in my setup? The encryption is a requirement. Could the problem be caused by something as stupid as using a RANDOM KEY instead of a PASSPHRASE on /tmp and swap?
I recently bought two DreamPlugs and replaced the preinstalled aged Ubuntu 9.04 with Debian Squeeze on them.I built a Marvell Orion 2.6.35 kernel from git. OpenSSL performes lousy on this hardware (my VIA Nano with PadLock support gives me ~690 000k on 8192 size blocks):
VirtualBox is awesome tool for experiment and learning Linux.On the Linux guest OS, I installed standard system without Xorg.i expected it remove all the packages that come along with gnome-terminal previously.Only gnome-terminal was removed, 750kB free space. Now the system have 149MB packages as waste data IMHO.It doesn't look right to me.
I'm trying to install KDE, but I can't. I've tried using tasksel, but it gave me an error, so I tried to install task-kde-desktop myself. When I did that, I ran into some dependency issues:
Code: Select allSome packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following packages have unmet dependencies:
 task-kde-desktop : Depends: kde-standard but it is not going to be installed           Depends: kdm but it is not going to be installed           Recommends: kdeaccessibility but it is not going to be installed           Recommends: k3b but it is not going to be installed      [Code]...
Here's my problem: I'm running a Lenny laptop and I need both wifi and virtualbox to work. I had to do a kernel upgrade to run the wifi. It works with either the 2.6.29 or 2.6.30 kernels, but with 2.6.30 I'm having screen brightness issues that I can't seem to get rid of. So I want to run 2.6.29, but virtualbox is a bit of a problem because it requires linux-headers-2.6.29, but when I try to install the amd64 headers it tells me that it cannot install the dependency linux-kbuild-2.6.29. Is there any way I can get that dependency installed on my computer?
I've got a Lenny system on a quad core system with 4GB of ram. Currently Linux www 2.6.26-2-amd64 #1 SMP Thu Nov 25 02:05:44 UTC 2010 x86_64
I've had it for a couple of years, and its been fine, very fast and reliable.
Lately, its got a problem: after its been running for a day or two, access using SSH, or TLS/HTTPS gets really slow. Painfully slow. A reboot returns the system to normal fast operation.
I can't think of anything that has changed, other than I got a new SSL cert and installed it.
The system is mostly a vanity domain server, with Apache HTTPD running a half dozen very low volume services. Its running bind9, mysql, and a few other things, nothing big, nothing that would load down a quad core with lots of ram. The disk is only 14% used.
I run a Laptop (Mint 17.1), which is connected to a Debian 8.1 server over a LAN. The systems are connected through a router. Both of them show no problems when working independently and when doing work on the internet. Also, ping works fine (no lost packets, no delays!) from Debian to Mint. However when doing a ping from the Laptop (Mint) to the Debian server, I experience frequent packet losses and timeouts. In fact, a "first" ping may lose the first 20 to 30 "tries". Thereafter, if I repeat pings immediately and quickly one after the other, they might in geral not lose packages or show delays. Ping to and from the router also works perfectly in either direction!
Of course, functions such as ssh or samba-sharing are hampered as well by this behaviour. Also, if I DO in fact manage to connect to the Debian server via ssh, my console (KDE 14) is freuqently "locked" (i.e. - doesn't show my input for a while) but in the end DOES show the characters entered and gets processed o.k. (eg. when doing an "ls"-command). Both systems are at the latest software-level and I just finished installing Debian 8.1. The situation was the same on Debian Wheezy, however.
I like my monitor to turn off when I'm not at the computer for more than 10 or 20 minutes or so and it wasn't doing that. I haven't used Linux for years and was used to xorg.conf/x11.conf and xinitrc and such.
So I rediscovered xset is responsible for DPMS settings. xset -q revealed DPMS was off. So I used it and put it in ~/.xinitrc. It didn't work. After some canoodling around I found out about xfce's Session and Startup gui thing. I was using that to run ~/.xinitrc.
When I got to my desktop and did a check with xfce4-terminal by running xset -q it would show DPMS enabled but the values were wrong. 600, 0, 900 to be exact.
After some searching I came across the information that xscreensaver will override DPMS settings as it manages DPMS too. So after more canoodling I found out about xfce's Screensaver preferences dialogue and used that to set my values. The values would immediately be set but the problem is that they are not persistent. If I reboot or log out the values will revert to 600, 0, 900. They will only reset to what I want them to be by running xfce's Screensaver preferences dialogue manually.
man gdm3, info gdm3, grep -r DPMS in /etc/gdm3, grep -r dpms in /etc/gdm3 reveal nothing related to DPMS. I've done some searching and nothing useful.
there is an /etc/X11/app-defaults/XScreenSaver-nogl which has some DPMS settings but the times are too large (2 hours); the only thing that matches is the off setting which is specified there.
xscreensaver -no-splash is present in the output of ps so it is xscreensaver and not gnome-screensaver.
The weird thing is that I re-enabled my ~/.xinitrc in xfce's Session and Startup gui thing and it is being run, but the numbers are getting set wrong after it is run. (I put an echo command after xset dpms 900 1200 1500, and the file is appearing in ~)
Where does 600, 0, 900 come from? Mystified on how to proceed from here. I don't remember enough on how to see what's doing what. Is there some sys thing or proc thing I can monitor to find out what's setting these values?
Short version: my xset dpms values are getting reset to 600, 0, 900 every time I logout or reboot. They revert to 600, 0, 900 every time I get to my desktop. I use gdm3 and xfce. Where are these coming from?
Having installed 9,10 onto a laptop my cherubic daughter swicthed off the power (no battery) and upon restarting i am faced with "Starting Init crypto disks... OK) and there it stops!! I had hoped that I could go to recovery mode and fix it but am faced with the same stalling point. I see others are unresolved in this.
i just migrated from fedora to debian, and i already love this system. it only seems that i am facing a serious problem with this graphic card.running on debian 8.3.booting my system, i do get this message:
[8.167619] [drm:radeon_pci_probe] *ERROR* radeon kernel modesettingfor r600 or later requires firmware-linux-nonfree.
after that the system seems to run normally except of the fact that it doesn't look well and i cannot set the appropriate resolution for my monitor.
lspci -nn | grep VGA output: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]
already tried both, the open source and the proprietary drivers, and both cause serious problems.
i tried to install the proprietary driver following these instructions: URL...
after restarting the system i get a black screen with a blinking cursor at the top left corner, and that's it.
then tried to install the open source driver following these instructions:URL...
but after restarting the system my monitor goes into some sort of a "sleep monitor mode", and that's it.in both cases i wasn't able to boot the system through the recovery mode, so i didn't know what else to do and re-installed the whole system each and every time i tried a driver.let's say i have installed the system like 5 times in the past 12 hours.
A week ago I opened this thread viewtopic.php?f=17&t=61580 in "Board index ‹ Help ‹ Installation" and asked for a moderator to move this to here. Because it hasnt happened up to know, I am reopening the thread here. It would be reeeeally great if somebody could help me with my problem!
I own two computers, one netbook and one laptop. I want to boot my netbook as a diskless client via PXE.I set up a dhcp-, tftp and nfs-server on my laptop but when i boot my netbook, the follwoing messages are displayed:(to make it more clear, i uploaded the whole output and shortened the output below)
I am a Linux noob (running Ubuntu 9.10) and not even an advanced Win. user. However, my switch to Linux was for simplicity, stability, fewer crashes,and the open-source software philosophy. However, Ubuntu hasn't been what I am hoping for. While Scientific Linux and Vector seem like good second choices, they don't seem to have the community/enthusiasm that Slackware has. However everything I read is all about "dependency management" w/r/t Slackware. Is this really a big problem? As a newbie, how will I deal with it? I am willing to learn but realize that I am starting from scratch.
I've had my share of troubles with Ubuntu before and always been able to find help just by reading the forums, but this time it doesn't seem to be happening. Basically, I think I did something stupid by trying to change the permissions on my home folder to 777. (I'm the only person who uses my computer and got sick of always having to get root permissions.) Halfway through the process, the computer slowed to a crawl and text in dialog boxes started getting replaced with empty squares.
Naturally I rebooted - or tried to. Regular boot didn't work, so I tried recovery mode, which was kind enough to tell me I had a kernel panic because sbin/init wasn't found. Here's where things got weird: I then tried to boot from my Ubuntu USB stick, and couldn't. I got to the USB menu, hit the "run" option, and after a few seconds of the Ubuntu boot screen, my monitor went blank. Actually, to be technical, it didn't just show a black screen - the screen shut off. That's as far as I've been able to get.
By the way, just before I tried what I'm now calling the chmod-of-death, I also had an update freeze in the middle. I am able to boot into Windows, and have checked my USB stick - all seems fine. Any thoughts on this? Worst case, I can reformat the partition and reinstall, but I'd rather not lose all that data.
UPDATE: Okay, so I *did* manage, after about ten more tries, to boot from the USB stick. I went in from there and changed all the permissions back to 755. Tried to boot in recovery again, and still getting the same sbin/init error - so I'm wondering now if it had more to do with the failed update than the permission change....
I have just installed Ubuntu (/dev/sda7) and Debian (/dev/sda4), but since I have updated all informations on Ubuntu, then Debian did not appear anymore on the grub list. There is an wiki I have found, but I an not really sure about what to do.
Here are the boot informations: Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> Grub 2 is installed in the MBR of /dev/sda and looks at sector 488861020 of the same hard drive for core.img, core.img is at this location on /dev/sda and looks on partition #3 for (,gpt3)/grub.
[Code]...
ps: on this file, it says that the /boot is installed on the MBR and /dev/sda3. I will remove the boot from MBR as I am now using /dev/sda3 instead. Sorry for my english
Without going into a lot of the reasons, I have a bootable program on a USB stick that i would like to 'boot' when debian is starting up (or after it completes, or whenever it makes sense to do it). My MB does not support a USB boot, I've removed the floppy and CD so I can add additional HDs (its a small box but well ventilated).
Another option I have is to use my bios 'network boot' option, but I have no clue how to use it and the only description in the mb manual says "Allows system to be booted over a network" In network boots, *usually* one is given an option of specifying a device address, and the network boot executes a boot protocol (e.g. bootp), and the boot image file is downloaded to the target, stored and run out of RAM. No evidence of this behavior is exhibited when the network boot option is selected in the bios...
I know that boot partition is possible to create within debian distribution that has grub 2.0, as I have done before with ubuntu. I have been trying many different options with my preseed file but it keeps taking the boot partition out of LVM and creating and extended partition too and then creates the LVM primary partition.
### Partitioning. # you can specify a disk to partition. The device name can be given in either # devfs or traditional non-devfs format. For example, to use the first disk
how, and if, I enable 3Dnow, and other CPU related features?
I'm not having any problems or anything to that effect. I am only curious. Is this something that's automatically done? Is this something I must do during compile and install of applications?
haunted@haunted-desktop:~$ sudo grep flags /proc/cpuinfo flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
If this is something I must enable manually per application, then for example, if I wanted it enabled for FlightGear, how would I go about doing that?
I just blindly install 'java' in GNU/Linux Debian SID -- so I could use it as a plugin for iceweasel -- Unfortunately, things didn't work as expected. I was used to Debian's APT to take care of things for me as it had done for more years than I could remember. (Being a desktop user/programmer and a beginner system network admin). I want a clean install of java plugin for iceweasel. So I want to remove completely all java related packages --
How do I know which is which and if they are safe to remove without affecting any other part of the system? Now, to install -- what do I need to install in order for iceweasel to have the Java plugin and let java work as it should? I prefer from the Debian package. But if it doesn't work, I'll accept JRE from the java site and install them myself.
how to display the modules related to my wifi card, using lsmod all the kernel modules are displayed but I would like to display just the related to my wifi, is there a way to do this?
On a bunch of servers, we use integrity checking tool on a large amount of data. Therefore, we compute SHA1 hash from a lot of files everyday. The CPU is a "generic" one, enough powerful for normal use, but get's totally saturated when integrity check begins. Is there any kind of server using a crypto-processor so as to delegate crypto functions to this dedicated processor?
How do you find what typs of crypto ciphers are supported.? I've dumped out /proc/crypto, which lists out a bunch of types, but none of the names listed seem to work. So far I have only got a couple types to work, the default(when I don't supply cryptsetup any cipher type) aes-cbc-plain and aes-ecb.
Since I don't even see aes-cbc-plain in /proc/crypto
Linux ulet 2.6.26-2-686-bigmem #1 SMP Tue Mar 9 18:01:52 UTC 2010 i686 GNU/Linux
In order to get a newer kernel that would recognize a linksys usb wifi adapter I got the advice to upgrade to a newer kernel - 2.6.30 or newer. Which I am able to get from backports.
But when I try with .30 or .32 my machine will not boot. I do have a raid, but it is only used for data files - I do not boot from it or have any system files on it.
First I get this error:
I have not resumed the machine so I have no idea what is going on. So I press ENTER:
I installed Debian, apparently without KDE or gnome capabilities. At least that's what it tells me when I try to follow instructions for installing same. So, I figured I created an image of an installation disk without those, or OpenOffice, or Xwindows capabilities - (debian-505-i386-xfce+lxde-CD-1.iso). So I created another image on CD of debian-505-i386-CD-1.iso, which I planned to install over the original install. However, I cannot get the computer to boot off the CD anymore; it always reverts to the Boot Menu (I have Windows and Debian partitions). The disk whirs around for a while, and then the multiple OS boot menu comes up. This is all being driven by the fact that I don't seem to have a working copy of OpenOffice.Org installed. Although I have managed to play around with mounting and unmounting the CDROM, and using the file commands, I don't seem to be able to actually get an application working. I downloaded the complete OpenOffice.org installation from their website, and extracted all *.deb files to CD. I attempted to unpack and install the OpenOffice.org files directly, and it seemed to do that, but the program does not seem to be available to me. I figure my best option is to reinstall with the right image.
Warning: NooB typing this. Two days ago I replaced an old version of Kubuntu with Squeeze. (This is not the computer/system I've written about in two recent threads.) Installation went smoothly, but one very early boot (I think the very first after installation) halted very early on, with:Waiting for /dev to be fully populated... [ 4.051267]ACPI: I/O resource 0000:00:1f.3 [0x1c00:0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f]I stared at that for a very long time, used another computer to google for clues on what to do about it, couldn't find any text that I could understand -- I don't have a degree in anything computer-related, I'm just Joe Blow who wants to get things done on a computer without malware scares -- and eventually gave up and rebooted.
The reboot went well and I hoped there'd just been some kind of fluke. Just now, however, booting -- for perhaps the second or third time since the frozen mis-boot -- brought an elegant message telling me of a kernel failure and asking me if I wanted to inform whoever of it. (Yes, I responded.) The computer seems to be working fine: I haven't rebooted it since that error message, yet here I am browsing and posting away.Unlike this person, for example, I don't know what the hell I'm doing. (Well, I do know that he's using SuSE, I'm using Debian Squeeze, and they're not the same.)The computer's a circa-two-year-old laptop; I doubt that it's flaky because I there were no (visible) boot problems with Kubuntu just last week. I haven't installed anything other than from debian.org's squeeze repository. The mouse that's plugged in now isn't the same as the trackball plugged in yesterday, but that's the extent of any "hardware changes".If this computer fails to boot one time in four and at other times gives scary error messages that I can safely ignore -- well, I can live with that. But my guess is that it's more like an oil pressure warning light in a car: that I ignore this stuff at my peril.
I installed squeeze on virtualbox on arch linux.After squeeze is booted up, ifconfig says no ip address is given to eth0.I tried ifdown/up eth0, then an ip address was properly given.Does anyone have the same problem or know how to solve this?The network of virtualbox is set to bridged adapter.The host os has only eth0, no br0 and wiredly connected to a wifi router which has the dhcpd.
I want to add a boot up splash screen to my Debian installation but I cannot find a splash screen manager in the repos. I understand why Debian likes to have no splash screen initially, but have they opted to not have splash screens at all in the repos?
I have this machine (motherboard ITX Jetaway NF94-270-LF based on CPU Atom N270, full specs here) as a server for some time now (about 4 years). Debian 8.1 is installed on it.
Two days ago, after a power failure, the machine was not able to complete the boot process. I attached a keyboard and a monitor (on VGA port, the motherboard also as a DVI one, but I don't have a suitable monitor) to be able to see what's happening and interact with the machine. Unluckily, at a certain point during the booting sequence the screen goes blank and the monitor goes in standby mode; apart from that, the boot process continues in the background.
As far as I can recall, this behaviour existed for at least a couple of years (if not from the beginning) and the boot process was always completed successfully until two days ago.
The screen goes blank after the setup of the keyboard mapping. I tried everything to avoid the screen going blank: in the Grub menu I set the "vga" parameter, the "nomodeset" parameter, the grub_gfxmode parameter, I removed the "quiet" option, I removed the "load_video" line, I forced the BIOS to only use the VGA port for the video and so on, in order to disable or configure differently the video and the framebuffer. All these stuff had no effect at all: the screen keeps going blank at the same point during the boot process.
The only way I was able to use a fully booted system through keyboard and monitor was via the rescue mode of the Debian 8.1 netinst image. But that way, of course, I wasn't able to observe the normal boot process. So, I checked the boot parameters of the rescue mode and I found that the only usefull parameter was "vga", which I already used and was ineffective.
