Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #176365 > unrolled thread

Urgent help needed - Debian boot hangs

Back to article view | Back to linux.debian.user

Contents

  Urgent help needed - Debian boot hangs hans@hanswkraus.com - 2017-01-06 15:40 +0100
    Re: Urgent help needed - Debian boot hangs Dan Ritter <dsr@randomstring.org> - 2017-01-06 15:50 +0100
      Re: Urgent help needed - Debian boot hangs hans@hanswkraus.com - 2017-01-06 16:00 +0100
        Re: Urgent help needed - Debian boot hangs Bob Weber <bobrweber@gmail.com> - 2017-01-06 16:40 +0100
        Re: Urgent help needed - Debian boot hangs Dan Ritter <dsr@randomstring.org> - 2017-01-06 17:20 +0100
    Re: Urgent help needed - Debian boot hangs Henning Follmann <hfollmann@itcfollmann.com> - 2017-01-06 16:00 +0100
    Re: Urgent help needed - Debian boot hangs David Wright <deblis@lionunicorn.co.uk> - 2017-01-06 18:20 +0100
      Re: Urgent help needed - Debian boot hangs hans@hanswkraus.com - 2017-01-06 20:20 +0100
        Re: Urgent help needed - Debian boot hangs Michael Biebl <biebl@debian.org> - 2017-01-06 21:20 +0100
          Re: Urgent help needed - Debian boot hangs hans@hanswkraus.com - 2017-01-06 22:00 +0100
            More info, still urgent :-)  [was: Re: Urgent help needed - Debian  boot hangs] hans@hanswkraus.com - 2017-01-08 11:00 +0100
              Re: More info, still urgent :-)  [was: Re: Urgent help needed - Debian boot hangs] deloptes <deloptes@gmail.com> - 2017-01-08 11:20 +0100
              Re: More info, still urgent :-)  [was: Re: Urgent help needed - Debian boot hangs] Lisi Reisz <lisi.reisz@gmail.com> - 2017-01-08 13:10 +0100
                [´Solved] Re: More info, still urgent :-)  [was: Re: Urgent help needed - Debian boot hangs] Lisi Reisz <lisi.reisz@gmail.com> - 2017-01-08 14:10 +0100

#176365 — Urgent help needed - Debian boot hangs

[Multipart message — attachments visible in raw view] — view raw

Hi, 

urgent help needed. After adding an iptable entry for masquerading my
local network and making it permanent with
the package "iptables-persistent" my Debian server doesn't boot any
more.
It hangs with the line:
A start job is running for LSB: Raise network interfaces. ( ... /no
limit)
The root file system where it boots from is on an Adaptec HW Raid
interface, the motherboard is a Asrock. 

I habe tried to boot from a live CD (by pressing F11 as the short boot
msg of the motherboard suggests), but with no avail,
the boot menue doesn't appear. I don't see the Grub menue, the screen is
momentarily blank.
The computer insists on booting from the Adaptec. 

Is there any chance to interrupt the booting process? The other command
windows (Alt-F2 .. Alt-F6) show only the line
A start job is running for LSB: Raise network interfaces. ( ... /no
limit) 

Kind regards,
Hans

[toc] | [next] | [standalone]

#176367

On Fri, Jan 06, 2017 at 03:32:01PM +0100, hans@hanswkraus.com wrote:
> Hi, 
> 
> urgent help needed. After adding an iptable entry for masquerading my
> local network and making it permanent with
> the package "iptables-persistent" my Debian server doesn't boot any
> more.
> It hangs with the line:
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit)
> The root file system where it boots from is on an Adaptec HW Raid
> interface, the motherboard is a Asrock. 
> 
> I habe tried to boot from a live CD (by pressing F11 as the short boot
> msg of the motherboard suggests), but with no avail,
> the boot menue doesn't appear. I don't see the Grub menue, the screen is
> momentarily blank.
> The computer insists on booting from the Adaptec. 
> 
> Is there any chance to interrupt the booting process? The other command
> windows (Alt-F2 .. Alt-F6) show only the line
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit) 

