Re: boot takes too long (swap?)

[Bruno Schneider]

I found that one partition has "mount count" greater than "maximum
mount count". Systemd starts an fsck but can't finish it. Therefore,
it tries again on next boot.

It seems I'm hit by bug #788050 (
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050;msg=9 )

I'll follow there. Thanks.

-- 
Bruno Schneider

Re: boot takes too long (swap?)

[Felix Miata]

Bruno Schneider composed on 2015-11-30 10:15 (UTC-0200):

> I found that one partition has "mount count" greater than "maximum
> mount count". Systemd starts an fsck but can't finish it. Therefore,
> it tries again on next boot.

> It seems I'm hit by bug #788050 (
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050;msg=9 )

If you are rebooting daily, an arbitrary maximal mount count is arguably
ludicrous. I would never hit this bug, because my extX filesystems have had
the following applied:

tune2fs -c0 -i0

and thus get checked only as circumstance dictates or when I choose to do so
manually.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: boot takes too long (swap?)

[Sven Joachim]

On 2015-11-27 14:35 -0200, Bruno Schneider wrote:

> Updating:
>
> I commented out the swap partition in fstab, boot still took a long
> time, after boot, no swap was active. I didn't try other swap related
> suggestions such as mkswap.
>
> The output of systemd-analyze critical-chain was not useful, as
> everything mentioned starts after 3min.
>
> The output of systemd-analyze blame seems more useful:
>
> # systemd-analyze blame
> 2min 55.271s
> systemd-fsck@dev-disk-by\x2duuid-f81a6f4e\x2dd547\x2d41dc\x2d9ecf\x2dd1a5922d0aaa.service
>  11.396s wicd.service
>   7.838s exim4.service
>
> I don't know much about systemd, but the name seems to imply a file
> system check is been done on one or more partitions.

Only on one partition, the one with uuid
f81a6f4e-dd547-d41dc-d9ecf-dd1a5922d0aaa.  Consult /etc/fstab or the
/dev/disk/by-uuid/ directory to find out which one it is.

> Now I need to
> find out why does it think it needs to check it at every boot.

Indeed.

Cheers,
   Sven

Re: boot takes too long (swap?)

[Bruno Schneider]

Updating:

I commented out the swap partition in fstab, boot still took a long
time, after boot, no swap was active. I didn't try other swap related
suggestions such as mkswap.

The output of systemd-analyze critical-chain was not useful, as
everything mentioned starts after 3min.

The output of systemd-analyze blame seems more useful:

# systemd-analyze blame
2min 55.271s
systemd-fsck@dev-disk-by\x2duuid-f81a6f4e\x2dd547\x2d41dc\x2d9ecf\x2dd1a5922d0aaa.service
 11.396s wicd.service
  7.838s exim4.service

I don't know much about systemd, but the name seems to imply a file
system check is been done on one or more partitions. Now I need to
find out why does it think it needs to check it at every boot.

Thanks for the help, Michael Biebl.

-- 
Bruno Schneider

Re: boot takes too long (swap?)

[Michael Biebl]

Am 26.11.2015 um 16:34 schrieb Mario Castelán Castro:
> Also try disabling the space swap, filling it with zero bytes (using
> dd), rebuilding the swap space (with mkswap) and re-enabling it.

Running mkswap changes the UUID unless you specify it via --uuid.
So either re-use the existing UUID or change /etc/fstab and
/etc/initramfs-tools/conf.d/resume afterwards.

Michael

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



signature.asc
Description: OpenPGP digital signature

Re: boot takes too long (swap?)

[Michael Biebl]

Am 26.11.2015 um 16:04 schrieb Bruno Schneider:
> I have a notebook with Debian testing (Stretch) that suddenly started
> going through long (4 min) boots.
> 
> Something disk intensive stops the boot process for more than 3 miinutes.
> 
> Looking at dmesg, I see a large time gap here:

Assuming you use systemd, can you attach the output of
systemd-analyze critical-chain

and maybe the top 10 lines of systemd-analyze blame

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



signature.asc
Description: OpenPGP digital signature

Re: boot takes too long (swap?)

[Felix Miata]

Michael Biebl composed on 2015-11-26 16:40 (UTC+0100):

> Mario Castelán Castro wrote:

>> Also try disabling the space swap, filling it with zero bytes (using
>> dd), rebuilding the swap space (with mkswap) and re-enabling it.

> Running mkswap changes the UUID unless you specify it via --uuid.
> So either re-use the existing UUID or change /etc/fstab and
> /etc/initramfs-tools/conf.d/resume afterwards.

Easier to change fstab to mount swap LABEL= instead of UUID=, then

mkswap -L somethingMemorable

e.g. p3swapper. All my fstabs mount native filesystems by LABEL.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: boot takes too long (swap?)

[Ron]

On Thu, 26 Nov 2015 11:13:24 -0500
Felix Miata  wrote:

> Easier to change fstab to mount swap LABEL= instead of UUID=, then

/dev/sd6   noneswapsw  0   0
 
Cheers,
 
Ron.
-- 
   Stercus accidit.

   -- http://www.olgiati-in-paraguay.org --
 

