I have an issue with some of our debian 8 servers. Sometimes our servers refuse to boot. We try to check some disk and memory issue but we found nothing. We think about a network issue (our server in the screen has many failover IPs), so we try to reduce the network configuration to the minimum (only lo and eth0 configuration). The network connectivity is working right (all alright in rescue mode and alright when the server success to boot).  Screenshot of the boot process
122431
I have multiboot Debian with others Unix/linux distro. During the boot process ,i get the following error:  A start job is running for dev-disk by \x2duuid-.....1min:30 s Dependencies failed for swap   After 1min : 30 s the boot process continued without problem , How to solve it?
117106
After the most recent kernel upgrade, my system hangs during boot.  Since my machine seems especially persnickety about pulling up the grub menu*, what is the best way to set the previous kernel as the default until the next upgrade?  *I have to hit ESC at exactly the right moment, which usually means rebooting several times until I get it.
78563
I have a dual boot laptop (Windows 10). I ran general updates and now my Ubuntu won't boot.   I ran in recovery mode and still it freezes in the same place.      Kernel panic – not syncing: Attempted to kill init! exit code=0x00007f00
82365
A colleague once told me that the last option when everything has failed to debug on Linux was to use .  I tried to learn the science behind this strange tool, but I am not a system admin guru and I didn’t really get results.  So,   What is it exactly and what does it do? How and in which cases should it be used? How should the output be understood and processed?   In brief, in simple words, how does this stuff work?
45730
I have 4 servers with Debian Wheezy OS. I have Apticron installed that informs me about updates. Debian updates are realized so often that when I finish to update the last of 4 servers I get new email about new updates on the first server. I try to update all servers when I get a notification but I never know if there is a need to reboot the servers. I have read that if the directory "/var/run" contains file "reboot-required" I have to reboot the server. But I never have seen this file in "/var/run". How can I know when reboot is required? I don't want reboot my servers every time when I install new updates if it's not needed.  I understand that if I update PHP or MySQL, etc I don't need to reboot the server but updates usually contain many "lib...".  Below are 9 updates (I have received this week).  krb5-locales 1.10.1+dfsg-5+deb7u3 libdbus-1-3 1.6.8-1+deb7u6 libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 libk5crypto3 1.10.1+dfsg-5+deb7u3 libkrb5-3 1.10.1+dfsg-5+deb7u3 libkrb5support0 1.10.1+dfsg-5+deb7u3 libruby1.8 1.8.7.358-7.1+deb7u2 libxml2 2.8.0+dfsg1-7+wheezy3 ruby1.8 1.8.7.358-7.1+deb7u2   I have no idea what is "libkrb,libgssapi", etc. How can I detect if reboot is needed? Please do not suggest to install UnattendedUpgrades to let the servers update automatically because this can cause websites going offline if something updates not correct.
2927
I am experiencing an issue on Centos7 when attempting to start the network service. I receive the below error message.  Failed to start LSB: Bring up/down networking   The issue arised when I realised it wasn't taking my static IP address from the /etc/sysconfig/network-scripts/ifcfg-eth0 file (found below).  DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.0.16 NETMASK=255.255.255.0 HWADDR=B8:27:EB:C3:1E:EC NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet   On reboot, the device would load with IP address of 192.168.0.7, clearly not that static IP address assigned, and not sure how it is getting information of a DHCP server (which I do have, my router)  I attempted to disable the NetworkManager, as this might have been causing havoc with the network service by issuing the below command.  systemctl stop NetworkManager   and then enable network  systemctl start network   again the same error came up, I then killed the dhclient process, and attempted to start network service once more and again got the same error.  Losing patience, since I did have connectivity to the internet at the time on the server through the DHCP IP, performed a "yum remove Network Manager" and tried a reboot, again to no avail. I'm not sure if that was a good idea or not, but hey it wasn't working anyway.  I seem to have exhausted suggestions I could find on the internet. Wondering if anybody else has any idea what might be going on.   edit: one more note, this is not a VM or related to Virtualisation in any way. This is simply a RaspberryPI 3  Many thanks.  Edit: Log entries:  Jan 01 00:00:06 &lt;hostname&gt; systemd[1]: Starting LSB: Bring up/down networking...  Jan 01 00:00:06 &lt;hostname&gt; systemd[1]: network.service: control process exited, code=exited status=6  Jan 01 00:00:06 &lt;hostname&gt; systemd[1]: Failed to start LSB: Bring up/down networking  Jan 01 00:00:06 &lt;hostname&gt; systemd[1]: Unit network.service entered failed state  Jan 01 00:00:06 &lt;hostname&gt; systemd[1]: network.service failed
29167
Is there a workaround for ?  Problem: I want to have a network configuration on Debian with the following properties:   Automatically ifup network interface when a cable is plugged in boots without blocking for a long time when no cable is connected on boot not switching my init system   The standard way to do this would be the following snippet in /etc/network/interfaces:  allow-hotplug eth0 iface eth0 inet dhcp   However, this leads to the problem described in the linked bug report: The boot process blocks for >1min when no network cable is plugged in with the following message:  configuring network interfaces... ifup: waiting for lock on /run/network/ifstate.eth0   A workaround given in  seems to be changing allow-hotplug to auto:  auto eth0 iface eth0 inet dhcp   This effectively makes the boot blocking message disappear, however, the system now blocks right before a login prompt is shown at tty1. This time dhclient is blocking because it tries to get a dhcp reply on eth0, which is not connected, and waits for several attempts to timeout. The login prompt only appears after the dhclient timeouts.  For users with a graphical DE, this might not be a problem, as they don't need to log in on tty1, instead their DE boots and they never see the dhclient message.  Another workaround would probably be to use network-manager. Ideally, I would prefer to not use networkmanager, but as a last resort, I tried that. However, on Debian buster, network-manager's dependency chain conflicts with sysvinit-core, which is my init system.  The last alternative which comes to my mind is to not configure eth0 in interfaces(5). This makes all boot blocks go away, however, I need to manually ifup eth0 after plugging in an ethernet cable.  Any better ideas?  UPDATE: To address the quote from @sourcejedi, "allow-hotplug" is specified to "start interface  when the kernel detects a hotplug event from the interface" in the Debian docs under . Related questions:  and
106670
I have problem installing debian directly from hard drive. Say, i have a logical partition /dev/sda5 and there is debian DVD iso file located in (hd0,5)/iso/debian-8.0.0-amd64-DVD-1.iso with initrd file there too. Then I created grub menu entry with this:  menuentry "Debian Jessie (stable)" {     set isofile='/iso/debian-8.0.0-amd64-DVD-1.iso'     set initrdfile='/iso/debian-8.0.0-hdd.initrd.gz'     loopback loop (hd0,5)$isofile     linux (loop)/install.amd/vmlinuz iso-scan/ask_second_pass=true iso-scan/filename=$isofile     initrd (hd0,5)$initrdfile }   Booting is successful. But, when come to searching debian CD it fails. The iso file cannot be found by installer. If I use USB drive, every thing goes fine. In USB, I put debian DVD iso in `/boot/iso/debian-8.0.0-amd64-DVD-1.iso'. And the menuentry look like this:  menuentry 'Debian Jessie (stable)' {     set isofile='/boot/iso/debian-8.0.0-amd64-DVD-1.iso'     set initrdfile='/boot/iso/debian-8.0.0-amd64-DVD-1.hdd.initrd.gz'     loopback loop $isofile     linux (loop)/install.amd/vmlinuz iso-scan/ask_second_pass=true iso-scan/filename=$isofile     initrd $initrdfile }   My /dev/sda5 is formatted in NTFS and my USB drive is formatted in FAT32. So, I guess the problem is because of filesystem format. And if it is, how can I boot debian iso file properly from NTFS partition?  Update  The NTFS partiton is logical partition. Is it causeing problem too?
14415
I have a small server which I use for testing and programming. Currently it runs Debian 9.4 stretch with 4.14.0-0.bpo.3-amd64 kernel.  Today I tried to connect through SSH but I couldn't then I tried to ping it and it was unreachable. Therefore I had to hard-restart it by unplugging power cable. Then I went to  /var/log/syslog  and I found a strange line containing exactly 6140 characters like the following  ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@  then nothing else until new log entries of system restart. This is actually the first time it happens.  Does someone know what could it be?
69204
I have looked all over the Internet trying to find a fix, but I can't seem to find one. I have a custom built PC running an AMD processor, Nvidia graphics, 16GB of ram and a 1TB HDD for Ubuntu. I am not trying to dual boot, I just have Ubuntu 13.04 on the hard drive nothing else.  Every time I press 'Shutdown' or 'Restart', it goes through its normal shutting down thing; but, after that, there is just a black screen and nothing more. Nothing happens, it's just black. The only way for me to turn off Ubuntu at the moment is to press shutdown, wait for the screen to go dark, and then force shutdown it by pressing the physical shutdown button on the PC.  Could someone please tell me what is wrong and how I can get Ubuntu to work correctly? (Never had this problem when I was dual booting on my old HDD.)  P.S. I am able to log out.  After running Sudo shutdown it gave me an error this is the error:  'Modem-manger[5062]: Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory modem-manger[5078]:  ModeUbuntu 13.04rsion 0.6.0.0) starting... modem-manger[5078]: Could not get. . . . m bus. Make sure the message [FAIL] e   * Will now switch to single-user modenect to socket /var/run/dbus/system_bus_so root@mauritz-ubuntu:~# irectory'  And then just a ton of OK checking's, To me it seems like much of the text that it is displaying is overlapping on other text, so thats why it seems really weird.  Second error (running sudo shutdown as root): "sudo shutdown now *Disabling power management... [OK] Saned disabled; edit /etc/default/saned Speech-dispatcher disabled; edit /etc/default/speech-dispatcher  * Asking all remaining processes to terminate... [OK]  * Killing all remaining processes... [FAIL]  * Will now switch to singel-user mode"
46075
Why is it sometimes that I need to restart my computer after installing new software and at other times I don't?  Is there any reason why it needs this reboot or why it's not always one way or the other?
100332
Actually not debian, but Raspbian Wheezy to Raspbian Jessie. I upgrade it using some commands which found on Raspbian official forum.  cat /etc/debian_version = 8.0.  The problem is, I can't view any result when I restart the service.  Before upgrade(Wheezy):  # service tor restart [ok] cccc [ok] ddd # _   After upgrade(Jessie):  # service tor restart # _   And all results are written to /var/log/syslog... How can I revert this thing? I want to see actual result, not written to log.
94616
Since some system updates, my machine can no longer boot properly. I am no Ubuntu guru. I do not have a week to spare diagnosing the issue. I just want to retrieve important data from this machine's hard drive and get a working computer again ASAP.  What should I do?
115988
Our server: HP Proliant ml350p g8 has a single Xeon e5-2609 1.4Ghz processor. Our manager wanted to update it a little, so we looked at 2x E5-2609V2 processors...we ran it past HP Enterprise chat who said it was compatible.  We now have the new CPUs and when we installed them our Health LED was solid red and server wouldn't POST. We've tried each of the new CPUs individually and together but same result. We thought perhaps it was the BIOS (it was dated 2012!).  Our server is out of warranty so we initially wasn't allowed to download the latest BIOS, but our manager persuaded HP to give us the latest BIOS version (2015), which we have installed. Trying the CPUs again has the same result...server still won't POST  If anyone could please shed some light on what we have missed that would be great.  (We are in the process of getting quotes for HP Maintenance Contract - since we are past 30 days expired on our Warranty, so we can't get a care pack)
66895
I was at school SSHing to my homebox. All of a sudden, my connection was closed. Attempting to reconnect failed. When I returned home, I discovered that my computer was off.  Nobody was at my house and I am sure that I did not have a power outage.  How can I figure out how or why my computer shut off? Is there some log in /var/log that could point me in the right direction? Should there be a core dump somewhere that I should find? If so, how do I use core dumps?
95888
I installed Windows 10 on my Dell Precision T5400 a little over a week ago. It is a pretty old computer but it has two physical 4 core xeon processors, 32GB of Ram and a Crucial 525GB SSD. It is very speedy once it gets booted up and I have been using it for doing video editing and playing around with the new linux subsystem built in. The lengthy boot time is very inconvenient though. When installing it took forever to boot and each subsequent time has taken forever to boot. I actually thought it was just installing updates the first few times. I recently started trying to diagnose and repair the problem and I have only been able to narrow the excessive boot time down to the pre session init phase. I would also note that it takes just as long to do a safe mode boot without networking. I downloaded and installed the performance recorder tools but beyond seeing that it is something in the pre session init phase I am at loss as to what to do next. If someone could help steer me in the right direction I would greatly appreciate. I am unsure how to post the logs in this post but I will be glad to with some instruction. Thanks again in advance.
28679
I was given a laptop with a totally dead display. I do not want to pay to replace the broken display, but I would like to use the laptop as a server and connect to it via SSH to control it.  I have pulled out the internal hard drive from the broken laptop, and I want to install Debian GNU/Linux and the SSH server onto this HDD using a working Debian laptop.  However, the hardware in the two laptops is very different, and I am wondering what kind of problems I would run into when I plugged the drive back in to the laptop with the broken display because of this?  How would I make this work? What is the proper way for me to install a bootable copy of Linux onto a HDD that will be used by a computer with different hardware?