Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

30 Good

About S80_UK

  • Rank


  • Gender
  • Location
    Huntingdon, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Maybe I am missing something - from your log you are running an Intel Core 2 Duo E7200. This suggests that your hardware should be 64 bit capable already... https://ark.intel.com/content/www/us/en/ark/products/35348/intel-core-2-duo-processor-e7200-3m-cache-2-53-ghz-1066-mhz-fsb.html
  2. If the UPS firmware is as old as v3.5 you may be out of luck, but take a look at the thread that @Frank1940 pointed you to. Note that you may need to change mode from USB to Modbus, even though it still uses a USB connection. Also take a look here... https://www.apc.com/us/en/faqs/content/?id=FA281865
  3. Thanks - I just picked up a secondhand unit last week. My unit is also the SMT1500I. I guess I got lucky with the build date. The updated software seems to read some of the voltages a bit differently (mains and battery) and includes a battery calibrate function which I did not find in the earlier firmware. My batteries were replaced only about a year ago, but I ran the calibrate anyway. It's a very nice UPS.
  4. This worked for me too - BUT - I had to update the firmware on my UPS first. I have a Smart-UPS 1500 which was reporting firmware 8.3. There was no Modbus option in the advanced configuration menu until I updated to current firmware (version 9.4 as I write this). Download from Schneider's site here... https://www.apc.com/us/en/faqs/content/?id=FA281865 Note - you need to have the PC doing the update (and ideally its monitor) powered direct from the mains, since the UPS outputs will be turned off during the update process. It takes just two or three minutes. My screen was still on the UPS so I lost that during the update, and although I could see that it had completed on the UPS screen, I then had to manually re-enable the output on the UPS to get the screen back. 🙄
  5. It's a very long time ago, but I shall try... (I have been playing with Twonly under Linux since 2007 and these day's I don't touch it since "it just works". I current run 8.3 which is not the latest.) In the package of files that you would download from Twonky's web site there is a readme called "Linux-HowTo.txt" in the Linux builds that tells you how to set up and run it. As part of this you need to modifiy some file permissions to make some of the files executable. I install it into a folder on my cache drive called ".twonkymedia". I use the old .foldername convention to stop te folder being moved by the mover routine every night. All of the files and folders that make up Twonky sit in that folder. Among them is an executable that is proved with Twonky called "twonkystarter". Near the end of the "go" script that is run when you start up Unraid I have a line like this.... /mnt/cache/.twonkymedia/twonkystarter -inifile /mnt/cache/.twonkymedia/twonkymedia-server.ini -appdata /mnt/cache/.twonkymedia/data echo "FLAC server started" In the simple case that is about it. I actually have several separate copies on my cache drive, each in their own folder, each with their own configuration and each accessible from a web browser using a different port setting instead of the default port 9000 (it's all set up in the twonkymedia-server.ini file which is editable). These days, you also need to have an account with Twonky's owners to allow the licence key to be authenticated. Hope this helps a little.
  6. @itimpi is correct. Reconstruct-writes are fast so long as no other disk activity is taking place at the same time. So it is fast for copying from external sources (as fast as your slowest drive, anyway). But as soon as you read from one array drive and then want to write to a differnt place in the array using reconstruct-writes, not only is the source drive reading the data to be copied, but it also has to perform a seek to read its share of the data stipe that is needed to calculate parity. That seek operation is what slows it down so much. In such a case, conventional writes are to be prefered, since although the destination and parity drives must both perform read and write operations, neither drive needs to seek to a different area of the disk between these operations.
  7. I am not using Docker for it, but I run Twonky Media Server quite happily, just starting it up from the "go" file after everything else.
  8. It's not really the maximum power dissipation of the processor that's the issue, but it's more related to how much power the chip saves when it is idle or only lightly loaded. Historically, Intel have always been much better at that than AMD, and the newer Intel processors seem to be exceptional in this area. At least Unraid makes motherboard swaps relatively painless. Drives are identified by serial number rather than by port, so it's often just a case of plugging in and away you go. I would recommend a few passes of Memtest (from the Unraid boot menu) before giving the new hardware full access to your drives.
  9. I agree, and MSI seem worse than the bigger brands in terms of web based support for their products. My small HTPC is an MSI box, and it works great, but I'd challenage anyone to try to find detailed information about the machine or its similar brethren on their site. They have only very light marketing material. Biostar are similarly light when it comes to the details. It's probably the main reason that I stick with Asus, Asrock and Gigabyte for motherboards.
  10. Thanks for creating this plugin. I have set up successfully and I'm currently part way through a check that I'm spreading across three nights. Looks good so far.
  11. I agree with @trurl - this does not look like the normal Unraid folders - On my 6.6.7 machine (set up as a basic NAS device) I do not have folders "media" "opt" and "svr" so it looks to us as though you are looking at something else. What to you see in those folders? What do you see in the "boot" folder. It may give a clue as to what happened.
  12. Season's Greetings to you all. And thank you for all that you do for the UNRAID community. All good wishes for 2019. Les.
  13. RAM can die of old age / temperature cycling etc. I have had it happen in my server and also in my main home PC. In each case just one stick started to go consistently bad and it wasn't due to pushing the speed or voltage limits for example. It just didn't work properly anymore. I have also had RAM that just works pretty much forever, but you never know... It's why some people choose to run with ECC RAM in their servers. I don't right now since my motherboard doesn't support it, but next time I upgrade I may go in that direction.
  14. It's up to you, to be honest. I know from experience that one can spend many hours working on a project and documenting it for others, but only a few will follow your lead. Please don't do it on my account - my time to explore in-depth is relatiely limited at the moment. At the same time, projects such as your are very cool, and a great way to share technical knowledge. Thank you again.
  15. On Windows I use a combination of methods. I use Window's built-in Backup to regularly backup selected folder structures such as My Documents. For me there's enough flexibilty in terms of choossing the content to back up and simple scheduling. I also use FreeFileSync which I run manually from time to time to manage backups of large amounts of infrequently updated material. I found FreeFileSync good enough that I have paid for it for a year to keep up to date with newer versions. Both are worth considering in my view. I am sure there will be other recommendations.