When you boot normally, do you get a GRUB menu flashing by? If
so, you can interrupt it there (try down-arrow) and edit the
boot line to change the init system to init=/bin/sh

Then you can mount your root filesystem r/w 
mount -o remount,rw /
and edit your iptables troubles away.

-dsr-

[toc] | [prev] | [next] | [standalone]

#176369

[Multipart message — attachments visible in raw view] — view raw

Am 06.01.2017 15:45, schrieb Dan Ritter:

> On Fri, Jan 06, 2017 at 03:32:01PM +0100, hans@hanswkraus.com wrote: 
> 
>> Hi, 
>> 
>> urgent help needed. After adding an iptable entry for masquerading my
>> local network and making it permanent with
>> the package "iptables-persistent" my Debian server doesn't boot any
>> more.
>> It hangs with the line:
>> A start job is running for LSB: Raise network interfaces. ( ... /no
>> limit)
>> The root file system where it boots from is on an Adaptec HW Raid
>> interface, the motherboard is a Asrock. 
>> 
>> I habe tried to boot from a live CD (by pressing F11 as the short boot
>> msg of the motherboard suggests), but with no avail,
>> the boot menue doesn't appear. I don't see the Grub menue, the screen is
>> momentarily blank.
>> The computer insists on booting from the Adaptec. 
>> 
>> Is there any chance to interrupt the booting process? The other command
>> windows (Alt-F2 .. Alt-F6) show only the line
>> A start job is running for LSB: Raise network interfaces. ( ... /no
>> limit)
> 
> When you boot normally, do you get a GRUB menu flashing by? If
> so, you can interrupt it there (try down-arrow) and edit the
> boot line to change the init system to init=/bin/sh
> 
> Then you can mount your root filesystem r/w 
> mount -o remount,rw /
> and edit your iptables troubles away.
> 
> -dsr-

Hi Dan, 

tanks for the help but I don't see a GRUB menu. Maybe it's there because
I get an info
from the screen: frequency out of range... After a dew seconds the
system beeps once
and continues booting. 

Kind regards,
Hans

[toc] | [prev] | [next] | [standalone]

#176371

[Multipart message — attachments visible in raw view] — view raw

On 01/06/2017 09:57 AM, hans@hanswkraus.com wrote:
>
> Am 06.01.2017 15:45, schrieb Dan Ritter:
>
>> On Fri, Jan 06, 2017 at 03:32:01PM +0100, hans@hanswkraus.com
>> <mailto:hans@hanswkraus.com> wrote:
>>> Hi,
>>>
>>> urgent help needed. After adding an iptable entry for masquerading my
>>> local network and making it permanent with
>>> the package "iptables-persistent" my Debian server doesn't boot any
>>> more.
>>> It hangs with the line:
>>> A start job is running for LSB: Raise network interfaces. ( ... /no
>>> limit)
>>> The root file system where it boots from is on an Adaptec HW Raid
>>> interface, the motherboard is a Asrock.
>>>
>>> I habe tried to boot from a live CD (by pressing F11 as the short boot
>>> msg of the motherboard suggests), but with no avail,
>>> the boot menue doesn't appear. I don't see the Grub menue, the screen is
>>> momentarily blank.
>>> The computer insists on booting from the Adaptec.
>>>
>>> Is there any chance to interrupt the booting process? The other command
>>> windows (Alt-F2 .. Alt-F6) show only the line
>>> A start job is running for LSB: Raise network interfaces. ( ... /no
>>> limit)
>>
>> When you boot normally, do you get a GRUB menu flashing by? If
>> so, you can interrupt it there (try down-arrow) and edit the
>> boot line to change the init system to init=/bin/sh
>>
>> Then you can mount your root filesystem r/w
>> mount -o remount,rw /
>> and edit your iptables troubles away.
>>
>> -dsr-
>>
> Hi Dan,
>
> tanks for the help but I don't see a GRUB menu. Maybe it's there because I get
> an info
> from the screen: frequency out of range... After a dew seconds the system
> beeps once
> and continues booting.
>

