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

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

Strange message during boot

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

Contents

  Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-10 15:30 +0100
    Re: Strange message during boot David Wright <deblis@lionunicorn.co.uk> - 2018-01-10 16:00 +0100
    Re: Strange message during boot Darac Marjal <mailinglist@darac.org.uk> - 2018-01-10 16:40 +0100
    Re: Strange message during boot Jeroen Mathon <jeroenmathonmac@gmail.com> - 2018-01-11 09:40 +0100
      Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-11 11:40 +0100
        Re: Strange message during boot rhkramer@gmail.com - 2018-01-11 14:30 +0100
          Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-11 15:40 +0100
            Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-11 15:50 +0100
              Re: Strange message during boot Brian <ad44@cityscape.co.uk> - 2018-01-11 16:30 +0100
                Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-11 16:30 +0100
                  Re: Strange message during boot Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-11 16:40 +0100
                    Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-11 16:50 +0100
                      Re: Strange message during boot Sven Joachim <svenjoac@gmx.de> - 2018-01-11 18:40 +0100
              Re: Strange message during boot Curt <curty@free.fr> - 2018-01-13 11:50 +0100
                [LIKELY Resolved] - was [Re: Strange message during boot] Richard Owlett <rowlett@cloud85.net> - 2018-01-13 13:50 +0100
    Re: [Diagnostic Summary] Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-11 18:20 +0100
      Re: [Diagnostic Summary] Re: Strange message during boot bw <bwtnguy@yahoo.com> - 2018-01-11 18:40 +0100
        Re: [Diagnostic Summary] Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-11 18:40 +0100
          Re: [Diagnostic Summary] Re: Strange message during boot bw <bwtnguy@yahoo.com> - 2018-01-11 18:50 +0100
            Re: [Diagnostic Summary] Re: Strange message during boot The Wanderer <wanderer@fastmail.fm> - 2018-01-12 14:00 +0100
          Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-12 17:10 +0100
        Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-11 19:50 +0100
          Re: [Diagnostic Summary] Re: Strange message during boot bw <bwtnguy@yahoo.com> - 2018-01-11 20:30 +0100
            Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-12 13:10 +0100
    [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-11 18:20 +0100
      Re: [Diagnostic Summary] Re: Strange message during boot bw <bwtnguy@yahoo.com> - 2018-01-11 18:30 +0100
        Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-12 17:10 +0100
      Re: [Diagnostic Summary] Re: Strange message during boot David Wright <deblis@lionunicorn.co.uk> - 2018-01-11 20:50 +0100
        Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-12 13:30 +0100
          Re: [Diagnostic Summary] Re: Strange message during boot David Wright <deblis@lionunicorn.co.uk> - 2018-01-12 16:30 +0100
            Re: [Diagnostic Summary] Re: Strange message during boot Richard Owlett <rowlett@cloud85.net> - 2018-01-12 17:30 +0100
            HELP!! - was [Re: [Diagnostic Summary] Re: Strange message during  boot] Richard Owlett <rowlett@cloud85.net> - 2018-01-13 02:50 +0100

Page 1 of 2  [1] 2  Next page →

#190895 — Strange message during boot

I multi-boot several varieties of Debian.
When booting one specific install I many repetitions to the effect that 
it is beginning a specific script.

It then proceeds to bring up an apparently normal system.

Would this be logged somewhere?
Where?

TIA

[toc] | [next] | [standalone]

#190899

On Wed 10 Jan 2018 at 08:22:51 (-0600), Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install I many repetitions to the effect
> that it is beginning a specific script.
> 
> It then proceeds to bring up an apparently normal system.
> 
> Would this be logged somewhere?
> Where?

Maybe /var/log/syslog.

Cheers,
David.

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

#190900

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

On Wed, Jan 10, 2018 at 08:22:51AM -0600, Richard Owlett wrote:
>I multi-boot several varieties of Debian.
>When booting one specific install I many repetitions to the effect 
>that it is beginning a specific script.
>
>It then proceeds to bring up an apparently normal system.
>
>Would this be logged somewhere?
>Where?

If the instance of Debian is new enough to use systemd, try:

journactl -xb

("Show journal messages from the current boot with explanations")

Otherwise, try looking in /var/log/bootlog. If that doesn't exist, you 
may install the 'boootlogd' package and restart (installing it will 
configure the boot process appropriately, but you'll need to do one more 
boot to actually start capturing the logs).

>
>TIA
>

-- 
For more information, please reread.

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

#190923

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

Hey Richard,


Perhaps it is just me but i am having trouble deciphering this sentence:
"When booting one specific install I many repetitions to the effect that
it is beginning a specific script." could you please elaborate upon it?


On 01/10/2018 03:22 PM, Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install I many repetitions to the effect
> that it is beginning a specific script.
>
> It then proceeds to bring up an apparently normal system.
>
> Would this be logged somewhere?
> Where?
>
> TIA
>

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

#190926

On 01/11/2018 02:32 AM, Jeroen Mathon wrote:
> Hey Richard,
>
>
> Perhaps it is just me but i am having trouble deciphering this
> sentence:
> "When booting one specific install I many repetitions to the effect
> that it is beginning a specific script." could you please elaborate
> upon it?

OOPS, typos and awkward phrasing. It should have read:
When booting one specific install, it displays many repetitions of the 
line to the effect that it is beginning a specific script.

Specifics:
sda1 - Always has the latest version of Debian, currently 9.1 .
        For housekeeping reasons it has the only copy of Grub
        on my machine.
sda8 - The problem install is Debian 8. It had been my primary work
        install until I trashed some data files. It has been kept to
        reconstruct those files as I have time.
sda9 - Current work install of Debian 9.1





>
>
> On 01/10/2018 03:22 PM, Richard Owlett wrote:
>> I multi-boot several varieties of Debian.
>> When booting one specific install I many repetitions to the effect
>> that it is beginning a specific script.
>>
>> It then proceeds to bring up an apparently normal system.
>>
>> Would this be logged somewhere?
>> Where?
>>
>> TIA
>>
>
>

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

#190933

On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
> OOPS, typos and awkward phrasing. It should have read:
> When booting one specific install, it displays many repetitions of the
> line to the effect that it is beginning a specific script.
> 

Did it give you the name of the specific script?  

Perhaps it would help if you shared that here (along with as much of the 
message as you can duplicate (presumably from memory or after doing a reboot).



> Specifics:
> sda1 - Always has the latest version of Debian, currently 9.1 .
>         For housekeeping reasons it has the only copy of Grub
>         on my machine.
> sda8 - The problem install is Debian 8. It had been my primary work
>         install until I trashed some data files. It has been kept to
>         reconstruct those files as I have time.
> sda9 - Current work install of Debian 9.1
> 

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

#190936

On 01/11/2018 07:26 AM, rhkramer@gmail.com wrote:
> On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
>> OOPS, typos and awkward phrasing. It should have read:
>> When booting one specific install, it displays many repetitions of the
>> line to the effect that it is beginning a specific script.
>>
>
> Did it give you the name of the specific script?
>
> Perhaps it would help if you shared that here (along with as much of the
> message as you can duplicate (presumably from memory or after doing a reboot).


Did a reboot with pen and paper at hand.
The line is:
> Begin: Running /scrips/local-block ... done.

As to other suggestions:

journactl -xb yields:
>
> root@stretch-2nd:~# journactl -xb > testlog.txt
> bash: journactl: command not found
> root@stretch-2nd:~#

Installed bootlogd with Synaptic. /var/log/bootlog does not exist after 
multiple boots

However, /var/log/boot contains:
> (Nothing has been logged yet. If you're still seeing this message your current init system might not write bootup messages to the system console at all.)

/etc/apt/sources.list indicates the install had been done with:
deb cdrom:[Debian GNU/Linux stretch-DI-rc3 _Stretch_ - Official Snapshot 
i386 NETINST Binary-1 20170409-00:50]/ stretch main

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

#190937

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

On 2018-01-11 at 09:36, Richard Owlett wrote:

> On 01/11/2018 07:26 AM, rhkramer@gmail.com wrote:
>
>> On Thursday, January 11, 2018 05:29:42 AM Richard Owlett wrote:
>>
>>> OOPS, typos and awkward phrasing. It should have read:
>>> When booting one specific install, it displays many repetitions of the
>>> line to the effect that it is beginning a specific script.
>>
>> Did it give you the name of the specific script?
>>
>> Perhaps it would help if you shared that here (along with as much of the
>> message as you can duplicate (presumably from memory or after doing a reboot).
> 
> 
> Did a reboot with pen and paper at hand.
> The line is:
>> Begin: Running /scrips/local-block ... done.

Does it really say 'scrips' rather than 'scripts'?

Googling on that error message (with the presumed typo corrected) leads
me to http://forums.debian.net/viewtopic.php?f=5&t=133578 as a first
hit.

'dlocate scripts/local-block' finds three packages on my system:
cryptsetup, lvm2, and mdadm. Results on your system may differ. I would
suggest running that command on your system and investigating the
resulting list of packages.

> As to other suggestions:
> 
> journactl -xb yields:

That should be 'journalctl'.

>> root@stretch-2nd:~# journactl -xb > testlog.txt
>> bash: journactl: command not found
>> root@stretch-2nd:~#
> 
> Installed bootlogd with Synaptic. /var/log/bootlog does not exist after 
> multiple boots
> 
> However, /var/log/boot contains:
>> (Nothing has been logged yet. If you're still seeing this message your current init system might not write bootup messages to the system console at all.)

What init system are you running?

Usually, this can be determined by 'dlocate /sbin/init', but I can't
guarantee that that will hold for all systems.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#190939

On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:

> What init system are you running?
> 
> Usually, this can be determined by 'dlocate /sbin/init', but I can't
> guarantee that that will hold for all systems.

Guaranteed: 'cat /proc/1/comm'.

-- 
Brian.

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

#190940

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

On 2018-01-11 at 10:23, Brian wrote:

> On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:
> 
>> What init system are you running?
>> 
>> Usually, this can be determined by 'dlocate /sbin/init', but I can't
>> guarantee that that will hold for all systems.
> 
> Guaranteed: 'cat /proc/1/comm'.

On my system:

$ dlocate /sbin/init
sysvinit-core: /sbin/init
$ cat /proc/1/comm
init

So the former command produces recognizably useful information, whereas
the latter does not.

I can't be sure what the latter command would output on a different
system, not having tested it - but since AFAIK the standard practice is
to launch the init system via /sbin/init (symlinked to something else if
necessary) regardless, I would expect the command to be 'init' in all
cases.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#190941

On Thu, Jan 11, 2018 at 10:27:33AM -0500, The Wanderer wrote:
> On 2018-01-11 at 10:23, Brian wrote:
> 
> > On Thu 11 Jan 2018 at 09:45:35 -0500, The Wanderer wrote:
> > 
> >> What init system are you running?
> >> 
> >> Usually, this can be determined by 'dlocate /sbin/init', but I can't
> >> guarantee that that will hold for all systems.
> > 
> > Guaranteed: 'cat /proc/1/comm'.
> 
> On my system:
> 
> $ dlocate /sbin/init
> sysvinit-core: /sbin/init
> $ cat /proc/1/comm
> init
> 
> So the former command produces recognizably useful information, whereas
> the latter does not.
> 
> I can't be sure what the latter command would output on a different
> system, not having tested it - but since AFAIK the standard practice is
> to launch the init system via /sbin/init (symlinked to something else if
> necessary) regardless, I would expect the command to be 'init' in all
> cases.

wooledg:~$ ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Jul  5  2017 /sbin/init -> /lib/systemd/systemd
wooledg:~$ cat /proc/1/comm
systemd

P.S. "ls -l /sbin/init" is the command we usually give to people in
#debian when they ask similar questions.

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

#190942

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

On 2018-01-11 at 10:35, Greg Wooledge wrote:

> On Thu, Jan 11, 2018 at 10:27:33AM -0500, The Wanderer wrote:
>
>> On 2018-01-11 at 10:23, Brian wrote:

>>> Guaranteed: 'cat /proc/1/comm'.
>> 
>> On my system:
>> 
>> $ dlocate /sbin/init
>> sysvinit-core: /sbin/init
>> $ cat /proc/1/comm
>> init
>> 
>> So the former command produces recognizably useful information, whereas
>> the latter does not.
>> 
>> I can't be sure what the latter command would output on a different
>> system, not having tested it - but since AFAIK the standard practice is
>> to launch the init system via /sbin/init (symlinked to something else if
>> necessary) regardless, I would expect the command to be 'init' in all
>> cases.
> 
> wooledg:~$ ls -l /sbin/init
> lrwxrwxrwx 1 root root 20 Jul  5  2017 /sbin/init -> /lib/systemd/systemd
> wooledg:~$ cat /proc/1/comm
> systemd

So it's smart enough to bypass the name of the symlink when populating
this node? I'm a little bit surprised, especially given the number of
programs which intentionally behave differently depending on which name
they were invoked with, but that could be useful in some circumstances.

> P.S. "ls -l /sbin/init" is the command we usually give to people in
> #debian when they ask similar questions.

Right. I meant to bring that up at some point in the thread, but it
slipped my mind during editing passes on what I'd already written.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#190947

On 2018-01-11 10:44 -0500, The Wanderer wrote:

> On 2018-01-11 at 10:35, Greg Wooledge wrote:
>
>> wooledg:~$ ls -l /sbin/init
>> lrwxrwxrwx 1 root root 20 Jul  5  2017 /sbin/init -> /lib/systemd/systemd
>> wooledg:~$ cat /proc/1/comm
>> systemd
>
> So it's smart enough to bypass the name of the symlink when populating
> this node?

No, it is systemd itself which sets its title, very early on in main():

,----
|         static char systemd[] = "systemd";
|         [...]
|         /* If we get started via the /sbin/init symlink then we are
|            called 'init'. After a subsequent reexecution we are then
|            called 'systemd'. That is confusing, hence let's call us
|            systemd right-away. */
|         program_invocation_short_name = systemd;
|         (void) prctl(PR_SET_NAME, systemd);
`----

Cheers,
       Sven

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

#191027

On 2018-01-11, The Wanderer <wanderer@fastmail.fm> wrote:
>
> Googling on that error message (with the presumed typo corrected) leads
> me to http://forums.debian.net/viewtopic.php?f=3D5&t=3D133578 as a first
> hit.
>

That's funny; I am led here first-hit wise:

https://lists.debian.org/debian-kernel/2017/04/msg00192.html

(bug in initramfs-tools version: 0.128)

-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

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

#191030 — [LIKELY Resolved] - was [Re: Strange message during boot]

On 01/13/2018 04:43 AM, Curt wrote:
> On 2018-01-11, The Wanderer <wanderer@fastmail.fm> wrote:
>>
>> Googling on that error message (with the presumed typo corrected) leads
>> me to http://forums.debian.net/viewtopic.php?f=3D5&t=3D133578 as a first
>> hit.
>>
>
> That's funny; I am led here first-hit wise:
>
> https://lists.debian.org/debian-kernel/2017/04/msg00192.html
>
> (bug in initramfs-tools version: 0.128)

Just reviewed bugs 860533 and 860403.Looks like what I was seeing.

Thank you.

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

#190944 — Re: [Diagnostic Summary] Re: Strange message during boot

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

On 2018-01-11 at 12:10, Richard Owlett wrote:

> I multi-boot several varieties of Debian.
> When booting one specific install, it displays many repetitions of:
>>> Begin: Running /scripts/local-block ... done.
> 
> It then proceeds to bring up an apparently normal system.

> Suggested diagnostics yielded:
> 
>> root@stretch-2nd:~# ls -l /sbin/init
>> lrwxrwxrwx 1 root root 20 Jun  4  2017 /sbin/init -> /lib/systemd/systemd
>> root@stretch-2nd:~#

Not particularly unexpected. (This also obviates any need to 'dlocate
/sbin/init', since it confirms which init system you're running.)

>> bash: dlocate: command not found

Install it ('apt-get install dlocate'), then try
'dlocate scripts/local-block'. If that fails, try running 'updatedb' to
initialize the search database, then run the command again.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#190948 — Re: [Diagnostic Summary] Re: Strange message during boot

On Thu, 11 Jan 2018, The Wanderer wrote:

> On 2018-01-11 at 12:10, Richard Owlett wrote:
> 
> > I multi-boot several varieties of Debian.
> > When booting one specific install, it displays many repetitions of:
> >>> Begin: Running /scripts/local-block ... done.
> > 
> > It then proceeds to bring up an apparently normal system.
> 
> > Suggested diagnostics yielded:
> > 
> >> root@stretch-2nd:~# ls -l /sbin/init
> >> lrwxrwxrwx 1 root root 20 Jun  4  2017 /sbin/init -> /lib/systemd/systemd
> >> root@stretch-2nd:~#
> 
> Not particularly unexpected. (This also obviates any need to 'dlocate
> /sbin/init', since it confirms which init system you're running.)
> 
> >> bash: dlocate: command not found
> 
> Install it ('apt-get install dlocate'), then try
> 'dlocate scripts/local-block'. If that fails, try running 'updatedb' to
> initialize the search database, then run the command again.
> 

On stretch local_block is a function in a script named local, maybe using 
a stretch tool on jessie has things confused?  or the initramfs-tools pkg 
is hosed on the bad system.  Sounds complicated, one version of grub but 
separate boot partitions always gets me confused too.

grep local_block /usr/share/initramfs-tools/scripts/local
local_block()
                        local_block "${dev_id}"

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

#190949 — Re: [Diagnostic Summary] Re: Strange message during boot

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

On 2018-01-11 at 12:35, bw wrote:

> On Thu, 11 Jan 2018, The Wanderer wrote:
> 
>> On 2018-01-11 at 12:10, Richard Owlett wrote:
>> 
>> > I multi-boot several varieties of Debian.
>> > When booting one specific install, it displays many repetitions of:
>> >>> Begin: Running /scripts/local-block ... done.
>> > 
>> > It then proceeds to bring up an apparently normal system.
>> 
>> > Suggested diagnostics yielded:
>> > 
>> >> root@stretch-2nd:~# ls -l /sbin/init
>> >> lrwxrwxrwx 1 root root 20 Jun  4  2017 /sbin/init -> /lib/systemd/systemd
>> >> root@stretch-2nd:~#
>> 
>> Not particularly unexpected. (This also obviates any need to 'dlocate
>> /sbin/init', since it confirms which init system you're running.)
>> 
>> >> bash: dlocate: command not found
>> 
>> Install it ('apt-get install dlocate'), then try
>> 'dlocate scripts/local-block'. If that fails, try running 'updatedb' to
>> initialize the search database, then run the command again.
> 
> On stretch local_block is a function in a script named local, maybe using 
> a stretch tool on jessie has things confused?  or the initramfs-tools pkg 
> is hosed on the bad system.  Sounds complicated, one version of grub but 
> separate boot partitions always gets me confused too.
> 
> grep local_block /usr/share/initramfs-tools/scripts/local
> local_block()
>                         local_block "${dev_id}"

That's local_block; this appears to be local-block.

On my system (stable+testing, though with sysvinit rather than systemd):

$ dlocate scripts/local-block
mdadm: /usr/share/initramfs-tools/scripts/local-block
mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm
lvm2: /usr/share/initramfs-tools/scripts/local-block
lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#190950 — Re: [Diagnostic Summary] Re: Strange message during boot

On Thu, 11 Jan 2018, The Wanderer wrote:

> On 2018-01-11 at 12:35, bw wrote:
> 
> > 
> > On stretch local_block is a function in a script named local, maybe using 
> > a stretch tool on jessie has things confused?  or the initramfs-tools pkg 
> > is hosed on the bad system.  Sounds complicated, one version of grub but 
> > separate boot partitions always gets me confused too.
> > 
> > grep local_block /usr/share/initramfs-tools/scripts/local
> > local_block()
> >                         local_block "${dev_id}"
> 
> That's local_block; this appears to be local-block.
> 
> On my system (stable+testing, though with sysvinit rather than systemd):
> 
> $ dlocate scripts/local-block
> mdadm: /usr/share/initramfs-tools/scripts/local-block
> mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm
> lvm2: /usr/share/initramfs-tools/scripts/local-block
> lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2
> 

Okay, that is weird.  I had no idea that a sysV system installed 
different scripts, or why that is the case.

# find / -name local-block*
#
ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Nov 12 00:28 /sbin/init -> /lib/systemd/systemd

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

#190979 — Re: [Diagnostic Summary] Re: Strange message during boot

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

On 2018-01-11 at 12:45, bw wrote:

> On Thu, 11 Jan 2018, The Wanderer wrote:
> 
>> On 2018-01-11 at 12:35, bw wrote:
>> 
>> > On stretch local_block is a function in a script named local, maybe using 
>> > a stretch tool on jessie has things confused?  or the initramfs-tools pkg 
>> > is hosed on the bad system.  Sounds complicated, one version of grub but 
>> > separate boot partitions always gets me confused too.
>> > 
>> > grep local_block /usr/share/initramfs-tools/scripts/local
>> > local_block()
>> >                         local_block "${dev_id}"
>> 
>> That's local_block; this appears to be local-block.
>> 
>> On my system (stable+testing, though with sysvinit rather than systemd):
>> 
>> $ dlocate scripts/local-block
>> mdadm: /usr/share/initramfs-tools/scripts/local-block
>> mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm
>> lvm2: /usr/share/initramfs-tools/scripts/local-block
>> lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2
> 
> Okay, that is weird.  I had no idea that a sysV system installed 
> different scripts, or why that is the case.
> 
> # find / -name local-block*
> #
> ls -l /sbin/init
> lrwxrwxrwx 1 root root 20 Nov 12 00:28 /sbin/init -> /lib/systemd/systemd

I don't think its being sysvinit has anything to do with it; I think
it's just a matter of the specific packages involved.

$ apt-file search scripts/local-block
cryptsetup: /usr/share/initramfs-tools/scripts/local-block/cryptroot
lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2
mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm

and of course the output of apt-file should have nothing to do with what
init system is active.

Do you have any of those three packages on your system? If not, that
would explain why you don't have any of these files.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web