Himself

Thanks for the information. I'll have to remove them and re-install. Such is lfe 😎

I'll start with an apology as the problem is of my own making. The USB stick with the OS on failed so I reconstituted the server on the lastest version of Unraid, Recovered the array without error and the Docker containers have all restarted, but cannot find their template files. Appdata has been set to cache preferred and mover is running. I've searched the array for any other occurance of appdata and can't find any. So if there was anything, it would appear to have been moved. FCP shows that the templates are mising - "Template URL for docker application PlexMediaServer is missing." Usingthe FCP "Apply Fix" also refers me to the missing template, however there is one in GITHub, I could download an put in the required location. When attempting to update Plex to the new version, the container update routine can't run without the template file. Is there a way to recover from the corner I have painted myself into or is re-installation the solution? Thanks for the help.

Thankfully, I had a list of how the drives were arranges and so was able to reconstruct the array. All of the data is there and parity check has just finished running. If you don't have a copy of how your drives are arranged in you array, might be worth taking a creen grab just in case. Don't store it o nthe server though 😁 All of the user accounts were gone. Luckily for me this is a home media server so it is easy to recreate a small number of users. Otherwise, installing 6.8 was simple ... Now I just need to add in all of the tweaks and changes that I had. Thanks for the help.

cool thank you. I've just got the server to boot. I'll see what I can recover

Yes - It should be in my share - I'd have to dig about to find the actual disk However, at the moment I have a dumb server - I'm just creating a new Unraid USB boot stick

First let me establish that I'm the idiot. While moving powered down server today I caught the USB drive and bent it. I've tried several different methods, but USB stick is dead. I can create a new boot USB, but I'd appricate any advice on what to expect when starting a server with Shares, VMs and Containers with a fresh USB stick. And the backup I hear you ask ... It is on the server - Yes I am "that" guy -- Doh! Thank you in advance for the help.

Thank you Squid!!

I have managed to lock myself out of the webUI for binhex-sabnzbd. When I select the WEbUI option I get the message "Access Denied" I've tried deleting the container and re-installing, +/- a reboot just in case, however my idiocy appears to have reached new heights. Is there anyway around this? I can delete the container again, but there seems to be something else I need to do to clear the block Thanks for the help

Two days in a 6TB of data transferred. All is well. Jumbo frames were the problem with the "new" server. Sleep seems to have been the problem with one of the HP Microservers Thanks to Squid for walking me through a few processes and some fault finding.

Still running tests, but on the "new" i7 based server, it looks to have been jumbo frames that were the problem. With an MTU of 1500 we seem to be running without error.

The ethernet ports are the built-in ones on the motherboard. Time to change the cable and the switch port - although I would have said I'd done that, but with all the rebuilding, I may have reused something. Thanks for your help Squid. I do appreciate it Cheers

OK -- Finally workout a way of letting it fail and then getting the diagnostics. It seems to be losing network connectivity as the GUI is running (localhost) but nothing is accessible on across the network. Hopefully, these diagnostics point the way. Thanks for the help. Much appreciated deathstar-diagnostics-20180121-1809.zip

Diagnostics run and attached ..forgive the unimaginative server name :-) If anyone can help a Unix idiot that last looked at the Unix command line 15 years ago, with some instructions on how to downgrade I'd be obliged. Total disclaimer: if you are kind enough to help me, the risk of any action is on me :-) deathstar-diagnostics-20180121-1418.zip

So ... Sleep has been removed. It isn't the Gui boot either. The server ran for a couple of hours before developing this "feature" Fix Common problems has just thrown up a "Call Traces" problem Time to go back to 6.3 I think ... Wonder if I can remember Unix commands .... but I'll run diagnostics first

Nope ... thought I had it fixed but I don't So, Original problem that moved from one HP Microserver to another, fixed by removing S3 Sleep The new large server I build (i7 P6X58D motherboard) ran for 2 hours when booted with the GUI. Boot the same server headless and it goes to sleep. Same basic issue, Shell is still active, but no disk or IP connectivity. Test that is currently running is to reboot the new server with the GUI running and try to pump the data from the HP to the New Server and see if it will stay running.

Thank you Squid - I thought I'd deleted this post as I believe I've found the problem - S3 Sleep The strange thing was one server was fine and the other acted up. Swap the boot USB and the disks and the problem moves too. Removing S3 Sleep appears to have removed the problem. Good news is that the server upgrade I've been planning has finally been done. There is always an upside