This is where your initial problem is.  Apparently your monitor can't sync to
the resolution your system is using during boot.  If you can try another monitor
that might have a better sync range.  Maybe try to jump into the bios setup and
see if there are any options that would affect the video resolution like setting
a generic VGA mode.  I've had this happen but I have been able to ssh into the
machine after it boots to try different grub options.
 
>
> Kind regards,
> Hans
>
>  




*...Bob*

[toc] | [prev] | [next] | [standalone]

#176373

On Fri, Jan 06, 2017 at 03:57:53PM +0100, hans@hanswkraus.com wrote:
> Am 06.01.2017 15:45, schrieb Dan Ritter:
> 
> > On Fri, Jan 06, 2017 at 03:32:01PM +0100, hans@hanswkraus.com wrote: 
> > 
> >> I habe tried to boot from a live CD (by pressing F11 as the short boot
> >> msg of the motherboard suggests), but with no avail,
> >> the boot menue doesn't appear. I don't see the Grub menue, the screen is
> >> momentarily blank.
> >> The computer insists on booting from the Adaptec. 
> >> 
> >> Is there any chance to interrupt the booting process? The other command
> >> windows (Alt-F2 .. Alt-F6) show only the line
> >> A start job is running for LSB: Raise network interfaces. ( ... /no
> >> limit)
> > 
> > When you boot normally, do you get a GRUB menu flashing by? If
> > so, you can interrupt it there (try down-arrow) and edit the
> > boot line to change the init system to init=/bin/sh
> 
> tanks for the help but I don't see a GRUB menu. Maybe it's there because
> I get an info
> from the screen: frequency out of range... After a dew seconds the
> system beeps once
> and continues booting. 

OK. Assume that the GRUB menu does happen while your monitor is
flickering, and tap the down-arrow key repeatedly. Hopefully you
get a stable monitor image displaying the GRUB menu, now without
a timeout.

-dsr-

[toc] | [prev] | [next] | [standalone]

#176368

On Fri, Jan 06, 2017 at 03:32:01PM +0100, hans@hanswkraus.com wrote:
> Hi, 
> 
> urgent help needed. After adding an iptable entry for masquerading my
> local network and making it permanent with
> the package "iptables-persistent" my Debian server doesn't boot any
> more.
> It hangs with the line:
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit)
> The root file system where it boots from is on an Adaptec HW Raid
> interface, the motherboard is a Asrock. 
> 
> I habe tried to boot from a live CD (by pressing F11 as the short boot
> msg of the motherboard suggests), but with no avail,
> the boot menue doesn't appear. I don't see the Grub menue, the screen is
> momentarily blank.
> The computer insists on booting from the Adaptec. 
> 
> Is there any chance to interrupt the booting process? The other command
> windows (Alt-F2 .. Alt-F6) show only the line
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit) 
> 

This usually happens if you use /etc/network/interfaces in combination of
systemd managed services.
Usually this happens if the network is not available (network card not
plugged in). In those case I had both not booting at all/hanging or a very
long delay.

Don't blame systemd. And use systemd-networkd for your network. It will
resolve the issue.

However how you get this running again... - good luck!


-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [next] | [standalone]

#176378

On Fri 06 Jan 2017 at 15:32:01 (+0100), hans@hanswkraus.com wrote:
> Hi, 
> 
> urgent help needed. After adding an iptable entry for masquerading my
> local network and making it permanent with
> the package "iptables-persistent" my Debian server doesn't boot any
> more.
> It hangs with the line:
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit)
> The root file system where it boots from is on an Adaptec HW Raid
> interface, the motherboard is a Asrock. 
> 
> I habe tried to boot from a live CD (by pressing F11 as the short boot
> msg of the motherboard suggests), but with no avail,

