Unable to load web interface or Hit Shares [SOLVED]

[pickthenimp]

EDIT: converting all of my drives to xfs solved the issue.

 

Hello, I just did a clean upgrade to Unraid 6.  Been running smooth for a few days and got some dockers spun up.  I am now unable to hit my web interface or any shares.  I can still access my docker apps just fine.  I only installed 2 plugins...dynamix system stats and the  Community Applications plugin for docker apps.

 

Syslog attached.  This part concerns me:

 

Aug 20 15:30:00 nas kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

Aug 20 15:30:00 nas kernel: IP: [<ffffffff8114cf24>] __discard_prealloc+0x98/0xb3

Aug 20 15:30:00 nas kernel: PGD cdb1e067 PUD cdb1f067 PMD 0

Aug 20 15:30:00 nas kernel: Oops: 0002 [#1] PREEMPT SMP

Aug 20 15:30:00 nas kernel: Modules linked in: veth xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat kvm_amd kvm md_mod k10temp i2c_piix4 pata_atiixp ahci sata_sil24 libahci r8169 mii acpi_cpufreq [last unloaded: md_mod]

Aug 20 15:30:00 nas kernel: CPU: 0 PID: 2383 Comm: shfs Not tainted 4.0.4-unRAID #5

Aug 20 15:30:00 nas kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./HZ03-GT-V2, BIOS 080015  12/24/2010

Aug 20 15:30:00 nas kernel: task: ffff88011abce3c0 ti: ffff8800cdbe0000 task.ti: ffff8800cdbe0000

Aug 20 15:30:00 nas kernel: RIP: 0010:[<ffffffff8114cf24>]  [<ffffffff8114cf24>] __discard_prealloc+0x98/0xb3

Aug 20 15:30:00 nas kernel: RSP: 0018:ffff8800cdbe3b98  EFLAGS: 00010246

Aug 20 15:30:00 nas kernel: RAX: ffff8800cccb02e8 RBX: ffff8800cccb02c0 RCX: 0000000000000000

Aug 20 15:30:00 nas kernel: RDX: ffffffff816462d0 RSI: ffff8800cccb02c0 RDI: ffff8800cdbe3cd8

Aug 20 15:30:00 nas kernel: RBP: ffff8800cdbe3bc8 R08: 0000000000001c7e R09: 000000000001e689

Aug 20 15:30:00 nas kernel: R10: ffffffff00001001 R11: ffffffff8115a6bd R12: ffff8800cdbe3cd8

Aug 20 15:30:00 nas kernel: R13: ffff8800cccb0360 R14: ffff8800cdbe3cd8 R15: 0000000000000000

Aug 20 15:30:00 nas kernel: FS:  00002b330e371700(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000

Aug 20 15:30:00 nas kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 20 15:30:00 nas kernel: CR2: 0000000000000008 CR3: 00000000cdcbe000 CR4: 00000000000007f0

Aug 20 15:30:00 nas kernel: Stack:

Aug 20 15:30:00 nas kernel: ffff8800cbbdb600 ffff8800cdbe3cd8 ffffc90010d13000 ffffc90010d331e8

Aug 20 15:30:00 nas kernel: ffff8800cdbe3cd8 ffff8800c9113000 ffff8800cdbe3bf8 ffffffff8114cfa3

Aug 20 15:30:00 nas kernel: ffff8800cdbe3cd8 ffff88011abce3c0 ffffc90010d13000 ffffc90010d13000

Aug 20 15:30:00 nas kernel: Call Trace:

Aug 20 15:30:00 nas kernel: [<ffffffff8114cfa3>] reiserfs_discard_all_prealloc+0x44/0x4e

Aug 20 15:30:00 nas kernel: [<ffffffff811697e4>] do_journal_end+0x4e7/0xc78

Aug 20 15:30:00 nas kernel: [<ffffffff8116a4d4>] journal_end+0xae/0xb6

Aug 20 15:30:00 nas kernel: [<ffffffff81150d48>] reiserfs_unlink+0x1de/0x23f

Aug 20 15:30:00 nas kernel: [<ffffffff81100148>] vfs_unlink+0xc5/0x165

Aug 20 15:30:00 nas kernel: [<ffffffff81103cca>] do_unlinkat+0x107/0x22f

Aug 20 15:30:00 nas kernel: [<ffffffff810fb823>] ? SyS_newlstat+0x25/0x2e

Aug 20 15:30:00 nas kernel: [<ffffffff8110450e>] SyS_unlink+0x11/0x13

Aug 20 15:30:00 nas kernel: [<ffffffff81604e09>] system_call_fastpath+0x12/0x17

Aug 20 15:30:00 nas kernel: Code: 1c 75 bb 0f 0b 85 c0 74 12 48 8b 93 e8 00 00 00 4c 89 ee 4c 89 e7 e8 bf 6e 00 00 48 8b 4b 28 44 89 7b 1c 48 8d 43 28 48 8b 53 30 <48> 89 51 08 48 89 0a 48 89 43 28 48 89 43 30 58 5b 41 5c 41 5d

Aug 20 15:30:00 nas kernel: RIP  [<ffffffff8114cf24>] __discard_prealloc+0x98/0xb3

Aug 20 15:30:00 nas kernel: RSP <ffff8800cdbe3b98>

Aug 20 15:30:00 nas kernel: CR2: 0000000000000008

Aug 20 15:30:00 nas kernel: ---[ end trace 80b3a205ff0566af ]---

 

Any ideas?

 

Also, not sure why this is all over my syslog: Invalid response packet from host 192.168.1.240

That is a windows machine on my network that has the shares mapped via unc path...

syslog.txt

[pickthenimp]

Unexciting update: I could not get this thing to gracefully shutdown to save my life.  Had to do a hard reset.  After it rebooted I am able to hit web interface and access shares again.  It forced me to do a parity check since it did not gracefully shutdown.  Wondering how long it will last...

 

Anyone have any insight based on my syslog above?  Thanks in advance.

[RobJ]

Hello, I just did a clean upgrade to Unraid 6.  Been running smooth for a few days and got some dockers spun up.  I am now unable to hit my web interface or any shares.  I can still access my docker apps just fine.  I only installed 2 plugins...dynamix system stats and the  Community Applications plugin for docker apps.

 

Syslog attached.  This part concerns me:

 

Aug 20 15:30:00 nas kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

Aug 20 15:30:00 nas kernel: IP: [<ffffffff8114cf24>] __discard_prealloc+0x98/0xb3

...

Aug 20 15:30:00 nas kernel: Call Trace:

Aug 20 15:30:00 nas kernel: [<ffffffff8114cfa3>] reiserfs_discard_all_prealloc+0x44/0x4e

...

It appears to be a one time crash while working in a Reiser file system.  There are no other apparent ReiserFS related issues, and I cannot see any other clues as to what actually crashed it, so it *may* be harmless.  To be safe, I would read Check Disk File systems wiki page, and in the webGui run a Check on every data drive and the Cache drive, since they all are formatted with ReiserFS.

 

Also, not sure why this is all over my syslog: Invalid response packet from host 192.168.1.240

That is a windows machine on my network that has the shares mapped via unc path...

That's a known issue and you've identified the nuisance spewing it.  unRAID 6.1 suppresses it, but is still in beta or RC.  You can either live with it for now (it's a harmless nuisance), or upgrade unRAID to the current v6.1-rc5.

 

Two different drives showed indications of a faulty SATA cable, ST3000DM001-9YN166 Z1F12JLY twice (Disk 5) and WDC WD20EARS-00MVWB0 WD-WMAZA3638502 (Disk 1).  I would replace their SATA cables with better quality ones.

[RobJ]

One more small item, forgot to mention it, it looks like you have 512MB reserved for graphics use.  I would go into your BIOS settings and change that to the lowest possible RAM reservation, as unRAID only uses a text console.  That should give you almost 512MB of additional RAM for unRAID to use.

[pickthenimp]

Thanks for the reply Rob!  I am running check disk now on each drive and will report back if I find anything.

 

I upgraded to rc5 just and it has surpressed that nusiance.

 

 

Interesting note on the sata cables...I will look into replacing those in the near future, but probably did not cause my crash right?

 

And great tip on the reserved memory!  Had no idea I was only able to use 3.5 of my 4GB

[mr-hexen]

I dont get those invalid response nuisance reports in my log. I have AFP disabled.

[pickthenimp]

So, everything was running fine for a few days...now I can't access my shares again.  Web GUI is up but pretty useless.  I try to reboot via the web but it won't let me.  I noticed it says Mover is running?

 

Here is relevant syslog entries.  Did apcupsd try to shutdown my machine?

 

Aug 22 15:26:16 nas php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php

Aug 22 15:26:19 nas php:  Updating templates...  Updating info...  Done.

Aug 22 15:27:32 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 22 15:38:02 nas kernel: mdcmd (76): spindown 3

Aug 22 16:31:44 nas kernel: mdcmd (77): spindown 3

Aug 22 16:31:46 nas kernel: mdcmd (78): spindown 2

Aug 22 16:31:48 nas kernel: mdcmd (79): spindown 5

Aug 22 16:44:03 nas kernel: mdcmd (80): spindown 1

Aug 22 17:10:02 nas kernel: mdcmd (81): spindown 4

Aug 22 18:17:56 nas kernel: mdcmd (82): spindown 4

Aug 22 19:21:31 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 22 19:26:25 nas kernel: mdcmd (83): spindown 4

Aug 22 19:41:13 nas kernel: mdcmd (84): spindown 5

Aug 22 19:43:10 nas kernel: mdcmd (85): spindown 3

Aug 22 20:31:39 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 22 20:36:49 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 22 20:44:57 nas kernel: mdcmd (86): spindown 4

Aug 22 22:09:35 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 22 22:41:48 nas kernel: mdcmd (87): spindown 1

Aug 22 22:43:59 nas kernel: mdcmd (88): spindown 3

Aug 22 22:43:59 nas kernel: mdcmd (89): spindown 4

Aug 22 22:46:26 nas kernel: mdcmd (90): spindown 5

Aug 23 00:01:56 nas kernel: mdcmd (91): spindown 2

Aug 23 00:28:50 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 23 01:00:01 nas logger: mover started

Aug 23 01:00:01 nas logger: moving "TV"

Aug 23 01:00:01 nas logger: ./TV/Why! With Hannibal Buress/Season 01/Why! With Hannibal Buress - S01E07 - Episode 7 - HDTV-720p.mkv

Aug 23 01:00:07 nas logger: .d..t...... ./

Aug 23 01:30:39 nas kernel: mdcmd (92): spindown 0

Aug 23 01:58:53 nas kernel: mdcmd (93): spindown 1

Aug 23 01:59:02 nas kernel: mdcmd (94): spindown 2

Aug 23 01:59:09 nas kernel: mdcmd (95): spindown 3

Aug 23 01:59:18 nas kernel: mdcmd (96): spindown 4

Aug 23 02:01:30 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 23 02:30:27 nas kernel: mdcmd (97): spindown 3

Aug 23 04:20:45 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 23 04:40:01 nas apcupsd[1882]: apcupsd exiting, signal 15

Aug 23 04:40:01 nas apcupsd[1882]: apcupsd shutdown succeeded

Aug 23 04:40:04 nas apcupsd[10225]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded

Aug 23 04:40:04 nas apcupsd[10225]: NIS server startup succeeded

Aug 23 05:48:15 nas avahi-daemon[26711]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

[pickthenimp]

So I am pretty sure my lockups are tied directly to the scheduled mover task.  The past two days my unraid has locked up and the last entry in syslog pertains to starting the mover (and never finishing).  I can see the web interface "Mover is running".

 

Aug 24 01:00:01 nas logger: mover started

Aug 24 01:00:01 nas logger: moving "TV"

Aug 24 01:00:01 nas logger: ./TV/The Brink/Season 01/The Brink - S01E10 - There Will Be Consequences - HDTV-720p.mkv

Aug 24 01:00:01 nas logger: .d..t...... ./

Aug 24 01:56:22 nas kernel: mdcmd (68): spindown 1

Aug 24 01:56:23 nas kernel: mdcmd (69): spindown 4

Aug 24 01:56:53 nas kernel: mdcmd (70): spindown 2

Aug 24 01:59:15 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UT

F-8 problem?)

Aug 24 02:31:22 nas kernel: mdcmd (71): spindown 4

Aug 24 02:45:37 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 24 07:13:33 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

root@nas:~#

 

I would really appreciate any help troubleshooting this.  Thanks.

[goinsnoopin]

I am having a similar issue...check out my thread:  http://lime-technology.com/forum/index.php?topic=41861.0

 

In my instance, I am still able to telnet into the unraid console even though the webgui has crashed.  If you are able to do so, type the command diagnostics, as it will create a zip file with all of the diagnostics that can be used by others in helping you to troubleshoot the crash.

 

What motherboard, cpu and how much ram do you have?

 

If you type ps -A when the webgui is crashed do you have a bunch of smbd processes running?  When in the crashed state I seem to have a ton of these running and I am convinced that it is related to the crash...but am not sure.

 

Hopefully, someone fill find a solution.

 

Dan

 

[pickthenimp]

 

If you type ps -A when the webgui is crashed do you have a bunch of smbd processes running?  When in the crashed state I seem to have a ton of these running and I am convinced that it is related to the crash...but am not sure.

 

Hopefully, someone fill find a solution.

 

Dan

 

Hey Dan, thanks for the response.  I have a ton of smbd processes when I run ps -A.  I ran the diagnostics and will try to get this off my flash drive when I get home.  I will have to manually reboot my server since it does not accept shutdown or reboot commands.

 

I have 4 GB of RAM, will get you the other specs this evening.

[goinsnoopin]

So it sounds like we are in a similar position, hopefully someone will be able to identify this issue!  I only have 2GB ram in my server and others were thinking that maybe I was running out of ram...but since you have 4GB, that may not be the case.  Don't know if you read through my thread yet...but I did eliminate all plugins and dockers in an attempt to get to eliminate them as possibilities for introducing errors...so I am completely stock unraid.

 

Hopefully someone will come up with a solution soon as manual reboots are not good and since the time between crashes appears to be random (sometimes less than 24 hours...to sometimes as long as 4 days) it has become frustrating to the less technical people in my house.

 

Dan

[itimpi]

Hopefully someone will come up with a solution soon as manual reboots are not good and since the time between crashes appears to be random (sometimes less than 24 hours...to sometimes as long as 4 days) it has become frustrating to the less technical people in my house.

You might want to install the Powerdown plugin.  With that installed you should be able to close down/reboot from a telnet session even if the GUI is hanging.  I think that plugin also saves logs to the flash before shutting down which can be useful if you forgot to save it yourself.

[goinsnoopin]

I did install the powerdown plugin, however with this crash, it is unable to shutdown the unraid server.  It gives the message that powerdown script has initiated and that the server is going down...however after 8 hours of waiting, it never went down and no messages show up on the console. So since it did not work, I removed it as well until this bug (?) is resolved.

 

[pickthenimp]

Dan, I am having Dejavu reading your post.

 

"Additional Info:

 

I tried to follow limetech's instructions in this post to shutdown unraid from the console:  http://lime-technology.com/forum/index.php?topic=41938.msg398562#msg398562

 

When I run: umount /mnt/disk*  I get a couple of disks that are in use or busy and to run lsof or fuser to see the list of files in use.  "

 

Same exact thing is happening to me.  My telnet sessions keep locking up. I cant get this thing to gracefully shutdown to save my life.  Installing the powerdown script was going to be my next step but sad to hear it does not work for you...

[bonienl]

So I am pretty sure my lockups are tied directly to the scheduled mover task.  The past two days my unraid has locked up and the last entry in syslog pertains to starting the mover (and never finishing).  I can see the web interface "Mover is running".

 

Aug 24 01:00:01 nas logger: mover started

Aug 24 01:00:01 nas logger: moving "TV"

Aug 24 01:00:01 nas logger: ./TV/The Brink/Season 01/The Brink - S01E10 - There Will Be Consequences - HDTV-720p.mkv

Aug 24 01:00:01 nas logger: .d..t...... ./

Aug 24 01:56:22 nas kernel: mdcmd (68): spindown 1

Aug 24 01:56:23 nas kernel: mdcmd (69): spindown 4

Aug 24 01:56:53 nas kernel: mdcmd (70): spindown 2

Aug 24 01:59:15 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UT

F-8 problem?)

Aug 24 02:31:22 nas kernel: mdcmd (71): spindown 4

Aug 24 02:45:37 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

Aug 24 07:13:33 nas avahi-daemon[1969]: server.c: Packet too short or invalid while reading response record. (Maybe a UTF-8 problem?)

root@nas:~#

 

I would really appreciate any help troubleshooting this.  Thanks.

 

What are the folder names on your cache drive (including hidden ones), it might be that the mover is choking on one of them?

 

[pickthenimp]

@bonienl Not sure what you mean exactly.  I have an apps folder which is set to live on the cache drive and not be moved.  Then whenever I move something to my "TV" or "Movies" share it creates that same folder name on the Cache drive until it is moved at night via the mover script.  Whats interesting is if I manually run the mover script it completes successfully without any issue.

[bonienl]

@bonienl Not sure what you mean exactly.  I have an apps folder which is set to live on the cache drive and not be moved.  Then whenever I move something to my "TV" or "Movies" share it creates that same folder name on the Cache drive until it is moved at night via the mover script.  Whats interesting is if I manually run the mover script it completes successfully without any issue.

 

I was thinking that you might have had other top-level folders on your cache which could interfere with the mover, but if a manual run does finish it isn't the case.

 

Default schedule of the mover is daily at 03:40am, did you create any other activities to be initiated around that time (or time your mover is running)?

 

[pickthenimp]

@bonienl Not sure what you mean exactly.  I have an apps folder which is set to live on the cache drive and not be moved.  Then whenever I move something to my "TV" or "Movies" share it creates that same folder name on the Cache drive until it is moved at night via the mover script.  Whats interesting is if I manually run the mover script it completes successfully without any issue.

 

I was thinking that you might have had other top-level folders on your cache which could interfere with the mover, but if a manual run does finish it isn't the case.

 

Default schedule of the mover is daily at 03:40am, did you create any other activities to be initiated around that time (or time your mover is running)?

 

Gotcha, nothing else runs at that time.  Maybe I will try disabling the mover script and just manually kick it off for a few days and see if that makes a difference...

[bonienl]

Maybe I will try disabling the mover script and just manually kick it off for a few days and see if that makes a difference...

 

The easiest way to do that is rename (or delete) the file /boot/config/plugins/dynamix/mover.cron

 

And run the command: update_cron

 

Afterwards you can simply re-apply the mover settings in the GUI or restore the .cron file and rerun the update command.

 

[pickthenimp]

Attached is my diagnostics.  Hopefully this is valuable.

 

nas-diagnostics-20150824-1002.zip

[pickthenimp]

I made it 2.5 days without a crash..but just checked this morning and see "Mover is running..." again on the web gui.  New errors in the syslog.  Does this mean anything?

 

Aug 27 01:15:01 nas logger: mover started

Aug 27 01:15:01 nas logger: moving "Movies"

Aug 27 01:15:01 nas logger: ./Movies/hd/What We Do in the Shadows (2014)/What We Do in the Shadows (2014).mkv

Aug 27 01:15:08 nas logger: .d..t...... ./

Aug 27 01:15:33 nas kernel: REISERFS error (device md5): vs-4020 is_reusable: bitmap block168558592(22357) can't be freed or reused

Aug 27 01:15:33 nas kernel: REISERFS (device md5): Remounting filesystem read-only

Aug 27 01:15:41 nas kernel: REISERFS warning (device md5): journal-1409 journal_mark_dirty: returning because j_wcount was 0

 

 

And when I initiate the powerdown script, I get this returned:

 

 

The system is going down for reboot NOW!

root@nas:~#

Message from syslogd@nas at Aug 27 09:58:27 ...

kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1

 

EDIT: added latest diagnostics

nas-diagnostics-20150827-1023.zip

[trurl]

I made it 2.5 days without a crash..but just checked this morning and see "Mover is running..." again on the web gui.  New errors in the syslog.  Does this mean anything?

 

Aug 27 01:15:01 nas logger: mover started

Aug 27 01:15:01 nas logger: moving "Movies"

Aug 27 01:15:01 nas logger: ./Movies/hd/What We Do in the Shadows (2014)/What We Do in the Shadows (2014).mkv

Aug 27 01:15:08 nas logger: .d..t...... ./

Aug 27 01:15:33 nas kernel: REISERFS error (device md5): vs-4020 is_reusable: bitmap block168558592(22357) can't be freed or reused

Aug 27 01:15:33 nas kernel: REISERFS (device md5): Remounting filesystem read-only

Aug 27 01:15:41 nas kernel: REISERFS warning (device md5): journal-1409 journal_mark_dirty: returning because j_wcount was 0

 

 

And when I initiate the powerdown script, I get this returned:

 

 

The system is going down for reboot NOW!

root@nas:~#

Message from syslogd@nas at Aug 27 09:58:27 ...

kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1

 

EDIT: added latest diagnostics

See Check Disk Filesystems in the wiki

[pickthenimp]

I made it 2.5 days without a crash..but just checked this morning and see "Mover is running..." again on the web gui.  New errors in the syslog.  Does this mean anything?

 

Aug 27 01:15:01 nas logger: mover started

Aug 27 01:15:01 nas logger: moving "Movies"

Aug 27 01:15:01 nas logger: ./Movies/hd/What We Do in the Shadows (2014)/What We Do in the Shadows (2014).mkv

Aug 27 01:15:08 nas logger: .d..t...... ./

Aug 27 01:15:33 nas kernel: REISERFS error (device md5): vs-4020 is_reusable: bitmap block168558592(22357) can't be freed or reused

Aug 27 01:15:33 nas kernel: REISERFS (device md5): Remounting filesystem read-only

Aug 27 01:15:41 nas kernel: REISERFS warning (device md5): journal-1409 journal_mark_dirty: returning because j_wcount was 0

 

 

And when I initiate the powerdown script, I get this returned:

 

 

The system is going down for reboot NOW!

root@nas:~#

Message from syslogd@nas at Aug 27 09:58:27 ...

kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1

 

EDIT: added latest diagnostics

See Check Disk Filesystems in the wiki

 

Thanks for the response Trurl, I ran reiserfsck last week when I was suggested to and it reported no errors.

[trurl]

I made it 2.5 days without a crash..but just checked this morning and see "Mover is running..." again on the web gui.  New errors in the syslog.  Does this mean anything?

 

Aug 27 01:15:01 nas logger: mover started

Aug 27 01:15:01 nas logger: moving "Movies"

Aug 27 01:15:01 nas logger: ./Movies/hd/What We Do in the Shadows (2014)/What We Do in the Shadows (2014).mkv

Aug 27 01:15:08 nas logger: .d..t...... ./

Aug 27 01:15:33 nas kernel: REISERFS error (device md5): vs-4020 is_reusable: bitmap block168558592(22357) can't be freed or reused

Aug 27 01:15:33 nas kernel: REISERFS (device md5): Remounting filesystem read-only

Aug 27 01:15:41 nas kernel: REISERFS warning (device md5): journal-1409 journal_mark_dirty: returning because j_wcount was 0

 

 

And when I initiate the powerdown script, I get this returned:

 

 

The system is going down for reboot NOW!

root@nas:~#

Message from syslogd@nas at Aug 27 09:58:27 ...

kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1

 

EDIT: added latest diagnostics

See Check Disk Filesystems in the wiki

 

Thanks for the response Trurl, I ran reiserfsck last week when I was suggested to and it reported no errors.

That was last week. The syslog excerpt you posted is telling you that drive5 has been made read-only due to corruption.

[pickthenimp]

Thanks, I will run it again once I get my unraid rebooted.  Any tips on how I can do so cleanly?

 

I started killing processes to try to get this thing to gracefully shutdown.  Running a ps I saw a 'fuser' was running and once I killed it, It finally said "mover script complete" and I attempted to stop the arraid from the web gui.

 

 

Then, I tried to invoke the powerdown script again but it is getting hung up and wont go down:

 

 

Aug 27 11:20:09 nas emhttp: Retry unmounting user share(s)...

Aug 27 11:20:14 nas emhttp: shcmd (290): set -o pipefail ; umount /mnt/user |& logger

Aug 27 11:20:14 nas logger: umount: /mnt/user: device is busy.

Aug 27 11:20:14 nas logger:        (In some cases useful info about processes that use

Aug 27 11:20:14 nas logger:          the device is found by lsof( or fuser(1))

Aug 27 11:20:14 nas emhttp: shcmd: shcmd (290): exit status: 1

Aug 27 11:20:14 nas emhttp: shcmd (291): rmdir /mnt/user |& logger

Aug 27 11:20:14 nas logger: rmdir: failed to remove '/mnt/user': Device or resource busy

Aug 27 11:20:14 nas emhttp: shcmd (292): set -o pipefail ; umount /mnt/user0 |& logger

Aug 27 11:20:14 nas logger: umount: /mnt/user0: device is busy.

Aug 27 11:20:14 nas logger:        (In some cases useful info about processes that use

Aug 27 11:20:14 nas logger:          the device is found by lsof( or fuser(1))

Aug 27 11:20:14 nas emhttp: shcmd: shcmd (292): exit status: 1

Aug 27 11:20:14 nas emhttp: shcmd (293): rmdir /mnt/user0 |& logger

Aug 27 11:20:14 nas logger: rmdir: failed to remove '/mnt/user0': Device or resource busy

Aug 27 11:20:14 nas emhttp: shcmd (294): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule

:#01215 1 * * * /usr/local/sbin/mover |& logger#012"

Aug 27 11:20:14 nas emhttp: shcmd (295): /usr/local/sbin/update_cron &> /dev/null

Aug 27 11:20:14 nas emhttp: Retry unmounting user share(s)...