-
Posts
1132 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by optiman
-
-
For the above issue, I moved that to the correct board area, the unRAID OS 5.0-rc Board area.
It is now resolved. I had to remove the PHP package re unmenu. The main web gui is now there and working fine.
The only surprise was that the array started on it's own. The Release Notes say that it will come up in a STOP state and I would have to Start it, after confirming drives looked ok and after adding the cache drive back. That didn't happen, again it just started. Everything looks ok however.
I'm now trying to figure out the email notification stuff. Status emails and ReSync emails now all look the same, and they are not very informative. Still doesn't tell you how much time is remaining on a resync nor if there are any errors. I will also have to confirm that the other packages are ok, APC UPS, etc.
-
Thanks! I will try that. Unmenu will not load now, so I'll have to power off and load the usb drive in my pc. I assume the manual process to remove php package would be to just delete the files in the Packages folder (I see 4 or 5) and to delete the one file in the UnMenu folder, php-unmenu-package.conf
Would that be correct?
-
Need a little help. I'm going from 4.7 to 5 rc5. I'm following the instructions and I'm at the point where I reboot the server. I do not have a monitor on my server so I rely on Putty or IE. I prefer just using the web gui. However, I cannot connect via my web browser. I see mostly a blank page, but there is a Lime Tech banner at the top. There is one button / link below the banner, but it's not in English so I don't know what it says. The link doesn't work. There is another button at the top right that says log, it gave me the following,
Jun 24 10:14:27 Tower emhttp_event: disks_mounted
Jun 24 10:14:27 Tower emhttp: shcmd (54): :>/etc/samba/smb-shares.conf
Jun 24 10:14:27 Tower emhttp: Restart SMB...
Jun 24 10:14:27 Tower emhttp: shcmd (55): killall -HUP smbd
Jun 24 10:14:27 Tower emhttp: shcmd (56): ps axc | grep -q rpc.mountd
Jun 24 10:14:27 Tower emhttp: _shcmd: shcmd (56): exit status: 1
Jun 24 10:14:27 Tower emhttp: shcmd (57): /usr/local/sbin/emhttp_event svcs_restarted
Jun 24 10:14:27 Tower emhttp_event: svcs_restarted
Jun 24 10:22:31 Tower in.telnetd[3928]: connect from 10.11.79.167 (10.11.79.167)
Jun 24 10:22:35 Tower login[3929]: ROOT LOGIN on '/dev/pts/0' from '10.11.79.167'
How can I access my server via my web browser so I can continue with the upgrade?
Is there a special port I need to use now when accessing via web gui?
Update: Putty works fine and so does UnMenu on port 8080. The main web gui is not loading. Another scary part is that UnMenu shows my Array started. This was the part of the instructions that said it should come up at a STOP state and I will need to confirm drives are ok, reconfigure cache drivce, then START. Not sure why the array started on it's own. That said, the drives all look fine. The cache drive is not configured so it looks like it saw everything was ok and just started.
I only run the UnMenu addon and the packages within there are very limited, APC, Notify, etc. I didn't change any of these prior to my upgrade.
I changed the root password via telnet.
syslog attached.
Thanks!
-
woops, thanks...done
-
browser cache not it...even tried from my mac. I only get the top portion of the page (banner)
-
I just tried to go from 4.7 to 5 rc5 and got no web gui either. Putty works and I'm able to use the web browser and get to the Unmenu screen, but the main web gui is gone. WTF?
-
Per the instructions, I've moved this question to the unRAID OS 5.0-rc Board area.
Need a little help. I'm going from 4.7 to 5 rc5. I'm following the instructions and I'm at the point where I reboot the server. I do not have a monitor on my server so I rely on Putty or IE. I prefer just using the web gui. However, I cannot connect via my web browser. I see mostly a blank page, but there is a Lime Tech banner at the top. There is one button / link below the banner, but it's not in English so I don't know what it says. The link doesn't work. There is another button at the top right that says log, it gave me the following,
Jun 24 10:14:27 Tower emhttp_event: disks_mounted
Jun 24 10:14:27 Tower emhttp: shcmd (54): :>/etc/samba/smb-shares.conf
Jun 24 10:14:27 Tower emhttp: Restart SMB...
Jun 24 10:14:27 Tower emhttp: shcmd (55): killall -HUP smbd
Jun 24 10:14:27 Tower emhttp: shcmd (56): ps axc | grep -q rpc.mountd
Jun 24 10:14:27 Tower emhttp: _shcmd: shcmd (56): exit status: 1
Jun 24 10:14:27 Tower emhttp: shcmd (57): /usr/local/sbin/emhttp_event svcs_restarted
Jun 24 10:14:27 Tower emhttp_event: svcs_restarted
Jun 24 10:22:31 Tower in.telnetd[3928]: connect from 10.11.79.167 (10.11.79.167)
Jun 24 10:22:35 Tower login[3929]: ROOT LOGIN on '/dev/pts/0' from '10.11.79.167'
How can I access my server via my web browser so I can continue with the upgrade?
Is there a special port I need to use now when accessing via web gui?
Update: Putty works fine and so does UnMenu on port 8080. The main web gui is not loading. Another scary part is that UnMenu shows my Array started. This was the part of the instructions that said it should come up at a STOP state and I will need to confirm drives are ok, reconfigure cache drivce, then START. Not sure why the array started on it's own. That said, the drives all look fine. The cache drive is not configured so it looks like it saw everything was ok and just started.
I only run the UnMenu addon and the packages within there are very limited, APC, Notify, etc. I didn't change any of these prior to my upgrade.
Perhaps the first thing I need to do is set the Root password via Putty -- Yes?
syslog attached.
Thanks!
-
Hi Joe! It's been a while.
I just read the release notes, and wow there are a few more steps to go from 4.7 to 5. Are these additional steps required for each upgrade going forward, or was this only to move from 4.7 to 5? I hope going forward we just have to replace the two files and not loose any users or configuration data.
Thanks!
-
Thanks! Looks easy.
After checking, the only thing I see to watch out for is if you have a LSI sata chipset. I have the Super C2SEE with a Adaptec SATA card, so I should be safe.
-
Ok, I'm ready to jump in version 5. I'm currently on 4.7. Is this upgrade work the same as all others, or are there specific speps to go from 4.7 to 5?
I have done this in the past and was planning to follow this for version 5;
-run Check Parity
-dl the new unraid install package and connect to my Flash drive (from my Win7 pc).
-copied the two main files, bzimage and bzroot to the root of my flash drive
-Restart the Unraid server
Will that getter done?
-
I just downloaded Plex for Unraid 0.9.6.4. I also downloaded the Light version from page 1 of this thread. Please let me know if that is not the latest link /file.
My current setup is Unraid 4.7, so I'll be upgrading to 5 first. My movie files are on stored on my Unraid via Share. I use my Popcorn Hour A110 and A300 to connect to the Share and play the movies.
I would like to Run Plex on the Unraid and connect my PCH devices (as well as iPhone and others). Does anyone have this same setup working?
UPDATE: I'm on 5 rc5 and ready to install Plex. Can anyone confirm I have the correct files and if this will work with my popcorn hour stuff?
Thanks!
-
So for the housekeeping junk, are you saying to just ignor all that mess?
thanks
-
Yes, I clicked on the button the main screen and the parity check was ok, zero errors. I always do that after the rebuild is complete for replacement drives. I do not use the server during the rebuild. By that, I don't connect with my pc or stream any media during that time. I guess my mac could auto connect and that would create a connection, but no real use. In any case, it would be nice to get the update and close this gap.
It's still running at 58% and still says 7 errors. I hope you are right and this clears it up. After this is done, I will run it yet again and it should come up with zero errors. Fingers crossed!
update: ok the parity check completed and ended with the same 7 errors, but as pointed out, they were corrected this time. I rebooted the server and then kicked off another parity check, resulting in zero errors, So, while I don't understand why this happened or what was corrected, things seem to be back to normal.
So for the housekeeping junk, are you saying to just ignor all that mess?
Thanks,
Steve
-
I said "Run a 3rd parity check" as in run once more.
not
run a "3rd party" parity checker.
On your version of unRAID, the button on the unRAID screen checks and corrects parity. To perform a check only, you must either use the button on the unMENU web-page, or type the command on the command line.
/root/mdcmd check NOCORRECT
Ok, thanks Joe! So would you recommend that I change the unmenu monthly parity checker to CORRECT when it runs?
-
Did you do any array maintenance since the last parity check?
- rebuild failed disk
- upsize a disk
- add a new disk
- add any addons
- ...
The fact that the parity blocks are pretty small seems to indicate the parity issues are in the "housekeeping" area - a good thing because file data is not stored there.
Yes, here is the recent history.....
-last month the auto parity check ran with no errors, as it has for a long time.
-After that check, I replaced a old drive with a larger one, which I've done many times in the past. The rebuild process worked with no errors. I then ran a CHECK via the button on the main screen. From Joe's message, that does a CORRECT check. It resulted in NO errors.
-I then used my server all month with no issues, until the scheduled monthly unmenu service ran last night, resulting in these 7 errors.
No addons were added, no other new drives, etc. A simple yank out the old, put in the new, clear it, and then start the rebuild.
What is the housekeeping area and should I do anything to clean that up?
Thanks
-
Hi Joe!
You wrote:
Last time you invoked it in NOCORRECT mode, this time you invoked it in CORRECT mode.
The same addresses were still incorrect, but this time they were corrected.
I use the unmenu addon that runs the parity check monthly automaticaly. I guess you are saying that package is configured to NOCORRECT. Should it be?
When I restarted my server, I manually pushed the CHECK button on the main screen, and I guess based on what you are saying, that does a CORRECT check. Again, should I change this setting?
If you run a third parity check you'll probably find all is OK.
Other than the packages in unmenu, what 3rd party checkers do you use?
There is no easy way to determine which files correspond to the blocks with the errors. It might be part of the empty space on the drive, or part of the file-system structures, or parts of one or more files.
Ok, that isn't very good. Not much use in reporting a error if you can't figure out what is causing it and what data is impacted. I wish this service could provide more information about the errors.
Thanks again Joe!
-
No, the past several parity checks have all been zero errors and no hard crashes.Did you have a hard shutdown of the server since the last parity check?
Ok, so how can I find out what the errors are, meaning what files on what drives are not happy?
I will run another check, as you have suggested, but how will I confirm the errors are the same, or new ones?
And last, how can I correct the errors so parity is happy again?
edit
Ok, so I powered down my server completely and restarted it. I then kicked off another parity check and here is what is in the syslog, oh and the status screen shows it just started a parity check, but already has the 7 errors again,
Dec 1 12:13:09 Tower ntpd[1484]: time reset -0.216085 s
Dec 1 12:14:20 Tower kernel: mdcmd (24): check CORRECT (unRAID engine)
Dec 1 12:14:20 Tower kernel: md: recovery thread woken up ... (unRAID engine)
Dec 1 12:14:20 Tower kernel: md: recovery thread checking parity... (unRAID engine)
Dec 1 12:14:20 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 7784 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 7792 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 7808 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 7816 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 8040 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 12368 (Errors)
Dec 1 12:14:20 Tower kernel: md: parity incorrect: 12376 (Errors)
Dec 1 12:16:45 Tower unmenu[1569]: awk: ./unmenu.awk:630: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer) (Minor Issues)
help!
-
No, the past several parity checks have all been zero errors and no hard crashes.Did you have a hard shutdown of the server since the last parity check?
-
I'm running 4.7 Final for a long time now, and each month my parity check runs with Zero errors. For some reason this month (today), I got 7 errors so far, as it's still running for another 120 minutes. I'll check it when I get home from work to see if I have more than 7.
My question is "Should I be worried about this?" I guess that is the reason the check runs in the first place, but should I look at any logs or confirm that the CORRECTED errors were actually errors and the corrections were good? I read here somewhere a while back that not all corrections are what you may want, as parity may be wrong.
The only thing in the syslog is this,
Dec 1 00:00:01 Tower kernel: mdcmd (507): check NOCORRECT (unRAID engine)
Dec 1 00:00:01 Tower kernel: (Routine)
Dec 1 00:00:01 Tower kernel: md: recovery thread woken up ... (unRAID engine)
Dec 1 00:00:01 Tower kernel: md: recovery thread checking parity... (unRAID engine)
Dec 1 00:00:02 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 7784 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 7792 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 7808 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 7816 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 8040 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 12368 (Errors)
Dec 1 00:00:30 Tower kernel: md: parity incorrect: 12376 (Errors)
Given this is the first time I've had this issue, in 3 years of running my unraid, I thought I better ask.
Thanks!
Steve
-
Hi,
I'm running 4.7 and I noticed that I'm now getting the following errors about once a day. There were a few days that didn't get the error at all, but it occurs most days and never at the same time. Time seems to be random. I pasted the few lines after, but I'm focusing on the errors lines.
Jun 18 14:04:19 Tower kernel: mdcmd (520): spinup 8 (Routine)
Jun 18 14:04:27 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)
Jun 18 14:04:27 Tower kernel: ata1.00: failed command: IDLE (Minor Issues)
Jun 18 14:04:27 Tower kernel: ata1.00: cmd e3/00:00:00:00:00/00:00:00:00:00/40 tag 0 (Drive related)
Jun 18 14:04:27 Tower kernel:res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)
Jun 18 14:04:27 Tower kernel: ata1.00: status: { DRDY } (Drive related)
Jun 18 14:04:27 Tower kernel: ata1: hard resetting link (Minor Issues)
Jun 18 14:04:33 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) (Drive related
)Jun 18 14:04:34 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 14:04:34 Tower kernel: ata1.00: configured for UDMA/133 (Drive related)
Jun 18 14:04:34 Tower kernel: ata1: EH complete (Drive related)
Jun 18 14:47:11 Tower sSMTP[19545]: Creating SSL connection to host
SMART log looks good and I have no performance issues, that I'm aware of anyways.
Should I be concerned with this?
-
Thanks for the help. Actually, I found the issue. One of my Shares some how got set to SMB export --> read only... I don't know how that was changed but when I put back to RW, all good again.
Thanks!
-
I have not had any issues with my Windows 7 pc and my unraid setup, until recently. The only change I can think of is the 4.7 update I did. Has anyone else had this issue?
I've reshared out my shares..duh, ensured I was connected with the correct login info, etc...
-rwx------ is what is next to the in Unmenu File Browser. what is the easest way to set all my permissions to Full Control for Root?
Thanks,
Steve
-
-
Sorry if this is a 'duh' kind of question, but I am going to upgrade to 4.5.4 to get support for a card I just purchased. I have been running 4.4.2 for a couple years now, and would have happily stayed on that platform, running bubbaq for the rest of the life of my hardware.
So, I know that the simple upgrade steps are (obviously) simple. But, what does bubbaraid add to the mix? Do I have to remove bubbaraid and then upgrade and add bubbaraid back? Or do I drop 4.5.4 on top of by bubbaraid/4.4.2 system?
Thanks,
Chris
Bubbaraid is compiled for specific vesrions of unraid and there is not a newer version that I'm aware of. Therefore, you say goodbye to Bubbaraid when do you upgrade. I was using it as well and then upgraded. It's simple, just run the "Disable" script on your flash drive to remove/disable it, then do the upgrade by swapping the two files. I then installed unmenu, which has all the features that Bubbaraid has and many more. I really enjoyed bubbaraid too, but say goodbye, don't need it anymore. Joe has done a tone with unmenu and you will really like it, and it's easy to install.
Plex Media Server plugin for unRAID (v0.3 - Aug 7 2011)
in User Customizations
Posted
ok, I think Plex is running now, as it says this at the bottom when viewing the icon in Settings,
Plex Media Server is running with version v0.9.6.4.154-c16a2c6
Is that the latest / best version?
Also, I have a stupid question. All of my movies are stored on a Share, which means the files are actually located on several disks. Within Plex config, how do I point the Plex server to the movie Share? I tried \\ip address\Share but that didn't work. The Plex screen is blank, showing no content at all.
I created library and temp folds on disk 5 and pointed Plex to those. I just selected a disk for now but I would prefer to move this to the Cache drive so my array can go to sleep.
For my Popcorn hour, I have the new A300. I'll check and see if there is a special app for Plex. I will be happy to test this if I can get my Plex server running correctly.
Update: I figured out how to point Plex to my share /mnt/user/share_name