Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Over on this thread http://www.linuxquestions.org/questi...es-4175549373/ I was helped to see what was causing slow boot. Right now I'm just under 3 minutes to boot. One of the biggest culprits is my /home hard drive which takes 37 seconds to mount.
The hard drive is btrfs, SATA III, and 3TB. What could be making it take so long? What could I do to improve it?
It should be in the SMART data of the drive. gnome-disks can tell you that.
EDIT: Added a screenshot of my old 1TB drive's SMART data. If the assessment of the spinup time is not OK, then you should probably look into getting a new drive.
Last edited by Ihatewindows522; 07-31-2015 at 11:31 AM.
It should be in the SMART data of the drive. gnome-disks can tell you that.
EDIT: Added a screenshot of my old 1TB drive's SMART data. If the assessment of the spinup time is not OK, then you should probably look into getting a new drive.
My gnome-disks doesn't look like that. But here's the commandline output:
Code:
# smartctl -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.0.8-300.fc22.x86_64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital AV-GP (AF)
Device Model: WDC WD30EURS-73TLHY0
Serial Number: WD-WMC4N0272254
LU WWN Device Id: 5 0014ee 603ae630b
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Jul 31 14:53:13 2015 EDT
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: (39720) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 399) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x7035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 183 179 021 Pre-fail Always - 5850
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 287
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 7841
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 287
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 29
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 257
194 Temperature_Celsius 0x0022 109 105 000 Old_age Always - 41
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
If I'm reading this right, it takes 5.85 seconds to spin up. (1000ms = 1sec) My old hard drive takes about a half second, and I'm able to mount it after about 15 seconds of powering it on. This would most certainly account for at least some of the time it takes for you to mount yours. As the SMART data says, if it is at or exceeds the threshold (which yours is pretty close), it indicates that the drive will fail soon. Personally that's not the drive I'd want my home folder on.
Hmm, as I look through this - IF the SMART data is accurate ... my home drive is a 5400 RPM drive. Perhaps that's the big culprit? A 5400 RPM drive with nearly 3TB of data.
Hmm, as I look through this - IF the SMART data is accurate ... my home drive is a 5400 RPM drive. Perhaps that's the big culprit? A 5400 RPM drive with nearly 3TB of data.
No...a 3TB drive @ 5400 RPM would be faster than a 1TB drive @ 5400 RPM. It's like the difference between a CD and a DVD, the DVD is faster (even spinning at the same speed) because the data is condensed tighter.
Yeah, I *THINK* it's the type of drive. I think WD has some tuning on it that makes it load up more slowly because it's meant to go into Tivos or something like that
That might explain the subpar 5400 RPM, but not the 37 second mount time. I've never really delt with DVRs, but I would imagine that 37 secs is a little long to be waiting even for a DVR.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.