Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About _vern_

  • Rank
    Advanced Member


  • Gender
  • Location
    West Virginia
  • Personal Text
    The lack of money is the root of all evil!
  1. Disregard. I got it figured out after all. I have a user script that I have been running for months and all of a sudden it decided to run amok. Once I shut that down, Unraid is not so upset now.
  2. I have something in mind and want to see if this is a valid methodology. Can I create a new config and see if the array will start? And then add in disks one at a time to see if it is a disk that is perhaps hanging? I haven't done this before, so I'm trying to see if there is some means to at least get it to a point that it can start the array and troubleshoot further. Of course, this is assuming that a disk is a culprit. If not, may not help me at all. Thoughts? Thanx!
  3. Hello all, I'm having a bit of an issue...came home and Unraid was upset! Nothing was working right. Long story short...have tried rebooting a few times and it keeps hanging while trying to mount disks. I don't see any issues in the logs. Requesting some assistance to troubleshoot. Diagnostics attached... media-server-diagnostics-20190906-2024.zip
  4. I have been using unraid for over 10 years and have had a pro license for the since 2012. I have three kids in college (they are finishing up now) and it's been great to serve up their shows because they can never watch them when they are on due to studies and so forth. I have had several hard drives die on me and it's always a breeze to change them out or even upgrade when needed. I can't say enough good things about the product! Please keep up the fantastic work!
  5. Hello all, I have three dirs setup in /cache (appdata, domains, systems) and it's been that way for years. They are, and have been for as long as I can remember, configured to only use cache. However, looking at the shares in the Shares tab in unraid and then click on the folder to view the contents the location shows as "Cache", but the path at the top of the page is showing /mnt/user/appdata, which of course is not right. Working from two session in putty, It appears these paths are pointing to the same place. In other words, looking at /mnt/cache/appdata and /mnt/user/appdata and then make a change in one it shows in the other. I'm not exactly sure what to do to get this corrected and of course I'm concerned that I'm going to destroy my data...like Plex...and I really don't want to have to cry today! I'm attaching the diagnostics file here if that helps...but I'm looking for some advice on how to correct this. Any help would be much appreciated! Unraid Version: 6.7.2 media-server-diagnostics-20190701-2356.zip
  6. Thank you...I have figured out what has changed. The virsh domblklist --details command output has changed...the line of data now begins with a space so the pattern "^file" no longer matches it. Mystery solved. Thank you for the reply!
  7. Hello all, I'm really just posting this because I want to see if anyone else has experienced this behavior with grep in unraid. I don't think this is an issue with unraid per se. I have a bash shell script that I have been running for several years without issue. The day after I upgraded to 6.7 the script broke and I had no idea why. After a couple of hours of trouble shooting I discovered the line below, which the output is supposed to be saved to a variable, wasn't grabbing anything. Note: this is not the full line of code...just the part the demonstrates the behavior. virsh domblklist "domain" --details | grep ^file If you run this line at the command line in unraid, assuming you are running virtual machines, and replace "domain" with the name of a VM, it should return a line of information on the VM...or so it used to. When I run this now it returns nothing, which caused the variables to never get populated which caused the script to fail. If I drop the caret (regex), it returns what is expected. It appears the grep version changed in 6.7, but I can't find any information concerning any changes to grep that would have caused this behavior. So, I'm curious if anyone else has run across this behavior and maybe more importantly, educate me. It's just one of those little mysteries that causes me to slowly lose my sanity! Thanx!
  8. Just wanted to pass along that your change corrected the issue. Thank you very much!
  9. Thank you for the reply...I just want to double check something...I see line 368 that starts out with "<img class="moviePoster"...", is this the line that your line should be replacing? If so, that would appear to be line 368 unless you are intending something different like to insert your line as line 369 pushing everything beyond that down a line. I wasn't sure...I was going to play with this later this evening and figure it out. Thanx for the information!
  10. Thank you very much for that information...very useful! Thanx!
  11. I get different results with different viewers...in Windows 10 "Mail App" I see what you see. In google mail in the browser, it renders the posters all the same size...the smaller size. In Edge, they render correctly as well. I don't have Outlook running. Apparently the HTML being used for displaying these email don't comply with all the various means of displaying the email...
  12. Thank you for the reply...but, this seems odd to me. Cron jobs are typically logged to syslog as a standard and of course can be configured to log else where if desired. In the case of unRaid, if it's up to the user to setup logging to show that the cron job executed (not the results or output of what was run, just the fact that that cron job ran) would also mean that the user wouldn't be able the use the interface of unRaid to see that...unless the user has the ability to send custom logging to the unRaid System Log (this can probably be done, but haven't really dug into it). This seems like an oversight to me...IMHO cron job execution should be part of the system log as a default configuration. Just my 2 cents...thanx!
  13. Are cron jobs logged? I'm looking in System Log found under Tools, but I'm not finding any entries where cron jobs are executed. Are they being logged else where by chance? I have a custom job that is running and I was sort of expecting when it ran that I would find an entry in the system log, but that doesn't appear to be happening and I know the cron job is working right. Perhaps this has been addressed in another thread, but I wasn't able to find it if so. Thanx for any information that anyone can provide...
  14. Just wanted to pass along that I sort of figured out what the issue is. Apparently there are some directories where the permissions are not being set that satisfies the Ruby bundle installer. By running... chmod +t -R ~/.bundle/cache ...seems to do the trick. It obviously just sets the sticky bit on everything below the /cache directory there by making everything not world writable, which is what it was complaining about. After that, it appears to run normally.
  15. I'm running into an error while trying install this and was wondering if you could help me out. The error comes after launching initial_setup.sh. I get the prompt asking if I'm sure I want to run this and then after a few second...this is what I get... Thank you for any assistance that you can provide... thanx,