wirenut

still hoping for a response... am I in the wrong area?? Try checking your unmenu_local.conf file for the following line: MyHost = <some value> Set it to the proper value. If the server IP address if 192.168.1.10 use: MyHost = 192.168.1.10 You may need to restart unmenu for this to work. interesting... I do not have that file. only conf files i have are myMain.conf, syslog_match.conf and unmenu.conf OK< found missing conf file in unraid flash backup from January, copied over to server, restarted unmenu and seems to be working now. thanks for clearing my frustrated vision and steering me to finding the solution.

still hoping for a response... am I in the wrong area?? Try checking your unmenu_local.conf file for the following line: MyHost = <some value> Set it to the proper value. If the server IP address if 192.168.1.10 use: MyHost = 192.168.1.10 You may need to restart unmenu for this to work. interesting... I do not have that file. only conf files i have are myMain.conf, syslog_match.conf and unmenu.conf

still hoping for a response... am I in the wrong area?? Is unRAID set to local master in SMB settings? yes

still hoping for a response... am I in the wrong area??

help im lost. everything was fine then i couldn't access unmenu via tower:8080. no changes had been made for some time and been running v5.0.6 of unraid. if i typed in ip xxx.xxx.x.xxx:8080 unmenu main would display. if i let it auto refresh i get a timeout error, if i click any of the menu tabs i get a time out error. using ip:8080/"desired page here" it works but none of the icons pictures display. i pulled flash drive from server and ran chkdisk on my windows pc and it found and corrected errors. reinstalled in server and got same results. frustarted i decided to start over and install my new flash with unraid v6.14b and did a clean install of unmenu. same results. i also have the same results from a laptop and my android phone. I am guessing at this point I have developed some kind of network issue but i do not know. I hope somebody can help me diagnose my situation and help me get my unmenu back please.

Yes I would. +1

After you upgrade, this may interest you also http://lime-technology.com/forum/index.php?topic=31474.0

correct - GUILTY even more guilty in the fact that I have read garycase's backups thread and thought to my self "yeah I should do something like that" even so far as putting a list together of parts for a backup server build but ignoring the easiest first step in the process of checksums. no dirty shutdown, maybe??. 19 days ago we had a power outage but I assume the apcups plugin installed through unmenu did what it was supposed to do. When the power was restored 12 hours later the server rebooted just fine and no parity check was automatically started which is what I thought unraid would do by default if dirty shutdown was the case. ?? guess i should look at the log file to see if that was indeed the case. started "correct parity" check before leaving for work today, should be finished by the time i get home and will start another to check again if there are no problems reported. I'm asking now! Thanks for the help and guidance. Lesson learned

viewing the results after work today from last nights monthly check i find there were errors. Now this is the first time i have experience this so I look to the experts for guidance and or re-assurance. the main page displays this message: Last checked on Tue Apr 1 13:07:15 2014 CDT (today), finding 2 errors. > Duration: 13 hours, 7 minutes, 13 seconds. Average speed: 84.7 MB/sec the unmenu main status page displays this message: STARTED, 14 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 2 times to address sync errors. there are no disk errors in the error column on the main screen. i ran a smart report on the parity disk and it reports nothing wrong copied from syslog at start of parity check to end of log: Apr 1 00:00:01 Tower kernel: mdcmd (328): check NOCORRECT (unRAID engine) Apr 1 00:00:01 Tower kernel: (Routine) Apr 1 00:00:01 Tower kernel: md: recovery thread woken up ... (unRAID engine) Apr 1 00:00:01 Tower kernel: md: recovery thread checking parity... (unRAID engine) Apr 1 00:00:01 Tower kernel: md: using 2560k window, over a total of 3907018532 blocks. (unRAID engine) Apr 1 00:00:12 Tower kernel: md: parity incorrect, sector=5464 (Errors) Apr 1 00:00:12 Tower kernel: md: parity incorrect, sector=5656 (Errors) Apr 1 04:40:01 Tower logger: mover started Apr 1 04:40:01 Tower logger: skipping applications/ Apr 1 04:40:01 Tower logger: mover finished Apr 1 06:58:49 Tower kernel: mdcmd (329): spindown 2 (Routine) Apr 1 06:58:50 Tower kernel: mdcmd (330): spindown 3 (Routine) Apr 1 06:58:51 Tower kernel: mdcmd (331): spindown 4 (Routine) Apr 1 06:58:51 Tower kernel: mdcmd (332): spindown 5 (Routine) Apr 1 06:58:52 Tower kernel: mdcmd (333): spindown 7 (Routine) Apr 1 06:58:53 Tower kernel: mdcmd (334): spindown 11 (Routine) Apr 1 09:08:06 Tower kernel: mdcmd (335): spindown 13 (Routine) Apr 1 11:19:48 Tower kernel: mdcmd (336): spindown 1 (Routine) Apr 1 11:19:49 Tower kernel: mdcmd (337): spindown 6 (Routine) Apr 1 11:19:49 Tower kernel: mdcmd (338): spindown 8 (Routine) Apr 1 11:19:49 Tower kernel: mdcmd (339): spindown 10 (Routine) Apr 1 11:19:50 Tower kernel: mdcmd (340): spindown 12 (Routine) Apr 1 13:07:15 Tower kernel: md: sync done. time=47233sec (unRAID engine) Apr 1 13:07:15 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine) Apr 1 13:37:22 Tower kernel: mdcmd (341): spindown 0 (Routine) Apr 1 16:07:24 Tower kernel: mdcmd (342): spindown 9 (Routine) should i run a "correct parity" check and then a "nocorrect" to verify? do i just let it be? Is this something to worry about? Thank You

