You are not logged in.

Pages: 1

#1 2020-10-30 20:07:42

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

[SOLVED] Very long boot time

I have installed Arch Linux on a new computer and it takes much longer than my previous (much less powerful) computer to enter the Plasma desktop.

$ systemd-analyze blame                                   
10.641s multimedia.mount
8.367s NetworkManager-wait-online.service

multimedia.mount is the assembly of a hard disk with the following configuration in the fstab file:

# /dev/sda1 LABEL=multimedia
UUID=256db611-dc2d-41d4-8374-b3c4e72bec00       /multimedia     btrfs rw,noatime,autodefrag,compress=zstd,nossd,space_cache=v2    0 0

Can I deactivate the "NetworkManager-wait-online.service"?
Is it normal that it takes so long to mount a hard disk? Is it caused by the file system (BTRFS) or any of the file system options?

Last edited by j1simon (2020-11-07 20:48:55)

Offline

#2 2020-11-03 13:12:46

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

Today the delay has been much greater:

$ systemd-analyze blame
39.990s multimedia.mount
11.806s NetworkManager-wait-online.service

It's the first time I use this filesystem (BTRFS) and maybe the problem is some of the mounting options I have indicated.
Please, could someone help me?
Thanks in advance.

Offline

#3 2020-11-03 14:45:11

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,081

Re: [SOLVED] Very long boot time

What about the rest of your fstab? This reads to me like you have a networkmount that waits for network-online to trigger and the multimedia mount afterwards which has to wait for it to complete.

Generally yes you can disable the wait-online service, it also isn't enabled by default so you likely had an intention here.

Online

#4 2020-11-03 14:53:07

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

V1del wrote:

What about the rest of your fstab? This reads to me like you have a networkmount that waits for network-online to trigger and the multimedia mount afterwards which has to wait for it to complete.

Generally yes you can disable the wait-online service, it also isn't enabled by default so you likely had an intention here.

There is no network mount:

$ cat /etc/fstab

# /dev/nvme0n1p1
UUID=A0BA-6372 /boot vfat rw,lazytime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro     0 2

# /dev/nvme0n1p2 LABEL=archLinux
UUID=f296f216-8bdf-4105-878a-75d433259bb4       / f2fs rw,lazytime,data_flush,noquota,nodiscard,no_heap,inline_xattr,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix,compress_algorithm=zstd,compress_log_size=2       0 1

# /dev/sda1 LABEL=multimedia
UUID=256db611-dc2d-41d4-8374-b3c4e72bec00       /multimedia     btrfs rw,noatime,autodefrag,compress=zstd,nossd,space_cache=v2  0 0

The BTRFS hard disk is 16 TB. Can it be because of the high capacity of the disk?

Offline

#5 2020-11-05 14:11:31

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

I have put in verbose mode the boot of the system and I have taken these photos:
440b401358698136.jpg
df122e1358698139.jpg
6884da1358698140.jpg

Is there a way to capture in a file all the output from the Linux boot?

Offline

#6 2020-11-05 14:39:55

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,081

Re: [SOLVED] Very long boot time

Yes 

journalctl -b

should provide most of what's relevant.

From what we see here it seems to have some real issues with your /dev/sda, it might be on the brink of dying. Which harddisk vendor is this? I suggest you stop actively using it,  run a long SMART check and post the output of 

smartctl -a /dev/sda

after the mentioned time has elapsed.

Last edited by V1del (2020-11-05 14:40:46)

Online

#7 2020-11-06 07:53:20

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

The disk is a "16TB SEAGATE IRONWOLF PRO 3.5", 7200 RPM 256MB CACHE":

