Jump to content

mcai3db3

Members
  • Content Count

    46
  • Joined

  • Last visited

Everything posted by mcai3db3

  1. Consider me a +1 on this one. I can't use the TVHProxy plugin because of the requirement to set IP addresses for each Docker. This would be great.
  2. So basically, does anyone have a suggestion on how to force phaze plugins to wait until the SSD is ready before trying to start up? Is there a way of putting a forced delay in? (I'm not even sure if this'll work, given it could delay UD too). Thanks! Anyone have any suggestions?
  3. This is a crosspost, as I'm not sure if it's an Unassigned Devices issue, or a plugin issue (of which all of my plugins are Phaze plugins), so here goes: http://lime-technology.com/forum/index.php?topic=45807.msg465130#msg465130 So basically, does anyone have a suggestion on how to force phaze plugins to wait until the SSD is ready before trying to start up? Is there a way of putting a forced delay in? (I'm not even sure if this'll work, given it could delay UD too). Thanks!
  4. By plugin's, do you mean Plugins or Docker Applications? If docker Applications, then you have to stop and start the entire docker service in order for any apps to see any mountings that UD performs (6.1.x) If you're under 6.2, then you can modify your volume mountings to use the new "slave" option which should fix this up for you. Just plugins I'm afraid. I've never ventured into the world of Docker.
  5. Howdy all... I'm hoping this is a common issue, or me being stupid somehow, but here goes: My setup is basically that I have 1 "unassigned device" SSD, and on that disk, I install my various plugins (sabnzbd et al.) But I'm having this issue where every single time I restart the server/array, the plugins all run their annoying "wizards" as they are failing to read the config folder held on my SSD. I can see in my logs that the SSD (sdd1) is not mounting until after the plugins have tried to install. So basically, how do I force UD to mount this disk before the plugins try and run? Thanks! And thanks for keeping this plugin alive dlandon! p.s. both UnRAID and UD are completely up-to-date.
  6. Yes HDD, but with an extra SSD for my apps.
  7. 10 drives 4tb parity 2 * 4tb data 4 * 2tb data 1 * 1tb data 1 * 500gb cache 1 * 120gb ssd - outside of array as application drive
  8. I've already run it on disk1 and the cache disk. I had errors on the cache disk, which have since been fixed, but the problem persists. I can try doing it on the other disks, but I'm pretty sure the issue exists between these two drives. Another attempt I made to fix this was to define minimum free space on each share, and to delete all drive names from the "included/not included" parts of the settings. This still didn't work. Every time the mover runs, this error happens, and my system locks up and requires a hard restart. This is not ideal. I want to use the cache disk for the purpose of installing plugins, but would be happy to disable it from "cache" usage. Unfortunately my attempts to do this are failing, as I've told each Share not to use the cache.. and yet it continues to do so. EDIT: Looks like it actually deleted the files it was trying to move. Great!
  9. I believe I'm in the same boat on this one. Did you ever get a fix? (http://pastebin.com/4diqSEDA)
  10. The prices will find their way back down again, it just is gonna take a while. Right now they're loving the profits, but soon enough one manufacturer will undercut another and prices will have to drop to stay competitive. Though, it would not shock me if we're looking at a year or more before that happens.
  11. Mine have arrived! Ha, took some time but they're finally here. Now I've no need to install them right now... has anyone else taken the plunge?
  12. You have any issues w/ movie skipping? I noticed this when I just wake up the server and start playing the movie from the boxee. I then will have to stop the movie and start over after that its smooth as butter. The loading circle thing appears when I'm waking up server HDDs, which is expected, but I haven't had any skipping issues. Connected to the server using smb links to UnRAID shares, on unRAID 4.7 and the most up-to-date version of Boxee (well, technically not, since they updated yesterday and I'm yet to turn it on since).
  13. I have a Boxee Box playing files from my unRAID server and it's been nothing but a treat. I barely use it's online capabilities to stream things, so perhaps that's an area that isn't getting such rave reviews? As a local media streaming device w/scraping capabilities, it's been perfect.
  14. I've not got that syslog anymore, but I can tell you exactly what I can do to cause such an error...! Earlier today I will have got that message, it was rebuilding a drive I removed, onto a new drive. So the array was 'Starting' at this point. Then I went into the 'Shares' tab of the unraid management page. I made a change to one of the shares, adding a disk to a share or something like that. At this point when that page refreshes, all but one of my Shares shows on the Shares setup page, the rest disappear. Once the array is started up, only the one remaining Share is findable on the network. So, at that point I decide I want to reboot the thing, so I can have my Shares back!... OK, so I disconnect everything from the server, and then I try and stop the array. Not so fast. UnRAID says no. It basically just gets stuck on Unmounting for multiple drives, until I end up powering down with UnMenu. When I restart, all is fine. I get that IRQ message during that whole affair. Right now I'm in no mood to be fiddling around with the box, it's been working for 4/5 days and I just don't want to mess with it unless it proves itself to be an issue. Oh, and the only reason I was suspicious over my cache drive was due to frequent inability to unmount said drive. But that could've been caused by anything. It was also a convenient way to remove my 500GB Cache and replace it with a 2TB data drive that I just bought (and downgrade a 1TB data drive to cache duty).
  15. After removing the dirty cache drive, it hasn't crashed yet. Been about 4 days. Still evaluating. Gonna add a cache drive (a different drive) soon, see if issues arise then. Not touched voltages yet. Scared.
  16. haha I think you're grossly overestimating my knowledge on this kinda thing! Right now the voltages will be whatever the default was. I'll give them a look tonight and let you know what they say.
  17. My ram is Kingston HyperX 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model KHX1600C9AD3K2/4G I'll take a look at the BIOS tonight and see what my settings are, I believe I already updated the BIOS when I first received the components. I'm not sure how easy it is to change all of this stuff though, will have to take a look. I'm apprehensive to change anything until it crashes again though, thanks for your help.
  18. Ok thanks. Well for now I've removed my cache driving that was giving me grief. I've got sab/sick installed on a regular disk, which is far from ideal, but will do for a week or so. I'm basically just going to wait it out and see if it crashes again. At some point I'll open her up and dust off the various connection cables & make sure they're all kosher. Also, I have a spare 2TB drive, and one of my array disks is 1TB 7200, so I may just swap the array disk out for my 2TB and then make that disk my new cache. If my theory of crappy cache drive is actually anywhere near correct. Last note: I think my syslog that I posted wasn't helpful because it just showed the problems caused by the random reboot, rather than the cause of the reboot. This was why the user folder was not empty, because UnRAID had issues after the reboot, it did not create all the shares, only created one of them (and then it couldn't get rid of that 1 share when I tried to stop the array - thus it wasn't empty).
  19. I've attached a screenshot of my unMenu main screen - I was confused by the sda and sda1 that exists there for the cache drive. Is this normal?
  20. My entire Go script as requested: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu #sleep for 30 seconds sleep 30 #Start SABnzbd installpkg /mnt/cache/.custom/SABnzbdDependencies-2.1-i486-unRAID.tgz python /mnt/cache/.custom/sabnzbd/SABnzbd.py -f /mnt/cache/.custom/sabnzbd.ini -d -s 192.168.1.2:1066 python /mnt/cache/.custom/sickbeard/SickBeard.py --daemon cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c
  21. Ok, first of all, here is a recent error I just got: Feb 10 17:24:19 SERVER kernel: irq 16: nobody cared (try booting with the "irqpoll" option) (Errors) Feb 10 17:24:19 SERVER kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 10 17:24:19 SERVER kernel: Call Trace: (Errors) Feb 10 17:24:19 SERVER kernel: [<c10451cf>] __report_bad_irq+0x2e/0x6f (Errors) Feb 10 17:24:19 SERVER kernel: [<c1045305>] note_interrupt+0xf5/0x13c (Errors) Feb 10 17:24:19 SERVER kernel: [<c1045a14>] handle_fasteoi_irq+0x5f/0x9d (Errors) Feb 10 17:24:19 SERVER kernel: [<c1004a82>] handle_irq+0x1a/0x24 (Errors) Feb 10 17:24:19 SERVER kernel: [<c1004285>] do_IRQ+0x40/0x96 (Errors) Feb 10 17:24:19 SERVER kernel: [<c1002f29>] common_interrupt+0x29/0x30 (Errors) Feb 10 17:24:19 SERVER kernel: [<c10085f9>] ? mwait_idle+0x4c/0x52 (Errors) Feb 10 17:24:19 SERVER kernel: [<c1001a14>] cpu_idle+0x3a/0x4e (Errors) Feb 10 17:24:19 SERVER kernel: [<c129c662>] start_secondary+0x195/0x19a (Errors) Feb 10 17:24:19 SERVER kernel: handlers: Feb 10 17:24:19 SERVER kernel: [<c11ead61>] (usb_hcd_irq+0x0/0x5b) (Drive related) Feb 10 17:24:19 SERVER kernel: [<c11ead61>] (usb_hcd_irq+0x0/0x5b) (Drive related) Feb 10 17:24:19 SERVER kernel: [<f8247022>] (ahci_interrupt+0x0/0x3df [ahci]) (Drive related) Feb 10 17:24:19 SERVER kernel: Disabling IRQ #16
  22. First thing I noticed was that instead of 'installpkg' you have 'installpgk'...
  23. Thanks for your help Joe. I'll take a look at this further this evening, but my first comments are: RE: Time sync - I have no clue what any of that means RE: Add-ons - off the top of my head I have sabnzbd, sickbeard and the add-on for printer drivers. I'm going to take my cache offline for now and thus remove sabnzbd and sickbeard. I will uninstall any other add-ons I have and see how it runs for a few days. The go script DOES have a 30 seconds wait before installing sab/sick. When I get home I'll post my exact goscript. It's worth noting - that syslog was taken after my system had done one of it's random reboots, at this point the system tries to parity check (I stopped it). At that point when you connect to the server most of the shares do not appear, so I tried to stop my array and start it again. It would not stop, then I powered down. This makes me think the syslog in question may have errors that would not normally appear in day-to-day use, and maybe a product of the shares not being available.
  24. Towards the end it's me telling the system to stop the array and the cache drive not wanting to unmount, can't remember the exact steps but I just tried to shut down all sab/sickbeard etc and tried to close everything I could think of... it didn't help, I ended up just using powerdown in UnMENU. Also the cache drive temperature does not display in unRAID, so thats one of the errors (it just shows 0C - but it works fine in unMENU). sda is my cache btw.