Lenovo px4-400d - hard drive sound every 5 seconds

Damon1
Posts: 13
Joined: Mon Aug 28, 2017 8:17 am

Re: Lenovo px4-400d - hard drive sound every 5 seconds

Post by Damon1 » Tue Aug 29, 2017 9:05 pm

Mijzelf wrote:
Damon1 wrote:any idea what I should be looking at or for?
You are looking for something which is accessing the disk every 5 secondes. Duh.

As nothing should be accessing the disk when idle for more than, let's say, 30 minutes, everything in the log is suspicious.
Any idea what the timestamp is set to I can't understand [35172.213677]. Take a look below at the logs, thanks.

https://uploadfiles.io/f9lej
https://uploadfiles.io/e10yi

Mijzelf
Posts: 6206
Joined: Mon Jun 16, 2008 10:45 am

Re: Lenovo px4-400d - hard drive sound every 5 seconds

Post by Mijzelf » Wed Aug 30, 2017 11:08 am

The timestamp is in seconds since kernel boot. To map it in the 'real world', the script regularly dumps a 'real timestamp' in the log:
[38583.539109] md0_raid1(4135): WRITE block 0 on sdb1 (1 sectors)
==== Tue Aug 29 20:56:01 BST 2017 ====
When running some filters and a uniq counter on log1, I get

Code: Select all

   1929 cma          10489): [35226.922167] dirtied inode 657689           EPOAGENT3700LYNX_UPDATE_0.ini) on dm-1
    344 flush-253:0          22068): [36300.524724] WRITE block 1778647144 on dm-0           8 sectors)
    172 flush-7:1          890): [35196.703301] WRITE block 4 on loop1           2 sectors)
    101 flush-8:32          891): [35206.315241] WRITE block 1048592 on sdc1           8 sectors)
   8070 jbd2/dm-0-8          4222): [36275.831343] WRITE block 2906917872 on dm-0           8 sectors)
   1659 loop1          871): [35191.700065] dirtied inode 30595           config) on sdc1
    232 lvscan          19436): [36049.099165] READ block 130944 on ram0           2 sectors)
   3556 md0_raid1          4135): [35176.986132] WRITE block 0 on sda1           1 sectors)
     60 md1_raid1          4149): [36048.820568] WRITE block 8 on sda2           8 sectors)
    168 mdadm          19405): [36048.665621] READ block 41961728 on sdb1           8 sectors)
    111 Mue_InUse          19147): [38826.232923] dirtied inode 657701           McScript.log) on dm-1
     34 mv          1471): [37304.849957] dirtied inode 1179817           kern.log.20170829203440.gz) on dm-1
      2 nailsd          5088): [35228.667635] dirtied inode 657679           ?) on dm-1
   2450 nailslogd          5099): [35176.986394] dirtied inode 657682           nailsd.db-journal) on dm-1
     70 nmbd          18208): [38743.922910] WRITE block 8 on loop1           2 sectors)
    208 pvscan          19434): [36049.066763] READ block 130944 on ram0           2 sectors)
    105 smbd          11041): [39801.825888] dirtied inode 289           smbpasswd) on loop1
       4 twonkyserver          3403): [36270.538573] dirtied inode 55574546           report-info.xml) on dm-0
    404 vgchange          19430): [36048.964961] READ block 130944 on ram0           2 sectors)
    404 vgs          19428): [36048.931820] READ block 130944 on ram0           2 sectors)
    210 vgscan          19425): [36048.877690] READ block 130944 on ram0           2 sectors)
     34 winbindd
which means cma was logged 1929 times, flush-253:0 344 times, etc.

You don't have to care about flush*, jbd2*, loop1 and *raid1. These processes are responsible for maintaining the filesystems, and are active because others are accessing the filesystems.
The processes pvscan, vgs, vgscan vgchange mdadm and lvscan are strange here. These are used for raid and LVM maintenance, but I wouldn't expect them to be active when you are not setting up the volumes.
The processes windbindd, smbd and nmbd are responsible for the samba system. 'Windows shares'. This line: 'smbd dirtied inode 289 smbpasswd) on loop1' means the samba password file was changed. Are you sure you weren't doing maintenance?

Then we have a nailslogd and a nailsd. Seeing the names I expect them to have something to do with thumbnail generation. Maybe nailslogd logs which media files are available/changed, possible in a file nailsd.db-journal, and nailsd reads that and creates thumbnails?

Mue_InUse seems to write a log McScript.log. If you can find it maybe it's clear why it is active.

mv is moving logfiles. I think this is normal maintenance, triggered by activities of other processes, growing the logs too big.

And we have cma, which is updating files like UpdateOptions.ini and UpdateHistory.ini. So maybe it has something to do with automatic updates.

And finally twonkyserver, which updated report-info.xml and twonky-locations-70.db.

Looking at the spread, I'd say nailslogd is the culprit. But I don't know why.

Damon1
Posts: 13
Joined: Mon Aug 28, 2017 8:17 am

Re: Lenovo px4-400d - hard drive sound every 5 seconds

Post by Damon1 » Mon Sep 04, 2017 12:47 pm

Hi, thanks a lot for all your help and time, appreciate it.

I have reset my box back to factory default, and the nailslog you mentioned is for the Antivirus which I have left disabled this time. Whilst doing this, I deleted all Shares and the noise completely went and was quiet.

It seems that when I put it in RAID1 the noise could be the copying? Even when it's idle and nothing is going on, looks like it's constantly looking for new data to copy.

I could get 4 disks would RAID 5 or RAID 10 be any different? RAID 0 is silent and so is 'None'.

Mijzelf
Posts: 6206
Joined: Mon Jun 16, 2008 10:45 am

Re: Lenovo px4-400d - hard drive sound every 5 seconds

Post by Mijzelf » Mon Sep 04, 2017 5:43 pm

Damon1 wrote:when I put it in RAID1 the noise could be the copying?
No. There is no copying. The data is written to both disks simultaneously.

Post Reply