Re: boot takes too long (swap?)

[Mario Castelán Castro]

El 26/11/15 a las 09:04, Bruno Schneider escribió:

I have a notebook with Debian testing (Stretch) that suddenly started
going through long (4 min) boots.

Something disk intensive stops the boot process for more than 3 miinutes.

Looking at dmesg, I see a large time gap here:

[   20.661252] Adding 4208992k swap on /dev/sda1.  Priority:-1
extents:1 across:4208992k FS
[  196.805214] EXT4-fs (sda4): mounting ext3 file system using the
ext4 subsystem

So, it looks like swap is taking a long to mount. I checked my fstab,
and the swap line is:

UUID=d30ec1b1-0dab-455d-a7b1-51ca86631bc2 noneswapsw
0   0

The UUID is correct. The swap partition is working after boot.

Can anyone help on how to investigate further?


One _possible_ source of this anomaly (not very likely, continue 
looking) is that the hard disk has non-remapped damaged sectors; reading 
them is much slower. A scan triggered using smartctl from smartmontools 
will tell you whether this is the case.


Also try disabling the space swap, filling it with zero bytes (using 
dd), rebuilding the swap space (with mkswap) and re-enabling it.

Re: boot takes too long (swap?)

[Felix Miata]

Renaud (Ron) OLGIATI composed on 2015-11-26 14:28 (UTC-0300):

> On Thu, 26 Nov 2015 11:13:24 -0500 Felix Miata wrote:

>> Easier to change fstab to mount swap LABEL= instead of UUID=, then

> /dev/sd6   noneswapsw  0   0

If you try to boot without removing that USB stick or powering down that USB
HD you forgot was connected, /dev/sda6 may get you a very similar hang,
because of the stick or external enumerated as sda instead of the internal
HD. By LABEL and by UUID both avoid that risk.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: boot takes too long (swap?)

[Mario Castelán Castro]

El 26/11/15 a las 09:40, Michael Biebl escribió:

Am 26.11.2015 um 16:34 schrieb Mario Castelán Castro:

Also try disabling the space swap, filling it with zero bytes (using
dd), rebuilding the swap space (with mkswap) and re-enabling it.


Running mkswap changes the UUID unless you specify it via --uuid.
So either re-use the existing UUID or change /etc/fstab and
/etc/initramfs-tools/conf.d/resume afterwards.


Good catch.

Re: boot takes too long (swap?)

[Ron]

On Thu, 26 Nov 2015 12:41:27 -0500
Felix Miata  wrote:

> > /dev/sd6   noneswapsw  0   0  
> 
> If you try to boot without removing that USB stick or powering down that USB
> HD you forgot was connected, /dev/sda6 may get you a very similar hang,
> because of the stick or external enumerated as sda instead of the internal
> HD. By LABEL and by UUID both avoid that risk.

No risk: when I want to boot from the USB I do it (F8 at boot) from the Grub 
installed on the USB.
 
No UUID crap needed.

Cheers,
 
Ron.
-- 
   Stercus accidit.

   -- http://www.olgiati-in-paraguay.org --
 

Re: boot takes too long (swap?)

[Pascal Hambourg]

Renaud (Ron) OLGIATI a écrit :
> On Thu, 26 Nov 2015 12:41:27 -0500
> Felix Miata  wrote:
> 
>>> /dev/sd6   noneswapsw  0   0  
>>
>> If you try to boot without removing that USB stick or powering down that USB
>> HD you forgot was connected, /dev/sda6 may get you a very similar hang,
>> because of the stick or external enumerated as sda instead of the internal
>> HD. By LABEL and by UUID both avoid that risk.

I agree for UUID. I would be more careful about LABEL, as it is easier
to create duplicates.

> No risk: when I want to boot from the USB I do it (F8 at boot) from
> the Grub installed on the USB.

You didn't get the point. The disk naming order is random by nature and
has nothing to do with the boot order.

Re: boot takes too long (swap?)

[Felix Miata]

Pascal Hambourg composed on 2015-11-27 00:19 (UTC+0100):

> Renaud (Ron) OLGIATI composed:

> On Thu, 26 Nov 2015 12:41:27 -0500 Felix Miata wrote:

 /dev/sd6   noneswapsw  0   0  

>>> If you try to boot without removing that USB stick or powering down that USB
>>> HD you forgot was connected, /dev/sda6 may get you a very similar hang,
   

>>> because of the stick or external enumerated as sda instead of the internal
>>> HD. By LABEL and by UUID both avoid that risk.

> I agree for UUID. I would be more careful about LABEL, as it is easier
> to create duplicates.

Not a big enough difference to overpower the incovenience that can result
when a UUID gets obliterated.

>> No risk: when I want to boot from the USB I do it (F8 at boot) from
>> the Grub installed on the USB.

That's what happens when you *want*, not when you forgot, or didn't know your
other half or kid stuck one in or flipped the switch on, or a "smart" one
auto-powers up on reboot.

> You didn't get the point. The disk naming order is random by nature and
> has nothing to do with the boot order.

While your point is valid, you may have missed my same point.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/