> You might run a smartctl --all /dev/<disk> and see if the disk is
> reporting issues with sectors.
>
> A few slow but still readable sectors would push up the time.
>
hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 8624 MB in 1.99 seconds = 4323.10 MB/sec
Timing buffered disk reads: 398 MB in 3.01 seconds = 132.12 MB/sec
did short smartctl test see no errors.
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.13-200.fc31.x86_64] (local
build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Mobile HDD
Device Model: ST1000LM035-1RK172
Serial Number: ZDEBD551
LU WWN Device Id: 5 000c50 0b21db1f2
Firmware Version: SDM2
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri May 29 23:43:17 2020 ChST
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 0) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No 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: ( 162) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3035) SCT Status 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 082 064 006 Pre-fail Always
- 148372794
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always
- 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always
- 37
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000f 082 060 045 Pre-fail Always
- 168378750
9 Power_On_Hours 0x0032 089 089 000 Old_age Always
- 9738 (126 157 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always
- 36
184 End-to-End_Error 0x0032 100 100 099 Old_age Always
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always
- 0
190 Airflow_Temperature_Cel 0x0022 054 046 040 Old_age Always
- 46 (Min/Max 33/52)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always
- 252
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always
- 4
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always
- 201701
194 Temperature_Celsius 0x0022 046 054 000 Old_age Always
- 46 (0 25 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 200 000 Old_age Always
- 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline
- 9457 (101 150 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline
- 10494634824
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline
- 2837485253
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always
- 0
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 Short offline Completed without error 00% 9738
-
# 2 Short offline Completed without error 00% 1509
-
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.
> On Fri, May 29, 2020 at 1:25 AM Michael D. Setzer II via users
> <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> > On 2020-05-29 01:58, Michael D. Setzer II via users wrote:
>> >> I've got 5 Fedora machines at my house. Recently
>> >> upgraded a couple since FC30 was becoming EOL.
>> >>
>> >> Some I did a clean install. New Hard disk, and install
>> >> from iso. Usually, that takes about 1/2 hour for whole
>> >> process. Including install of OS, and then install of a
>> >> number of other packages I use that are not installed by
>> >> default.
>> >>
>> >> Did update on my notebook machine as well using dnf
>> >> system update. This system has some more packages
>> >> installed. Showed 5070 versus about 2000+ for the
>> >> clean install. Download process took about 30 minutes,
>> >> but then the reboot and upgrade process took just over
>> >> 14 hours. Total was 14 hours 50 minutes.
>> >>
>> >> Not clear why it would take 15 times as long? Checked
>> >> while running, and dnf was running at 100%, but just
>> >> using 1 cpu. Notebook has dual cpus. Don't know if
>> >> others just run it, and check when done, but seems to
>> >> be a bigger difference in time than it should be.
>> >
>> > I do not know why your upgrade would have taken so long. I just
>> upgraded
>> > an
>> > F30 VM to F32. It is a pretty vanilla Workstation install. The
>> VM's
>> > disks are actually
>> > hosted on a NAS over nfs and are traditional spinning HW.
>> >
>> > I upgraded via "dnf system-upgrade". The number of packages
>> upgraded was
>> > 1656.
>> > The download phase took 9 minutes 10 seconds. The upgrade phase
>> took a
>> > few ticks
>> > over 25 minutes.
>> >
>> > I would think that checking
>> >
>> > dnf system-upgrade log
>> >
>> > and seeing if one area in particular was responsible for the
>> excessive
>> > time may be
>> > helpful.
>> >
>> > Another recent upgrade of an old notebook from F31->F32, Core2 Duo
>> CPU,
>> > with 2626
>> > packages upgraded took 58 minutes. That notebook does have an SSD.
>> >
>> > --
>> > The key to getting good answers is to ask good questions.
>>
>> Pulled the data from the boot.log
>> 31814 lines
>> Total Time 14:59.59.05
>> Longest single change was 1156.203674 seconds
>> [ 1740.207952] dnf[807]: Running scriptlet:
>> filesystem-3.12-2.fc31.x86_64 1/1
>> Average of transactions 1.6918392547953
>> Only 11 transactions took 60 seconds or longer
>>
>> Had to clean out lines that where mixed in with the upgrade of starting
>> and stopping things during process.
>> Extracted the time data, and then compared the times of each process to
>> calculate the difference.
>>
>> CPU is Intel(R) Pentium(R) CPU 2020M @ 2.40GHz with just 2 cores.
>> Has 12G of Ram.
>>
>> If you want, I could send you the libreoffice calc file. Perhaps you
>> would
>> see something that I've missed.
>>
>> > _______________________________________________
>> > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
>> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> > Fedora Code of Conduct:
>> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> > List Guidelines:
>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>> > List Archives:
>> > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
>> >
>>
>> _______________________________________________
>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