I have a random problem I'm trying to solve. I have two HP Microservers (N54L) both running Unraid 6.3 - been running perfectly for over a year. I upgraded the 1st to 6.4 and everything is fine. Simple process. Reboot. Perfection. Since upgrading the 2nd it runs for a short while and then Unraid stops. The server is still powered and if I press the power button the server will start without issue, and then after a short period shut down again. Had to be a hardware fault. So I've swapped the disks into the other Microserver (the one that upgraded and ran without error) and the problem has followed the disks and the memory stick they boot from. I've changed the power lead and the ethernet cable. Tried a different port on the switch, just in case. The server never looses power, unraid just stop running. Even the green light on the power switch stays green. Moving to another chassis seems a fruitless move. Is there a way to going back to 6.3 as this is what I changed? (First rule of bug fixing - What changed?) Preserving the data on the array is the primary concern ~ naturally :-) ~ or just getting the system to run long enough to copy it off. Most bizarre... any suggestions?

Excellent. Thanks for the information. Guess what I'm doing this weekend :-)

One of my HP N54L Microservers died this morning. It will power up and run happily for a few minute and then powers off. It isn't heat or dust, most likely the power supply is just that old and running 5x2TB Seagate drivers has finally caused it to shed off its mortal coil after many years of service. The "good" news is that for a while now I've been plotting the replacement of my desktop with my laptop. i7 with 16GB ram and a tall tower case makes a good replacement, and I can condense two N54L into one platform So my question is - If I move the drives from the failed server into the desktop and use the same memory stick, will Unraid boot on the "new" hardware, please?

Itimpi's reply was right on the money. I built a 2nd unRAID server from spare parts and cannibalised a portable drive for the 120GB Corsair SSD. Performance is now way more than acceptable, it is impressive. The array is still building, while I installed Win7, connected it to the original unRAID shares and now I'm patching the do-dar out of the VM. Most impressed and thanks for the pointer.

Cool - that could be the reason why. Being new to unRAID I took as many of the defaults as I could, one of which was the leave the disk Primary vDisk Location in Auto ( /mnt/user/domains/Windows 7/vdisk1.img) I'll attach a portable SSD drive to the USB (only USB2, but good for a test) and try again. Thanks

A whole mix of factors ... have delivered me unRAID 6.3.3 running on my trusty (or is that rusty) HP N54L, complete with TheBay BIOS 5x2TB drives and 8GB of ram. Previously I've been running FreeNAS and even more recently Win2008R2, but in an effort to find that perfect mix of raided NAS (media) server and something I can run a Win based IMAP spam scanner on, unRAID seems to be the perfect answer. I've been using the time while the data pumps from the current media server on to unRAID, to create a WIN7 VM. To say that performance is awful would be an understatement. 4 hours (I kid you not 4 hours) for the install from ISO to complete. VNC runs in bursts some 3-10 seconds behind the keyboard inputs. Important to say here in case anyone thinks I'm moaning about a product I installed 36 hours ago .. I'm not .. I'm just a little puzzled and looking for some pointers, please. The N54L is never going to offer epic performance - It is a great unit, but it is what it is. That said, in its previous configuration running Win2008R2 it wasn't too bad and would serve disk, run a mail scanner and respond the RDP sessions with just the odd pause while it sorted itself out. It would even run VirtualBox, although why I would want to run a Win7 VM on a 2008 server, still puzzles me. Having trashed the WIn2008 server to provide the base for unRAID, any suggestions as to why VM performance would be so slow? Allocating 4GB and both CPUs made little difference. Pausing the data pump gave a marginal improvement. It must be me, failing to find the right thread and running naff settings :-) With the data pumping, I'm showing CPU0@ 22% and CPU1 @ 26%. Memory usage is 13% - would indicate enough head room to run a VM. The other item that has me puzzled (my skills finding stuff in the forum also seem to suck) relate to the "Go Script" and: echo 50 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold & logger Go Script - ondemand up_threshold set to 50 echo 50 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor & logger Go Script - ondemand sampling_down_factor set to 50 A number of the comments reference unRAID5 when mentioning this mod, but I unable to track down the original problem this solved. Appreciate your help. Now I need to sort out the MTU sizes... Cheers Himself