Timing may be critical: if your computer is anything like this one,
casually pressing Fx after the message appears is not going to work.
The next time you boot, press the key repeatedly from the very start.
That goes for both F2 (CMOS) and F12 (one-time menu) here.

> the boot menue doesn't appear. I don't see the Grub menue, the screen is
> momentarily blank.
> The computer insists on booting from the Adaptec. 

Once you hear the beep, pressing ↓ and ↑ is a good idea as that
should pause Grub at its menu, whether you can see it or not.
Does that happen? (ie booting never continues until you press
Return (up to several times if there are nested menu options).

(For most people, pressing ↓ and ↑ once each is idempotent,
so later pressing Return should run the default entry.)

> Is there any chance to interrupt the booting process? The other command
> windows (Alt-F2 .. Alt-F6) show only the line
> A start job is running for LSB: Raise network interfaces. ( ... /no
> limit) 

If you can get to Grub, the contents of
https://freedesktop.org/wiki/Software/systemd/Debugging/
might be useful.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#176385

[Multipart message — attachments visible in raw view] — view raw

Am 06.01.2017 18:14, schrieb David Wright:

> On Fri 06 Jan 2017 at 15:32:01 (+0100), hans@hanswkraus.com wrote: 
> 
>> Hi, 
>> 
>> urgent help needed. After adding an iptable entry for masquerading my
>> local network and making it permanent with
>> the package "iptables-persistent" my Debian server doesn't boot any
>> more.
>> It hangs with the line:
>> A start job is running for LSB: Raise network interfaces. ( ... /no
>> limit)
>> The root file system where it boots from is on an Adaptec HW Raid
>> interface, the motherboard is a Asrock. 
>> 
>> I habe tried to boot from a live CD (by pressing F11 as the short boot
>> msg of the motherboard suggests), but with no avail,
> 
> Timing may be critical: if your computer is anything like this one,
> casually pressing Fx after the message appears is not going to work.
> The next time you boot, press the key repeatedly from the very start.
> That goes for both F2 (CMOS) and F12 (one-time menu) here.
> 
>> the boot menue doesn't appear. I don't see the Grub menue, the screen is
>> momentarily blank.
>> The computer insists on booting from the Adaptec.
> 
> Once you hear the beep, pressing ↓ and ↑ is a good idea as that
> should pause Grub at its menu, whether you can see it or not.
> Does that happen? (ie booting never continues until you press
> Return (up to several times if there are nested menu options).
> 
> (For most people, pressing ↓ and ↑ once each is idempotent,
> so later pressing Return should run the default entry.)
> 
>> Is there any chance to interrupt the booting process? The other command
>> windows (Alt-F2 .. Alt-F6) show only the line
>> A start job is running for LSB: Raise network interfaces. ( ... /no
>> limit)
> 
> If you can get to Grub, the contents of
> https://freedesktop.org/wiki/Software/systemd/Debugging/
> might be useful.
> 
> Cheers,
> David.

Thanks to all who have helped. I've proceeded a bit further. 

My monitor/keyboard/mouse were connected via a Aten monitor switch which
somehow swallowed
the first key presses. I think the system now waits at Grub for the
input. I still get the screen msg"switch to 90 khz/60 Hz". A second
screen only outputs 'Out of range'. 

I get now the Boot menu, but I don't see the DVD drive. 

When I press 'Arrow down' and Enter after the beep I get more messages
from the system boot.
It seems that the first network interface 'eth0' gets an address via
dhcp from my router. Then I geta msg about samba started and afterwards
the system hangs. I think it will now configure the second
network interface. Would it make sense to remove the network card for
the second interface (only the
first one is on the motherboard)? 

Any more tips for me? Since it's a bit late I will wait until tomorrow. 

Kind regards,
Hans

[toc] | [prev] | [next] | [standalone]

#176388

[Multipart message — attachments visible in raw view] — view raw

Am 06.01.2017 um 20:17 schrieb hans@hanswkraus.com:
> I get now the Boot menu, but I don't see the DVD drive.


> Any more tips for me? Since it's a bit late I will wait until tomorrow.

If you can get into the grub menu, then go to the advanced options menu
and select the recovery mode option.
This will boot into a rescue shell where ifupdown is not started.

I assume you have a dead lock in one of your if-up.d hooks in
/etc/network/if-up.d/

You could disable them one by one to find out which one it is.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [next] | [standalone]

#176389

[Multipart message — attachments visible in raw view] — view raw

Am 06.01.2017 21:12, schrieb Michael Biebl:

> Am 06.01.2017 um 20:17 schrieb hans@hanswkraus.com: 
> 
>> I get now the Boot menu, but I don't see the DVD drive.
> 
>> Any more tips for me? Since it's a bit late I will wait until tomorrow.
> 
> If you can get into the grub menu, then go to the advanced options menu
> and select the recovery mode option.
> This will boot into a rescue shell where ifupdown is not started.
> 
> I assume you have a dead lock in one of your if-up.d hooks in
> /etc/network/if-up.d/
> 
> You could disable them one by one to find out which one it is.

Hi Michael, 

I'm entering the grub menu only per guess. Both monitors I tried
displayed 'out of range'
btw. something similar. Is there a failsafe recipe for keypresses after
the beep to go to
the advanced options menu? 

I'm somewhat hesitating to buy a new monitor to only cope with that
problem. 

Kind regards,
Hans 

PS: I connected an external BluRay drive and see this in the BIOS boot
menu. Which
image should I burn to a DVD and what options should I select for
starting?

[toc] | [prev] | [next] | [standalone]

#176437 — More info, still urgent :-) [was: Re: Urgent help needed - Debian boot hangs]

[Multipart message — attachments visible in raw view] — view raw

Hi, 

I've found a monitor which was able to display the Grub menu. In the
"Advanced options for Debian GNU/Linux" I found the entries: 

Debian GNU/Linux with Linux 3.16.0-4-amd64
Debian GNU/Linux with Linux 3.16.0-4-amd64 (sysvinit)
Debian GNU/Linux with Linux 3.16.0-4-amd64 (recovery mode)
Debian GNU/Linux with Linux 3.2.0-4-amd64
Debian GNU/Linux with Linux 3.2.0-4-amd64 (sysvinit)
Debian GNU/Linux with Linux 3.2.0-4-amd64 (recovery mode) 

Each of them insists on starting the network. Is there any remedy? 

The boot & root FS is on an Adaptec 6405E HW raid controller. When I
boot from a Debian live DVD
I get the disks reported as "LVM2 Physical Volume".
I installed lvm2 via "sudo apt-get install lvm2". But when I try to
mount them I get the error
"Not able to mount a LVM2_member" (from memory; the wording cound be a
bit different). 

How do I mount the LVM2 volumes from a current Debian Live DVD? 

Kind regards,
Hans

[toc] | [prev] | [next] | [standalone]

#176438 — Re: More info, still urgent :-) [was: Re: Urgent help needed - Debian boot hangs]

hans@hanswkraus.com wrote:

> How do I mount the LVM2 volumes from a current Debian Live DVD?

to activate all volumes
vgchange -ay

to activate specific one
vgchange -ay VOLGROUP

[toc] | [prev] | [next] | [standalone]

#176441 — Re: More info, still urgent :-) [was: Re: Urgent help needed - Debian boot hangs]

On Sunday 08 January 2017 09:56:34 hans@hanswkraus.com wrote:
> Hi,
>
> I've found a monitor which was able to display the Grub menu. In the
> "Advanced options for Debian GNU/Linux" I found the entries:
>
> Debian GNU/Linux with Linux 3.16.0-4-amd64
> Debian GNU/Linux with Linux 3.16.0-4-amd64 (sysvinit)
> Debian GNU/Linux with Linux 3.16.0-4-amd64 (recovery mode)
> Debian GNU/Linux with Linux 3.2.0-4-amd64
> Debian GNU/Linux with Linux 3.2.0-4-amd64 (sysvinit)
> Debian GNU/Linux with Linux 3.2.0-4-amd64 (recovery mode)
>
> Each of them insists on starting the network. Is there any remedy?

sysvinit should start without the network eventually if there is a problem 
with the network (after a short delay), and recovery mode ought not to start 
the network. So are you quite sure that they all insist on starting the 
network?  By which I take it that you still mean that it won't start without 
it.

Lisi



> The boot & root FS is on an Adaptec 6405E HW raid controller. When I
> boot from a Debian live DVD
> I get the disks reported as "LVM2 Physical Volume".
> I installed lvm2 via "sudo apt-get install lvm2". But when I try to
> mount them I get the error
> "Not able to mount a LVM2_member" (from memory; the wording cound be a
> bit different).
>
> How do I mount the LVM2 volumes from a current Debian Live DVD?
>
> Kind regards,
> Hans

[toc] | [prev] | [next] | [standalone]

#176443 — [´Solved] Re: More info, still urgent :-) [was: Re: Urgent help needed - Debian boot hangs]

I received the following private reply.  Since it says "and all others" I am 
sending it to the list!  (with the subject header taken from my private 
reply)

Glad you got it solved, Hans.

Lisi
------------------------------------------
Hi Lisi & all others,

Am 08.01.2017 um 13:09 schrieb Lisi Reisz:
> On Sunday 08 January 2017 09:56:34 hans@hanswkraus.com wrote:
>> Hi,
>>
>> I've found a monitor which was able to display the Grub menu. In the
>> "Advanced options for Debian GNU/Linux" I found the entries:
>>
>> Debian GNU/Linux with Linux 3.16.0-4-amd64
>> Debian GNU/Linux with Linux 3.16.0-4-amd64 (sysvinit)
>> Debian GNU/Linux with Linux 3.16.0-4-amd64 (recovery mode)
>> Debian GNU/Linux with Linux 3.2.0-4-amd64
>> Debian GNU/Linux with Linux 3.2.0-4-amd64 (sysvinit)
>> Debian GNU/Linux with Linux 3.2.0-4-amd64 (recovery mode)
>>
>> Each of them insists on starting the network. Is there any remedy?
>
> sysvinit should start without the network eventually if there is a problem
> with the network (after a short delay), and recovery mode ought not to start
> the network. So are you quite sure that they all insist on starting the
> network?  By which I take it that you still mean that it won't start without
> it.
>
> Lisi

Yes, I am sure. I waited for both the the sysvinit and recovery mode for
approximately half an hour. Both got stuck at the network part.

I found the problem: I added the line: "iface eth0 inet6 dhcp" to
/etc/network/interfaces (I found somewhare on the net that this is a
good idea and my router has an IPV6 address). This gave all the
troubles.

The troublesome stanza:
----------------------------------------------------------------------
# The primary network interface
auto eth0
iface eth0 inet dhcp
iface eth0 inet6 dhcp
# iface eth0 inet static
#       address 192.168.1.100
#       netmask 255.255.255.0
#       gateway 192.168.1.20
#       # dns-* options are implemented by the resolvconf package, if 
installed
----------------------------------------------------------------------
After correcting it to:
----------------------------------------------------------------------
# The primary network interface
auto eth0
iface eth0 inet dhcp
# iface eth0 inet6 dhcp
# iface eth0 inet static
#       address 192.168.1.100
#       netmask 255.255.255.0
#       gateway 192.168.1.20
#       # dns-* options are implemented by the resolvconf package, if 
installed
----------------------------------------------------------------------
The system works again.

To do this I booted the system via a Debian Jessie Live-DVD, added
lvm2 and started it (the root system is on an Adaptec HW Raid), mounted
the root and editet '/etc/network/interfaces'.

Many thanks to all who have helped & kind regards,
Hans

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web