I had a similar issue with my Smart D1. I had to delete the shortcut on my favorites screen and then cold boot the dune for it to see my shares again. Been fine and working normal since.

SUPERMICRO MBD-X8SIL-F-O Linux 3.9.11p-unRAID. root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:69:44:42 inet addr:192.168.0.222 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:113028557 errors:0 dropped:2627 overruns:0 frame:0 TX packets:82137354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:114413550893 (106.5 GiB) TX bytes:105962295138 (98.6 GiB) Interrupt:16 Memory:fb5e0000-fb600000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:6733 errors:0 dropped:0 overruns:0 frame:0 TX packets:6733 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:972850 (950.0 KiB) TX bytes:972850 (950.0 KiB)

I have similar performance hit results with my seagate drives as well. my WD, hitatchi and samsung drives do not.

just upgraded to new web gui. is there supposed to be a "plugins tab"? running v2014.01.24a on v5.0.5

yep working now. placed order, thanks

keep getting 504 gateway time-out error when I press the buy button.

Thanks!

New flash drive. Tom will issue a license based on the GUID you enter into the web form. He must be able to find you as a current customer based on the email you submit. so... am I walking through this correctly? 1. copy current flash to new flash drive of choice, 2. boot server with this new flash to retrieve GUID from main page, 3. copy GUID to order form and send off to Tom, 4. boot server with original flash drive and all is well. 5. wait for new license key to arrive...

+1

repeats for each disk, and does complete for all drives. Is this expected behavior? ran as diskspeed.sh -i 3 Performance testing parity drive at 3811 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3809 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3807 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3805 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3803 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3801 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3799 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3797 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3795 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3793 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3791 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3789 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3787 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3785 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3783 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3781 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3779 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3777 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3775 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3773 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3771 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3769 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3767 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3765 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3763 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3761 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3759 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3757 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3755 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3753 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3751 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3749 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3747 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3745 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3743 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3741 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3739 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3737 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3735 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3733 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3731 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3729 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3727 GB (hit end of disk) (100%), pass 1 of Performance testing parity drive at 3725 GB (hit end of disk) (100%), pass 1 of Parity: 140 MB/sec avg

Ran it tonight on my server. It worked perfectly now and tested all disks. THANKS!

Telnet into your server and log in. Then enter the following command: cp /proc/mdcmd /boot/mdcmd.txt Then you'll be able to use Windows Explorer to navigate to your UNRAID server and mdcmd.txt will be in the "flash" share. Got it. I was close, but still learning slowly. Thanks! here ya go. [dont know if this is useful or not but the graph does list the disks not being tested.] mdcmd.txt

yes but i will need some instruction. I tried to figure out how to do it but have failed. I am a beginner level.

Thanks for this, curious how fast or slow my current mixture of disks actually are. please see my results, any help why it doesnt test past drive 9? DS_Results.txt

The drives arrived today [late but that's another story] I'm going with Joe's advice. He suggests it, he authored it, minimize the risk. Thanks for the input!

pretty stock here also, unMenu is all.