S80_UK

Yes, a slow down is normal - the actual speed will depend on the drive, but I have some older drives that go down to below 65MB/s towards the end of the disk. By convention disk drves access from the outer cylinders first. Since they are physically longer they have more sectors and since the rotation speed is fixed the data rate starts high and then reduces as the heads are moved in to the higher numbered cylinders.

OK - I would try clearing the settings, apply, and then put them back again, then apply. Beyond that, someone else may be able to help. What I described worked for me on my backup server when I upgraded earlier today.

OK - but you also have Never send selected. Would that make a difference if you set once per day?

Click on the "here" to enter the settings. Enable the notifications you need selecting notifation type and frequency but only using browser notifications. Click apply. Done. It's a way to help ensure that users don't miss important notifications from their system, and relatively benign since there's no need to go so far as setting up to send emails for example.

Can you install and run Belarc Advisor? I have no clue about running that in a VM, but it's a handy tool for such purposes on a regular installation. https://www.belarc.com/products_belarc_advisor

Not when I replied - updated later I guess. I had to look up the numbers from the image.

Probably worth adding this information - DDR4, 2133MHz, Registered ECC http://uk.crucial.com/gbr/en/ct16g4rfd4213 to save everyone trying to figure it out...

Really good post. I've been using unRAID for over seven years* now, and it's a great platform and has evolved massively over that time, as I have gone from one, to three, to four unRAID licenses (main, backup, daughter, spare). To be honest, you've done well to gain such a grasp of its capabliities in such a short time. Your feedback is valuable, not only to Lime Technology, but also as an concise overview of the capabilities and strengths of the system. I singled out the comment on the cache settings in particular, since that is something that often trips up new users who end up asking why their cache drive is full and none of the files are being moved... * Wow! I just checked - didn't know it was that long.

I am not familiar with badblocks, but wouldn't the device be /dev/sdb (or /dev/sdc or /dev/sdd etc.) according to the device name assigned? Check in the UI for the actual assignment, but note that this can potentially change from one boot up to the next.

You need one machine connected to the UPS. it also connects to the network and acts as master as far as UPS interfacing is concerned. The other(s) connect via the local network and are set up as slaves. You need to keep the network powered from the UPS as well while the servers are running - so router and / or switches at least should also be connected. Read up on APCUPSD master and slave configuration. It has also been covered a few times on this forum. This thread has some useful info.... http://lime-technology.com/forum/index.php?topic=28261.msg250988

I stand corrected! To be fair, my comment was based on my Back-UPS RS 800 and from what I have seen that unit has no way to complain except to simply not work. So it's perfectly possible that the battery-changed entry does have an effect in those UPS systems that are aware of the passsage of time. Mine seems not to be that smart, and has no UI other than a single button and four LEDs.

That sounds like progress. Weird stuff can happen. I'd still recommend a calibration run at some point. I try to do one about once a year. I avoid doing that too frequently because it does take the batteries down to 25% which is pretty hard on them, but OK once in a while.

One question... in the UPS's internal settings did you ever set up a selftest? Regardless, I belive that you can recalibrate the UPS to its current battery state like this... Rather than using a separate keyboard and monitor - you can run this from the terminal window that unRAID now provides. That wasn't an option when I wrote the linked procedure. Within the apctest program described you can also set the time that the battery was last changed. That may help in your case.

Yes - that was an unRAID limitation. But that was unRAID 4.x. Since then their have mostly only been restirctions on drive size caused by old harware.

The memory utilisation looks completely normal. Linux operating systems generally use spare RAM as cache since it's faster than disk drives. The important part is the Used section in the lighter colour - that's well under 10%, so not a problem. Also see the utilisation reported under the Dashboard tab. Lastly, a basic outline here - https://www.linuxatemyram.com/

You don't need a RAID controller - unRAID is not RAID and does not require RAID hardware. You do however need suitable host-bus-adaptors (HBA) to support the drives that you intend to use, and many of those happen to be RAID controllers but are not used as such. Typically they are either reconfigured into a JBOD mode via their BIOS settings, or they are reflashed with non-RAID firmware. There are many suitable HBAs, including the LSI 9210 ireflashed to IT mode that you already have.

As @johnnie.black says, the controller is a good suspect. But if drives are missing after a power up from off, but are less often missing after a reboot then it would be worth seeing if you can check the power supply (maybe a temporay swap from another machine?). Power supplies do age, and over time can loose their capacity to provide the higher currents needed at start up.

Updated main server from 6.5.0-rc6 without issue. Will update backup server in a few days. Many thanks for this update. Much appreciated..

I just noticed the sleaving over the cables from the HBA in your photo. That's not a huge length to be holding together, but it might not be helping in terms of crosstalk between cables. It won't be elegant, but I'd be tempted to cut that sleeving back and let the cables hang free and slightly separated. Then even if they are in close ontact, it will only be for an inch or so at a time.

