Debian Configuration :: System Won't Boot Properly After Crash During Upgrade
Feb 7, 2016
I am on debian jessie. I ran "apt-get update && apt-get upgrade" and midway through the upgrade my computer suddenly rebooted.
I wasn't paying close attention to the upgrade process so I didnt see if there was any error messages right before the reboot. The laptop was plugged in, fully charged and I've never had issues with overheating.
When I boot now I get to a shell with a message that says:
Code: Select allWelcome to emergency mode. After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
If I try "systemctl default" there's a message that simply says "Hangup", nothing else happens.
Looking through "journalctl -xb" I see this:
Code: Select allFailed to insert module 'autofs4'
Failed to open /dev/autofs: No such file or directory
Failed to initialize automounter: No such file or directory
Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
Failed to start Load Kernel Modules.
If I retry "apt-get upgrade" it says:
Code: Select alldpkg was interrupted, you must maually run dpkg --configure -a to correct the problem
If I run "dpkg --configure -a" stops at the package cups-browsed with message saying "Hangup"
Output of a few commands I saw in another forum thread:
$ lsmod
Code: Select allModule         Size Used by
ext4Â Â Â Â Â Â Â Â Â 473802Â 1
crc16Â Â Â Â Â Â Â Â Â 12343Â 1 ext4
mbcache        17171 1 ext4
jbd2Â Â Â Â Â Â Â Â Â Â 82522Â 1 ext4
[Code] ....
Is this fixable without jumping through too many hoops or should I just reinstall the system? I need the computer for work so Im not gonna spend days trying to fix it without reinstalling.
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
I am running Debian on an ARM module (BananaPi).5 minutes ago, i started upgrading the system, but fortunately the power cable moved and the system closed.Now i open it up again and i'm trying to re-upgrade the system but i'm always getting this message
# apt-get upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:" "Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
I have always used apt-get to update the system. Yesterday, I was doing some tests and one of them was to try to update the system using the aptitude command, instead. I ran aptitude update and then aptitude safe-ugrade. I thought that wouldn't be a problem, but I was wrong. This morning I found the computer just can't boot.
I get this message:
I have Squeeze in another partition on that computer. I can access the system through the terminal (the graphic is screwed). Is it possible to try my Lenny from this partition? If not, I also have a live cd for Squeeze. Right now I'm on another computer.
I've installed 6.0.1a on my xi3 box [URL] and it works great. However when I remove the monitor and keyboard it doesn't boot (I don't know how far it gets, there is no monitor...). I did not install, and do not want, any kind of GUI interface, command line only. This is going in a closet as a solid state rsync backup repo. I have another small system (not this exact one) running Lenny that runs just fine headless - is this some kind of Squeeze regression? Is there any way I can get this running headless (I can't run Lenny on this box because I don't think the Marvell GbE driver is there or is working in Lenny.
I have a Dell studio running ubuntu for two years now. I had ubuntu 10.04, but a few days ago, the update manager started to bug me that some stuff don't work properly and that I need to to a partial upgrade. I postponed that for a while, and all worked fine, but I finally had sometime and clicked "yes", all began collapsing:
1) the update manager crashed while updating.
2) I rebooted and ran it again. same crash at the same stage.
3) I decided, god knows why, to do a full upgrade to 10.10, which also crasehd.
Now it won't even boot. It always get stuck at a line saying "no IPv6 routers present" or something of that sort. when I switch off manually the wireless switch on the laptop, the boot gets stuck a bit earlier, on a line that says: "laptop login:"
EDIT: I just remembered something which might be important: I had a hibernation problem on the upgrade to 10.04, so I played around a bit with that. now it uses libgcrypt, and I remember I set up something manually then, but I can't remember what.
I want to build a custom system and I need your opinions. I have an old laptop which I want to configure as a system for troubleshooting purpose, my idea is to have multi-boot system with multiple root file systems, e.g. one root file system has only BIND to work as DNS server, another root file system has only Samba, etc., and I can choose which system to boot into from grub, or a custom menu after booting grub.
I thought of setting multiple partitions and install a full system on each one, but I thought that there might be a better way to do this, I'd like to hear your opinions.
I have just recently installed firestarter to get an idea of iptables editing with a GUI. Firestarter works great and I love it, however when I turn my system on, and my system is booting up the terminal displays a "Failed" message when attempting to start up firestarter. Now I have been doing my homework (reserch) and have read that a user will get this error because firestarter trys to load prior to the network manager starting up. I have also read some other variables that can cause this is if you use network manager and have a password on your user account (which I do have) can cause this issue.
However in most cases from what I have read is even though it gives the user a "Failed" startup message, once the user logs in, and is connected to the internet firestarter will actually load the iptables. I did some tests and from what I understand I can see that this is true because I have allowed access to certain torrent trackers, and denied access to others, and I can see some come online. Does firestarter load iptables once the user logs in? Or once it fails to load, does it not load at all unless you manually open/load the application. If firestarter just modifies iptables, then once I save my listings in firestarter then I really don't need it to start up correct?
I use Debian testing for six months and I started used it six months ago. I use apt-get distupgrade for long times , but today after apt-get update and apt-get dist-upgrade , my system reboot and can not boot and I see URL...and system can not , I see this errors after grub
Was running the upgrade through the manager this morning and the download got about 3/4 of the way and froze up making the system unresponsive I left this for an hour to see if it would resolve its self but no luck so as the installation hadn't begun I hit the power button. BIG mistake now when I try boot to 9.10 it hits a black screen with white ubuntu logo much like 9.10 but no loading bar. it just hangs at this now. I am currently posting this from a live usb I made from an ISO of 10.4 i downloaded on my girl friends windows machine. Is it possible to either fix the 9.10 installation or update the files on the 9.10 installation to 10.4 from the live disk(I have the option to make a 9.10 live disk if needed)?
First of all, my computer is running Debian Jessie. uname -a gives me this output: Code: Select allLinux felix-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
So today I updated my system with aptitude update and aptitude upgrade, and there was few paquages that were updated. Among them was one "linux-image" or "linux-headers". I believe that it is linked to this security update: [URL].... .
During the time aptitude upgrade was running, I was simply surfing on Iceweasel. However, it seems that my system suddenly restarted, without asking me the permission or without notifying me. It really looked like I pressed the restart key, but I actually didn't. My computer battery was full charged and plugged in. So, I do believe that it is my system that rebooted himself after the aptitude upgrade was completed (or even during the upgrade, I don't know).
So my computer restarts, and brings me to GRUB menu: I boot Debian and then I get the usual [ OK ] ***** lines telling that the system boots normally. But this time, I get some errors:
Code: Select all[FAILED] Failed to set up automount Arbitrary Executable file format file system Automount point ... [FAILED] Failed to start load kernel module ... [FAILED] Failed to mount /boot/efi [DEPEND] Dependency failed for Local File Systems
I arrive then in Emergency mode with this message: Code: Select all Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
I tried systemctl default but it doesn't boot my system normally. I also tried Control-D but it just reprints the same message. And finally I typed journalctl -xb, which gives me a long log file (855 lines) that I do not understand.
I would give this log file, but it seems that my internet connexion is broken (because of the kernel, I mean), even with an Ethernet cable. So I can't connect with ssh to the computer I use at the moment, and I can't either send it to myself by mail. I tried to mount an usb key, but it seems that any key won't be mounted because of a kernel problem.
An obvious solution to my problem may be to come back to an older kernel version. However, only the lasted kernel version (x86_64 Linux 3.16.0-4-amd64) is installed. dpkg --list | grep linux-image gives me indeed:
Code: Select alliF linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 amd64 Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
I do not know how to come back to an older kernel, as far as I haven't any internet connection and as far as I seem to not be able to load an usb key.
I tried assuming that the touchpad was a synaptics device and configure it as such, but it wasn't and this caused X to crash. (I also tried piping the output to grep -i and search for some key terms).
I've got a server with bit of chaos on it. There is similar data on different partitions which I like to mount remotely with samba. So I setup aufs on the server and then share the merged aufs directory (as read only). All seemed fine, and I was able to mount it nicely. However, when I enter the directory in question does the kernel on the mounting puter start misbehaving.
First it freezes for about a minute. Then I get a bunch of oops-looking messages in dmesg and the system eventually locks up totally. This is what it looks like:
I run an old Toshiba Satellite M35x S114 Laptop with Debian Testing, it always runned smoothly - although it IS testing . Since the latest update to kernel 2.6.32 , the X server just freezes. The init goes all the way to gdm, and then a blank screen , no mouse pointer, no way to get out of this screen (not CTRL+ALT+BACSPACE not CTRL+ALT+F1 / F2 ... etc) just a hard reset.
I can boot to the older .30 kernel with absolutely no problem, gdm starts normally login successfull (as I am able to write this on the reffered machine and all).
Here comes the gory details:
>>> The graphic card: lspci | grep gra 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) >>> When it works with .30 kernel: cat /var/log/Xorg.0.log code....
Noting that there are no more Modlines in the new Xorg.0.log
Besides, X is disabling the mouse and keyboard in the configuration.
I've got a problem with touchscreen (NNK Switches 5.7" model: FT-CU04B). It is not supported under Linux, but I managed to get it working with usbtouchscreen module, after some modifications of course. It gets recognized by system now, it is possible to calibrate it correctly through xinput_calibrator but it isn't possible to "left click with it". I know that it's weird so I want to make myself clear - touchscreen recognizes touch - when touching button for example, it reacts with "going down" but when I'm releasing button, it "goes up" again, without action. I've tried mapping left mouse button with xinput set-button map 1 0 0 0 0 0, but without success, buttons remain "unclickable".
lsusb: Code: Select allBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
When trying to do a system update, I'm facing following error:
Code: Select allroot@machine: apt-get upgrade Reading package lists... Done Building dependency tree    Reading state information... Done The following packages have been kept back:  libdevmapper1.02.1 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed.
[Code] ....
No such file or directory of an older and unused kernel? What's wrong with my system?
More about my machine, which runs Debian 6: Code: Select allroot@machine: uname -a Linux machine 2.6.32-5-686 #1 SMP Sat Jul 12 22:59:16 UTC 2014 i686 GNU/Linux
Code: Select allroot@machine: cat /etc/apt/sources.list deb http://http.debian.net/debian/ squeeze main contrib non-free deb-src http://http.debian.net/debian/ squeeze main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free deb http://http.debian.net/debian squeeze-lts main contrib non-free deb-src http://http.debian.net/debian squeeze-lts main contrib non-free
I'm running Testing and need to pass some parameters to my bttv tv tunner card, for this reason I created the following file /etc/modprobe.d/kozumi.conf with this content:
alias char-major-81 videodev alias char-major-81-0 bttv options pll=1 radio=1 bttv_verbose=1 card=151 tuner=38 gbuffers=4
The problem is that for some reason this options aren't properly set after booting the computer, I've tried different combinations for line 1 and 2 without success.
I'm used to rmmod the bttv driver and modprobe manually with those settings but I'd like to automate the process.
I tend to get constant crashes when using internet browsers ( Google Chrome and Firefox ) basically the application hangs not moving in any way, then eventually completely freezes up, the system then locks up and finally crashes.
Upon system re-start I get "Read Error" at boot ( No further information, it literally just says "Read Error" ).
It is sometimes fixed by going into the BIOS and select "Hold on No Error".
I tried installing OpenBios to see if using different BIOS firmware would resolve the issue, but the OpenBios install failed ....so no dice there either.
I am trying to work out if it is a hard drive problem or if it is purely a problem with Fedora.
It was working fine for a couple of months and when it does boot up ... the system works fine, ( Until another crash ).
It seems like the internet browsers crash the system and then the system crashes and can then no longer remember how to boot up.
what this could be that could be software based....if not it looks like I will need a new hard-drive.
System continues to boot OK and everything seems to work fine as I expect. I am not sure what the above causes. It looks related to USB, but I am not sure. lsusb gives:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The announcement of several new make scripts in the 2.6.32 release notes is very exciting.1.8. Easy local kernel configuration.Most people uses the kernel shipped by distros - and that's good. But some people like to compile their own kernels from kernel.org, or maybe they like following the Linux development and want to try it. Configuring your own kernel, however, has become a very difficult and tedious task - there're too many options, and some times userspace software will stop working if you don't enable some key option. You can use a standard distro .config file, but it takes too many time to compile all the options it enables.
To make easier the process of configuration, a new build target has been added: make localmodconfig. It runs "lsmod" to find all the modules loaded on the current running system. It will read all the Makefiles to map which CONFIG enables a module. It will read the Kconfig files to find the dependencies and selects that may be needed to support a CONFIG. Finally, it reads the .config file and removes any module "=m" that is not needed to enable the currently loaded modules. With this tool, you can strip a distro .config of all the unuseful drivers that are not needed in our machine, and it will take much less time to build the kernel. There's an additional "make localyesconfig" target, in case you don't want to use modules and/or initrds.
I'm not really sure what the problem is here, but sshd does seem to start on system boot. tty1 does list "OpenBSD Secure Shell server" at least. Also, # service --status-all; indicates that sshd is running, but if I try and actually ssh into my box, I get a "Connection refused" response.
I am, however able to restart the service manually and everything magically works again. Odd...?
I am using Squessze and Gnome. When I try to use the gui System>Administration>Network or Users and Groups I get the error The configuration could not be loaded. You are not allowed to access the system configuration.Everything was working before. I read around a bit. In some cases,it was caused by mismatching group and password files after using the gui. I do not know how to check if they are matching. Of course I do not know for sure that is the problem in my case.
I have an hp pavilion 15-b106ed with UEFI. I disabled secure boot and installed debian jessie form the CD1 iso (RC1 installer) burned to an USB key. Installation went smoothly, but after rebooting I get grub's terminal-like screen saying:
"GNU GRUB version 2.02 beta2-9ubuntu1. Minimal BASH-like line editing is supported... etc"
The problem is that as soon as I turn on the computer that grub screen shows up and I can't boot from USB anymore nor access the BIOS settings, no matter how fast I press F9, F10 and such. I guess I have to tell him to boot from the USB using the grub terminal...
