Influencer

Members
  • Posts

    2067
  • Joined

  • Last visited

Everything posted by Influencer

  1. No problem, the unraid community is one of the best around. Many very knowledgeable people here that do not mind sharing their knowledge, even when it means spoon feeding noobs, . We all were noobs once (I know my way around pretty good, but there are people on here that blow me away)
  2. The main reason it is advised to use a cache drive vs using an array drive for plug-ins, aside from the fact parity would always be spinning with the data drive, is the plug-in can actually cause a race condition with the array. Say, for example, the plex plug-in waits for the array to start before it starts plex up. To do this we use an event issued by unraid. Sometimes this event is triggered before all of the array drives are active. When the plug-in specifies the data directory, for example /mnt/disk1/apps/plex/, if the array has not been fully started yet the directory will be created in ram. The issue is once the directory has been created in ram unraid cannot mount "disk1", as the "directory is not empty"(the error linux will give). This will cause unraid to wait for the array to start, which it never will because it cannot mount disk1. This does not affect every user. Different systems start up with different speeds. I for one have NEVER been able to reproduce this on my production server, but it happens every time on a server I built for a friend with the same components. You can give it a try, it won't blow your server up. But if you reboot and the array never comes online, you know the most likely reason, . If that happens just shutdown(I advise installing the powerdown script, search the forums), put the flash drive in another PC and move the plug-ins to another directory or change the extension so they don't start on boot. Hope this helps,
  3. The logs should roll when they get a certain size. When this happens they should be named: sickbeard.log sickbeard.log.1 sickbeard.log.2 etc... EDIT: Scratch that, just checked, it does seem like the logs get deleted every day. Wish I would have caught this thread quicker and could have got a hold of those logs!
  4. What all programs access your server? ITunes, xbmc, etc?
  5. If Sickbeard is suspect please post sickbeards log. Id like to see if something happened with it. This could be a rather disastrous bug.
  6. Hardly anyone's fault, a little humor is always welcomed. Anywho, my train of thought is this: those that want a 64 bit kernel for more memory are interested in New functionality. V5 delivers on this with the plugin system + other additions. Users that don't want/need more than 4 GB are only interested in a solid build that works on older hardware. V5 delivers here as well, the exception being the slow speed issues when using pae. They also want to be able to use bigger harddrives, not currently possible on V4.7. I would say compile the 32 bit kernel occasionally to give support for larger drives, but no porting of new features. Question is, how feasible is this? Using a new kernel can break something else, as we have seen with V5 development. Do you update the kernel until something breaks? One group will be unhappy no matter what the decision is. Going forward it would make sense that even users who are using spare parts will be using 64 bit capable parts as they are by large the norm now. In my mind, if I'm willing to drop $150+ on the newest, largest capacity drive on the market, the extra $150 for a 64 bit system isn't too bad. My entire server, minus drives, is 64 bit capable and cost less than $200. Exclude case and (most likely) powersupply from what would be needed to make the jump to 64 bit, it would be more around $110. I could shave off more if I discounted for the 8 GB ram I put in it and only priced for <4. Keep in mind I'm figuring for the bare essential needed for a user only interested in file serving, no plugins, which would in large be (in my mind) the bulk of the 32 bit crowd. Your in the business of making the best, most capable file serving OS you can. Your move should reflect this. Keep in mind the other thread you commented on about unraid having a dated GUI, making it unappealing to potential buyers. How does the footnote "32 bit only, no more than 4 GB supported" read to you? To me it reads a little dated itself.
  7. It likely is as I described then. Setting it to boot from "Sandisk" the BIOS would detect a different model was inserted, even if the name was the same. It does make it difficult for automatic booting, but every BIOS has a boot menu option, for mine its ESC. Pressing that a startup I can pick any boot device I want. That makes booting from different media/disks easier
  8. Wow, that veered off course quickly. And mayhem2408, maybe a 64bit kernel would be good for you. No distractions at the office anymore! Sliced? ... and toasted. With Jelly!!! or Mango Chutney spicy please... Unfortunately, 32bit bread is also stale. So its a 32bit crouton now!
  9. Depending on how your BIOS is designed, some allow to choose "USB Storage" or "USB HDD" as the boot device, others state it more specifically, like "Sandisk Cruzer 8 GB". Chances are your BIOS is the latter and when the original flash drive is not installed it tries booting off of a harddrive(which obviously it can't). Selecting the new flash drive as the boot device should solve your issue.
  10. There is a powerdown script that works much better. Not at home so can't link to it but I believe its available as an unmenu conf and as a plugin for v5. Search google for unraid powerdown script
  11. I'm with the function over form crowd. While I like eye candy, if it works I'm happy. And testing/troubleshooting plugins for other users I probably look at the GUI more than most. I understand the sentiment for the updated interface, and I partially look at design when purchasing, but in the end if it looks good but doesn't function well, I'll pass. Plus the look has a nostalgia factor . Now some of the functionality simple features introduces should be in the stock installation.
  12. My thought is although unraid is a server os, its greatest strength is the ability to use it on consumer hardware or just hardware laying around. I think the incompatibility is being a little exaggerated. Realtek nics can be iffy, but all it would take is a bad driver update and Intel nics can be as well. The fact of the matter is most boards have realtek nics. Plus the nic issue is peanuts compared to other issues. A different driver for the affected chipset and all is well. As for 64 bit vs 32, I think the move would be beneficial. The older servers could still run on the version they are on, but would not get new features. Happens all the time in the tech world. And they are still doing the job they were bought for. No tech is considered lifetime, sooner or later it will need to be upgraded. I'm sure many users went and bought the iPhone 5, and it will still do what they want when the iPhone 6 comes out, but if they want that new feature.... Time to upgrade. And might I add, that iPhone Costs as much if not more than a lot of the unraid servers out there. I know I built mine for half the cost. It's not like dropping 32 bit support is going to cause your server to stop functioning.
  13. Yep, must be Simple Features. So use to it I forget its not stock. Original post edited to reflect this.
  14. I recognise that URL just form looking at it. Its amazing how inaccurate some of the ways posted are. For me this is likely the most user friendly (from that link) short of emHTTP displaying it grep --color=always -iw lm /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm lahf_lm I would like if possible emHTTP to inform all users in a non shell way so we can start getting a real feel for it It does on mine, not sure if it does on other peoples systems, but thought I'd throw it out there. On the unRAID GUI, under Utils > System profiler, if I choose "Processor Information" at the bottom I get "Characteristics: 64-bit capable" EDIT: You will only see this if you have SimpleFeatures installed. It is not part of the stock unraid GUI. Thanks Joe L for pointing this out!
  15. Can haggle on price. I don't mind having a spare CPU around, but figured I'd offer here
  16. If its the Antec 1200 V3(as your title suggests) underneath the 5.25 drive bays at the bottom of the case are 4 holes, the case should have came with 4 rubber spaces that push through those holes and 4 longish screws. Its made to mount a SSD specifically. I just built a PC for a friend using this case and installed his SSD in that location. Using some nylon washers bought at any hardware store you could replace the spacers, should be able to get a few shorter screws for it as well.
  17. Upgraded my processor so I've got a Sempron 145 up for sale. Used for almost a year, no problems at all. CAN be unlocked if you choose to do so and your Motherboard/BIOS supports it. I unlocked it to see if it could but was more interested in the low-power aspect so I didn't leave it unlocked. Because of this I cannot speak to the stability while unlocked, just that it can be. $15 Will ship anywhere in the US, buyer pays shipping.
  18. Built it, didn't need it. Just trying to get my money out of it. I've booted it up a few times and played with it but for the most part its just sitting here. Check out the craigslist add, PM me with any questions, I would be willing to ship, buying paying shipping, we can negotiate something. http://charlotte.craigslist.org/sys/3569519681.html
  19. Does this mean Limetech's official position on Realtek NIC's is that you do not recommend them? I know that Intel NIC's are cream of the crop, especially for unraid use, but most motherboards come with realtek.
  20. How much ram does your htpc have? It sounds like your buffering sucks, if physical memory is low the buffer will go to virtual memory which is very slow compared to physical.
  21. So your wanting to remove one (empty) drive from the array for now? If so, do this: Run a parity check to ensure everything is well Take a screenshot of your disk configuration (main screen, which disk is in which spot)....Running a 5Beta build this is only necessary to know which disk is parity. Stop the array Unassign the disk you want to remove Powerdown Remove the drive Power back up, a disk will show as missing, make sure this is the disk you want! Stop the array if its running Go to Utils page Click "New Configuration" This will invalidate parity and cause parity to rebuild. Your other disks will be unprotected during this. Its a good idea to run a parity check after it rebuilds. If the disk you want to remove is not empty, first move the data off of that disk and then do as above.
  22. I would start by running memtest for a night to rule out any memory errors. The error mentions scsi, as well as "ata_softreset" and "nv_hardreset", so it is getting a kernel panic when its interacting with the discs. I see your MB has 8 onboard ports, and you also have two expansion cards giving you another 8 internal and 4 e-sata ports. Where are the discs plugged into? Also seeing the icydocks. As much of a pain as it sounds, I would move some stuff around, it could be an issue with one of the backplanes going bad, a bad cable, or something funky with the ports you are using. If your currently using the onboard ports, try switching to the expansion cards, or vice versa. If the drives are plugged into the icydocks, try moving some from the partially filled icydock to a direct connection with sata(how a normal pc would be built). If that doesn't solve the panic, try moving the drives from the other icydock to the (now) empty one. You are correct in your search that it is most likely a hardware fault. I have seen on other forums where users get a MCE(machine check exception) when booting into certain flavors of linux and not when using others. Have also seen where a live disk works fine but a full install does not.
  23. Figured I'd give this a shot. I'm needing a more powerful processor but not a lot of extra cash right now. Preferrably a Tri-core or quad-core.
  24. Yes, its like your own personal nzbmatrix. Without being open to the internet for others to access, you don't have to worry about it being shutdown.
  25. If you check the cookies that are set, if the total size is above 4KB then they won't work. Another workaround would be for the dev to set the cookies to the full path instead of root. So instead of setting to "tower/" set it to "tower/headphones". That should work around the 4KB limit if one of the cookies are set by unraid, which I believe is the case.