Conversation
Notices
-
aaaargh! I cannot reboot Nikola ( !Debian ) - I keep getting into "Emergency mode", did disk checks in maintenance mode, don't know what else to do #help!
-
did this happen out of blue? or anything (hardware) changed before last reboot? never had this, so guessing into blue: 1. start a live cd and chroot and check for stuff like logs 2. I assume you consulted your fav. search engine with this already? boot "Emergency mode" debian
-
@erkanyilmaz there were a load of updates and I went through them all; I've also been making changes to fstab but after some initial grumbles all drives seem to mount normal; emergency mode gives me a few things to try, but I need to log in (as root); tere's no net in emergency mode. looked through log, but like I said first some grumbles, then thnigs seem to load normally
-
@erkanyilmaz this http://forums.debian.net/viewtopic.php?f=5&t=116524 tells me that "sometimes things break on testing". I know - but I need it for workable graphics software...
-
@erkanyilmaz also, I tried to edit fstab (to comment out some things) but vi complains it's read-only (even thogh I'm editing as root) ???
-
@mk Either / is still mounted readonly (this is normal in early stage of startup) or you are inside an initrd (initial RAMdisk) @erkanyilmaz
-
@mk try mount / -o remount,rw @erkanyilmaz
-
@mcscx but all drives were mounted. I used a rescue CD, checked all extX devices (again, no problem), removed data from /var (while nothing mounted there), edited fstab and commented out a bunch of things; also disabled the systemd's emergency.service & emergency.target (so I could not get stuck there); then rebooted (with a few wrinkles). now Nikola *does* reboot, but has no network (which probably was the main problem in the first place). for all this, I picked up some hints from here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757072
-
@mk oh. I'm still on Debian Wheezy know nothing about systemd yet.Looks like startup is messed up & network init script & others not started
-
@mcscx yes - NetworkManager (no longer called network-manager) lives in /usr/sbin, dated 2 Sep so this seems to have come with the recept updates. But I cannot start that from the commandline (it just returns) ... maybe I need to use systemd for that?
-
-
-
@mcscx s, no I need to figure out how to get network back :( (the rescuecd DID have network, so it's not the hardware or the modem)
-
@mk on the fly you could try (assuming you're still using Fritzbox) ifconfig eth0 192.168.178.2;route add -net 0.0.0.0 gw 192.168.178.1
-
@mcscx what is the .2 and the .1 in that? FRITZ!box's IP is 192.168.178.1; btw, the LAN works: I just found I could connect to the #NAS via samba (at least I can see the shared folders)
-
@mk the .2 was meant to get yourself a an IP.But as you say you actually *have* network,just no internet.May be either 1)no routing 2)no DNS
-
-
@mcscx also, NetworkManager is actually running, but the GUI applet network-manager-gnome seems to have gone missing. looks like I hit some in-between state where the network stuff isn't fully working (or even present)
-
@mk Sounds like "a complex situation". I dont use NetworkManager on most of my machines (only on some notebooks). It adds to complexity.
-
@mcscx it is... I'm still finding hints and trying things, but no joy so far; just edited /etc/network/interfaces and replaced the 'allow-hotplug eth0' by 'auto eth0' (it seems the former may cause problems); then again ifconfig eth0 up and networking restart - no joy. going to dump my terminal sessions in text files and try to reboot... #ihaterebooting
-
-
-
@mcscx *sigh* eth0 is UP and RUNNING; also tried 'ifconfig eth0 up' (seems to toggle UP status) followed by '/etc/init.d/networking restart' (says it's OK); also rebooted FRITZ. still no internet...
-
@mk probably you can ping 192.168.178.1, but not ping 8.8.8.8 (google). Then the route is missing. Or try ping heise.de to see if DNS works
-
@mcscx I FOUND IT!!! For the whole new networking set up I had changed some IP adresses around - and apparently not rebooted since then. Turns out the /etc/network/interfaces file had the wrong gateway and primary DNS. (apparently I had adapted that IP address in the FRITZ comnfig though I can not remember that). Once I edited those, a domain name I was pinging 1)) resolved and 2) responded.
-
@mcscx thanks for the help and 'handholding'! @erkanyilmaz, too! (the network manager applet for the tray is still missing - I may hav to reinstall that...). the whole thing was complicated by the fact that apparently also a slight error in fstab can trip up systemd as well - so it was a situation with several things combined - no wonder it was hard to figure out
-
@mk maybe that means NetworkManager isn't running at all, b/c as soon as it takes control network/interfaces will be ignored (AFAIK)
-
@mcscx but if I can see it in task manager it's running isn't it? the tray applet is just a GUI to control the NetworkManager, and options entered in there do end up in the normal configutation files. I like it especially on the laptop or netbook because it gives a quick way to select an appropriate Wifi access point.
-
-
-
@mcscx btw I normally use three 'layers' for pinging: 1) the modem (now FRITZ @ 192.168.178.1) 2) a DNS server of my ISP 3) one of my (live) domains, with a short name
-
-
-
-
-
-
-