$ sudo hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
Model Number:       ST16000NE000-2RW103                     
Serial Number:      ZL277D53
Firmware Revision:  EN02    
Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0xffff) 
Supported: 11 10 9 8 7 6 5 
Likely used: 11
Configuration:
Logical         max     current
cylinders       16383   16383
heads           16      16
sectors/track   63      63
--
CHS current addressable sectors:    16514064
LBA    user addressable sectors:   268435455
LBA48  user addressable sectors: 31251759104
Logical  Sector size:                   512 bytes [ Supported: 256 2048 ]
Physical Sector size:                  4096 bytes
Logical Sector-0 offset:                  0 bytes
device size with M = 1024*1024:    15259648 MBytes
device size with M = 1000*1000:    16000900 MBytes (16000 GB)
cache/buffer size  = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16  Current = 16
Recommended acoustic management value: 254, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4 
Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
Enabled Supported:
*    SMART feature set
Security Mode feature set
*    Power Management feature set
*    Write cache
*    Look-ahead
*    WRITE_BUFFER command
*    READ_BUFFER command
*    DOWNLOAD_MICROCODE
Power-Up In Standby feature set
*    SET_FEATURES required to spinup after power up
SET_MAX security extension
*    48-bit Address feature set
*    Mandatory FLUSH_CACHE
*    FLUSH_CACHE_EXT
*    SMART error logging
*    SMART self-test
*    Media Card Pass-Through
*    General Purpose Logging feature set
*    WRITE_{DMA|MULTIPLE}_FUA_EXT
*    64-bit World wide name
*    IDLE_IMMEDIATE with UNLOAD
Write-Read-Verify feature set
*    WRITE_UNCORRECTABLE_EXT command
*    {READ,WRITE}_DMA_EXT_GPL commands
*    Segmented DOWNLOAD_MICROCODE
*    unknown 119[6]
*    unknown 119[7]
unknown 119[8]
unknown 119[9]
*    Gen1 signaling speed (1.5Gb/s)
*    Gen2 signaling speed (3.0Gb/s)
*    Gen3 signaling speed (6.0Gb/s)
*    Native Command Queueing (NCQ)
*    Phy event counters
*    Idle-Unload when NCQ is active
*    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
*    DMA Setup Auto-Activate optimization
Device-initiated interface power management
*    Software settings preservation
unknown 78[7]
*    SMART Command Transport (SCT) feature set
*    SCT Write Same (AC2)
*    SCT Error Recovery Control (AC3)
*    SCT Features Control (AC4)
*    SCT Data Tables (AC5)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[14] (vendor specific)
*    SANITIZE_ANTIFREEZE_LOCK_EXT command
*    SANITIZE feature set
*    OVERWRITE_EXT command
*    reserved 69[3]
Security:
Master password revision code = 65534
supported
not     enabled
not     locked
not     frozen
not     expired: security count
supported: enhanced erase
1414min for SECURITY ERASE UNIT. 1414min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c500c68770bb
NAA             : 5
IEEE OUI        : 000c50
Unique ID       : 0c68770bb
Checksum: correct

I started a long test with "sudo smartctl -t long /dev/sda" yesterday afternoon but it is not over yet:

$ sudo smartctl -l selftest /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.3-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Self-test routine in progress 40%       907         -

I'll put the result here when it' s completed.

Offline

#8 2020-11-06 20:58:07

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

The test is finally over (it took a little more than 1 day). It seems that the result is correct:

$ sudo smartctl -l selftest /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.3-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       919         -
$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.9.3-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST16000NE000-2RW103
Serial Number:    ZL277D53
LU WWN Device Id: 5 000c50 0c68770bb
Firmware Version: EN02
User Capacity:    16.000.900.661.248 bytes [16,0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Fri Nov  6 21:52:49 2020 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  567) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (1412) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x50bd)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   076   064   044    Pre-fail  Always       -       42496816
  3 Spin_Up_Time            0x0003   089   088   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       19
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   045    Pre-fail  Always       -       37665023
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       920
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       18
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   001   000    Old_age   Always       -       90195755530
190 Airflow_Temperature_Cel 0x0022   064   045   040    Old_age   Always       -       36 (Min/Max 30/40)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       4
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1224
194 Temperature_Celsius     0x0022   036   042   000    Old_age   Always       -       36 (0 18 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   001   000    Old_age   Always       -       1049
200 Multi_Zone_Error_Rate   0x0023   100   100   001    Pre-fail  Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       709 (60 19 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       25082981857
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       26586622213

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       919         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I have created a bootable USB with SeaTools programs to pass its own tests.

Offline

#9 2020-11-07 20:48:37

j1simon
Member
From: Denmark
Registered: 2016-01-28
Posts: 189

Re: [SOLVED] Very long boot time

Problem solved by updating the system BIOS.

Offline

Pages: 1

Board footer

Powered by FluxBB