Is my Pro6 failing (keeps disappearing from network during backup job) (Pro6 v6.9.3)

[powellandy1]

Hi

I'm running a backup job on my 104 using the Pro6 as a source. Four times now it has just disappeared from the network (and the backup job has failed on the 104). Three times I could restart through the front panel, the last time I just had to hold the power button down for an unsafe restart. It was not pingable prior on any occasion.

Looking in the logs I noted lots of errors about the UPS (which is connected to the 312 and then shared) - although these errors did not appear on the 104 which was on the whole time as well and shares the same UPS remotely. Anyway - I deleted the remote UPS on the Pro6 and it still died a fourth time.

Looking in the logs (which I have emailed) I see lots of:

Aug 11 10:40:18 Pro6 kernel: ------------[ cut here ]------------
Aug 11 10:40:18 Pro6 kernel:  ffff88004616bcc0
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633 ffff88004616bca0 ffffffff8806f3ac ffff8800638cf000
Aug 11 10:40:18 Pro6 kernel: cleanup rbuf bug: copied A135174F seq A135172F rcvnxt A135172F
Aug 11 10:40:18 Pro6 kernel:  ffff88004616bcc0
Aug 11 10:40:18 Pro6 kernel:  00000000fffffff5 ffff8800638cf0a8 0000000000000000 ffff8800638cf4b8
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc88 ffffffff883ec5a8 ffff88004616bcd0
Aug 11 10:40:18 Pro6 kernel:  ffff8800638cf0a8 0000000000000000 ffff8800638cf4b8
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc68 ffffffff883ec5a8 ffff88004616bcb0
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633 ffff88004616bca0 ffffffff8806f3ac ffff8800638cf000
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633 ffff88004616bca0 ffffffff8806f3ac ffff8800638cf000
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc88 ffffffff883ec5a8 ffff88004616bcd0
Aug 11 10:40:18 Pro6 kernel: cleanup rbuf bug: copied A135174F seq A135172F rcvnxt A135172F
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff881427e1>] vfs_read+0x81/0x130
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633 ffff88004616bca0 ffffffff8806f3ac ffff8800638cf000
Aug 11 10:40:18 Pro6 kernel:  ffff8800638cf000
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633
Aug 11 10:40:18 Pro6 kernel:  ffffffff883ec5a8 ffff88004616bcd0
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff8806f3ac>] warn_slowpath_common+0x7c/0xb0
Aug 11 10:40:18 Pro6 kernel:  00000000fffffff5 ffff8800638cf0a8 0000000000000000
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc88 ffffffff883ec5a8 ffff88004616bcd0
Aug 11 10:40:18 Pro6 kernel:  ffff88004616bca0
Aug 11 10:40:18 Pro6 kernel: cleanup rbuf bug: copied A135174F seq A135172F rcvnxt A135172F
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff8806f427>] warn_slowpath_fmt+0x47/0x50
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633 ffff88004616bcc0 ffffffff8806f3ac ffff880064b04d00
Aug 11 10:40:18 Pro6 kernel:  00000000fffffff5
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc68 ffffffff883ec5a8 ffff88004616bcb0
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff881420b2>] __vfs_read+0xa2/0xd0
Aug 11 10:40:18 Pro6 kernel: Modules linked in: nv6lcd(O) vpd(PO)
Aug 11 10:40:18 Pro6 kernel:  ffffffff88e05633
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc68 ffffffff883ec5a8 ffff88004616bcb0
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff881427e1>] vfs_read+0x81/0x130
Aug 11 10:40:18 Pro6 kernel: cleanup rbuf bug: copied A135174F seq A135172F rcvnxt A135172F
Aug 11 10:40:18 Pro6 kernel: ---[ end trace bd3f54c7fe61528b ]---
Aug 11 10:40:18 Pro6 kernel: ---[ end trace bd3f54c7fe615292 ]---
Aug 11 10:40:18 Pro6 kernel:  [<ffffffff8899983d>] inet_recvmsg+0x6d/0x80
Aug 11 10:40:18 Pro6 kernel:  0000000000000000 ffff88004616bc68
-- Reboot --
Aug 11 18:37:03 Pro6 kernel: Initializing cgroup subsys cpuset
Aug 11 18:37:03 Pro6 kernel: Initializing cgroup subsys cpu
Aug 11 18:37:03 Pro6 kernel: Initializing cgroup subsys cpuacct

Disk health looks fine.

Can any one pinpoint the problem??
Thanks

Andy

[StephenB]

That's a new one on me.

What apps/packages are installed on the NAS?

Perhaps run a memory test???

[powellandy1]

Hi

Just SMB Plus v1.0.8

I will run a memory test, thanks.

Cheers

Andy

[mdgm-ntgr]

How did the memory test go? A few passes should be sufficient.

[powellandy1]

Hi

It's still running the backup since I last rebooted it.

I'm just letting get on with it until it finishes or dies again and then I'll run the memory test.

My little 104 only writes at about 19MB/s and it's got about 13TB to do (although it's done 10TB now)

Will post here when test is run.

Thanks

Andy

[powellandy1]

Hi

Just run 5 passes (a little over 2h) with no errors on the LCD.

Anything else it could  be??
Thanks

Andy

[mdgm-ntgr]

Please send in your logs (see the Sending Logs link in my sig)

[powellandy1]

Hi

I sent some in 12/8 to the email address. Forwarded again now - subject 'Fw: Pro6 failing'

I'll send another set tonight - although I've since taken the 6 disks that were in there at the time out and it just has a scratch disk in (if that's relevant).

Thanks

Andy

[powellandy1]

Hi

Sorry - it looks like the log moves with the disk - so the log from the Pro6 (which now has a 2TB disk that used to be in the 312 in) looks like what was the 312 log. The 6 disks that were in the pro6 were factory reset in the 516. I'm afraid the log above is the only one I have remaining.

Cheers

Andy

[StephenB]

---

@powellandy1 wrote: it looks like the log moves with the disk

---

Of course.  Like the configuration, it is stored in the OS partition on the disks.