Having Issues with my NAS. Shares missing, WebUI broken.

[Jocko]

Yes, you have to use exactly the same name (be careful it is also case sensitive).

So yes there is an issue with your raid previously. Currently it has a clean status. So currently do nothing, later I will send you a command to force a resyncing.

About the browser, try to clean the cache or use the developer tools of the browser (key: F12), and disable the cache (network tab)

[Woodani]

I recreated my shares and it looks like my data is all there! :woohoo very happy about that.

Let me know what I need to do next as far a forcing a resync or anything.

I cleared the cache in Firefox and Chrome and nothing changed. I also enabled the developer tools and disabled cache in both and nothing changed. I did see a number of errors in the console in chrome. I'm not sure if they are relevant but I can post them if you'd like.

Thanks.

[Jocko]

About md, either you use a tip found on the net or the raid issue set it but now you should disable the bitmaps option. Anyhow according your output it is set badly as there is no used pages.
For example, you should have

Code: Select all

root@Acrab:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid5 sdb8[0] sdd8[6] sda8[5] sde8[7] sdc8[4]
      11709457408 blocks super 1.0 level 5, 128k chunk, algorithm 2 [5/5] [UUUUU]
      bitmap: 2/22 pages [8KB], 65536KB chunk

md1 : active raid1 sdc9[2] sdc10[1]
      1401792 blocks super 1.0 [2/2] [UU]

unused devices: <none>
root@Acrab:/ #


So run

Code: Select all

 mdadm --grow --bitmap=none /dev/md0

and the bitmap line should be gone

Code: Select all

cat /proc/mdstat

To check your raid you can use this command

Code: Select all

 mdadm --misc --action=check /dev/md0

Please to note with 3Tb disk the job runs for around 2 days and you must not stop the nas.


About fw interface, please to post the console messages because on my side all is clean with Chrome or FF.

[Jocko]

I also noticed you set a custom chunk size on your raid (512kB).
According with my own tests, this value degrades r/w performances on a 5big2 and 128k seems to be better

[Woodani]

I haven't intentionally done anything to enable the bitmap and the only things I've done to the NAS (besides setting up shares and such in the webgui) were what you all instructed me to do when you helped me get the NAS working originally. If i enabled the bitmap option I did it by mistake.

Here is the output of cat /proc/mdstat

Code: Select all

root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid5 sda8[0] sde8[4] sdd8[3] sdc8[2] sdb8[1]
      15616464896 blocks super 1.0 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>

The bitmap line is gone so I assume that worked as intended.

I ran the command to check my raid and it seems to have completed instantly. See the output of my terminal.

Code: Select all

root@fvdwsl-base:/ # mdadm --misc --action=check /dev/md0
root@fvdwsl-base:/ #

If that check is still running in the background how will I know when it is finished and what the results of the check are?

On the browser issue. Here is what errors I saw in the console in chrome. The formatting of this looks a little screwed up. I'll also attach a screenshot for more clarity.

Code: Select all

dataEngine.js?v=182-1410:37 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
getXML @ dataEngine.js?v=182-1410:37
data_Engine @ dataEngine.js?v=182-1410:18
App @ objects.js?v=182-1410:50
(anonymous) @ global.js?v=182-1410:1
objects.js?v=182-1410:118 Uncaught TypeError: Cannot read property 'firstChild' of undefined
    at scalarHidden.loadSclrData [as loadData] (objects.js?v=182-1410:118)
    at scalarHidden.createScalar (objects.js?v=182-1410:116)
    at new scalarHidden (objects.js?v=182-1410:188)
    at home_m.htm?v=182-1410:54
loadSclrData @ objects.js?v=182-1410:118
createScalar @ objects.js?v=182-1410:116
scalarHidden @ objects.js?v=182-1410:188
(anonymous) @ home_m.htm?v=182-1410:54

2020-12-10 17_46_11-.png

It's not an issue for me to continue using edge or IE but I am curious about whats causing the issue. I'll try accessing it from a different PC using chrome and firefox and see what the results are there.

[Woodani]

I didn't intentionally set a custom chunk size so again if I did that I did it by mistake.

If you look at my first post on this forum here http://plugout.net/viewtopic.php?f=26&t=3365 you'll see that my 5big2 was the first one fvdw had ever seen without 64bit support in uboot so I have a strange NAS. I'm not sure if something we did during that original setup could have changed the chuck size but I doubt that because I don't think he helped me set up the raid itself. It might be another side effect of this strange nas or something I changed by mistake.

In any case, is there a safe way to change the chunk size down to 128k? I have noticed I wasn't getting a good r/w speeds as I was expecting.

Thanks again for your help.

[Jocko]

If that check is still running in the background how will I know when it is finished and what the results of the check are?

Yes it runs in background and you can see progress with mdstat

Code: Select all

root@Acrab:/ # mdadm --misc --action=check /dev/md1
root@Acrab:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid5 sdb8[0] sdd8[6] sda8[5] sde8[7] sdc8[4]
      11709457408 blocks super 1.0 level 5, 128k chunk, algorithm 2 [5/5] [UUUUU]
      bitmap: 2/22 pages [8KB], 65536KB chunk

md1 : active raid1 sdc9[2] sdc10[1]
      1401792 blocks super 1.0 [2/2] [UU]
      [>....................]  check =  3.9% (55424/1401792) finish=1.2min speed=18474K/sec


About web-interface, first warning is not an issue and yes we have to use synchronous request...
So the issue in on some corrupted files of the web-interface and then js fails to reach an html box with the instruction firstChild...

I go to do some tests on a fresh version 18.2

About chunk size, I think you can not change it without destroying the raid and rebuilding it (so you lose your data) I go to check this point

[Jocko]

about chunk yes you can change it without destroying the raid.

If you want to change the value, run this command

Code: Select all

mdadm --grow --chunk=128 /dev/md0

But you should run it only when the check is complete and note this action takes more time than a check job (here around 4 days)

[Woodani]

Ok. I will wait for the check to complete then. In the meantime let me know if there is anything else you'd like me to test on my end to help you with the browser issue.

Thanks for all your help again. I'll donate some more to your paypal since you guys have been so helpful.

[Jocko]

Hi

For testing, I installed a fresh version 18.2 on a nwsp2 and at each time I cleared the browser cache and I also disabled it
So on two laptops with win8.1/64bits and win10/64bits, the web-interface is rightly loaded on the latest version of Chrome, FF and Edge :scratch

I also reloaded successfully the web-interface if I use all supported languages (a corrupted dictionary may occur this behaviour)

Some idea which may explain the behaviour on your side:
- some files of the web-interface are corrupted
- either your antivirus or some safety guard add-ons prevent the browser from loading some init files

For the last point, you can easily validate it : start FF with its safe mode (which disables all add-ons) => Go to the help menu. If the web-interface is still not rightly loaded, try by disabling the web shield of your anti-virus

For the first point, open the web-interface on Edge and upgrade again the firmware even if it claims you have the latest version, this will install again a fresh version (without changing your settings). But should wait all raid check is complete to do it