There's no fixed standard for the board fixing of the bracket. It very much depends on the card manufacturer and whether there are any connection going through the bracket with other conenctors. You might get lucky with a spare card, but even if the distance between the fixings is correct, they could be inset from the edge by a different amount, or offset upwards or downwards. In either case the card would then not fit properly in your chassis.

Chances are is just the updated reporting since 6.4.1. Once acknowledged the error counts are known and are only flagged again if they go up. The errors that you're seeing now are most likely historic and nothing to worry about. See this thread and also the 6.4.1 release notes...

In my experience that's true for most forums. Not aimed at anyone here, but there is an increasing tendency for people to ask questions in forums rather than refine their Google searching technique.

One of my pet hates where Microsoft are concerned. Every major Windows 10 update breaks a bunch of carefully crafted settings. Forgetting the power management options for some hardware in Device Manager is another area to watch out for.

According to Asus the motherboard rates 2933 and 3200 for RAM are regarded as an overclock - the official nominal rating is 2600MHz - https://www.asus.com/uk/Motherboards/PRIME-X370-PRO/specifications/ For the CPU, AMD also rate the memory interface at 2667MHz - https://www.amd.com/en/products/cpu/amd-ryzen-5-1600 Normally there is relatively little to gain from faster RAM clocks since the number of cycles required to access data is generally increased at the higher clock speeds. You should treat Memtest as a guide. It tells you that the system runs or fails Memtest at a particular setting. But even if everything passes, there can still be potential issues with other software, especilly if overclocking.

Sorry for the delay. So, this is what I do... On my cache drive I create a folder called .AssetUPnP - the . is the old way of making the folder non-moveable. In that folder I place the file that I download for the AssetUPnP Linux 64-bit version. The URL that you have is correct for the trial version. I have a paid license for AssetUPnP so I use the file that I download when I look up my order from the program creators. I prefer to do the download manually, then I always know which version is beng run. I don't want the download to change just because they've updated the program in case it breaks something. I do the download under Windows, but it desn't matter. It's just an archive file that gets copied into that .AssetUPnP folder. Also in the .AssetUPnP folder I have a simple script derived from the one that the AssetUPnP guys have placed in their support forums for the Linux version. It is named as AssetUPnP.sh Mine looks like this... # Asset UPnP for Linux # should already be here, but just in case cd /mnt/cache/.AssetUPnP # Unpack the downloaded archive - change file name here to match downloaded archive file for AssetUPnP tar -zxvf AssetUPnP-Linux-x64-premium.tar.gz # Create a folder for the database cd /mnt/cache mkdir .dBpoweramp chown nobody:users .dBpoweramp # AssetUPnP doesn't know about my cache drive, it uses a folder called /root/.dBpoweramp which would normally be in RAM so I need to creat a soft-link to redirect from there to the cache # I set this up twice, once in / and once in /root # At different times I have needed different locations. It's safe to leave both in the code. # remove any old link (if just restarting Asset; normally will generate an error) cd / rm .dBpoweramp # remove any folder contents (if present; normally will just generate an error) rm -r .dBpoweramp # create a soft-link to the database on the cache drive ln -s /mnt/cache/.dBpoweramp .dBpoweramp # change ownership of the soft-link chown nobody:users .dBpoweramp # remove any old link (if just restarting Asset; normally will generate an error) cd /root rm .dBpoweramp # remove any folder contents (if present; normally will just generate an error) rm -r .dBpoweramp # create a soft-link to the database on the cache drive ln -s /mnt/cache/.dBpoweramp .dBpoweramp chown nobody:users .dBpoweramp # The path to the binaries changed after V5, so... # this cd for 5.x # cd /mnt/cache/.AssetUPnP/bin # this cd for 6.x cd /mnt/cache/.AssetUPnP/Asset-R6-Linux-x64-registered/bin # start the program ./AssetUPnP The key detail is that Asset by default would place the database of scanned metadata from your music in the RAM filing system. So that it survives reboots and to save RAM I choose build it on the cache drive. The above sets up a link from the RAM filing system to that folder on the cache drive. After that Asset is happy to use it. In the go file I place a simple call to the above start up script like this... # other startup stuff here. Array must be started before starting AssetUPnP... # # # # AssetUPnP server cd /mnt/cache/.AssetUPnP ./AssetUPnP.sh & cd /boot/config echo "AssetUPnP server started" # # # # Any more start up stuff... Once AssetUPnP is started, you need to go to its local web page (unRAID-server-IP-address:45537). You can then go to the configuration page and set up the path(s) to your media files and any other options. In my case that it simply a share on the server /mnt/user/FLAC That's it. You'll probably need to tweak this to suit your own needs. This does not have the benefits of running in a Docker session, but I have struggled to find good info on how to make that work. In fact the documentation on the docker site is pretty impenetrable for people that don't already understand enough about how it works, IMHO.