SlackwareThis Forum is for the discussion of Slackware 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.
It's slocate - it's updating it's filesystem databases and it schedules it for that exact time on a default Slackware system.
chmod -x that or remove it from cron. The other two hardly do anything - logrotate copies about three files about (less than a meg each usually) and kmod doesn't touch the disk at all (releases unused kernel modules).
But slocate is reading the filename of every file on every mounted disk and storing the info in a compressed database. It takes about 30 minutes on my computer, slagging the disk all the time, and I've only got about 150Gb.
If you do disable it (crontab -e or chmod), then the slocate command won't work properly (stale data) but everything else will be absolutely fine. Most people don't even know about slocate, let alone use it.
Think of it as the Linux equivalent of Microsoft Find Fast.
Coming back to the 'noise' issue, a HD really shouldn't be considered 'noisy' unless it is pretty old or pretty unhealthy. Within reason, does it sound 'normal' ?
I can't even hear mine, at all..
Well, just something to keep in mind: have backups up to date.
I can hear mine in my laptop not my desktop. But on my desktop you can hear the fans instead ... much louder than my laptop.
If you want, you can try to use hdparm to make the drive quiter:
Quote:
-M
Get/set Automatic Acoustic Management (AAM) setting. Most modern harddisk drives have the ability to speed down the head movements to reduce their noise output. The possible values are between 0 and 254. 128 is the most quiet (and therefore slowest) setting and 254 the fastest (and loudest). Some drives have only two levels (quiet / fast), while others may have different levels between 128 and 254. At the moment, most drives only support 3 options, off, quiet, and fast. These have been assigned the values 0, 128, and 254 at present, respectively, but integer space has been incorporated for future expansion, should this change.
Cron daily runs at 4:40am by default, It's a good idea to keep slocate database up to date. I would change the time that cron daily runs to a more convenient time.
In my experience, few possiblity (maybe more) will mae noise. some of them can be solve and some of them can't.
1. manufacturer fault, a faulty hard disk escape from quality control department. normally won't apear easily since the manufacturer doing 100% testing. However, due to special accept rejected component from their production line may cause the hard disk quality drop within short period. Some defect like noise, motor jam and etc can be occur after short period (probably few month).
2. almost end of live, since hard disk is turning really fast (normally 5400rpm or above), this is easily the hard disk motor or archiveter arm(the reader) reach end of live after few years. Meaning the mechanical or electrical wear off.
3. Some usb hard disk will make noise if your pc/laptop provide not sufficient electricity. In that condition the usb hard disk's motor won't spin well and will make noise.
4. of course heavy read/write will cause the hard disk motor spin much faster, but normally (good hard disk) I believe it won't too noisey(but the fan yes).
In my opinion, the hearth of hard disk play important role whether it make noise or not. And the hearth of hard disk is hard to control since it will wear off after some times.
I've never had a HDD fail. I don't think this is the case here, not for such a specific time (4:40 - :45) when cron.daily runs. I can't really recommend one HDD over another, since none has broken yet , and even if they do break, they have served me well, may they RIP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.