RAIDar diagnostics

[davidr1]

I noticed from RAIDar diagnostics the following:

NAS314
Successfully completed diagnostics
System
Disk 1 has 1 Current Pending Sectors
Logs
2017-05-11 15:45:57: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-10 14:30:30: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-09 12:03:11: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-08 14:06:43: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-07 14:33:28: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-06 15:24:26: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-05 07:46:45: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-04 08:33:55: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-03 14:55:22: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-02 17:00:45: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-01 07:56:44: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-30 14:19:36: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-29 14:57:51: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-28 15:34:41: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-27 08:50:49: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-26 14:50:08: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-25 14:59:16: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-24 14:31:03: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-23 16:00:46: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-22 15:35:22: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-21 11:23:35: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-20 09:49:06: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-04-19 09:44:33: home.mount: Directory /home to mount over is not empty, mounting anyway.

PRO
Successfully completed diagnostics
System

Logs
2017-05-25 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-24 11:58:21: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-24 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-23 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-22 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-21 05:53:10: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-20 05:40:48: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-19 07:00:44: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-18 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-17 07:00:38: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-16 07:00:39: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-15 11:12:21: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-15 07:00:39: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-14 07:25:06: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-13 07:22:02: home.mount: Directory /home to mount over is not empty, mounting anyway.

ULTRA
Successfully completed diagnostics
System

Logs
2017-05-25 07:00:40: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-24 11:58:27: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-24 07:00:42: home.mount: Directory /home to mount over is not empty, mounting anyway.
2017-05-23 07:00:42: home.mount: Directory /home to mount over is not empty, mounting anyway.

1. Does 'Disk 1 has 1 Current Pending Sectors'indicate the start of disk failure?

2. Is the rest significant?

This is recent - on disks all of different ages all since April

Thanks

[mdgm-ntgr]

1 is not a lot, but you should certainly keep an eye on that disk.

As for the other issue it's not that important.

You could do

# mount --bind / /mnt
# rmdir /mnt/home/*
# umount /mnt

and that should get rid of that message.

[davidr1]

hi mdgm

Thanks but:

mount --bind / /mnt

 rmdir: failed to remove '/mnt/home/*': No such file or directory

though

mount --bind / /mnt

does seem syntactically correct to me???

[StephenB]

if you do ls /mnt do you see the home folder?

[davidr1]

Hi StephenB,

After

mount --bind / /mnt

 I see home

drwxr-xr-x 1 root  root     0 May 25 07:54 home
lrwxrwxrwx 1 root  root     5 Sep 25  2015 homes -> /home

[StephenB]

Good.  Is anything in that folder?

[davidr1]

On the Ultra:

# ls -ahl /home
total 16K
drwxr-xr-x 1 admin admin 0 Oct 3 2015 .
drwxr-xr-x 1 root root 242 May 28 08:31 ..
root@NASUltra:/home#

On the Pro:

# ls -ahl /home
total 16K
drwxr-xr-x 1 admin admin 20 Sep 18 2015 .
drwxr-xr-x 1 root root 276 May 30 08:08 ..
drwx------ 1 admin admin 0 May 27 10:32 admin
drwx------ 1 david users 0 Oct 9 2015 david
root@NASPro:/home#

I haven't woken the 314 up yet - doing some re-cabling

[StephenB]

The idea is to do ls -alh /mnt/home

/home is a mount point for /data/home.  Once the system is booted, when you browse that, you are really looking at the data volume.  

Your error messages are saying that the mount point itself has files in it - and it shouldn't.  Remounting / as /mnt allows you to see what's in the mount point, instead of the data volume.  But that only works if you look in /mnt/home.

[davidr1]

Apologies StephenB,

Carelessness - worse, I know! (Dumb...)

# mount --bind / /mnt
root@NASUltra:~# ls -alh /mnt/home
total 16K
drwxr-xr-x 1 root root 0 May 25 07:54 .
drwxr-xr-x 1 root root 242 May 28 08:31 ..
root@NASUltra:~#

# mount --bind / /mnt
root@NASPro:~# ls -alh /mnt/home
total 16K
drwxr-xr-x 1 root root   0 May 25 07:52 .
drwxr-xr-x 1 root root 276 May 30 08:08 ..
root@NASPro:~#

# mount --bind / /mnt
root@NAS314:~# ls -alh /mnt/home
total 16K
drwxr-xr-x 1 root root   0 May 11 15:55 .
drwxr-xr-x 1 root root 228 May 28 08:32 ..
root@NAS314:~#

 
David

[StephenB]

---

@davidr1 wrote:

Carelessness - worse, I know! (Dumb...)

---

I've done worse, and I suspect most others here have

Based on your latest post, it looks to me like either

• the original issue is now resolved
• there is a bug in the diagnostic

You might try re-running it, and see if it is still reported.