Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

34 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. Other stuff to check.... Is the 5 volt supply within spec? The USB subsystem is one of the few things that uses the 5 volt supply rail on modern motherboards. If it is on the high side (especially above 5.5 volts) then USB devices may suffer. Why are so there many writes to the USB? Do you have something perhaps writing data files or log files to the USB drive? My server sits at a few tens of writes only most days. It won't help you, but the USB drive in my main server which is powered continually has been in use for almost nine years.
  2. Nice simple update from 6.8.0-rc9. My thanks to the Limetech team.
  3. I often have both my servers live but have never seen this issue. I also wonder whether the similarity in the naming may have been helping your browser to auto-fill the address. I use IP addresses to direct the broswer rather than the server names (and have them stored in bookmarks) and that helps to avoid the problem I also have one server set to the black display theme and the other set to white, just to help make sure I know what I am doing.
  4. S80_UK

    UPS Issues

    You appear to have nothing entered in the fields "Battery level to initiate shutdown" and "Runtime left to initiate shutdown". From the details dispay it seems that these fields have therefore got some random data in them. In particular the charge left to initiate shutdown seems to be at over 5400%, and therefore even a full battery (yours is at 100%) may not be enough to prevent an instant shutdown. Try setting the first parameter to 50% and the second to maybe 5 or 10 minutes. Also - a word of advice.... It is generally not recommended to unplug in order to test to test a UPS. Instead, just switch off the power at the socket. This keeps any earth connection intact. Also, for testing, before cutting the power I stop the array and ensure all drives are at least spun up. This means that if power to teh server then fails without a graceful shutdown, you won't later have to go through a lengthy parity check cycle.
  5. Personally, I am not affected (not using VMs here), but that sounds like a good way forwards.
  6. Excellent suggestion. I would quite like to see this way of controlling the adaptive write method behaviour implemented at some point (even if not at 6.8).
  7. Some drives always seem to report the same value for Power-off retract count and for Load cycle count. On my main server, 10 out of 12 drives do this, although I never noticed until now. Of course, the power off retract count should never be greater than the number of power cycles if it was correctly reported. Your numbers are small. It is not uncommon to have load cycle count values in tens of thousands or even hundreds of thousands in some cases. I don't see anything here to be concerned about.
  8. 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
  9. 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
  10. 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.
  11. 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. 🙄
  12. 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.
  13. @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.
  14. 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.
  15. 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.